Closed Bug 716459 Opened 14 years ago Closed 13 years ago

Wrong window title bar rendering in Firefox 9.0.1, missing Minimize, Maximize, Close buttons

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
9 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 656891

People

(Reporter: roger, Unassigned)

References

Details

(Whiteboard: [Reopened])

Attachments

(5 files)

X.gif
46.40 KB, image/gif
Details
Same display without the problem
67.06 KB, image/gif
Details
about:support Graphics
18.47 KB, image/gif
Details
Again-after restarting from Hibernate
134.45 KB, image/gif
Details
Full-sceen version of this problem
62.57 KB, image/gif
Details
Attached image X.gif —
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Build ID: 20111220165912 Steps to reproduce: V9.0.1 - when the Menu bar is NOT being displayed, the Window Title line (with the minimize, maximize, and Close (X) buttons) is also NOT displayed. It MAY be tied to have many tabs opened... See attached screen capture.
I closed Firefox, and re-started it - the problem has disappeared!
Can you attach a screenshot where the problem is not existent?
Attached is the screen shot you requested
Now I see what you mean, thanks. Could be some problem with the theme or with HW acceleration. Please post contents of Graphics section of about:support. Were you just upgrading Firefox? Or did this happen while normally browsing with a Firefox version that didn't have this problem in the past. Please comment if you see the problem again.
Whiteboard: [CLOSEME 2012-02-01]
Fixed the summary to not confuse this bug with bug 701280.
Summary: Missing Title in V9.0.1 → Wrong window title bar rendering in Firefox 9.0.1, missing Minimize, Maximize, Close buttons
Attached image about:support Graphics —
Attached is the Graphics info you requested
(In reply to :aceman from comment #5) > Now I see what you mean, thanks. > Could be some problem with the theme or with HW acceleration. Please post > contents of Graphics section of about:support. > > Were you just upgrading Firefox? Or did this happen while normally browsing > with a Firefox version that didn't have this problem in the past. > > Please comment if you see the problem again. I had just upgraded to V9.0.1 a few hours before (at 01/08/2012 7:08 PM EST to be exact). I reported the problem right after noticing it (since I couldn't close Firefox!)
Restarted somputer form Hibernate state... noticed the problem w/ Firefox titile bar had reappeared.
I went to full screen for the problem, got this display.
Does it happen after each hibernation? Can you post contents of Graphics section of about:support ?
I appears that it might... I can't tell for sure, since I can't open Firefox today after restarting the computer from hibernate! The previous Firefox session was still there (and for a short time I could see the window in the 'Aero Peek' preview - and it did show the problem). Once I closed the session, then reopened it, the problem was gone. As for the 'Graphics section' I already did - see attachment 3 [details] [diff] [review] to this bug report.
If you can reproduce this reliably on every hibernate, try running in safe mode and try to reproduce. This could be some sort of bad interaction with an add-in.
Sorry, didn't notice. So it is an Nvidia GT 555M with Direct2D enabled. If you can't live without addons you could also try to temporarily disable HW acceleration in Option->Advanced->General. An hibernate with that setup.
It does NOT occur on EVERY restart after Hibernate, I just verified.
I also have the problem of the Minimize, Maximise and Close Buttons having disappeared since the 9.0.1 update. They occasionally appeared as a disembodied mini window floating separately from Firefox. At the time I didn't realise what they must be and just clicked on close, since when never seen again! Windows Vista 32 bit.
Since it wasn't mentioned here, there's bug 656891 about the titlebar getting messed up when Aero is switched off/on. In this bug we unfortunately don't have a good idea as to what might be causing this problem (is this related to hibernation? To some add-on / another app?), so please comment back if you come up with new information. For now I think it won't lead to a fix and should be closed as incomplete. (I noted this bug # in bug 656891 so that someone working on that will be able to find the information here if he needs to.)
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
This problem still occurs in V11
Problem still present in V12, and V13
Roger Shaw: This bug is closed so commenting here does not make much sense. Please file a new ticket if bug 656891 does not cover your problem.
Copying Roger's comments from bug 656891. Please reply here (and reopen) instead of confusing bug 656891. As I said there, what's going to help is figuring out what settings, actions, web content, and other software/hardware on the system makes this bug manifest, not confirming it's still a problem with the newest version. -- Roger Shaw 2012-06-18 08:34:20 PDT Created attachment 634054 [details] Title Bar rendering problem When the Menu bar is NOT being displayed, the Window Title line (with the minimize, maximize, and Close (X) buttons) is also NOT displayed. See attached .gif file This problem has been observed in V9, V10, V11, V12, V13. Originally reported as bug 716459 [reply] [-] Comment 8 Roger Shaw 2012-06-25 20:07:05 PDT Tonight this problem appeared again - under no known actions other than switching from one youtube video to another (all within the same tab). after switching a few times, the window title bar went black, the only button present was the "Firefox" button. I.e., it is apparently NOT tied to resuming form sleep or hibernate mode. This is with V13.0.1
I wish you would make up your mind... you tell me this is closed and to report via bug 656891 ( Andre Klapper 2012-06-18 04:55:20 PDT, above). Which I have been doing. Now Nickolay_Ponomarev (bug 656891 2012-10-28 14:55:34 PDT) tells me "Please post in bug 716459 (and reopen) or file a new bug when you have additional information." and that bug 716459 "is not obviously about the same issue as yours". So I am back... I opened this bug... don't know how/why it was "closed", since the problem has existed in EVERY Version up thru 16.0.2 (which I have reported under bug 716459)... and why was I transferred there if that bug si not the same issue?
Status: RESOLVED → VERIFIED
Whiteboard: [CLOSEME 2012-02-01] → [Reopened]
Andre's comment says "*if* bug 656891 does not cover your problem", which it isn't, since you're not switching themes. I explained the status of this bug in comment 17. Nothing has changed since.
I think it might make sense to maintain the "duplicate" relationship between this bug and bug 656891. Please change this bug back if that relationship is not desired for some reason
Status: VERIFIED → RESOLVED
Closed: 14 years ago → 13 years ago
Resolution: INCOMPLETE → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: