<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: A Cry For Help</title>
	<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/</link>
	<description>America's favorite blog</description>
	<pubDate>Fri, 21 Nov 2008 18:28:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Linkmeister</title>
		<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1664</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1664</guid>
					<description>I too suspect that it's simple; I also suspect it's addressed on the MT forums somewhere.  I'd go to the MT site and click the forum link, then do a search for sidetitle styles or something of that sort.  That's if nobody volunteers help here first.</description>
		<content:encoded><![CDATA[<p>I too suspect that it&#8217;s simple; I also suspect it&#8217;s addressed on the MT forums somewhere.  I&#8217;d go to the MT site and click the forum link, then do a search for sidetitle styles or something of that sort.  That&#8217;s if nobody volunteers help here first.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Steve</title>
		<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1665</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1665</guid>
					<description>Did they report which browser (and version) it looked messed up in? For instance, Internet Explorer 5.0/5.5/6.0? Mac Safari 1.0?

I looks good on recent versions of Mozilla on Linux and Windows.</description>
		<content:encoded><![CDATA[<p>Did they report which browser (and version) it looked messed up in? For instance, Internet Explorer 5.0/5.5/6.0? Mac Safari 1.0?</p>
<p>I looks good on recent versions of Mozilla on Linux and Windows.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Superskepticalman</title>
		<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1666</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1666</guid>
					<description>It's zombieQusay's fault. It always was.

It's just like his diabolical mind to work that way. Plus he didn't give the memo questioning the alleged non-zombie possibilities to Condi when he was supposed to.

Does this mean I can be your NSA in your regime..., oops, "administration"?</description>
		<content:encoded><![CDATA[<p>It&#8217;s zombieQusay&#8217;s fault. It always was.</p>
<p>It&#8217;s just like his diabolical mind to work that way. Plus he didn&#8217;t give the memo questioning the alleged non-zombie possibilities to Condi when he was supposed to.</p>
<p>Does this mean I can be your NSA in your regime&#8230;, oops, &#8220;administration&#8221;?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rook</title>
		<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1667</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1667</guid>
					<description>Is this a default design of Movable Type, or did you create this look yourself (sexy daaaarl'n, very very sexy)? I've been working on a new look for my site and have run into the same problem as well. I see that you are using a CSS file (I peeked at your source HTML code), so any ajustments would probable have to be done there. Since older versions of most browser were not fully supportive of CSS, that's more then likely the problem anyway. I also noticed you have an older version of Movable Type, any chance you might try updating to 2.64? That might also be the problem.
I want to be the opposition party to your regim......errrrr, administration. But please, no messy tortures, I have a weak constitution, especially towards blood and pain.</description>
		<content:encoded><![CDATA[<p>Is this a default design of Movable Type, or did you create this look yourself (sexy daaaarl&#8217;n, very very sexy)? I&#8217;ve been working on a new look for my site and have run into the same problem as well. I see that you are using a CSS file (I peeked at your source HTML code), so any ajustments would probable have to be done there. Since older versions of most browser were not fully supportive of CSS, that&#8217;s more then likely the problem anyway. I also noticed you have an older version of Movable Type, any chance you might try updating to 2.64? That might also be the problem.<br />
I want to be the opposition party to your regim&#8230;&#8230;errrrr, administration. But please, no messy tortures, I have a weak constitution, especially towards blood and pain.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: adam</title>
		<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1668</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1668</guid>
					<description>Answers- 

Rook - the CSS is indeed a custom design, put together by a friend of the site several months back.

Steve - I've actually heard the complaint, in various forms, from people with all types of systems and configurations.  Most recently (and alarmingly) from someone using Windows XP and IE 6.  So obviously it needs addressing.

Linkmeister - Haven't found the cure at the forums yet, though I have posted my particular complaint.

In general, it seems that the right column is too dominant - ideally, the page should clip or even wholly eliminate the right column depending on window width.  Instead, the nefarious column is drawn OVER the blog text when the width is an issue.  The bones of this problem can be seen on just about any browser when you narrow the window enogh.

http://www.boingboing.net/   is an example of a site that behaves correctly - the important column scales to fir the window, but when the window narrows to a certain width, the right column just gives up the ghost.  Same with Eschaton.  That's what I'd like to see.</description>
		<content:encoded><![CDATA[<p>Answers- </p>
<p>Rook - the CSS is indeed a custom design, put together by a friend of the site several months back.</p>
<p>Steve - I&#8217;ve actually heard the complaint, in various forms, from people with all types of systems and configurations.  Most recently (and alarmingly) from someone using Windows XP and IE 6.  So obviously it needs addressing.</p>
<p>Linkmeister - Haven&#8217;t found the cure at the forums yet, though I have posted my particular complaint.</p>
<p>In general, it seems that the right column is too dominant - ideally, the page should clip or even wholly eliminate the right column depending on window width.  Instead, the nefarious column is drawn OVER the blog text when the width is an issue.  The bones of this problem can be seen on just about any browser when you narrow the window enogh.</p>
<p><a href="http://www.boingboing.net/" rel="nofollow">http://www.boingboing.net/</a>   is an example of a site that behaves correctly - the important column scales to fir the window, but when the window narrows to a certain width, the right column just gives up the ghost.  Same with Eschaton.  That&#8217;s what I&#8217;d like to see.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ralph</title>
		<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1669</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1669</guid>
					<description>The problem with the right column overwriting the important stuff happens when the z-index of the box containing the right column is higher than the z-index of the box containing the content. Looking at your CSS file, the z-index isn't set for either of these, so browsers are automatically setting the z-index based on the order in which the boxes appear in your code. (The z-index, if you remember your Cartesian mathematics, refers to the stacking order above and below the plain of the x- and y-axes. Damned geek speak....)

You can fix this problem by explicitly setting the z-index for the two boxes in question. In your CSS file, these appear to be #content and #side for the left and right sides respectively. I added the following declaration to the definition of #content:

z-index: 20;

and the next declaration to the definition of #side:

z-index:10;

to a local copy of your front page that I downloaded to my computer. Then I resized the browser window to duplicate the conditions your users were complaining about. The right side box now falls behind your main content rather than obscuring it.

I'll take Michael Powell's job, please.</description>
		<content:encoded><![CDATA[<p>The problem with the right column overwriting the important stuff happens when the z-index of the box containing the right column is higher than the z-index of the box containing the content. Looking at your CSS file, the z-index isn&#8217;t set for either of these, so browsers are automatically setting the z-index based on the order in which the boxes appear in your code. (The z-index, if you remember your Cartesian mathematics, refers to the stacking order above and below the plain of the x- and y-axes. Damned geek speak&#8230;.)</p>
<p>You can fix this problem by explicitly setting the z-index for the two boxes in question. In your CSS file, these appear to be #content and #side for the left and right sides respectively. I added the following declaration to the definition of #content:</p>
<p>z-index: 20;</p>
<p>and the next declaration to the definition of #side:</p>
<p>z-index:10;</p>
<p>to a local copy of your front page that I downloaded to my computer. Then I resized the browser window to duplicate the conditions your users were complaining about. The right side box now falls behind your main content rather than obscuring it.</p>
<p>I&#8217;ll take Michael Powell&#8217;s job, please.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ralph</title>
		<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1670</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1670</guid>
					<description>Oh, I suppose I should make clear that the above is just a quick-and-dirty fix to the immediate problem. It's possible to create the kind of layout that BoingBoing and Eschaton have with CSS (although they both use tables rather than CSS), but it would require some serious CSS hackery and experimentation and the addition of another CSS file thanks to errors in the implementation of CSS in browsers like Netscape 4.x and IE 5 and 5.5 for Windows. It's a well-trodden path, but more than I would want to explain in a comments section.</description>
		<content:encoded><![CDATA[<p>Oh, I suppose I should make clear that the above is just a quick-and-dirty fix to the immediate problem. It&#8217;s possible to create the kind of layout that BoingBoing and Eschaton have with CSS (although they both use tables rather than CSS), but it would require some serious CSS hackery and experimentation and the addition of another CSS file thanks to errors in the implementation of CSS in browsers like Netscape 4.x and IE 5 and 5.5 for Windows. It&#8217;s a well-trodden path, but more than I would want to explain in a comments section.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: adam</title>
		<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1671</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1671</guid>
					<description>Thanks so much, Ralph.  I'd rather that ornery right column would just stop moving after a while, but at least it no longer covers up the left column, and that's a HUGE improvement.  

Thanks!  Your FCC chairmanship is assured.</description>
		<content:encoded><![CDATA[<p>Thanks so much, Ralph.  I&#8217;d rather that ornery right column would just stop moving after a while, but at least it no longer covers up the left column, and that&#8217;s a HUGE improvement.  </p>
<p>Thanks!  Your FCC chairmanship is assured.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Don</title>
		<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1672</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1672</guid>
					<description>Actually, the easiest answer is to follow the lead of the Adminustrashun:

Tell anyone who claims it's happening that it really isn't.

After several weeks you can announce that, when it &lt;i&gt;did&lt;/i&gt; happen it was because you were only setting up the site according to the advice of others who had all signed off on it.

Two weeks later, of course, someone would admit that now they remember that they had read about it in a memo a few months earlier, but - goldarn it all - they just forgot. So they never stopped you from doing it wrong.</description>
		<content:encoded><![CDATA[<p>Actually, the easiest answer is to follow the lead of the Adminustrashun:</p>
<p>Tell anyone who claims it&#8217;s happening that it really isn&#8217;t.</p>
<p>After several weeks you can announce that, when it <i>did</i> happen it was because you were only setting up the site according to the advice of others who had all signed off on it.</p>
<p>Two weeks later, of course, someone would admit that now they remember that they had read about it in a memo a few months earlier, but - goldarn it all - they just forgot. So they never stopped you from doing it wrong.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: John Isbell</title>
		<link>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1673</link>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://fanaticalapathy.com/2003/07/27/a-cry-for-help/#comment-1673</guid>
					<description>Don makes an excellent suggestion.
I sometimes get the green overlaid on stuff, like the dialog photospread. Whenever I come here, the layout starts normal, then after about 30 seconds the left text column turns about an inch wide, and I fix it by drifting over a comments link, which resizes the display (I bet all these words are wrong, but you get my meaning). Then, I scroll back up and start reading. But it's worth it!</description>
		<content:encoded><![CDATA[<p>Don makes an excellent suggestion.<br />
I sometimes get the green overlaid on stuff, like the dialog photospread. Whenever I come here, the layout starts normal, then after about 30 seconds the left text column turns about an inch wide, and I fix it by drifting over a comments link, which resizes the display (I bet all these words are wrong, but you get my meaning). Then, I scroll back up and start reading. But it&#8217;s worth it!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
