GTK2 build of Mozilla should use gtk2 themed widgets embedded in webpages



Core Graveyard
GFX: Gtk
14 years ago
4 years ago


(Reporter: Laurens Buhler, Assigned: romaxa)


Bug Flags:
blocking-aviary1.5 -

Firefox Tracking Flags

(Not tracked)




(1 attachment)



14 years ago
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20040113 Firebird/0.7

If we look at in Mozilla under Linux it has these "tk" style
search buttons. On Mozilla in Windows these buttons are drawn after the present
theme in use, this should also be the case for gtk2 builds.

Given that someone uses a gtk2 build these buttons aswell as the dropdown menus
and possibly other widgets (perhaps the radio buttons?) should also use gtk2 for
a consistent look/feel.

Reproducible: Always
Steps to Reproduce:
1. Every site with an embedded widget shows this

Actual Results:  
Widgets are drawn in a tk style

Expected Results:  
Draw these widgets using the gtk2 style presently in use by the system


14 years ago
Assignee: justdave → blizzard
Component: Bugzilla-General → GFX: Gtk
Product: Bugzilla → Browser
QA Contact: mattyt-bugzilla → ian
Version: unspecified → Trunk
bryner, do we have a bug for this yet?
Blocks: 92033

Comment 2

14 years ago
dup of bug 7246?

Comment 3

14 years ago
*** Bug 249658 has been marked as a duplicate of this bug. ***

Comment 4

14 years ago
What's the status on this one?

Iv'e heard that this is a WONTFIX since you need to implement CSS color
properties, and you can't do that with GTK2 widgets?

Would be a shame if we never got rid of the ugly "tk" buttons!

Comment 5

13 years ago
Flags: blocking-aviary1.1?

Comment 6

13 years ago
This is definitely a big draw back to have a nice desktop theme and firefox
using these ugly widgets.


13 years ago
Flags: blocking-aviary1.1? → blocking-aviary1.1-


13 years ago
Flags: blocking-aviary2.0?

Comment 7

13 years ago
*** Bug 301729 has been marked as a duplicate of this bug. ***

Comment 8

13 years ago
Any news on this? :(
I had a 30% patch for this that used GTK to render all the widgets, but didn't fix any of the rendering glitches that surfaced, and had problems with focus rectangles for all controls.

Unfortunately the patch got lost when my HDD died some weeks ago, and I haven't found the time to recode it.

For anyone interested in experimenting with this, I think you should start here:
<> (remove the check). Removing this check will lead to Gecko using GTK to render all widgets, and you'll have alot of problems with form widgets in general, but it's the first step.

Please stop posting useless comments.
This would require significant backend changes and isn't going to happen for Fx2
Flags: blocking-aviary2? → blocking-aviary2-

Comment 11

13 years ago
(In reply to comment #10)
> This would require significant backend changes and isn't going to happen for
> Fx2
How come the new firefox 1.5 error pages (such as "website could not be reached"), have a nice GTK2-rendered button "retry" right at the bottom of the message? What's the difference between that one and the "normal" forms in webpages? I would really like to know.

Comment 12

13 years ago
Jeff, I'm guessing that's because the page is layed out in XUL, and that's a XUL widget.

Comment 13

12 years ago
*** Bug 307427 has been marked as a duplicate of this bug. ***


12 years ago
Flags: blocking-firefox2-

Comment 14

12 years ago
If it's not easy to make mozilla use the gtk theme then perhaps at least the defaults could be changed to something else? Clearlooks perhaps? That would be a lot better than now.

Comment 16

12 years ago
Created attachment 247297 [details] [diff] [review]
Using preferences for enabling Native Gtk theme support

This patch will allow to set using Native Gtk Themes without engine rebuilding.


12 years ago
Assignee: blizzard → romaxa


11 years ago
Last Resolved: 11 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 329846
Product: Core → Core Graveyard


4 years ago
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.