<?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: Google Chrome and Javascript/HTML Debugging</title>
	<atom:link href="http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/</link>
	<description>my experiments with IT and beyond</description>
	<lastBuildDate>Sat, 17 Jul 2010 12:56:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: how to achieve a cross browser compatible webdesign ? - Page 2 - x10Hosting Forums</title>
		<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/comment-page-1/#comment-178</link>
		<dc:creator>how to achieve a cross browser compatible webdesign ? - Page 2 - x10Hosting Forums</dc:creator>
		<pubDate>Fri, 03 Apr 2009 07:06:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kapilchhabra.com/?p=109#comment-178</guid>
		<description>[...] debug JS. For Safari, just enable the developer menu (though it won&#039;t help much with JS debugging). Chrome and Opera similarly have built-in debugging tools. Eric Pascarello started a tutorial on JS [...]</description>
		<content:encoded><![CDATA[<p>[...] debug JS. For Safari, just enable the developer menu (though it won&#8217;t help much with JS debugging). Chrome and Opera similarly have built-in debugging tools. Eric Pascarello started a tutorial on JS [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ZeeControls</title>
		<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/comment-page-1/#comment-177</link>
		<dc:creator>ZeeControls</dc:creator>
		<pubDate>Mon, 16 Feb 2009 15:01:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kapilchhabra.com/?p=109#comment-177</guid>
		<description>Debugging JavaScripts is much easier on Firefox (with Firebug) and Internet Explorer (with Visual Studio). ASP.NET developers could avoid developing JavaScripts (and debugging on numerous browsers with vastly different tools) by using server controls that generate JavaScripts for you. Like the &lt;a href=&quot;http://www.zettacube.com/Products/ZeeWebDock.aspx&quot; rel=&quot;nofollow&quot;&gt;WebDock for ASP.NET&lt;/a&gt; and &lt;a href=&quot;http://www.zettacube.com/Products/ZeeWebSplitter.aspx&quot; rel=&quot;nofollow&quot;&gt;Web Splitter for ASP.NET&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Debugging JavaScripts is much easier on Firefox (with Firebug) and Internet Explorer (with Visual Studio). ASP.NET developers could avoid developing JavaScripts (and debugging on numerous browsers with vastly different tools) by using server controls that generate JavaScripts for you. Like the <a href="http://www.zettacube.com/Products/ZeeWebDock.aspx" rel="nofollow">WebDock for ASP.NET</a> and <a href="http://www.zettacube.com/Products/ZeeWebSplitter.aspx" rel="nofollow">Web Splitter for ASP.NET</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: .net code generator</title>
		<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/comment-page-1/#comment-176</link>
		<dc:creator>.net code generator</dc:creator>
		<pubDate>Sat, 24 Jan 2009 14:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kapilchhabra.com/?p=109#comment-176</guid>
		<description>Chrome &#039;s javascript execution is much different from other browsers.This has caused so many problems for us up to now.

Sara :
&lt;a href=&quot;http://www.source4dotnet.com&quot; rel=&quot;nofollow&quot;&gt;.Net Code Generator&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Chrome &#8217;s javascript execution is much different from other browsers.This has caused so many problems for us up to now.</p>
<p>Sara :<br />
<a href="http://www.source4dotnet.com" rel="nofollow">.Net Code Generator</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Debug javascript v&#7899;i Chrome - Forums PHP Viet Nam</title>
		<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/comment-page-1/#comment-175</link>
		<dc:creator>Debug javascript v&#7899;i Chrome - Forums PHP Viet Nam</dc:creator>
		<pubDate>Wed, 01 Oct 2008 03:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kapilchhabra.com/?p=109#comment-175</guid>
		<description>[...] Debug javascript v&#7899;i Chrome      Link n?y do I&#039;m Thang g&#7917;i  Google Chrome and Javascript/HTML Debugging at /kapil/blog [...]</description>
		<content:encoded><![CDATA[<p>[...] Debug javascript v&#7899;i Chrome      Link n?y do I&#8217;m Thang g&#7917;i  Google Chrome and Javascript/HTML Debugging at /kapil/blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/comment-page-1/#comment-174</link>
		<dc:creator>James</dc:creator>
		<pubDate>Fri, 19 Sep 2008 01:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kapilchhabra.com/?p=109#comment-174</guid>
		<description>Hi, I found your blog on this new directory of WordPress Blogs at blackhatbootcamp.com/listofwordpressblogs.  I dont know how your blog came up, must have been a typo, i duno.  Anyways, I just clicked it and here I am.  Your blog looks good.  Have a nice day.  James.</description>
		<content:encoded><![CDATA[<p>Hi, I found your blog on this new directory of WordPress Blogs at blackhatbootcamp.com/listofwordpressblogs.  I dont know how your blog came up, must have been a typo, i duno.  Anyways, I just clicked it and here I am.  Your blog looks good.  Have a nice day.  James.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: devajitbarman</title>
		<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/comment-page-1/#comment-173</link>
		<dc:creator>devajitbarman</dc:creator>
		<pubDate>Thu, 04 Sep 2008 04:59:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kapilchhabra.com/?p=109#comment-173</guid>
		<description>My websites Java scripts don&#039;t run on Chrome...</description>
		<content:encoded><![CDATA[<p>My websites Java scripts don&#8217;t run on Chrome&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Javier Ruiz Jiménez</title>
		<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/comment-page-1/#comment-172</link>
		<dc:creator>Javier Ruiz Jiménez</dc:creator>
		<pubDate>Wed, 03 Sep 2008 14:46:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kapilchhabra.com/?p=109#comment-172</guid>
		<description>How to debug in Google Chrome (article in Spanish)
Since Google Chrome documentation about debuging is still to come, I
just wrote a short article explaining how to use the different tools
&quot;for developers&quot; available in Google Chrome.

Please take a look at the artilcle (Pictures are self explanatory,
but text is in Spanish)

&quot;Depurar Aplicaciones y Páginas Web con Google Chrome&quot;
http://www.tecsisa.com/index.igw?item=1608

I will be glad to add, edit or do changes as information arrives, so
feel free to give feedback (use contact form).

Javier Ruiz
www.tecsisa.com</description>
		<content:encoded><![CDATA[<p>How to debug in Google Chrome (article in Spanish)<br />
Since Google Chrome documentation about debuging is still to come, I<br />
just wrote a short article explaining how to use the different tools<br />
&#8220;for developers&#8221; available in Google Chrome.</p>
<p>Please take a look at the artilcle (Pictures are self explanatory,<br />
but text is in Spanish)</p>
<p>&#8220;Depurar Aplicaciones y Páginas Web con Google Chrome&#8221;<br />
<a href="http://www.tecsisa.com/index.igw?item=1608" rel="nofollow">http://www.tecsisa.com/index.igw?item=1608</a></p>
<p>I will be glad to add, edit or do changes as information arrives, so<br />
feel free to give feedback (use contact form).</p>
<p>Javier Ruiz<br />
<a href="http://www.tecsisa.com" rel="nofollow">http://www.tecsisa.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/comment-page-1/#comment-171</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 03 Sep 2008 12:55:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kapilchhabra.com/?p=109#comment-171</guid>
		<description>Cool intro on Chrome. This is a great browser, however, we tested it on multiple AJAX sites and it&#039;s definitely not quite ready for that.

Having to built a complex AJAX site is difficult enough for IE and FireFox, at least they provide excellent (VStudio) and decent (Firebug) javascript debugging.

I understand Chrome is still a beta version, but in this AJAX world, I was expecting more in terms of javascript debugging.</description>
		<content:encoded><![CDATA[<p>Cool intro on Chrome. This is a great browser, however, we tested it on multiple AJAX sites and it&#8217;s definitely not quite ready for that.</p>
<p>Having to built a complex AJAX site is difficult enough for IE and FireFox, at least they provide excellent (VStudio) and decent (Firebug) javascript debugging.</p>
<p>I understand Chrome is still a beta version, but in this AJAX world, I was expecting more in terms of javascript debugging.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LX</title>
		<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/comment-page-1/#comment-170</link>
		<dc:creator>LX</dc:creator>
		<pubDate>Wed, 03 Sep 2008 12:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kapilchhabra.com/?p=109#comment-170</guid>
		<description>sorry, mistake - not rendering engine, but javascript engine. Since the JS is precompiled, it is impossible to do the things an interpreter can do while interpreting - so the only way to go was a core debugger like gdb (and it seems like it is gdb with just some minor changes or at least parts of gdb taken).</description>
		<content:encoded><![CDATA[<p>sorry, mistake &#8211; not rendering engine, but javascript engine. Since the JS is precompiled, it is impossible to do the things an interpreter can do while interpreting &#8211; so the only way to go was a core debugger like gdb (and it seems like it is gdb with just some minor changes or at least parts of gdb taken).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LX</title>
		<link>http://blog.kapilchhabra.com/2008/09/google-chrome-and-javascripthtml-debugging/comment-page-1/#comment-169</link>
		<dc:creator>LX</dc:creator>
		<pubDate>Wed, 03 Sep 2008 10:53:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kapilchhabra.com/?p=109#comment-169</guid>
		<description>The Debugger is unlike anything in Safari, though this was to be expected with a new rendering engine. Instead it looks a lot like gdb. I hope there is soon some documentation and some nifty things like tab completion.</description>
		<content:encoded><![CDATA[<p>The Debugger is unlike anything in Safari, though this was to be expected with a new rendering engine. Instead it looks a lot like gdb. I hope there is soon some documentation and some nifty things like tab completion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
