Closed
Bug 632767
Opened 13 years ago
Closed 13 years ago
Clicking a link in the 'About' dialogue creates a window with misaligned chrome
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 625367
People
(Reporter: laurencedurant1, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
531.06 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b12pre) Gecko/20110208 Firefox/4.0b12pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b12pre) Gecko/20110208 Firefox/4.0b12pre In help - about, clicking a link creates a window where the browser chrome (tabs, tab buttons) is a little higher than usual and if the window is maximised, the tabs extend beyond the window bounds. Reproducible: Always Steps to Reproduce: 1. Maximize window 2. Open help -> about 3. Click any link
Mozilla/5.0 (Windows NT 6.1; rv:2.0b12pre) Gecko/20110208 Firefox/4.0b12pre Confirmed. The size of the tabs and tab buttons are increased and the menu button and tabs extend beyond the window.
Updated•13 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Trunk
Comment 4•13 years ago
|
||
Regression window: Works: http://hg.mozilla.org/mozilla-central/rev/5634bfc97402 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9pre) Gecko/20110107 Firefox/4.0b9pre ID:20110107120511 Fails: http://hg.mozilla.org/mozilla-central/rev/019ae3c92eb4 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9pre) Gecko/20110107 Firefox/4.0b9pre ID:20110107123840 Pushlog http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5634bfc97402&tochange=019ae3c92eb4 Candidate: 019ae3c92eb4 Dão Gottwald — Bug 572160 - Put tabs in the title bar when the window is maximized. r=gavin ui-r=faaborg a=b This causes landing of Bug 572160.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•13 years ago
|
blocking2.0: ? → ---
It's like a merry go round! Hehe. That's OK though, the other bug was a better one. Alice, I'd guess it would be helpful for you to repost your findings in the other bug. Also, this is completely unrelated to this bug, but I've been trying to find out where best to bring this up, it's GFx/hardware acceleration related and I don't know if it's right for Bugzilla. My laptop is quite new, has a relatively decent graphics card and had no problems at all running Fx 4's hardware acceleration features during the time I was using the nightlies. A few weeks ago though it seems my driver was blacklisted. I updated to the newest drivers I could and the results were the same. I force enabled layers acceleration and Direct2D in about:config and it's still running as before. I'm just wondering how widespread this might be and what I should do about it. I can imagine there's going to be plenty of other people with a similar GFx hardware profile to me who will also be affected.
blocking2.0: --- → ?
Comment 7•13 years ago
|
||
Lozzy there is no need to set the blocking request on this bug. The bug it is marked a duplicate of already has the blocking status.
blocking2.0: ? → ---
Ah, my apologies. I believe I may have left the page open after it was changed and it saved over. Regardless, I didn't change it intentionally.
You need to log in
before you can comment on or make changes to this bug.
Description
•