<?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: Firebug and Firefox</title>
	<atom:link href="http://shawnwilsher.com/archives/102/feed" rel="self" type="application/rss+xml" />
	<link>http://shawnwilsher.com/archives/102</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: Allan Beaufour</title>
		<link>http://shawnwilsher.com/archives/102/comment-page-1#comment-1114</link>
		<dc:creator>Allan Beaufour</dc:creator>
		<pubDate>Fri, 08 Jun 2007 14:26:43 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/archives/102#comment-1114</guid>
		<description>Related to what people say about chrome/extensions DOM Inspector also work for XULRunner applications, Firebug does not.</description>
		<content:encoded><![CDATA[<p>Related to what people say about chrome/extensions DOM Inspector also work for XULRunner applications, Firebug does not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://shawnwilsher.com/archives/102/comment-page-1#comment-1104</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Fri, 01 Jun 2007 16:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/archives/102#comment-1104</guid>
		<description>Due to not using native widgets, Firebug isn&#039;t very keyboard friendly, either. Just try navigating a DOM tree without a mouse (you can&#039;t even tab to it). As a consequence, it somehow doesn&#039;t feel right.</description>
		<content:encoded><![CDATA[<p>Due to not using native widgets, Firebug isn&#8217;t very keyboard friendly, either. Just try navigating a DOM tree without a mouse (you can&#8217;t even tab to it). As a consequence, it somehow doesn&#8217;t feel right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Kaply</title>
		<link>http://shawnwilsher.com/archives/102/comment-page-1#comment-1101</link>
		<dc:creator>Mike Kaply</dc:creator>
		<pubDate>Fri, 01 Jun 2007 14:26:43 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/archives/102#comment-1101</guid>
		<description>Chrome, chrome and more chrome.

Until Firebug can be used to inspect and debug chrome files and extensions, it doesn&#039;t even come close to replacing DOM Inspector and Venkman.</description>
		<content:encoded><![CDATA[<p>Chrome, chrome and more chrome.</p>
<p>Until Firebug can be used to inspect and debug chrome files and extensions, it doesn&#8217;t even come close to replacing DOM Inspector and Venkman.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Arvidsson</title>
		<link>http://shawnwilsher.com/archives/102/comment-page-1#comment-1099</link>
		<dc:creator>Erik Arvidsson</dc:creator>
		<pubDate>Fri, 01 Jun 2007 02:20:32 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/archives/102#comment-1099</guid>
		<description>Venkman allows us to debug code that has been eval&#039;d (using the pretty print mode). This is a crucial feature for larger applications. Firebug just gets confused.

Firebug is also very slow at debugging large javascript files since the code it uses for displaying the formatted js is very inefficient.</description>
		<content:encoded><![CDATA[<p>Venkman allows us to debug code that has been eval&#8217;d (using the pretty print mode). This is a crucial feature for larger applications. Firebug just gets confused.</p>
<p>Firebug is also very slow at debugging large javascript files since the code it uses for displaying the formatted js is very inefficient.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: glob</title>
		<link>http://shawnwilsher.com/archives/102/comment-page-1#comment-1098</link>
		<dc:creator>glob</dc:creator>
		<pubDate>Fri, 01 Jun 2007 00:33:13 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/archives/102#comment-1098</guid>
		<description>i also love firebug but my biggest concern is it consumes (and perhaps leaks) massive amounts of memory.  i&#039;d always thought that firefox &quot;just uses lots of memory&quot; until i disabled the firebug extension.

until this has been resolved it isn&#039;t suitable for inclusion.</description>
		<content:encoded><![CDATA[<p>i also love firebug but my biggest concern is it consumes (and perhaps leaks) massive amounts of memory.  i&#8217;d always thought that firefox &#8220;just uses lots of memory&#8221; until i disabled the firebug extension.</p>
<p>until this has been resolved it isn&#8217;t suitable for inclusion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://shawnwilsher.com/archives/102/comment-page-1#comment-1097</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Thu, 31 May 2007 23:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/archives/102#comment-1097</guid>
		<description>I agree with pascalc, it would be good if firebug could show the built-in browser styles.  Even if it was just an option that could be enabled.</description>
		<content:encoded><![CDATA[<p>I agree with pascalc, it would be good if firebug could show the built-in browser styles.  Even if it was just an option that could be enabled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pascalc</title>
		<link>http://shawnwilsher.com/archives/102/comment-page-1#comment-1096</link>
		<dc:creator>pascalc</dc:creator>
		<pubDate>Thu, 31 May 2007 22:27:35 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/archives/102#comment-1096</guid>
		<description>With the DOM inspector you can view all the styles applied to an element, including the browser default styles (like resource://gre/res/forms.css), thanks to this information the computed style is more understandable than in Firebug.</description>
		<content:encoded><![CDATA[<p>With the DOM inspector you can view all the styles applied to an element, including the browser default styles (like resource://gre/res/forms.css), thanks to this information the computed style is more understandable than in Firebug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: clav</title>
		<link>http://shawnwilsher.com/archives/102/comment-page-1#comment-1095</link>
		<dc:creator>clav</dc:creator>
		<pubDate>Thu, 31 May 2007 22:02:12 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/archives/102#comment-1095</guid>
		<description>The main advantage of DOMi is probably that it can be used for extension development too, since you can point it at chrome documents, and it understands anonymous content (from XBL).</description>
		<content:encoded><![CDATA[<p>The main advantage of DOMi is probably that it can be used for extension development too, since you can point it at chrome documents, and it understands anonymous content (from XBL).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daryl</title>
		<link>http://shawnwilsher.com/archives/102/comment-page-1#comment-1094</link>
		<dc:creator>Daryl</dc:creator>
		<pubDate>Thu, 31 May 2007 20:44:20 +0000</pubDate>
		<guid isPermaLink="false">http://shawnwilsher.com/archives/102#comment-1094</guid>
		<description>Although I love Firebug, I don&#039;t know that it&#039;s terribly important to have it included in a distribution. Those who would use Firebug are likely to have a number of addons they install anyway, so this saves just one install. It&#039;d probably be more of a pain to get and update the special distribution than simply to install Firebug as an extension in the first place.</description>
		<content:encoded><![CDATA[<p>Although I love Firebug, I don&#8217;t know that it&#8217;s terribly important to have it included in a distribution. Those who would use Firebug are likely to have a number of addons they install anyway, so this saves just one install. It&#8217;d probably be more of a pain to get and update the special distribution than simply to install Firebug as an extension in the first place.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
