This thread points out a possible problem with Safari 2.0 that I had originally thought might just be a matter of convenience for some 'obscure browser to be named later'.
It seems, at least for the OP, and their experience is backed up somewhat by information I found on the web, that -khtml-opacity isn't how Safari 2.0 does opacity but rather just generic opacity.
The script I modded up for the OP in that thread solves this problem by abandoning both -moz-opacity and -khtml-opacity in favor of, you guessed it, opacity - with a twist.
When I was putting this script through its paces when DD first upgraded it, I discovered that certain older IE versions will try to go down the plain opacity route when they cannot, unless it is also tested for like so:
as shown in my modified code in that thread.Code:if (obj.opacity && !obj.filters)
An even better solution might be to provide the generic opacity option followed by both the -moz-opacity and -khtml-opacity options but, with modern Mozilla liking generic opacity as well, I saw little point in doing so.



Reply With Quote

Bookmarks