Closed
Bug 591018
Opened 15 years ago
Closed 13 years ago
toggeling the browser to Fullscreen while NNTP-access causes broken GUI
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: stefan.blumenrath, Unassigned)
Details
(Whiteboard: [Halloween2011Bug])
Attachments
(1 file)
34.38 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.11) Gecko/20100701 Lightning/1.0b1 Mnenhy/0.8.3pre5 SeaMonkey/2.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.11) Gecko/20100701 Lightning/1.0b1 Mnenhy/0.8.3pre5 SeaMonkey/2.0.6
When I toggle to fullscreen, the image of the window is broken, it has two window borders (instead of one) on the right side and two statusbars on the bottom. In a new profile everything is fine - until I get News in the background and try the browser to toggle to fullscreen (I use F11).
Reproducible: Always
Steps to Reproduce:
1.Create a New Profile and a NNTP-Account
2.Start getting news, be sure, there are enough articles to pull
3.Switch to the browser and press F11
Actual Results:
Broken GUI as described
Expected Results:
Fullscreen :-)
I use a rather small display, 1024x600. I don't think that it is from interest, but who knows.
Reporter | ||
Comment 1•15 years ago
|
||
This screenshot shows the broken fullscreen image
Comment 2•15 years ago
|
||
Hm, can't reproduce it with 2.0.7pre. Did you have any extensions in the new profile you tested?
Reporter | ||
Comment 3•15 years ago
|
||
No, it was a new profile for testing. I see this at least since 2.0.0 but didn't care about it. I use a local NNTP-Server, but that shouldn't change anything. The screenshot was my normal profile, where this problem often occurs. Deleting the localstore.rdf helps, but after a while the problem re-occured so i tried to reproduce it.
Reporter | ||
Comment 5•13 years ago
|
||
Quick Test: No!
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Whiteboard: [Halloween2011Bug]
You need to log in
before you can comment on or make changes to this bug.
Description
•