Closed
Bug 160116
Opened 23 years ago
Closed 23 years ago
Window layout looks "weird" after changing the xp desktop theme
Categories
(Core :: Layout, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 148530
People
(Reporter: wolfgang.robben, Assigned: attinasi)
Details
After changing XP's dektop theme, mozillas window layout looks rather weird. The
status bar is horizontally mirrored and half a heigh as the window. The window
itself behaves normal. You have to shutdown mozilla (using the quicklaunch
tool), to reset the layout.
sounds like bug 148530, which was later resolved as invalid, but hasn't been
verified as such.
Reporter: Which Mozilla theme are you using?
| Reporter | ||
Comment 2•23 years ago
|
||
*** This bug has been marked as a duplicate of 148530 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 3•23 years ago
|
||
R.K.Aa was right, it was a duplicate of bug 148530...
Verifying as duplicate. Reporter mailed:
--
"Thank you for the quick response!
You are right, as I see now it was bug 148530.
Sorry, I havn't found that bug in the bugzilla library when I was
submitting this one.
With the standard mozilla theme it works just fine.
Therefore I just marked the bug as a duplicate."
---
Wolfgang: Does this mean you too were using the Pinball theme for Mozilla when
this happened?
Status: RESOLVED → VERIFIED
| Reporter | ||
Comment 5•23 years ago
|
||
Yes in deed. I tried "Classic" and "Modern" skins too, but they did not produce
this bug.
When you take a look at the stylesheet files of the "Pinball" skin, you'll find
--8<-- snipp -->8--
.statusbarpanel-progress {
-moz-box-align: stretch;
border: 0px;
margin: 0px;
padding: 0px;
}
--8<-- snipp -->8--
I think the "stretch" alignment will cause this bug. The other skins either
don't have this tag or it is empty.
Unfortunally I don't know enough about skin programming, so I cannot verify this.
But maybe some other user is able to do this, in this case this bug may has to
be reopened, because that *would* be a bug in the chrome engine.
You need to log in
before you can comment on or make changes to this bug.
Description
•