<?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: Asynchronous Location Bar has Landed</title>
	<atom:link href="http://shawnwilsher.com/archives/279/feed" rel="self" type="application/rss+xml" />
	<link>http://shawnwilsher.com/archives/279</link>
	<description></description>
	<lastBuildDate>Wed, 03 Mar 2010 21:06:45 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Swing and a Miss : Shawn Wilsher</title>
		<link>http://shawnwilsher.com/archives/279/comment-page-1#comment-3849</link>
		<dc:creator>Swing and a Miss : Shawn Wilsher</dc:creator>
		<pubDate>Wed, 02 Sep 2009 21:48:48 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/?p=279#comment-3849</guid>
		<description>[...] we landed the asynchronous location bar, some people started to see substantially slower results. This was alarming since it was supposed [...]</description>
		<content:encoded><![CDATA[<p>[...] we landed the asynchronous location bar, some people started to see substantially slower results. This was alarming since it was supposed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Performance vs Responsiveness —or— How I Made the Parser Twice As Fast in One Day</title>
		<link>http://shawnwilsher.com/archives/279/comment-page-1#comment-3756</link>
		<dc:creator>Performance vs Responsiveness —or— How I Made the Parser Twice As Fast in One Day</dc:creator>
		<pubDate>Thu, 13 Aug 2009 06:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/?p=279#comment-3756</guid>
		<description>[...] This is analogous to a recent discussion of the asynchronous AwesomeBar.&#160;&#8617; [...]</description>
		<content:encoded><![CDATA[<p>[...] This is analogous to a recent discussion of the asynchronous AwesomeBar.&#160;&#8617; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://shawnwilsher.com/archives/279/comment-page-1#comment-3755</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 12 Aug 2009 18:22:43 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/?p=279#comment-3755</guid>
		<description>Fair point, bug filed. https://bugzilla.mozilla.org/show_bug.cgi?id=510016

I have never installed the prototype extension.</description>
		<content:encoded><![CDATA[<p>Fair point, bug filed. <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=510016" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=510016</a></p>
<p>I have never installed the prototype extension.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Wilsher</title>
		<link>http://shawnwilsher.com/archives/279/comment-page-1#comment-3754</link>
		<dc:creator>Shawn Wilsher</dc:creator>
		<pubDate>Wed, 12 Aug 2009 17:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/?p=279#comment-3754</guid>
		<description>None of you have the add-on installed, right?  This is the first I&#039;ve heard of the issue (why aren&#039;t people filing bugs?)</description>
		<content:encoded><![CDATA[<p>None of you have the add-on installed, right?  This is the first I&#8217;ve heard of the issue (why aren&#8217;t people filing bugs?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Wilsher</title>
		<link>http://shawnwilsher.com/archives/279/comment-page-1#comment-3753</link>
		<dc:creator>Shawn Wilsher</dc:creator>
		<pubDate>Wed, 12 Aug 2009 15:14:55 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/?p=279#comment-3753</guid>
		<description>This would run on a different core.  Contrary to popular belief, Firefox hasn&#039;t been single threaded in a very very long time.</description>
		<content:encoded><![CDATA[<p>This would run on a different core.  Contrary to popular belief, Firefox hasn&#8217;t been single threaded in a very very long time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: biesi</title>
		<link>http://shawnwilsher.com/archives/279/comment-page-1#comment-3752</link>
		<dc:creator>biesi</dc:creator>
		<pubDate>Wed, 12 Aug 2009 15:14:06 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/?p=279#comment-3752</guid>
		<description>Is this what makes the dropdown take forever to go away, and consequently what makes pressing enter take forever to take effect? (forever = ~1 sec or so)</description>
		<content:encoded><![CDATA[<p>Is this what makes the dropdown take forever to go away, and consequently what makes pressing enter take forever to take effect? (forever = ~1 sec or so)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Igor</title>
		<link>http://shawnwilsher.com/archives/279/comment-page-1#comment-3751</link>
		<dc:creator>Igor</dc:creator>
		<pubDate>Wed, 12 Aug 2009 11:10:31 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/?p=279#comment-3751</guid>
		<description>I can confirm what Dan said, it&#039;s been happening since Async bar has landed and still happens in the latest nightlies. It does happen even when the domain name isn&#039;t short and has already been found by the bar, and the delay in registering the enter is quite long.</description>
		<content:encoded><![CDATA[<p>I can confirm what Dan said, it&#8217;s been happening since Async bar has landed and still happens in the latest nightlies. It does happen even when the domain name isn&#8217;t short and has already been found by the bar, and the delay in registering the enter is quite long.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AV</title>
		<link>http://shawnwilsher.com/archives/279/comment-page-1#comment-3750</link>
		<dc:creator>AV</dc:creator>
		<pubDate>Wed, 12 Aug 2009 09:13:36 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/?p=279#comment-3750</guid>
		<description>Perhaps because I’m a lousy typist or perhaps because I have a very old PC, I find that because of bug 503701, results are very often slower to appear than before.</description>
		<content:encoded><![CDATA[<p>Perhaps because I’m a lousy typist or perhaps because I have a very old PC, I find that because of bug 503701, results are very often slower to appear than before.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian M</title>
		<link>http://shawnwilsher.com/archives/279/comment-page-1#comment-3749</link>
		<dc:creator>Ian M</dc:creator>
		<pubDate>Wed, 12 Aug 2009 08:46:10 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/?p=279#comment-3749</guid>
		<description>Will this thread run on a different core on a multi-core computer, or is it still all single threaded?</description>
		<content:encoded><![CDATA[<p>Will this thread run on a different core on a multi-core computer, or is it still all single threaded?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://shawnwilsher.com/archives/279/comment-page-1#comment-3747</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Tue, 11 Aug 2009 21:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/?p=279#comment-3747</guid>
		<description>I have noticed now that when I quickly type an address and hit enter (all in one go, bypassing the awesomebar) then the enter doesn&#039;t seem to be processed until after the results have been returned. This is normally the case when the domain is short and I can type it out and press enter quicker than typing part of it, waiting for the results, pressing the down arrow and then pressing enter.</description>
		<content:encoded><![CDATA[<p>I have noticed now that when I quickly type an address and hit enter (all in one go, bypassing the awesomebar) then the enter doesn&#8217;t seem to be processed until after the results have been returned. This is normally the case when the domain is short and I can type it out and press enter quicker than typing part of it, waiting for the results, pressing the down arrow and then pressing enter.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
