[Webkit-unassigned] [Bug 22457] Webpages without bgcolor definition are rendered transparent by default when transparency is activated

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Dec 8 09:19:56 PST 2008


------- Comment #7 from bwebe at dolby.com  2008-12-08 09:19 PDT -------
More detailed description of the problem:
During object initialization the background color value is reset to 0, to have
an initialized value there. Now, if the webpage does not have a background
color defined this value is never changed it stays at all 0 (0x00000000). In
case of 32bit ARGB that means that all alpha bits are set to 0 and therefore
the color is fully transparent. The system, however, recognizes that the color
is not valid, since it has never really been set, except during initialization.
If the system does no transparency it will fall back to the default background
color defined in FrameView.cpp in this check. For the transparency case,
however, it will not fall back to default since it will always find the alpha
value to be smaller than 0xFF, see above, initialization with 0.
I think this is wrong since the background color should either be defined as a
specific color or always fall back to a default color. That default color may
of course be transparent but this is not necessarily right in any case. The
programmer of an application should be able to decide what the behavior should
be, by defining the default background color. Right now he does have no choice
since it will always be set to transparent if no background color is defined in
the webpage.
As for the tests. I'm sorry but I don't have the time right now to look into
this. I'll attach an HTML file that should trigger the problem. 
Just wanted to make you guys aware of the issue here since we ran into it.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list