Cross-BrowserVariableOpacitywithPNG _ experience exchange

Cross-BrowserVariableOpacitywithPNG Periodically, someone tells me about the magic of PNG, how it's the ideal image format for the web, and that someday we'll all be using it on our sites instead of GIF. people have been saying this for years, and by now most of us have stopped listening. sadly, flaky browser support has made PNG impractical for almost everything; but now, with a few simple workarounds, we can finally put one of its most compelling features to use.

PNG? What?

The Portable Network Graphics, or PNG (pronounced "ping"), image format has been around since 1995, having cropped up during the now long-forgotten GIF scare, when Compuserve and Unisys announced they wocould begin charging royalties for the use of the GIF image format.

To provide GIF support in their applications, software makers like Adobe and Macromedia must pay royalty fees-fees which are passed down to the end user in the selling cost of the software.

When PNG appeared on the scene, web designers were ready to make the switch to the free, superior format and shun GIF forever. but over time, browsers continually failed to support PNG, and eventually most people started to forget about it. today, nearly everyone still uses GIF habitually.

Which is a shame, because PNG makes GIF look pretty pathetic: it supports gamma correction, (sometimes) smaller file sizes, loss-less compression, up to 48-bit color, and, best of all, true alpha transparency.

To get why alpha transparency is a big deal, we must first understand one of the most annoying limitations of GIF.

Binary Transparency: the Scourge of GIF

When it comes to transparency, GIF doesn't cut it. Whereas PNG supports alpha transparency, GIF only supports binary transparency, which is a big limitation and has a couple of important implications.

For one, a GIF image can either use no transparent colors at all or have one color that's completely transparent-there are no degrees of transparency.

And if a complex GIF does contain a transparent color, the background color of the web page must match the transparent color, or else the anti-aliased area around the transparent color will be surrounded by uugly haloing and fringing. if you 've spent more than five minutes as a web designer, you know what I'm talking about.

The result is that any anti-aliased transparent GIF is inextricably tied to the background color of the web page on which it lives. if you ever decide to change that color, you must also change the GIF.

Miraculously, PNG doesn't behave that way. a png can be transparent in varying degrees-in other words, it can be of variable opacity. and a transparent PNG is background-independent: it can live on any background color or image. say you want your navigation on monkeys-run-amuck.com to be 65% opaque so you can see through it to your orangutan background image. you can do that. A transparent anti- Liased "Gorillas, Chimps, Gibbons, et al" title that can sit on top of any background color or image? You can do that, too.

So What About Browser Support?

By now, of course, we 'd all be up to our ears in PNGs if browsers supported them reliably. but seven years after the format's inception, you still can't slap a PNG onto a web page like you can a GIF or JPG. it's disgraceful, but not as bad as it sounds.

It turns out that most of the latest versions of the major browsers fully support alpha transparency with PNG-namely, Netscape 6, Opera 6, and recently-released Mozilla 1, all on Windows; and, for the Mac, Internet Explorer 5, Netscape 6, Opera 5, Mozilla 1, OmniWeb 3.1, and ICab 1.9. incredibly, PNG even works on Opera 6 for Linux, on WebTV, and on Sega Dreamcast.

Now, what's missing from that list?

IE5.5 +/Win, bless its heart, will, in fact, display a PNG, but it doesn' t natively support alpha transparency. in IE5.5 +/Win, the transparent area of your PNG will display at 100% opacity-that is,It won't be transparent at all.

Bugger. So what do we do now?

Proprietary Code-o-Rama: AlphaImageLoaderFilter

IE4 +/Win supports a variety of non-standard, largely ridiculous visual filters that you can apply to any image's style. you can, for instance, fade in an image with a gradient wipe, or make it stretch from nothing to full size, or even make it swipe into place circularly, like a scene change in Star Wars.

A non-pointless gem among these isAlphaImageLoaderFilter, which is supported in IE5.5 +/Win. When used to display a PNG, it allows for full alpha transparency support. All you have to do is this:

»(src='myimage.png',sizingMethod='scale');">

(Line wraps are marked».-Ed.)

And you're in business. perfect alpha transparency. this code works great, with only the small drawback that it's not part of any accepted web standard, and no other browser on the planet understands it.

Serving up PNGs with JavaScript

So the trick is to determine the user's browser and serve up the images appropriately: if IE5.5 +/Win, then we useAlphaImageLoader; If a browser with native PNG support, then we display PNGs the normal way; if anything else, then we display alternate GIFs, because we can't be sure that a PNG will display correctly or at all.

Using a slightly tweaked version of Chris Nott's Browser Detect Lite, we set some global variables to this effect that we can use later on.

// if IE5.5+ on Win32, then display PNGs with AlphaImageLoaderif ((browser.isIE55 || browser.isIE6up) && browser.isWin32) {var pngAlpha = true;// else, if the browser can display PNGs normally, then do that} else if ((browser.isGecko) |»| (browser.isIE5up && browser.isMac) |»| (browser.isOpera && browser.isWin »&& browser.versionMajor >= 6) |»| (browser.isOpera && browser.isUnix »&& browser.versionMajor >= 6) |»| (browser.isOpera && browser.isMac »&& browser.versionMajor >= 5) |»| (browser.isOmniweb && »browser.versionMinor >= 3.1) |»| (browser.isIcab && »browser.versionMinor >= 1.9) |»| (browser.isWebtv) |»| (browser.isDreamcast)) {var pngNormal = true;}

(Note for the faint of heart: complete source code for all the examples we cover is available at the end of the article .)

Tactic 1: Quick and Dirty with document. writes

The simplest, most reliable way to spit out PNGs is using inline document. writes based on the above detection. So we use a function like this:

function od_displayImage(strId, strPath, intWidth, »intHeight, strClass, strAlt) { if (pngAlpha) { document.write('
»id="'+strId+'" class="'+strClass+'">
');} else if (pngNormal) { document.write('»width="'+intWidth+'"» height="'+intHeight+'" name="'+strId+'" »border="0" class="'+strClass+'" alt="'+strAlt+'" />');} else { document.write('»width="'+intWidth+'"» height="'+intHeight+'" name="'+strId+'" »border="0" class="'+strClass+'" alt="'+strAlt+'" />');}}

Now we can call the od_displayImage function from anywhere on the page. Any JavaScript-capable browser will display an image, and, if we want to be really careful, we can accompany each call with Tag that contains a regular Reference. So the respectable browsers get PNGs normally, IE5.5 +/Win gets them with the filter, and all other browsers get regular GIFs, whether they have JavaScript turned on or not.

It's a time-tested method, but what if we want more control over our PNGs?

Tactic 2: the Beauty & Majesty of Objects

When I told the programmer in the office next door that I was writing this article, he took one look at my code, glowered at me, and said, "Fool. where's the specific action? You need to use objects ."

So now we have a JavaScript object to display PNGs. Here's how we use it: