<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Image rollovers without JavaScript!</title>
	<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html</link>
	<description>The weblog for Summersault, LLC, a website development firm in Richmond, Indiana</description>
	<pubDate>Thu, 28 Aug 2008 18:12:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1.3</generator>

	<item>
		<title>by: slant</title>
		<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-4026</link>
		<pubDate>Thu, 07 Sep 2006 16:37:28 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-4026</guid>
					<description>Actually, option two seems very preferable.  If you go to seeunity.com - you'll see that the top nav uses the first method - but the first time you rollover - you'll get some funky experiences.  I am guessing that this second method will work better.</description>
		<content:encoded><![CDATA[	<p>Actually, option two seems very preferable.  If you go to seeunity.com - you&#8217;ll see that the top nav uses the first method - but the first time you rollover - you&#8217;ll get some funky experiences.  I am guessing that this second method will work better.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Evan Agee</title>
		<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-3254</link>
		<pubDate>Fri, 25 Aug 2006 15:50:08 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-3254</guid>
					<description>Yes, pre-loading is a good idea, just as it is with traditional Javascript-fueled rollovers.</description>
		<content:encoded><![CDATA[	<p>Yes, pre-loading is a good idea, just as it is with traditional Javascript-fueled rollovers.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Maria</title>
		<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-3253</link>
		<pubDate>Fri, 25 Aug 2006 15:47:45 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-3253</guid>
					<description>When you &lt;em&gt;preload&lt;/em&gt; the images it doesn't take as long... but thanks for the idea.  I like it a lot.</description>
		<content:encoded><![CDATA[	<p>When you <em>preload</em> the images it doesn&#8217;t take as long&#8230; but thanks for the idea.  I like it a lot.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ruud</title>
		<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-477</link>
		<pubDate>Thu, 08 Dec 2005 13:00:06 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-477</guid>
					<description>I used it in Netscape 8.0.4 and Firefox 1.0.7 but de red image doesn't stay when i clicked it, it returns to white with a border around the image.
On InternetExplorer 6 it works fine.
Is there a workaround for the other two browsers?</description>
		<content:encoded><![CDATA[	<p>I used it in Netscape 8.0.4 and Firefox 1.0.7 but de red image doesn&#8217;t stay when i clicked it, it returns to white with a border around the image.<br />
On InternetExplorer 6 it works fine.<br />
Is there a workaround for the other two browsers?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: nataz</title>
		<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-469</link>
		<pubDate>Thu, 01 Dec 2005 20:06:52 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-469</guid>
					<description>It works perfectly under Mac os X with Safari 2.0.2, IE 5.2.3, FireFox 1.0.6, Netscape 7.2, Shiira 0.9.5 and Opera 7.54 as well as under Windows XP pro with Netscape 7.2, FireFox 0.9.3 &amp;#38; 1.5, and IE 6.0.26.</description>
		<content:encoded><![CDATA[	<p>It works perfectly under Mac os X with Safari 2.0.2, IE 5.2.3, FireFox 1.0.6, Netscape 7.2, Shiira 0.9.5 and Opera 7.54 as well as under Windows XP pro with Netscape 7.2, FireFox 0.9.3 &amp; 1.5, and IE 6.0.26.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Nick Shaw</title>
		<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-15</link>
		<pubDate>Tue, 17 May 2005 08:43:44 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-15</guid>
					<description>I dont think Safari on the mac supports the background CSS.</description>
		<content:encoded><![CDATA[	<p>I dont think Safari on the mac supports the background CSS.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Evan Agee</title>
		<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-9</link>
		<pubDate>Mon, 25 Apr 2005 19:53:32 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-9</guid>
					<description>I've tested this code on Mozilla 1.0 and several versions of Netscape and IE and it seems to be fine. Please feel free to send me any browser/version information if you find a browser that this CSS doesn't work with.</description>
		<content:encoded><![CDATA[	<p>I&#8217;ve tested this code on Mozilla 1.0 and several versions of Netscape and IE and it seems to be fine. Please feel free to send me any browser/version information if you find a browser that this CSS doesn&#8217;t work with.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Martin</title>
		<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-7</link>
		<pubDate>Mon, 18 Apr 2005 23:50:12 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-7</guid>
					<description>I like the second option. but it does not seem to work in Gecko browsers...</description>
		<content:encoded><![CDATA[	<p>I like the second option. but it does not seem to work in Gecko browsers&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: csabi</title>
		<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-6</link>
		<pubDate>Mon, 11 Apr 2005 09:55:28 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-6</guid>
					<description>Using   background: url(&quot;x.gif&quot;)  is a very slow solution as you can see the menu from my homepage. Is a way to force the browser to cache the used images ?

 
</description>
		<content:encoded><![CDATA[	<p>Using   background: url(&#8221;x.gif&#8221;)  is a very slow solution as you can see the menu from my homepage. Is a way to force the browser to cache the used images ?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Evan Agee</title>
		<link>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-5</link>
		<pubDate>Tue, 29 Mar 2005 18:21:14 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/03/25/image-rollovers-without-javascript.html#comment-5</guid>
					<description>The first CSS rollover option is one that is basically the same in theory as using JavaScript. The second, as you stated, only uses one image, which is much easier to manage.

As far as a technical reason for why the second option is &quot;better&quot;, I believe the main reason is because you're only referencing one image file instead of two or more. Another technical issue fixed by using one master image instead of two or more is that there's no delay when you rollover using the 2nd option. With the first option the image isn't loaded until you move over the link, which can produce a delay on slower connections.</description>
		<content:encoded><![CDATA[	<p>The first CSS rollover option is one that is basically the same in theory as using JavaScript. The second, as you stated, only uses one image, which is much easier to manage.</p>
	<p>As far as a technical reason for why the second option is &#8220;better&#8221;, I believe the main reason is because you&#8217;re only referencing one image file instead of two or more. Another technical issue fixed by using one master image instead of two or more is that there&#8217;s no delay when you rollover using the 2nd option. With the first option the image isn&#8217;t loaded until you move over the link, which can produce a delay on slower connections.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
