Michael, yes this does help. However it does *not* help at least in the GtkEntry case.
However, please read comment #18 (which references bug #415494) carefully. Mozilla itself is filling the whole are with a base[NORMAL] background. Which means that there is no way of having transparency.
(It is correct that doing this is much closer to what GTK+ does.)
So basically you have two choices:
1. Ignore bug #415494 and do not fill in the background. Then a good way to figure this out from the engine. (The MozillaGtkWidget may be enough.)
2. Add a style property (or similar) that will cause both Mozilla *and* the engine/theme not to fill in the background.
In the end, neither Mozilla nor the theme/engine is allowed to fill the background.
A style property can easily be checked in both the engines and mozillas drawing code. (Will need a change in many themes, but it is one line, and does not harm if a hack like this is not needed anymore.)
Michael, yes this does help. However it does *not* help at least in the GtkEntry case.
However, please read comment #18 (which references bug #415494) carefully. Mozilla itself is filling the whole are with a base[NORMAL] background. Which means that there is no way of having transparency.
(It is correct that doing this is much closer to what GTK+ does.)
So basically you have two choices:
1. Ignore bug #415494 and do not fill in the background. Then a good way to figure this out from the engine. (The MozillaGtkWidget may be enough.)
2. Add a style property (or similar) that will cause both Mozilla *and* the engine/theme not to fill in the background.
In the end, neither Mozilla nor the theme/engine is allowed to fill the background.
A style property can easily be checked in both the engines and mozillas drawing code. (Will need a change in many themes, but it is one line, and does not harm if a hack like this is not needed anymore.)