new GTK widgets could look better

Bug #180962 reported by David Prieto
0
Affects Status Importance Assigned to Milestone
Mozilla Firefox
Invalid
Unknown
XULRunner
Fix Released
Unknown
xulrunner-1.9 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: epiphany-browser

In Hardy's latest epiphany versions, widgets have started looking like normal GTK widgets. However they have a weird white border and would look (even) better without it.

Revision history for this message
David Prieto (frandavid100-gmail) wrote :
Revision history for this message
David Prieto (frandavid100-gmail) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Likely a xulrunner-1.9 issue, reassigning

Changed in xulrunner:
status: Unknown → Confirmed
Changed in firefox:
status: Unknown → Confirmed
Revision history for this message
Conn O Griofa (psyke83) wrote :

Bruce,

It probably would have been better to mark this bug as a duplicate of mine: https://bugs.launchpad.net/bugs/195929

Please see my bug for a summary (and patches). The problem is complicated as

a) rendering of buttons can be (and have been) fixed in the theme engine's code (my bug has patches attached for gtk2-engines-murrine and gtk2-engines-ubuntulooks).
b) rendering of GtkEntry boxes cannot be fixed in GTK without "hacks", so cooperation is necessary from the Mozilla folks.

Please unmark my bug as a duplicate.

Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

Newer bugs are marked duplicates of older ones, not the other way round. Therefore, bug #195929 is a duplicate of this one.

Revision history for this message
Conn O Griofa (psyke83) wrote :

Bruce,

Yes, that is the general rule, except if a newer bug has made more progress or documented the issue more thoroughly. In my duplicate there is feedback from a GTK theme engine developer, and patches attached to fix half of the cases in this bug - they need to be seen more than this bare report.

For example, from Mozilla's duplicate process at http://www.mozilla.org/quality/help/screening-duplicates.html - "Other things being equal, newer bugs should be made DUPLICATES of older bugs, but, more importantly, whichever bug is further along in the process of getting fixed should not be made a duplicate."

Otherwise do I have to attach my patches and test cases here again, duplicating effort?

Changed in firefox:
status: Confirmed → Invalid
Changed in xulrunner:
status: Confirmed → In Progress
Changed in xulrunner:
status: In Progress → Confirmed
Changed in xulrunner:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.