Closed
Bug 424367
Opened 17 years ago
Closed 14 years ago
Focused checkbox is invisible
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: sjakub, Unassigned)
References
()
Details
(Whiteboard: [CLOSEME 2010-07-30])
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5pre) Gecko/2008032104 Minefield/3.0b5pre
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5pre) Gecko/2008032104 Minefield/3.0b5pre
This happens on 64bit Linux. Whenever I click any checkbox on a page, no matter if it is checked or not, it disappears (screenshot included). If I use tab, and focus changes to another checkbox, the one that looses focus appears again, and the next one disappears. If I click anywhere on the page making the checkbox focused loose the focus, it appears.
Reproducible: Always
Steps to Reproduce:
1. Click on any checkbox on the webpage
Actual Results:
Clicked checkbox disappeared
I used this build: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-3.0b5pre.en-US.linux-x86_64.tar.bz2 and it has a problem.
It was present in previous few betas as well, but those I compiled myself, and I wasn't sure if it was not because wrong compilation options.
I use Archlinux, gtk-2.12.9, cairo-1.4.14 (but I guess Firefox3 uses its own version)
I confirm the same problem on linux, with the betas 3,4 and 5 of firefox, but with a 32bit version.
I use gtk-2.12.1-2 and gtk-qt-engine-0.8.3
Comment 2•17 years ago
|
||
I'm having the same problem on my two Ubuntu Hardy Desktops (32 Bit). It happens with all Firefox betas I have tried until now.
Reporter | ||
Comment 3•17 years ago
|
||
I have gtk-2.12.9 and gtk-qt-engine 0.8.
It seems the problem is related to 'Qt' theme selected for gtk-qt-engine.
When, in 'GTK styles and fonts' section of KDE Control Center, I select either 'use my KDE Style in GTK applications' (for KDE I use Plastik), or 'Use another style' and select 'Qt', this bug occurs.
When I change the 'another style' to somethign else - the bug is gone. I now use 'Clearlooks' style and it's ok.
I also tried Gimp, and it doesn't have this problem, no matter which style I use.
Comment 4•17 years ago
|
||
I can confirm seeing this with Kubuntu 8.04 (32 bit) and Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008051202 Firefox/3.0.
I can also confirm that the fix/workaround of System Settings -> Appearance -> GTK Styles and Fonts -> (*) Use another style: Clearlooks has fixed the issue for me.
Comment 5•17 years ago
|
||
Confirm this with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008052904 Minefield/3.0pre and gtk-qt-engine_0.8-2 (Debian "lenny").
This bug is both Firefox and gtk-qt-engine.
Firefox just uses gtk_paint_focus() is a way that gtk-qt-engine doesn't expect.
gtk-qt-engine has following code:
=== cut ===
QColor bg(qApp->palette().active().background());
painter.fillRect(0,0,w,h,bg);
qApp->style().drawPrimitive(QStyle::PE_FocusRect, &painter, QRect(0,0,w,h), qApp->palette().active(), QStyle::Style_Default, QStyleOption(bg));
=== cut ===
This draws focus rect on the pixmap filled of bgcolor, and then this pixmap is drawn without any transparency ontop of checkmark using GDK gdk_draw_drawable().
I'm currently investigating how to make it honor transparency.
--
WBR, Andrew
Comment 6•17 years ago
|
||
Just fixed gtk-qt-engine. Will send patch to both gtk-qt-author and Debian maintainer.
--
WBR, Andrew
Comment 7•17 years ago
|
||
Here's the patch:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484882
Comment 8•14 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.x or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 3.0 Branch
Comment 9•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•