<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>K-Squared Ramblings &#187; JavaScript</title>
	<atom:link href="http://www.hyperborea.org/journal/tag/javascript/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hyperborea.org/journal</link>
	<description>Sci-fi, comics, humor, photos...it&#039;s all fair game.</description>
	<lastBuildDate>Sat, 04 Feb 2012 06:27:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Fixing broken sites in the browser</title>
		<link>http://www.hyperborea.org/journal/2005/06/fixing-broken-sites-in-the-browser/</link>
		<comments>http://www.hyperborea.org/journal/2005/06/fixing-broken-sites-in-the-browser/#comments</comments>
		<pubDate>Thu, 16 Jun 2005 16:47:49 +0000</pubDate>
		<dc:creator>Kelson</dc:creator>
				<category><![CDATA[Opera]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[greasemonkey]]></category>
		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2005/06/16/fixing-broken-sites-in-the-browser/</guid>
		<description><![CDATA[The new Opera 8.0.1 includes an experimental feature called Browser JavaScript. It&#8217;s a collection of client-side scripts that automatically corrects known errors on websites as they&#8217;re displayed. Opera downloads updated scripts once a week. It&#8217;s an extension of the User &#8230; <a href="http://www.hyperborea.org/journal/2005/06/fixing-broken-sites-in-the-browser/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The new Opera 8.0.1 includes an experimental feature called <a href="http://www.opera.com/docs/browserjs/">Browser JavaScript</a>.  It&#8217;s a collection of client-side scripts that automatically corrects known errors on websites as they&#8217;re displayed.  Opera downloads updated scripts once a week.</p>
<p>It&#8217;s an extension of the User JavaScript concept.  Firefox&#8217;s Greasemonkey is basically the same thing, and it&#8217;s gotten a lot of attention as a method for correcting or enhancing sites.  The key difference is that these scripts are centrally maintained, and automatically updated.</p>
<p>Browser JavaScript is disabled by default, and can be turned on by putting <code>Browser JavaScript=1</code> in the <code>[User Prefs]</code> section of your <a href="http://www.opera.com/support/usingopera/operaini/">opera6.ini</a> file.</p>
<p>(<a href="http://operawatch.com/news/2005/06/opera-801-final-released.html">via Opera Watch</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hyperborea.org/journal/2005/06/fixing-broken-sites-in-the-browser/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Focus!</title>
		<link>http://www.hyperborea.org/journal/2004/05/focus/</link>
		<comments>http://www.hyperborea.org/journal/2004/05/focus/#comments</comments>
		<pubDate>Thu, 20 May 2004 20:03:23 +0000</pubDate>
		<dc:creator>Kelson</dc:creator>
				<category><![CDATA[Annoyances]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2004/05/20/focus/</guid>
		<description><![CDATA[While working on a website for work, I inadvertently discovered why a web application I use frequently has the annoying habit of moving the cursor to the username field when I&#8217;m halfway through typing the password. The basic way to &#8230; <a href="http://www.hyperborea.org/journal/2004/05/focus/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>While working on a website for work, I inadvertently discovered why a web application I use frequently has the annoying habit of moving the cursor to the username field when I&#8217;m halfway through typing the password.</p>
<p>The basic way to set initial focus on a form field is to use JavaScript like this: </p>
<p><code>document.loginForm.usernameField.focus();</code></p>
<p>You can either embed it in the HTML after the form, or call it in the page&#8217;s <code>onload()</code> function.  The problem with using <code>onload</code> is that it fires when <em>everything</em> is loaded, which means it waits for images, plugins, and so on.  That&#8217;s very useful for some tasks, but isn&#8217;t the best choice here.</p>
<p>I&#8217;m impatient, especially with login forms.  I don&#8217;t need the logos and background, I want to type in my username and password as quickly as possible and start using the app.  Since this particular site isn&#8217;t exactly the fastest around, invariably the images don&#8217;t finish loading until I&#8217;ve started typing the password &#8212; and suddenly I&#8217;m typing the second half of the password in the username box.</p>
<p>Needless to say, I&#8217;m using the inline method on the site I&#8217;m building.  Not that the login page has any images right now, but if I add any later on, it&#8217;ll save the users some aggravation.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hyperborea.org/journal/2004/05/focus/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

