<?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: Web developer features in Safari</title>
	<atom:link href="http://mac.elated.com/2008/05/22/web-developer-features-in-safari/feed/" rel="self" type="application/rss+xml" />
	<link>http://mac.elated.com/2008/05/22/web-developer-features-in-safari/</link>
	<description>A blog about Macs and that</description>
	<lastBuildDate>Tue, 07 Feb 2012 21:10:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: OperÃ¡sok Ã­rtÃ¡k &#8211; oldalak hibÃ¡inak javÃ­tÃ¡sa &#171; Bot &#171; LavX Blog</title>
		<link>http://mac.elated.com/2008/05/22/web-developer-features-in-safari/comment-page-1/#comment-12960</link>
		<dc:creator>OperÃ¡sok Ã­rtÃ¡k &#8211; oldalak hibÃ¡inak javÃ­tÃ¡sa &#171; Bot &#171; LavX Blog</dc:creator>
		<pubDate>Sun, 17 Jan 2010 23:30:27 +0000</pubDate>
		<guid isPermaLink="false">http://mac.elated.com/?p=142#comment-12960</guid>
		<description>[...] Safari homÃ¡lyos, dokumentÃ¡latlan trÃ¼kkÃ¶ket [...]</description>
		<content:encoded><![CDATA[<p>[...] Safari homÃ¡lyos, dokumentÃ¡latlan trÃ¼kkÃ¶ket [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Parcheo de sitios en Opera - Foros de CHW</title>
		<link>http://mac.elated.com/2008/05/22/web-developer-features-in-safari/comment-page-1/#comment-12475</link>
		<dc:creator>Parcheo de sitios en Opera - Foros de CHW</dc:creator>
		<pubDate>Thu, 16 Apr 2009 05:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://mac.elated.com/?p=142#comment-12475</guid>
		<description></description>
		<content:encoded><![CDATA[<p>[...] Safari tiene hacks oscuros e indocumentados para sitios específicos [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://mac.elated.com/2008/05/22/web-developer-features-in-safari/comment-page-1/#comment-12386</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Thu, 22 Jan 2009 21:58:32 +0000</pubDate>
		<guid isPermaLink="false">http://mac.elated.com/?p=142#comment-12386</guid>
		<description>@Percy: Yes that&#039;s my guess too. It&#039;s the lesser of 3 evils as you say!</description>
		<content:encoded><![CDATA[<p>@Percy: Yes that&#8217;s my guess too. It&#8217;s the lesser of 3 evils as you say!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Percy</title>
		<link>http://mac.elated.com/2008/05/22/web-developer-features-in-safari/comment-page-1/#comment-12369</link>
		<dc:creator>Percy</dc:creator>
		<pubDate>Fri, 09 Jan 2009 07:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://mac.elated.com/?p=142#comment-12369</guid>
		<description>I&#039;m guessing the Site specific hacks is actually a good thing.  My guess is it&#039;s to fix HTML/CSS issues that make a site behave or look improperly when rendered *according to standards*.  Since these sites are likely quite popular,  it would potentially kill Safari&#039;s chance at ever being taken as a serious browser if they couldn&#039;t display these common sites properly.  (ie. &quot;Safari can&#039;t even render cnn.com properly, forget it!&quot;)  I obviously have no idea what sites they are, but you get the idea.  So, really, their choices as I see them are:

1) Insist on keeping the standards (not a bad idea), but make some popular (albeit poorly designed/tested sites) look bad.
2) Compromise by breaking Safari&#039;s excellent standards compliance and make it render things in a non-compliance method.
2) Create site specific CSS hacks to get the best of both worlds.  Transparently change the CSS (the real source of the problem) to make things look as people would expect, and do not compromise the excellence of your rendering engine.

That is not to say there aren&#039;t some down sides to Option #3, but I would think they are of less concern than #1 and #2.</description>
		<content:encoded><![CDATA[<p>I&#8217;m guessing the Site specific hacks is actually a good thing.  My guess is it&#8217;s to fix HTML/CSS issues that make a site behave or look improperly when rendered *according to standards*.  Since these sites are likely quite popular,  it would potentially kill Safari&#8217;s chance at ever being taken as a serious browser if they couldn&#8217;t display these common sites properly.  (ie. &#8220;Safari can&#8217;t even render cnn.com properly, forget it!&#8221;)  I obviously have no idea what sites they are, but you get the idea.  So, really, their choices as I see them are:</p>
<p>1) Insist on keeping the standards (not a bad idea), but make some popular (albeit poorly designed/tested sites) look bad.<br />
2) Compromise by breaking Safari&#8217;s excellent standards compliance and make it render things in a non-compliance method.<br />
2) Create site specific CSS hacks to get the best of both worlds.  Transparently change the CSS (the real source of the problem) to make things look as people would expect, and do not compromise the excellence of your rendering engine.</p>
<p>That is not to say there aren&#8217;t some down sides to Option #3, but I would think they are of less concern than #1 and #2.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zack Katz</title>
		<link>http://mac.elated.com/2008/05/22/web-developer-features-in-safari/comment-page-1/#comment-6248</link>
		<dc:creator>Zack Katz</dc:creator>
		<pubDate>Mon, 02 Jun 2008 16:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://mac.elated.com/?p=142#comment-6248</guid>
		<description>Nice overview of the new Safari 3 features.
I wrote a related article on how to assign keyboard shortcuts for &lt;a href=&quot;http://katzwebdesign.wordpress.com/2008/06/02/disable-styles-and-javascript-in-safari-with-keyboard-shortcuts-how-to/&quot; rel=&quot;nofollow&quot;&gt;disabling Styles and JavaScript in Safari&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Nice overview of the new Safari 3 features.<br />
I wrote a related article on how to assign keyboard shortcuts for <a href="http://katzwebdesign.wordpress.com/2008/06/02/disable-styles-and-javascript-in-safari-with-keyboard-shortcuts-how-to/" rel="nofollow">disabling Styles and JavaScript in Safari</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://mac.elated.com/2008/05/22/web-developer-features-in-safari/comment-page-1/#comment-6064</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 23 May 2008 07:20:30 +0000</pubDate>
		<guid isPermaLink="false">http://mac.elated.com/?p=142#comment-6064</guid>
		<description>It&#039;s great isn&#039;t it. Safari 2.x had the Debug menu which was pretty good, but this is better!</description>
		<content:encoded><![CDATA[<p>It&#8217;s great isn&#8217;t it. Safari 2.x had the Debug menu which was pretty good, but this is better!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Si</title>
		<link>http://mac.elated.com/2008/05/22/web-developer-features-in-safari/comment-page-1/#comment-6046</link>
		<dc:creator>Si</dc:creator>
		<pubDate>Thu, 22 May 2008 11:17:56 +0000</pubDate>
		<guid isPermaLink="false">http://mac.elated.com/?p=142#comment-6046</guid>
		<description>Very cool. I&#039;d never even noticed this before!</description>
		<content:encoded><![CDATA[<p>Very cool. I&#8217;d never even noticed this before!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

