<?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: Ten New Things in WebKit 3</title>
	<atom:link href="http://webkit.org/blog/122/webkit-3-10-new-things/feed/" rel="self" type="application/rss+xml" />
	<link>http://webkit.org/blog/122/webkit-3-10-new-things/</link>
	<description>All about WebKit development</description>
	<lastBuildDate>Sat, 21 Nov 2009 23:00:28 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: defender</title>
		<link>http://webkit.org/blog/122/webkit-3-10-new-things/comment-page-2/#comment-23721</link>
		<dc:creator>defender</dc:creator>
		<pubDate>Wed, 02 Jan 2008 03:48:41 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/122/webkit-3-10-new-things/#comment-23721</guid>
		<description>Can technologies like DOM and SVG be used as APIs for a Desktop operating system (read OS X), or are they only standards appropriate for a Web browser?

WebKit seems to be getting so powerful that it is a shame that some of its technologies don&#039;t make it into OS X itself.

There is a debate going on inside Apple about a resolution independent GUI. Instead of reinventing the wheel -- and forcing programmers to learn yet another proprietary API -- why doesn&#039;t Apple just use the ever-powerful, standards-compliant, time-tested SVG instead?</description>
		<content:encoded><![CDATA[<p>Can technologies like DOM and SVG be used as APIs for a Desktop operating system (read OS X), or are they only standards appropriate for a Web browser?</p>
<p>WebKit seems to be getting so powerful that it is a shame that some of its technologies don&#8217;t make it into OS X itself.</p>
<p>There is a debate going on inside Apple about a resolution independent GUI. Instead of reinventing the wheel &#8212; and forcing programmers to learn yet another proprietary API &#8212; why doesn&#8217;t Apple just use the ever-powerful, standards-compliant, time-tested SVG instead?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Logan</title>
		<link>http://webkit.org/blog/122/webkit-3-10-new-things/comment-page-2/#comment-23502</link>
		<dc:creator>Logan</dc:creator>
		<pubDate>Mon, 10 Dec 2007 21:59:22 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/122/webkit-3-10-new-things/#comment-23502</guid>
		<description>Please check out this link for how to activate the Web Inspector on the Windows version of Safari 3: 

http://www.typolight.org/forum/viewtopic.php?pid=18408#p18408</description>
		<content:encoded><![CDATA[<p>Please check out this link for how to activate the Web Inspector on the Windows version of Safari 3: </p>
<p><a href="http://www.typolight.org/forum/viewtopic.php?pid=18408#p18408" rel="nofollow">http://www.typolight.org/forum/viewtopic.php?pid=18408#p18408</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Surfin&#8217; Safari - Blog Archive &#187; Web Inspector Update</title>
		<link>http://webkit.org/blog/122/webkit-3-10-new-things/comment-page-2/#comment-23463</link>
		<dc:creator>Surfin&#8217; Safari - Blog Archive &#187; Web Inspector Update</dc:creator>
		<pubDate>Thu, 06 Dec 2007 20:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/122/webkit-3-10-new-things/#comment-23463</guid>
		<description>[...] Maciej said, web developer tools are a big new feature of WebKit 3. Since we first introduced the new Web [...]</description>
		<content:encoded><![CDATA[<p>[...] Maciej said, web developer tools are a big new feature of WebKit 3. Since we first introduced the new Web [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alp Toker &#187; Blog Archive &#187; WebKit/GTK+ API design</title>
		<link>http://webkit.org/blog/122/webkit-3-10-new-things/comment-page-2/#comment-23430</link>
		<dc:creator>Alp Toker &#187; Blog Archive &#187; WebKit/GTK+ API design</dc:creator>
		<pubDate>Fri, 30 Nov 2007 08:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/122/webkit-3-10-new-things/#comment-23430</guid>
		<description>[...] is nothing much worth keeping from the GtkHTML API as far as I can tell. WebKit now has excellent editable content support and exposes necessary public API for basic editing. Complex modifications will soon be possible [...]</description>
		<content:encoded><![CDATA[<p>[...] is nothing much worth keeping from the GtkHTML API as far as I can tell. WebKit now has excellent editable content support and exposes necessary public API for basic editing. Complex modifications will soon be possible [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: b.rvt</title>
		<link>http://webkit.org/blog/122/webkit-3-10-new-things/comment-page-1/#comment-23410</link>
		<dc:creator>b.rvt</dc:creator>
		<pubDate>Sat, 24 Nov 2007 21:59:48 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/122/webkit-3-10-new-things/#comment-23410</guid>
		<description>Visiting the Mac Fixit forum helped me find a workaround. I had PicLens installed (in /Library/Input Managers). Trashing PicLens solved the issue.

See http://www.macfixitforums.com/showflat.php?Cat=&amp;Board=tiger&amp;Number=838901&amp;page=0&amp;view=collapsed&amp;sb=5&amp;o=31&amp;fpart=1</description>
		<content:encoded><![CDATA[<p>Visiting the Mac Fixit forum helped me find a workaround. I had PicLens installed (in /Library/Input Managers). Trashing PicLens solved the issue.</p>
<p>See <a href="http://www.macfixitforums.com/showflat.php?Cat=&amp;Board=tiger&amp;Number=838901&amp;page=0&amp;view=collapsed&amp;sb=5&amp;o=31&amp;fpart=1" rel="nofollow">http://www.macfixitforums.com/showflat.php?Cat=&amp;Board=tiger&amp;Number=838901&amp;page=0&amp;view=collapsed&amp;sb=5&amp;o=31&amp;fpart=1</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Rowe</title>
		<link>http://webkit.org/blog/122/webkit-3-10-new-things/comment-page-1/#comment-23409</link>
		<dc:creator>Mark Rowe</dc:creator>
		<pubDate>Sat, 24 Nov 2007 21:22:56 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/122/webkit-3-10-new-things/#comment-23409</guid>
		<description>@b.rvt: This isn&#039;t really the right place to get support for Safari.  My suggestion would be to ensure you have no Safari extensions installed, and double-check that the Safari version matches the WebKit version..</description>
		<content:encoded><![CDATA[<p>@b.rvt: This isn&#8217;t really the right place to get support for Safari.  My suggestion would be to ensure you have no Safari extensions installed, and double-check that the Safari version matches the WebKit version..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: b.rvt</title>
		<link>http://webkit.org/blog/122/webkit-3-10-new-things/comment-page-1/#comment-23408</link>
		<dc:creator>b.rvt</dc:creator>
		<pubDate>Sat, 24 Nov 2007 19:45:36 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/122/webkit-3-10-new-things/#comment-23408</guid>
		<description>Upgrading from Mac OS X.4.10 to Mac OS X.4.11 completely destroyed Safari in the process. Safari does launch, but does not display any web page. Creating and new user and testing with this user does not help.</description>
		<content:encoded><![CDATA[<p>Upgrading from Mac OS X.4.10 to Mac OS X.4.11 completely destroyed Safari in the process. Safari does launch, but does not display any web page. Creating and new user and testing with this user does not help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DJCarbon43</title>
		<link>http://webkit.org/blog/122/webkit-3-10-new-things/comment-page-1/#comment-23402</link>
		<dc:creator>DJCarbon43</dc:creator>
		<pubDate>Fri, 23 Nov 2007 14:30:17 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/122/webkit-3-10-new-things/#comment-23402</guid>
		<description>@RichB:

Safari 3 is not listed as supporting 2k3 as far as I can tell by looking through webkit.org and http://www.apple.com/safari/download/. While it may have run, it has only been designed to support XP/Vista to my knowledge.

Sorry ;)</description>
		<content:encoded><![CDATA[<p>@RichB:</p>
<p>Safari 3 is not listed as supporting 2k3 as far as I can tell by looking through webkit.org and <a href="http://www.apple.com/safari/download/" rel="nofollow">http://www.apple.com/safari/download/</a>. While it may have run, it has only been designed to support XP/Vista to my knowledge.</p>
<p>Sorry <img src='http://webkit.org/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RichB</title>
		<link>http://webkit.org/blog/122/webkit-3-10-new-things/comment-page-1/#comment-23387</link>
		<dc:creator>RichB</dc:creator>
		<pubDate>Wed, 21 Nov 2007 07:10:53 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/122/webkit-3-10-new-things/#comment-23387</guid>
		<description>The latest Safari3/Windows hangs on Win2K3/64bit. Previous betas worked fine. I&#039;m not sure whether it&#039;s the 64bit-ness or the Win2K3-ness that&#039;s causing the problem.</description>
		<content:encoded><![CDATA[<p>The latest Safari3/Windows hangs on Win2K3/64bit. Previous betas worked fine. I&#8217;m not sure whether it&#8217;s the 64bit-ness or the Win2K3-ness that&#8217;s causing the problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Bloemendaal</title>
		<link>http://webkit.org/blog/122/webkit-3-10-new-things/comment-page-1/#comment-23366</link>
		<dc:creator>Danny Bloemendaal</dc:creator>
		<pubDate>Tue, 20 Nov 2007 08:19:28 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/122/webkit-3-10-new-things/#comment-23366</guid>
		<description>I agree completely with lookfirst. For me Safari is just a browser that I open every now and then to see if my pages work. But as long as there is no firebug equivalent for Safari, I am not going to use it as my main browser. I absolutely need Firebug for my work and what you guys have come up with so far doesn&#039;t even come close to be useful to me. And I know a lot of people who think about it the same. So if you ask me, if you really want to gain momentum in the browser world.. stop developing new css3 features and focus on these development tools.

Just my 2 cents :)</description>
		<content:encoded><![CDATA[<p>I agree completely with lookfirst. For me Safari is just a browser that I open every now and then to see if my pages work. But as long as there is no firebug equivalent for Safari, I am not going to use it as my main browser. I absolutely need Firebug for my work and what you guys have come up with so far doesn&#8217;t even come close to be useful to me. And I know a lot of people who think about it the same. So if you ask me, if you really want to gain momentum in the browser world.. stop developing new css3 features and focus on these development tools.</p>
<p>Just my 2 cents <img src='http://webkit.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
