Closed
Bug 598871
Opened 14 years ago
Closed 14 years ago
on launch, the Firefox window goes through several ugly transitions before it's complete
Categories
(Core :: Widget: Win32, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 594821
People
(Reporter: asa, Unassigned)
Details
Attachments
(4 files)
Hard to describe so I've got screenshots.
When you launch Firefox, there are several stages of ugly before the window is complete.
The first problem is that the toolbar area and the content area are different colors. The toolbar area is white while the content area is gray. You can see this in the first and second screenshots, most clearly in the second.
The second problem is that the toolbar white area extends up over the top of the top window frame. You can see this most clearly in the third screenshot though it is present in 1-3.
There may be better fixes, but I think making the chrome and content areas the same color before and getting the chrome area not to break out of the top of the window frame would go a long way to making the launch experience not look so janky.
Reporter | ||
Comment 1•14 years ago
|
||
Reporter | ||
Comment 2•14 years ago
|
||
Reporter | ||
Comment 3•14 years ago
|
||
Reporter | ||
Comment 4•14 years ago
|
||
Reporter | ||
Comment 5•14 years ago
|
||
If you open the four images in tabs and then ctrl tab through them, it gives you a sort of slow motion launch animation. If there's any way to make the window look like its final state for those first three shots, that'd be ideal. If not, then at least unifying the color and getting that top window border matching the sides and bottom.
Reporter | ||
Updated•14 years ago
|
blocking2.0: --- → ?
Comment 6•14 years ago
|
||
This is a dupe, I'm pretty sure, but the screenshots are good to have.
Component: General → Widget: Win32
Product: Firefox → Core
QA Contact: general → win32
Whiteboard: DUPEME
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
Updated•14 years ago
|
blocking2.0: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•