Comments on: 5 things you might not know about CSS sprites

By: click here

click here — Thu, 17 May 2012 22:51:59 +0000

Method worth checking….

[...]Just found it. It’s very new approach. I think you will be interested. This blog is full of innovative ideas.[...]…

By: sign in

Quality resource….

[...]A lot of useful information on the topic[...]…

By: http://www.piscineautoportante.net/

http://www.piscineautoportante.net/ — Thu, 17 May 2012 05:46:23 +0000

Looking around…

I love to surf in various places on the web, regularly I will just go to Stumble Upon and read and check stuff out…

By: Buy Facebook Fans

Buy Facebook Fans — Sat, 31 Dec 2011 05:25:53 +0000

Check This Out…

[...]Here are some of the sites we recommend for our visitors[...]…

By: Tim

Tim — Wed, 21 Dec 2011 12:50:00 +0000

Great article, can you also take a look at a utility I wrote? https://chrome.google.com/webstore/detail/dmnphgbpmlpkhpbhfeckpcbebpjflnne

By: Everything You Need To Know About CSS Sprites | Free themes download, wordpress themes, blogger themes

Sun, 12 Dec 2010 09:24:20 +0000

[...] 5 things you might not know about CSS sprites [...]

By: Riccardo

Riccardo — Thu, 05 Aug 2010 14:04:00 +0000

I have tried to replace the “BAD” transparent.gif technique, unsuccesfully. The background image doesn't appear at all. Tested on chrome and FF… what am I missing? I'd love to suppress those extra HTTP requests to transparent.gif….

By: 5 things you might not know about CSS sprites – Tom Altman’s Wedia Conversation | Tom Altman's WebDev Conversation

Tue, 11 May 2010 03:31:49 +0000

[...] 5 things you might not know about CSS sprites [...]

By: originalgeek

originalgeek — Thu, 03 Dec 2009 08:21:27 +0000

One benefit is that there are fewer HTTP requests needed to fetch the image. Each HTTP request fires cookies up to the web server, which is chewing up the slow side of the user's bandwidth. Bandwidth issues aside, sprites don't suffer from rollover lag because all states of the button are already loaded.

By: Armitage

Armitage — Wed, 02 Dec 2009 15:08:59 +0000

I understand the reasoning behind the semantic markup and using a background and hiding your html text. But, I don't see how having a single image for several elements is useful. Why spend the effort to postion the map for each element. Is it simply to lower the number of http GET's? Why not slice them up? Can someone explain that?