also it looks like my example didnt make it into the previous post…
here is a link to a text file you can view

the document.write solution is not a great idea because it keeps your xhtml from validating…this php php you have to do per browser but i have included all the major browsers in the example. this code works great in an include. for an example you can take a look at my site

once you have that in place create a very simple css file named opacity.css with your opacity css in it

I get this error message:

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).

I put this code up in the head of the doc:
hmm my code isnt showing up

document.write('');


Anyways, it is just what you have up there.. pasted before the end head tag
Any ideas about why this doesn’t work?

As for IE6/IE7, conditional comments and different style sheets takes care of them.

Creating according to standards is merely done to illustrate that you a) have the skills required b) care about your audience c) and most likely are a perfectionist…

Why people constantly seams to get upset because someone provides insight and/or solutions to validating issues is beyond me. Shouldn’t you rather be focussing on all those giant internet portals that doesn’t give a s***!

“Failed validation, 30 Errors”

what about the #1 internet portal?

“Failed validation, 34 Errors”

and yet everybody and their grandma uses these two services every day without issue. yet another proof that markup validation is big brother politics that most people just don’t bother with.

Try adding “background: white;” to your CSS/style rules. I had the same issue with the drop-shadow rendered completely black, but this provided at least a workable result. I don’t have the eyes to say whether it’s a perfect solution .. but you might like (or at least be able to live) with the result.

I understand your frustration, but there’s little we can do about it. It’s just Microsoft.

While not having tested this myself there might be a workaround to the IE7 opacity issue available.