<?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 I does Javascript!</title>
	<atom:link href="http://blog.stchur.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.stchur.com</link>
	<description>If you don&#039;t expect too much from me, you might not be let down.</description>
	<lastBuildDate>Thu, 26 Jan 2012 08:23:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>Comment on IE Bug dealing with CSS custom cusors by sstchur</title>
		<link>http://blog.stchur.com/2006/11/02/ie-bug-dealing-with-css-custom-cusors/comment-page-1/#comment-133078</link>
		<dc:creator>sstchur</dc:creator>
		<pubDate>Thu, 26 Jan 2012 08:23:55 +0000</pubDate>
		<guid isPermaLink="false">http://stchur.com/blog2/2006/11/02/ie-bug-dealing-with-css-custom-cusors/#comment-133078</guid>
		<description>Glad it helped!</description>
		<content:encoded><![CDATA[<p>Glad it helped!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on IE Bug dealing with CSS custom cusors by keith</title>
		<link>http://blog.stchur.com/2006/11/02/ie-bug-dealing-with-css-custom-cusors/comment-page-1/#comment-133051</link>
		<dc:creator>keith</dc:creator>
		<pubDate>Wed, 25 Jan 2012 22:19:04 +0000</pubDate>
		<guid isPermaLink="false">http://stchur.com/blog2/2006/11/02/ie-bug-dealing-with-css-custom-cusors/#comment-133051</guid>
		<description>wow. 5 years and 2 months later, I came across this post and it explains the issue ever so well. We don&#039;t support IE7 much anymore, but when IE7 users would hit our site, it would try and grab a url that didn&#039;t exist and was causing some load on the server.</description>
		<content:encoded><![CDATA[<p>wow. 5 years and 2 months later, I came across this post and it explains the issue ever so well. We don&#039;t support IE7 much anymore, but when IE7 users would hit our site, it would try and grab a url that didn&#039;t exist and was causing some load on the server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Avoiding recursion in Javascript by Andreas Frische</title>
		<link>http://blog.stchur.com/2007/07/06/avoiding-recursion-in-javascript/comment-page-1/#comment-131929</link>
		<dc:creator>Andreas Frische</dc:creator>
		<pubDate>Sat, 14 Jan 2012 21:25:18 +0000</pubDate>
		<guid isPermaLink="false">http://stchur.com/blog2/2007/07/06/avoiding-recursion-in-javascript/#comment-131929</guid>
		<description>You can have your cake and eat it too. Use Tail Recursion and you will only have one call to your function at once.
http://en.wikipedia.org/wiki/Tail_call</description>
		<content:encoded><![CDATA[<p>You can have your cake and eat it too. Use Tail Recursion and you will only have one call to your function at once.<br />
<a href="http://en.wikipedia.org/wiki/Tail_call" rel="nofollow">http://en.wikipedia.org/wiki/Tail_call</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Serializing Objects in Javascript by Ron Cemer</title>
		<link>http://blog.stchur.com/2007/04/06/serializing-objects-in-javascript/comment-page-1/#comment-130375</link>
		<dc:creator>Ron Cemer</dc:creator>
		<pubDate>Tue, 03 Jan 2012 07:05:53 +0000</pubDate>
		<guid isPermaLink="false">http://stchur.com/blog2/2007/04/06/serializing-objects-in-javascript/#comment-130375</guid>
		<description>Your string serialization isn&#039;t properly escaping special characters.  For example, quotes inside the string should be prefixed with backslashes; backslashes in the string should be replaced with double backslashes; characters outside the ASCII character range should (probably) be replaced with their hexadeximal unicode equivalent (\xNNNN).  The way it is now, all you have to do to break it is to include a single quote within a string anywhere in the object tree.  The result will be unparseable JavaScript due to syntax errors.  Try this instead, which is straight from the horse&#039;s moutn (download links at the bottom of the page): http://www.json.org/js.html</description>
		<content:encoded><![CDATA[<p>Your string serialization isn&#039;t properly escaping special characters.  For example, quotes inside the string should be prefixed with backslashes; backslashes in the string should be replaced with double backslashes; characters outside the ASCII character range should (probably) be replaced with their hexadeximal unicode equivalent (\xNNNN).  The way it is now, all you have to do to break it is to include a single quote within a string anywhere in the object tree.  The result will be unparseable JavaScript due to syntax errors.  Try this instead, which is straight from the horse&#039;s moutn (download links at the bottom of the page): <a href="http://www.json.org/js.html" rel="nofollow">http://www.json.org/js.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Converting to Pixels with javascript by sstchur</title>
		<link>http://blog.stchur.com/2006/09/20/converting-to-pixels-with-javascript/comment-page-1/#comment-128359</link>
		<dc:creator>sstchur</dc:creator>
		<pubDate>Fri, 16 Dec 2011 18:59:26 +0000</pubDate>
		<guid isPermaLink="false">http://stchur.com/blog2/2006/09/20/converting-to-pixels-with-javascript/#comment-128359</guid>
		<description>Joe:

This is a little bit tricky because you have to consider the fact that when you specify a dimension as a percentage in CSS, it&#039;s a percentage of the parent&#039;s STYLE height (that is, its height as specified in CSS).  Bear in mind that this could be rather different from its rendered height on screen.

For instance, if you specify that an element have height: 400px, but then also give it 10px padding all around, and a 20px border all around, the total height (offsetHeight) will actually be 60px more (30px on top and bottom).  However, that extra 60px doesn&#039;t come into play when calculating the height of some child element specified as a percentage.

What you really want then is the style height of the outer element (that is, you need the height in pixels of the outer element as specified in the CSS).  And to further complicate your life, that value might not be specified in px, and if you&#039;re in IE, then you&#039;ll need to convert it to px :-)

And you&#039;ll need the same value of the inner element.  Probably, your favorite Javascript library has a way of getting the height (or width) of an element as specified in CSS (note that reading .style.height will not work if the height was not specified via .style.height or via an inline style attribute).

I don&#039;t know how to do this in jQuery or Prototype or Dojo, but in Gimme (my library) it would look like:

var innerElemHeight = parseInt(Gimme(&#039;#innerElem&#039;).get_style(&#039;height&#039;));
var outerElemHeight = parseInt(Gimme(&#039;#outerElem&#039;).get_style(&#039;height&#039;));
var pct = innerElemHeight / outerElemHeight;

Hope this helps!</description>
		<content:encoded><![CDATA[<p>Joe:</p>
<p>This is a little bit tricky because you have to consider the fact that when you specify a dimension as a percentage in CSS, it&#039;s a percentage of the parent&#039;s STYLE height (that is, its height as specified in CSS).  Bear in mind that this could be rather different from its rendered height on screen.</p>
<p>For instance, if you specify that an element have height: 400px, but then also give it 10px padding all around, and a 20px border all around, the total height (offsetHeight) will actually be 60px more (30px on top and bottom).  However, that extra 60px doesn&#039;t come into play when calculating the height of some child element specified as a percentage.</p>
<p>What you really want then is the style height of the outer element (that is, you need the height in pixels of the outer element as specified in the CSS).  And to further complicate your life, that value might not be specified in px, and if you&#039;re in IE, then you&#039;ll need to convert it to px <img src='http://blog.stchur.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>And you&#039;ll need the same value of the inner element.  Probably, your favorite Javascript library has a way of getting the height (or width) of an element as specified in CSS (note that reading .style.height will not work if the height was not specified via .style.height or via an inline style attribute).</p>
<p>I don&#039;t know how to do this in jQuery or Prototype or Dojo, but in Gimme (my library) it would look like:</p>
<p>var innerElemHeight = parseInt(Gimme(&#039;#innerElem&#039;).get_style(&#039;height&#039;));<br />
var outerElemHeight = parseInt(Gimme(&#039;#outerElem&#039;).get_style(&#039;height&#039;));<br />
var pct = innerElemHeight / outerElemHeight;</p>
<p>Hope this helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Converting to Pixels with javascript by joe</title>
		<link>http://blog.stchur.com/2006/09/20/converting-to-pixels-with-javascript/comment-page-1/#comment-128357</link>
		<dc:creator>joe</dc:creator>
		<pubDate>Fri, 16 Dec 2011 18:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://stchur.com/blog2/2006/09/20/converting-to-pixels-with-javascript/#comment-128357</guid>
		<description>great stuff!  Now... How do I convert from pixels to percent?  I have a div within a div, and I want to find the percent the inner div is of the outerdiv.  I tried (slice/pie)*100; and then set the innerdiv to that percent, but sometimes it&#039;s off by a pixel.</description>
		<content:encoded><![CDATA[<p>great stuff!  Now&#8230; How do I convert from pixels to percent?  I have a div within a div, and I want to find the percent the inner div is of the outerdiv.  I tried (slice/pie)*100; and then set the innerdiv to that percent, but sometimes it&#039;s off by a pixel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The javascript ternary operator by Jared - Saskatoon Web Design</title>
		<link>http://blog.stchur.com/2006/07/14/the-javascript-ternary-operator/comment-page-1/#comment-122342</link>
		<dc:creator>Jared - Saskatoon Web Design</dc:creator>
		<pubDate>Sun, 09 Oct 2011 22:57:20 +0000</pubDate>
		<guid isPermaLink="false">http://stchur.com/blog2/2006/07/14/the-javascript-ternary-operator/#comment-122342</guid>
		<description>Nice break down, easy read. Maybe something on multiple conditions would be nice too!</description>
		<content:encoded><![CDATA[<p>Nice break down, easy read. Maybe something on multiple conditions would be nice too!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing IE&#039;s .attachEvent(..) failures by wes</title>
		<link>http://blog.stchur.com/2006/10/12/fixing-ies-attachevent-failures/comment-page-1/#comment-122092</link>
		<dc:creator>wes</dc:creator>
		<pubDate>Thu, 06 Oct 2011 19:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://stchur.com/blog2/2006/10/12/fixing-ies-attachevent-failures/#comment-122092</guid>
		<description>don&#039;t use attachEvent!
use an array of events instead for older IEs, because
attachEvent(&quot;load&quot;, a); attachEvent(&quot;load&quot;, b);
first is executed b, then a
with addEventListener first is executed a then b</description>
		<content:encoded><![CDATA[<p>don&#039;t use attachEvent!<br />
use an array of events instead for older IEs, because<br />
attachEvent(&#034;load&#034;, a); attachEvent(&#034;load&#034;, b);<br />
first is executed b, then a<br />
with addEventListener first is executed a then b</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Programmatically clicking a link in Javascript by Tarik</title>
		<link>http://blog.stchur.com/2010/01/15/programmatically-clicking-a-link-in-javascript/comment-page-1/#comment-121964</link>
		<dc:creator>Tarik</dc:creator>
		<pubDate>Wed, 05 Oct 2011 12:59:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stchur.com/?p=129#comment-121964</guid>
		<description>Cheers dude works like a charm</description>
		<content:encoded><![CDATA[<p>Cheers dude works like a charm</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on IE Bug dealing with CSS custom cusors by Custom Cursor with click animation + crossbrowser support &#124; Nuclear&#039;s Blog</title>
		<link>http://blog.stchur.com/2006/11/02/ie-bug-dealing-with-css-custom-cusors/comment-page-1/#comment-121924</link>
		<dc:creator>Custom Cursor with click animation + crossbrowser support &#124; Nuclear&#039;s Blog</dc:creator>
		<pubDate>Tue, 04 Oct 2011 23:30:47 +0000</pubDate>
		<guid isPermaLink="false">http://stchur.com/blog2/2006/11/02/ie-bug-dealing-with-css-custom-cusors/#comment-121924</guid>
		<description>[...] AGAIN, here comes shitload of problems again: 1) locating .cur files for CSS cursor is so buggy and retarded, this bug exists I think in all IE versions (atleast IE6-9 it does). I didn&#8217;t want to waste [...]</description>
		<content:encoded><![CDATA[<p>[...] AGAIN, here comes shitload of problems again: 1) locating .cur files for CSS cursor is so buggy and retarded, this bug exists I think in all IE versions (atleast IE6-9 it does). I didn&#039;t want to waste [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

