<?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: Firefox test page</title>
	<atom:link href="http://www.zeldman.com/2009/07/09/firefox-test-page/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zeldman.com/2009/07/09/firefox-test-page/</link>
	<description>Web design news and insights since 1995</description>
	<lastBuildDate>Thu, 11 Mar 2010 22:39:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Lascurettes</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-47530</link>
		<dc:creator>John Lascurettes</dc:creator>
		<pubDate>Fri, 21 Aug 2009 17:51:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-47530</guid>
		<description>So, in the end, if you read through all the comments on the original bug (the one that the above bug links to), they&#039;ve fixed it, but only in Gecko trunk 1.92 and &lt;em&gt;that&lt;/em&gt; won&#039;t land until Firefox 3.6.x. So current FF 3.0 and 3.5 users will never see a fix for this.</description>
		<content:encoded><![CDATA[<p>So, in the end, if you read through all the comments on the original bug (the one that the above bug links to), they&#8217;ve fixed it, but only in Gecko trunk 1.92 and <em>that</em> won&#8217;t land until Firefox 3.6.x. So current FF 3.0 and 3.5 users will never see a fix for this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Lascurettes</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-47529</link>
		<dc:creator>John Lascurettes</dc:creator>
		<pubDate>Fri, 21 Aug 2009 17:30:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-47529</guid>
		<description>Found it: https://bugzilla.mozilla.org/show_bug.cgi?id=503337</description>
		<content:encoded><![CDATA[<p>Found it: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=503337" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=503337</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Lascurettes</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-47528</link>
		<dc:creator>John Lascurettes</dc:creator>
		<pubDate>Fri, 21 Aug 2009 17:24:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-47528</guid>
		<description>Has this been filed over at https://bugzilla.mozilla.org/ ? I couldn&#039;t find one.</description>
		<content:encoded><![CDATA[<p>Has this been filed over at <a href="https://bugzilla.mozilla.org/" rel="nofollow">https://bugzilla.mozilla.org/</a> ? I couldn&#8217;t find one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bug 1650 &#8211; Display problem for long entry in Drifting</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-47525</link>
		<dc:creator>Bug 1650 &#8211; Display problem for long entry in Drifting</dc:creator>
		<pubDate>Fri, 21 Aug 2009 15:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-47525</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Google search for &quot;firefox windows long page cutoff&quot; turns up http://www.zeldman.com/2009/07/09/firefox-test-page/ which provides evidence that this is a bug in Firefox for Windows. There may be information [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] Google search for &quot;firefox windows long page cutoff&quot; turns up <a href="http://www.zeldman.com/2009/07/09/firefox-test-page/" rel="nofollow">http://www.zeldman.com/2009/07/09/firefox-test-page/</a> which provides evidence that this is a bug in Firefox for Windows. There may be information [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lyndon</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-46828</link>
		<dc:creator>Lyndon</dc:creator>
		<pubDate>Fri, 07 Aug 2009 10:10:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-46828</guid>
		<description>excited to used and convert into html5... i have to used this starting now..</description>
		<content:encoded><![CDATA[<p>excited to used and convert into html5&#8230; i have to used this starting now..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michel</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-45786</link>
		<dc:creator>Michel</dc:creator>
		<pubDate>Wed, 22 Jul 2009 13:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-45786</guid>
		<description>@Norman:

WinXP? WinVista? Win7? :-)

May we assume that 3.5 had the bug but it was already fixed in 3.5.1?</description>
		<content:encoded><![CDATA[<p>@Norman:</p>
<p>WinXP? WinVista? Win7? :-)</p>
<p>May we assume that 3.5 had the bug but it was already fixed in 3.5.1?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Norman Wingrove</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-45443</link>
		<dc:creator>Norman Wingrove</dc:creator>
		<pubDate>Sun, 19 Jul 2009 14:43:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-45443</guid>
		<description>Bottom of page did not show in Firefox 3.5. All OK in 3.5.1</description>
		<content:encoded><![CDATA[<p>Bottom of page did not show in Firefox 3.5. All OK in 3.5.1</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 일모리와 웹표준</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-44788</link>
		<dc:creator>일모리와 웹표준</dc:creator>
		<pubDate>Tue, 14 Jul 2009 17:37:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-44788</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Firefox test page &#187;&#160;Jeffrey Zeldman 5 days ago [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] Firefox test page &raquo;&nbsp;Jeffrey Zeldman 5 days ago [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Poulos</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-44685</link>
		<dc:creator>Nick Poulos</dc:creator>
		<pubDate>Mon, 13 Jul 2009 17:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-44685</guid>
		<description>For me, the test page displays all comments, including the comment form.

I&#039;m using Firefox 3.5 on Windows 7 RC x64.</description>
		<content:encoded><![CDATA[<p>For me, the test page displays all comments, including the comment form.</p>
<p>I&#8217;m using Firefox 3.5 on Windows 7 RC x64.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Travis</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-44621</link>
		<dc:creator>Travis</dc:creator>
		<pubDate>Sun, 12 Jul 2009 15:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-44621</guid>
		<description>Cut off during &lt;a&gt;44050&lt;/a&gt;.

Firefox 3.5 on Vista 64-bit.</description>
		<content:encoded><![CDATA[<p>Cut off during <a>44050</a>.</p>
<p>Firefox 3.5 on Vista 64-bit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William King</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-44604</link>
		<dc:creator>William King</dc:creator>
		<pubDate>Sun, 12 Jul 2009 05:48:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-44604</guid>
		<description>This isn&#039;t specifically about the bug in question, but I have a problem with Firefox 3.5 that I have discovered. I am hoping someone knows what the deal is. For whatever reason, regardless of what fonts families, font sizes, etc. I choose in the CSS, Firefox 3.5 refuses to display it. It has messed up the typography of so many web sites. Instead it displays Times New Roman consistently. Obviously I could go into the options and change this to my desired font, but that will not help the user when viewing the page. Any ideas?</description>
		<content:encoded><![CDATA[<p>This isn&#8217;t specifically about the bug in question, but I have a problem with Firefox 3.5 that I have discovered. I am hoping someone knows what the deal is. For whatever reason, regardless of what fonts families, font sizes, etc. I choose in the CSS, Firefox 3.5 refuses to display it. It has messed up the typography of so many web sites. Instead it displays Times New Roman consistently. Obviously I could go into the options and change this to my desired font, but that will not help the user when viewing the page. Any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jymmyr</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-44602</link>
		<dc:creator>jymmyr</dc:creator>
		<pubDate>Sat, 11 Jul 2009 22:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-44602</guid>
		<description>The test page breaks near comment 44050 with Fx 3.5 (Shiretoko) running on Ubuntu 9.04 x86_64. When I scroll down from the top of the page I see something like &lt;a href=&quot;http://paradogs.net/i/foxy.jpg&quot; rel=&quot;nofollow&quot;&gt;this&lt;/a&gt;. However, scrolling up from below the offending area shows no visible anomalies. In my case the footer looks fine, but even though links there and in the comments can be clicked, the text below the offending area cannot be highlighted with the mouse. I&#039;m very scared.</description>
		<content:encoded><![CDATA[<p>The test page breaks near comment 44050 with Fx 3.5 (Shiretoko) running on Ubuntu 9.04 x86_64. When I scroll down from the top of the page I see something like <a href="http://paradogs.net/i/foxy.jpg" rel="nofollow">this</a>. However, scrolling up from below the offending area shows no visible anomalies. In my case the footer looks fine, but even though links there and in the comments can be clicked, the text below the offending area cannot be highlighted with the mouse. I&#8217;m very scared.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: effika</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-44600</link>
		<dc:creator>effika</dc:creator>
		<pubDate>Sat, 11 Jul 2009 22:13:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-44600</guid>
		<description>It&#039;s broken in SeaMonkey 2.0a3 (build ID: 20090223135443) and 1.1.17 on Windows XP sp3, too.  Not that anybody USES SeaMonkey (there&#039;s like 20 of us), but maybe this will help point out that it&#039;s endemic to the engine and not just Firefox.</description>
		<content:encoded><![CDATA[<p>It&#8217;s broken in SeaMonkey 2.0a3 (build ID: 20090223135443) and 1.1.17 on Windows XP sp3, too.  Not that anybody USES SeaMonkey (there&#8217;s like 20 of us), but maybe this will help point out that it&#8217;s endemic to the engine and not just Firefox.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-44597</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 11 Jul 2009 18:02:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-44597</guid>
		<description>Looks great in Ubuntu 9.04/FF3</description>
		<content:encoded><![CDATA[<p>Looks great in Ubuntu 9.04/FF3</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kozakewich</title>
		<link>http://www.zeldman.com/2009/07/09/firefox-test-page/#comment-44596</link>
		<dc:creator>Michael Kozakewich</dc:creator>
		<pubDate>Sat, 11 Jul 2009 14:14:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=1592#comment-44596</guid>
		<description>People have mentioned in a couple comments that it&#039;s cut off after a certain number of pixels, and I&#039;m sure you&#039;re sizing some things in pixels. If you set the dimensions in ems, will it turn into 32767 em instead of 32767 px?

Maybe you (by which I mean anyone reading this page) could do tests with various elements exceeding 32767 pixels, and set to the offending overflow value.

Hey, I know a great fix! 7pt pixel font, with lines of text that stretch across the entire screen! Set the leading to a small number, and there you go: You can fit as much text as you can imagine, without ever reaching the pixel limit!</description>
		<content:encoded><![CDATA[<p>People have mentioned in a couple comments that it&#8217;s cut off after a certain number of pixels, and I&#8217;m sure you&#8217;re sizing some things in pixels. If you set the dimensions in ems, will it turn into 32767 em instead of 32767 px?</p>
<p>Maybe you (by which I mean anyone reading this page) could do tests with various elements exceeding 32767 pixels, and set to the offending overflow value.</p>
<p>Hey, I know a great fix! 7pt pixel font, with lines of text that stretch across the entire screen! Set the leading to a small number, and there you go: You can fit as much text as you can imagine, without ever reaching the pixel limit!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
