<?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 for a pint of javascript (and general web stuff)</title>
	<atom:link href="http://blog.gonchuki.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gonchuki.com</link>
	<description></description>
	<lastBuildDate>Tue, 30 Aug 2011 04:07:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on HTML5 vs Flash take 2: what Steve Jobs doesn&#039;t want you to know by mj</title>
		<link>http://blog.gonchuki.com/archives/html5-vs-flash-take-2-what-steve-jobs-doesnt-want-you-to-know/comment-page-1/#comment-605</link>
		<dc:creator>mj</dc:creator>
		<pubDate>Tue, 30 Aug 2011 04:07:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gonchuki.com/?p=134#comment-605</guid>
		<description>Ignore the technical details.  Apple is denying it&#039;s customers (and developers) choice.  What is their motive?  Do you think it is wise to let a single party make a choice for you?  Do you think they will have your best interest in mind?  They could have easily turned flash off by default and buried the checkbox to turn it on ten layers deep, but they didn&#039;t, they banned its use in their own self interest.</description>
		<content:encoded><![CDATA[<p>Ignore the technical details.  Apple is denying it&#039;s customers (and developers) choice.  What is their motive?  Do you think it is wise to let a single party make a choice for you?  Do you think they will have your best interest in mind?  They could have easily turned flash off by default and buried the checkbox to turn it on ten layers deep, but they didn&#039;t, they banned its use in their own self interest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on usability 101: adding a global &quot;back to top&quot; to your site by klaus Arends</title>
		<link>http://blog.gonchuki.com/archives/usability-101-adding-a-global-back-to-top-to-your-site/comment-page-1/#comment-600</link>
		<dc:creator>klaus Arends</dc:creator>
		<pubDate>Wed, 22 Jun 2011 18:25:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gonchuki.com/archives/usability-101-adding-a-global-back-to-top-to-your-site/#comment-600</guid>
		<description>Thanks a lot ... for the script.
I had a back up button on Joomla realized with jquery. 
It gave me some conflicts with mootools modules...
This is exactly the Solution i needed...
Regards from Spain...</description>
		<content:encoded><![CDATA[<p>Thanks a lot &#8230; for the script.<br />
I had a back up button on Joomla realized with jquery.<br />
It gave me some conflicts with mootools modules&#8230;<br />
This is exactly the Solution i needed&#8230;<br />
Regards from Spain&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HTML5 vs Flash take 2: what Steve Jobs doesn&#039;t want you to know by Repository of &#8220;Thoughts on Flash&#8221; responses and articles &#124; In Flagrante Delicto!</title>
		<link>http://blog.gonchuki.com/archives/html5-vs-flash-take-2-what-steve-jobs-doesnt-want-you-to-know/comment-page-1/#comment-599</link>
		<dc:creator>Repository of &#8220;Thoughts on Flash&#8221; responses and articles &#124; In Flagrante Delicto!</dc:creator>
		<pubDate>Wed, 23 Mar 2011 15:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gonchuki.com/?p=134#comment-599</guid>
		<description>[...] HTML5 vs Flash take 2: what Steve Jobs doesn&#8217;t want you to know [...]</description>
		<content:encoded><![CDATA[<p>[...] HTML5 vs Flash take 2: what Steve Jobs doesn&#039;t want you to know [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Standards Compliancy is a lie (or, how all browsers have a broken border-radius) by gonchuki</title>
		<link>http://blog.gonchuki.com/archives/standards-compliancy-is-a-lie-or-how-all-browsers-have-a-broken-border-radius/comment-page-1/#comment-548</link>
		<dc:creator>gonchuki</dc:creator>
		<pubDate>Wed, 07 Jul 2010 15:22:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gonchuki.com/?p=170#comment-548</guid>
		<description>I understand that CSS3 is not a finished standard, but &lt;a href=&quot;http://www.css3.info/border-radius-apple-vs-mozilla/&quot; rel=&quot;nofollow&quot;&gt;this post from early 2007&lt;/a&gt; shows how we had border-radius support in Gecko and Webkit for well over 3 years. It&#039;s clearly not a feature that was added sometime last Thursday.</description>
		<content:encoded><![CDATA[<p>I understand that CSS3 is not a finished standard, but <a href="http://www.css3.info/border-radius-apple-vs-mozilla/" rel="nofollow">this post from early 2007</a> shows how we had border-radius support in Gecko and Webkit for well over 3 years. It&#039;s clearly not a feature that was added sometime last Thursday.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Standards Compliancy is a lie (or, how all browsers have a broken border-radius) by Keith Cirkel</title>
		<link>http://blog.gonchuki.com/archives/standards-compliancy-is-a-lie-or-how-all-browsers-have-a-broken-border-radius/comment-page-1/#comment-546</link>
		<dc:creator>Keith Cirkel</dc:creator>
		<pubDate>Wed, 07 Jul 2010 09:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gonchuki.com/?p=170#comment-546</guid>
		<description>It&#039;s fine that all browsers have lost the vendor prefix, because the vendor prefix is there for syntax/lexical changes, so that any change to the standard doesn&#039;t destabilise existing website based on the vendor-prefix syntax standard (case in point, look at -moz-gradient and -webkit-gradient).

The bug here is a rendering issue. It&#039;s still bad, but its just rendering issues, fixable without impact. Bear in mind this is CSS3 W3C Candidate Recommendation, not a W3C Standard - meaning it&#039;s all very new still.</description>
		<content:encoded><![CDATA[<p>It&#039;s fine that all browsers have lost the vendor prefix, because the vendor prefix is there for syntax/lexical changes, so that any change to the standard doesn&#039;t destabilise existing website based on the vendor-prefix syntax standard (case in point, look at -moz-gradient and -webkit-gradient).</p>
<p>The bug here is a rendering issue. It&#039;s still bad, but its just rendering issues, fixable without impact. Bear in mind this is CSS3 <acronym title="World Wide Web Consortium">W3C</acronym> Candidate Recommendation, not a <acronym title="World Wide Web Consortium">W3C</acronym> Standard &#8211; meaning it&#039;s all very new still.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Standards Compliancy is a lie (or, how all browsers have a broken border-radius) by gonchuki</title>
		<link>http://blog.gonchuki.com/archives/standards-compliancy-is-a-lie-or-how-all-browsers-have-a-broken-border-radius/comment-page-1/#comment-545</link>
		<dc:creator>gonchuki</dc:creator>
		<pubDate>Wed, 07 Jul 2010 01:41:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gonchuki.com/?p=170#comment-545</guid>
		<description>Actually both Opera and the IE9 preview work without any vendor prefix for border-radius. None of them get it right.</description>
		<content:encoded><![CDATA[<p>Actually both Opera and the IE9 preview work without any vendor prefix for border-radius. None of them get it right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Standards Compliancy is a lie (or, how all browsers have a broken border-radius) by Zach Leatherman</title>
		<link>http://blog.gonchuki.com/archives/standards-compliancy-is-a-lie-or-how-all-browsers-have-a-broken-border-radius/comment-page-1/#comment-543</link>
		<dc:creator>Zach Leatherman</dc:creator>
		<pubDate>Wed, 07 Jul 2010 01:26:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gonchuki.com/?p=170#comment-543</guid>
		<description>This doesn&#039;t seem all that painful. Isn&#039;t this why we have vendor prefixes?

Which browsers have removed the vendor prefix and use just border-radius?</description>
		<content:encoded><![CDATA[<p>This doesn&#039;t seem all that painful. Isn&#039;t this why we have vendor prefixes?</p>
<p>Which browsers have removed the vendor prefix and use just border-radius?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSS Sprites2 &#8211; It&#039;s MooTools Time by Peter</title>
		<link>http://blog.gonchuki.com/archives/css-sprites2-its-mootools-time/comment-page-1/#comment-528</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sat, 22 May 2010 17:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gonchuki.com/?p=34#comment-528</guid>
		<description>First: excellent solution, pretty, clean motion! Thank YOU for sharing!

Second: What if one wanted to make this into an include file for a PHP file?

I&#039;ve seen some similar CURRENT PAGE scripts use the body id or a PHP function inserted at the top of the page to identify the page as the CURRENT PAGE, but the List Apart solution and yours only calls the class of the current page within the LI tag  for each link so it performs only if the code is included inline.

So, for a non-techie like myself, trying to figure out how to modify the JS and CSS  for use in a PHP include file -- i.e., exactly where and what to change to make it recognize when to use the CSS for the CURRENT PAGE as an include file is… a bit daunting.

Is this an easy fix, or does it require major revamping?

Any guidance would be greatly appreciated.

You rock!</description>
		<content:encoded><![CDATA[<p>First: excellent solution, pretty, clean motion! Thank YOU for sharing!</p>
<p>Second: What if one wanted to make this into an include file for a <acronym title="Hypertext PreProcessing">PHP</acronym> file?</p>
<p>I&#039;ve seen some similar CURRENT PAGE scripts use the body id or a <acronym title="Hypertext PreProcessing">PHP</acronym> function inserted at the top of the page to identify the page as the CURRENT PAGE, but the List Apart solution and yours only calls the class of the current page within the LI tag  for each link so it performs only if the code is included inline.</p>
<p>So, for a non-techie like myself, trying to figure out how to modify the <acronym title="JavaScript">JS</acronym> and <acronym title="Cascading Style Sheets">CSS</acronym>  for use in a <acronym title="Hypertext PreProcessing">PHP</acronym> include file &#8212; i.e., exactly where and what to change to make it recognize when to use the <acronym title="Cascading Style Sheets">CSS</acronym> for the CURRENT PAGE as an include file is… a bit daunting.</p>
<p>Is this an easy fix, or does it require major revamping?</p>
<p>Any guidance would be greatly appreciated.</p>
<p>You rock!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HTML5 vs Flash take 2: what Steve Jobs doesn&#039;t want you to know by mve</title>
		<link>http://blog.gonchuki.com/archives/html5-vs-flash-take-2-what-steve-jobs-doesnt-want-you-to-know/comment-page-1/#comment-511</link>
		<dc:creator>mve</dc:creator>
		<pubDate>Wed, 05 May 2010 10:30:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gonchuki.com/?p=134#comment-511</guid>
		<description>I agree, I think Adobe has put in some hard work over the years to really make Flash a usable format.  I saw some really cool i-pad type of device running Air as a digital magazine.  I think it was Wired if I&#039;m not mistaken.  Thanks for the post.</description>
		<content:encoded><![CDATA[<p>I agree, I think Adobe has put in some hard work over the years to really make Flash a usable format.  I saw some really cool i-pad type of device running Air as a digital magazine.  I think it was Wired if I&#039;m not mistaken.  Thanks for the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HTML5 vs Flash take 2: what Steve Jobs doesn&#039;t want you to know by gonchuki</title>
		<link>http://blog.gonchuki.com/archives/html5-vs-flash-take-2-what-steve-jobs-doesnt-want-you-to-know/comment-page-1/#comment-507</link>
		<dc:creator>gonchuki</dc:creator>
		<pubDate>Tue, 04 May 2010 22:20:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gonchuki.com/?p=134#comment-507</guid>
		<description>@Robin Annon
totally, and we must be rational and attribute the issue to all the parties: Macromedia, Adobe and most importantly: Apple, for giving very poor API support.</description>
		<content:encoded><![CDATA[<p>@Robin Annon<br />
totally, and we must be rational and attribute the issue to all the parties: Macromedia, Adobe and most importantly: Apple, for giving very poor <acronym title="Application Programming Interface">API</acronym> support.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

