Closed
Bug 1150701
Opened 10 years ago
Closed 10 years ago
Menus and Context Menus Mostly all Appear to be broken and Not Rendering Correctly vs Hardware Acceleration
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1150376
People
(Reporter: strifeshadow, Unassigned)
Details
(Keywords: regression, Whiteboard: gfx-noted)
User Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150330154247
Steps to reproduce:
Updated from Firefox 37 beta channel to 38 beta channel with hardware acceleartion enabled.
This also happened on my Thunderbird update to Thunderbird 38 beta as well. It may strongly seem, that they share the same bug in common, for v38 in each application.
Actual results:
Most all Menu items [File, Edit, View, History] in menu bar appear broken, missing rendering of menu items, and/or some kind of overlap/layering corruption.
Context Menus of most/any kind also exhibit this same bugged behavior.
This has been long working for my configuration, drivers, and hardware since before Firefox 38 beta, for many months, years now.
I worked around this by navigating around half blind on menus to end up at:
Tools => Options => Advanced => General
[UnChecked] Use hardware acceleration when available
Expected results:
Menu items [File, Edit, View, History] in menu bar should have rendered fairly, visibly and intact under hardware acceleration for my configuration, drivers, hardware.
Context Menus also should have rendered fairly, visibly, and intact.
Updated•10 years ago
|
Severity: normal → major
status-firefox37:
--- → unaffected
status-firefox38:
--- → affected
Component: Untriaged → Graphics
Keywords: regression,
regressionwindow-wanted
Product: Firefox → Core
Updated•10 years ago
|
Whiteboard: gfx-noted
Comment 1•10 years ago
|
||
Any chance of running mozregression to find out when this broke?
Flags: needinfo?(strifeshadow)
Just like the OP I am facing the same issue running Firefox 38 beta on Vista 32bit. Not sure if OP could confirm this but I have run mozregression (quite nice tool btw) and turns out that probably fix for bug 1147728 is causing this misbehaviour.
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=92aeec7102fe&tochange=96c8ca415e45
Updated•10 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
status-firefox37:
unaffected → ---
status-firefox38:
affected → ---
Flags: needinfo?(strifeshadow)
Keywords: regressionwindow-wanted
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•