Ticket #5393 (closed bug: fixed)
getColor reports inaccurate color for transparent elements in Webkit
|Reported by:||Rwhitbeck||Owned by:||gnarf|
I realize that getColor (from jquery.effects.core.js) is not an exposed function, but I did notice something odd about the logic which leads to it reporting incorrectly for transparent elements on Webkit. I copied getColor, getRGB and the 'colors' variable out into a simple example file with the latest jQuery and following contents:
- <div id="red" style="background-color:red;">
- <div id="trans">
- Some text.
And with the following call:
Webkit (Chrome) will alert 255,255,255 while Firefox will alert 255,0,0
This is because there are two places in the code that handle transparency. Firefox (and I assume IE) transparency is caught in the do/while loop in getColor while Webkit transparency falls through to getRGB and is caught with a regular expression, thus returning colorstransparent?, which happens to be white.
Shouldn't getColor also handle the Webkit transparency something like this:
|$.nodeName(elem, "body") )|
I saw mention of exposing getColor publicly and figured that this might be worth addressing before it's up for general use.
I've put together a working example of the issue and a copy of the getColor function with the logic moved so that it reports accurately for Webkit.