<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Curious Case of the Giant Scrollbar</title>
	<atom:link href="http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/</link>
	<description>Everybody Likes Ninjas</description>
	<lastBuildDate>Wed, 01 Feb 2012 08:03:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Andrew Mason</title>
		<link>http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/comment-page-1/#comment-198655</link>
		<dc:creator>Andrew Mason</dc:creator>
		<pubDate>Wed, 06 May 2009 14:29:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/?p=164#comment-198655</guid>
		<description>I ran across the same issue when working on a localisation project. A simple fix is to use:

overflow: hidden;

...on the parent element to clip the child off.

Bonus tip: The same trick of setting overflow: hidden; on the parent element prevents the focus dashed outline from stretching across the page when using image replacement technique with &lt;a&gt; links.</description>
		<content:encoded><![CDATA[<p>I ran across the same issue when working on a localisation project. A simple fix is to use:</p>
<p>overflow: hidden;</p>
<p>&#8230;on the parent element to clip the child off.</p>
<p>Bonus tip: The same trick of setting overflow: hidden; on the parent element prevents the focus dashed outline from stretching across the page when using image replacement technique with <a> links.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: confiq</title>
		<link>http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/comment-page-1/#comment-188917</link>
		<dc:creator>confiq</dc:creator>
		<pubDate>Fri, 27 Feb 2009 13:35:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/?p=164#comment-188917</guid>
		<description>--edit--
Hi rdoherty!
As one that writes lot of RTL sites i found this bug frustrating. 
Unfortunately i put display: none if i don’t have access to external JS (ex. facebook connect) but most of cases i resolve as you did…
Instead of left: 999em i write right: 999em;…

regards</description>
		<content:encoded><![CDATA[<p>&#8211;edit&#8211;<br />
Hi rdoherty!<br />
As one that writes lot of RTL sites i found this bug frustrating.<br />
Unfortunately i put display: none if i don’t have access to external JS (ex. facebook connect) but most of cases i resolve as you did…<br />
Instead of left: 999em i write right: 999em;…</p>
<p>regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rdoherty</title>
		<link>http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/comment-page-1/#comment-184582</link>
		<dc:creator>rdoherty</dc:creator>
		<pubDate>Fri, 06 Feb 2009 00:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/?p=164#comment-184582</guid>
		<description>Good questions:

@Daniel
display:none; hides the content from screen readers, which is not a good experience because most screen readers do not detect the DOM changing, which it does when the list expands. So blind or visually impaired users would never &#039;see&#039; the category list.

@Simon:
visibility:hidden; leaves elements in the document flow, so it could affect other element&#039;s display even when hidden.

@Dan &amp; Noel
top: -999em would get it offscreen, but there is a slight possibility that the element you are moving could have a width wide enough to cause a scrollbar. Especially if you are using a standard class of &#039;.hidden&#039; for multiple elements.</description>
		<content:encoded><![CDATA[<p>Good questions:</p>
<p>@Daniel<br />
display:none; hides the content from screen readers, which is not a good experience because most screen readers do not detect the DOM changing, which it does when the list expands. So blind or visually impaired users would never &#8216;see&#8217; the category list.</p>
<p>@Simon:<br />
visibility:hidden; leaves elements in the document flow, so it could affect other element&#8217;s display even when hidden.</p>
<p>@Dan &amp; Noel<br />
top: -999em would get it offscreen, but there is a slight possibility that the element you are moving could have a width wide enough to cause a scrollbar. Especially if you are using a standard class of &#8216;.hidden&#8217; for multiple elements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Rashbrook</title>
		<link>http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/comment-page-1/#comment-184321</link>
		<dc:creator>Neil Rashbrook</dc:creator>
		<pubDate>Wed, 04 Feb 2009 13:22:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/?p=164#comment-184321</guid>
		<description>This only raises more questions... why move the element at all? If as I&#039;m assuming it&#039;s for perf reasons, why not just move the element off the top only?</description>
		<content:encoded><![CDATA[<p>This only raises more questions&#8230; why move the element at all? If as I&#8217;m assuming it&#8217;s for perf reasons, why not just move the element off the top only?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noel Grandin</title>
		<link>http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/comment-page-1/#comment-184310</link>
		<dc:creator>Noel Grandin</dc:creator>
		<pubDate>Wed, 04 Feb 2009 11:10:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/?p=164#comment-184310</guid>
		<description>Wouldn&#039;t a position of 
 { left: 0em; top:-999em; }
move the element off-screen no-matter the language orientation?</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t a position of<br />
 { left: 0em; top:-999em; }<br />
move the element off-screen no-matter the language orientation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/comment-page-1/#comment-184275</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 04 Feb 2009 03:36:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/?p=164#comment-184275</guid>
		<description>Or since you&#039;re already moving it off the top 999px, just have it left: 0px;

Unless there exists a bottom to top language, then we have a problem. ;P

I personally hide stuff with display: none; instead of moving it offscreen.  Might be some reason whoever made that opted not to do it that way...</description>
		<content:encoded><![CDATA[<p>Or since you&#8217;re already moving it off the top 999px, just have it left: 0px;</p>
<p>Unless there exists a bottom to top language, then we have a problem. ;P</p>
<p>I personally hide stuff with display: none; instead of moving it offscreen.  Might be some reason whoever made that opted not to do it that way&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin</title>
		<link>http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/comment-page-1/#comment-184240</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Tue, 03 Feb 2009 23:38:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/?p=164#comment-184240</guid>
		<description>Ah, interesting issue. Will have to bear that in mind should I do any RTL sites.</description>
		<content:encoded><![CDATA[<p>Ah, interesting issue. Will have to bear that in mind should I do any RTL sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/comment-page-1/#comment-184234</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Tue, 03 Feb 2009 22:50:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/?p=164#comment-184234</guid>
		<description>Out of curiosity, why use off-screen positioning to hide the element? Wouldn&#039;t it be simpler to use visibility:hidden or display:none instead?</description>
		<content:encoded><![CDATA[<p>Out of curiosity, why use off-screen positioning to hide the element? Wouldn&#8217;t it be simpler to use visibility:hidden or display:none instead?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Einspanjer</title>
		<link>http://blog.mozilla.com/webdev/2009/02/03/the-curious-case-of-the-giant-scrollbar/comment-page-1/#comment-184227</link>
		<dc:creator>Daniel Einspanjer</dc:creator>
		<pubDate>Tue, 03 Feb 2009 22:00:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/webdev/?p=164#comment-184227</guid>
		<description>Why do you need to use an absolute offscreen position for that collapsed list of categories?  It seems like a display:none would be easier?</description>
		<content:encoded><![CDATA[<p>Why do you need to use an absolute offscreen position for that collapsed list of categories?  It seems like a display:none would be easier?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

