<?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"
	>
<channel>
	<title>Comments on: Four Recent WebDev&#160;Speedbumps</title>
	<atom:link href="http://particletree.com/notebook/four-recent-webdev-speedbumps/feed/" rel="self" type="application/rss+xml" />
	<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/</link>
	<description>Everyone needs a hug.</description>
	<pubDate>Tue, 06 Jan 2009 11:58:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Tyler McMullen</title>
		<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-6187</link>
		<dc:creator>Tyler McMullen</dc:creator>
		<pubDate>Thu, 21 Dec 2006 16:38:42 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-6187</guid>
		<description>&lt;p&gt;Regarding the AJAX comment... Yeah.. It doesn't even work on a different port of the same domain.  Big pain in my arse.  What I've taken to doing is just pointing it at a script on my domain, which loads and returns the content of the page/resource on another domain.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Regarding the AJAX comment&#8230; Yeah.. It doesn&#8217;t even work on a different port of the same domain.  Big pain in my arse.  What I&#8217;ve taken to doing is just pointing it at a script on my domain, which loads and returns the content of the page/resource on another domain.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Morgan Roderick</title>
		<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-5174</link>
		<dc:creator>Morgan Roderick</dc:creator>
		<pubDate>Thu, 14 Dec 2006 10:18:12 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-5174</guid>
		<description>&lt;p&gt;What i meant to say was:
&#60;button type="submit"&#62;Button&#60;/button&#62;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>What i meant to say was:
&lt;button type=&#8221;submit&#8221;&gt;Button&lt;/button&gt;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Morgan Roderick</title>
		<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-5173</link>
		<dc:creator>Morgan Roderick</dc:creator>
		<pubDate>Thu, 14 Dec 2006 10:16:44 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-5173</guid>
		<description>&lt;p&gt;if you're already doing all sorts of trickery with javascript when submitting forms, why not just go with GO, GADGET GO! ???&lt;/p&gt;

&lt;p&gt;It'll hold both images and text and can be styled in whatever way you desire. It's also easier to select with DOM methods, myForm.getElementsByTagName("button") ... instead of trying to figure out which one is the button returned in myForm.getElementsByTagName("input").&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>if you&#8217;re already doing all sorts of trickery with javascript when submitting forms, why not just go with GO, GADGET GO!&#160;???</p>

<p>It&#8217;ll hold both images and text and can be styled in whatever way you desire. It&#8217;s also easier to select with DOM methods, myForm.getElementsByTagName(&#8220;button&#8221;) &#8230; instead of trying to figure out which one is the button returned in myForm.getElementsByTagName(&#8220;input&#8221;).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: dd</title>
		<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-4854</link>
		<dc:creator>dd</dc:creator>
		<pubDate>Mon, 11 Dec 2006 19:26:40 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-4854</guid>
		<description>&lt;p&gt;Everyone needs a &lt;b&gt;hug&lt;/b&gt;.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Everyone needs a <b>hug</b>.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: 3stripe</title>
		<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-4761</link>
		<dc:creator>3stripe</dc:creator>
		<pubDate>Sun, 10 Dec 2006 15:24:53 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-4761</guid>
		<description>&lt;p&gt;You shouldn't really be naming your files with spaces in them, everyone knows that's bad practice... don't they?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You shouldn&#8217;t really be naming your files with spaces in them, everyone knows that&#8217;s bad practice&#8230; don&#8217;t they?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph</title>
		<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-4078</link>
		<dc:creator>Joseph</dc:creator>
		<pubDate>Fri, 01 Dec 2006 22:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-4078</guid>
		<description>&lt;p&gt;In regards to the input type switching bug:&lt;/p&gt;

&lt;p&gt;I usually just replace the element with a new input, created via the DOM.  I know it's inconvenient, but I still think it's better than using the display rule.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>In regards to the input type switching bug:</p>

<p>I usually just replace the element with a new input, created via the DOM.  I know it&#8217;s inconvenient, but I still think it&#8217;s better than using the display rule.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Povlot</title>
		<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-4051</link>
		<dc:creator>Scott Povlot</dc:creator>
		<pubDate>Fri, 01 Dec 2006 16:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-4051</guid>
		<description>&lt;p&gt;Regarding "Image inputs in a POST":&lt;/p&gt;

&lt;p&gt;These extra form variable are defined in the HTML standard.  (See http://www.w3.org/TR/html4/interact/forms.html#h-17.4)&lt;/p&gt;

&lt;p&gt;"When a pointing device is used to click on the image, the form is submitted and the click coordinates passed to the server. The x value is measured in pixels from the left of the image, and the y value in pixels from the top of the image. The submitted data includes name.x=x-value and name.y=y-value where "name" is the value of the name attribute, and x-value and y-value are the x and y coordinate values, respectively."&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Regarding &#8220;Image inputs in a POST&#8221;:</p>

<p>These extra form variable are defined in the HTML standard.  (See <a href="http://www.w3.org/TR/html4/interact/forms.html#h-17.4" rel="nofollow">http://www.w3.org/TR/html4/interact/forms.html#h-17.4</a>)</p>

<p>&#8220;When a pointing device is used to click on the image, the form is submitted and the click coordinates passed to the server. The x value is measured in pixels from the left of the image, and the y value in pixels from the top of the image. The submitted data includes name.x=x-value and name.y=y-value where &#8220;name&#8221; is the value of the name attribute, and x-value and y-value are the x and y coordinate values, respectively.&#8221;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Kant</title>
		<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-3989</link>
		<dc:creator>Andy Kant</dc:creator>
		<pubDate>Thu, 30 Nov 2006 22:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-3989</guid>
		<description>&lt;p&gt;Heh...By "by now," I just meant that you aren't a beginner and that would have been a beginner mistake. :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Heh&#8230;By &#8220;by now,&#8221; I just meant that you aren&#8217;t a beginner and that would have been a beginner mistake. :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-3983</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Thu, 30 Nov 2006 20:25:54 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-3983</guid>
		<description>&lt;p&gt;WRT "Image inputs in a POST": 
One thing that I have done in the past with the X and Y coordinates was to compile all of the coordinates each day for a certain amount of time and determine where the "hotspots" of the image(s) were. That greatly helped me push my A/B (C/D, etc... hehe) testing of different graphics to increase performance (whatever that meant for a specific page) of the page. Eventually the test would finally reach an equilibrium in performance.&lt;/p&gt;

&lt;p&gt;WRT "CSS background with a space": 
IMHO, the use of spaces, and to an extent capitalization, in any file that is used/viewed online is flirting with disaster. The space(s) issue has been noted already, but with capitalization you run the risk of yourself or others misspelling the name and causing 404's, missing images/*.js files, etc. In order to avoid this potential for error, I always try to stick with all lowercase letters and remove/replace spaces for filenames. It's not always possible (due to pre-existing client code, etc.), but if/when possible I make it happen.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>WRT &#8220;Image inputs in a POST&#8221;: 
One thing that I have done in the past with the X and Y coordinates was to compile all of the coordinates each day for a certain amount of time and determine where the &#8220;hotspots&#8221; of the image(s) were. That greatly helped me push my A/B (C/D, etc&#8230; hehe) testing of different graphics to increase performance (whatever that meant for a specific page) of the page. Eventually the test would finally reach an equilibrium in performance.</p>

<p>WRT &#8220;CSS background with a space&#8221;: 
IMHO, the use of spaces, and to an extent capitalization, in any file that is used/viewed online is flirting with disaster. The space(s) issue has been noted already, but with capitalization you run the risk of yourself or others misspelling the name and causing 404&#8217;s, missing images/*.js files, etc. In order to avoid this potential for error, I always try to stick with all lowercase letters and remove/replace spaces for filenames. It&#8217;s not always possible (due to pre-existing client code, etc.), but if/when possible I make it happen.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Hopkinson</title>
		<link>http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-3973</link>
		<dc:creator>Adam Hopkinson</dc:creator>
		<pubDate>Thu, 30 Nov 2006 17:58:10 +0000</pubDate>
		<guid isPermaLink="false">http://particletree.com/notebook/four-recent-webdev-speedbumps/#comment-3973</guid>
		<description>&lt;p&gt;I may be stating the obvious, but the _x and _y post vars submitted when clicking an input type of 'image' represent the coordinates on the image where the click occurred. Possibly usable for server side image maps, but as far as i can think there are easier ways of doing pretty much anything you could use this for.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I may be stating the obvious, but the _x and _y post vars submitted when clicking an input type of &#8216;image&#8217; represent the coordinates on the image where the click occurred. Possibly usable for server side image maps, but as far as i can think there are easier ways of doing pretty much anything you could use this for.</p>]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.891 seconds -->
