Closed Bug 310761 Opened 14 years ago Closed 14 years ago

hovering over stop button turns it into print button

Categories

(Core Graveyard :: GFX, defect, major)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ajschult784, Assigned: roc)

References

Details

(Keywords: regression)

Attachments

(1 file)

718 bytes, application/vnd.mozilla.xul+xml
Details
With classic theme and gtk2 (native theming), if I set the pref to "Show
toolbars as Pictures and text", the stop button turns into the print button and
the reload and forward buttons both turn into the back button if I hover over
them.  The stop button also changes to the print button when a page stops
loading.  Clicking on the page or focusing another window reverts all the
buttons back to what they should be.

This regressed between linux trunk 2005032002 and 2005033107.  I'm trying to
narrow that range down.
I tried pulling CVS by date, but even a Mar 10, 2005 build exhibits this bug, so
the regression range is probably bogus.  But I didn't see any changes to
buildconfig between the two builds.
Actually, this is from bug 173051.
In addition to the pictures-only pref, I also apparently need to set my screen
resolution to see this bug.  So:

user_pref("browser.chrome.toolbar_style", 0);
user_pref("browser.display.screen_resolution", 102);
Assignee: guifeatures → roc
Component: XP Apps: GUI Features → GFX
Product: Mozilla Application Suite → Core
QA Contact: ian
Depends on: 173051
This is Seamonkey only, right? Or can you create a standalone XUL file that
shows the problem?
I've only seen this in SeaMokey, but I wouldn't doubt that for some DPI setting,
it would also show up somewhere in FF/TB.  I've been meaning to make an XUL
testcase, but having been busy tracking down other regressions.
Attached file xul testcase
firefoxified testcase.

exhibits the bug in trunk firefox and seamonkey -- hover over the firefoxy
button to change it.  The displayed image switches to the area specified for
the second button.
Andrew, are you still seeing this?
this got fixed between 2006-01-23 and 2006-01-26, meaning bug 317375
Status: NEW → RESOLVED
Closed: 14 years ago
Depends on: 317375
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.