Closed
Bug 616379
Opened 14 years ago
Closed 10 years ago
Theme changes for in-content UI
Categories
(Firefox :: Theme, defect)
Firefox
Theme
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
blocking2.0 | --- | - |
People
(Reporter: mossop, Assigned: Unfocused)
References
Details
(Keywords: uiwanted)
Once bug 571970 lands there are going to be some theme changes to make things all pretty.
Reporter | ||
Comment 1•14 years ago
|
||
This should block as it is really required to not make in-content UI look nasty.
blocking2.0: --- → ?
Reporter | ||
Comment 2•14 years ago
|
||
We need a final design on how this should look and how it should behave with a lightweight theme applied here.
Keywords: uiwanted
Comment 3•14 years ago
|
||
Zero spec = high probability of risk, both bug-wise and schedule. blocking-.
blocking2.0: ? → -
Comment 5•13 years ago
|
||
What's needed for this bug?
Assignee | ||
Comment 6•13 years ago
|
||
Guess this belongs to me, since it goes hand-in-hand with bug 620963 (which is blocked by a platform bug). Bug 620963 fixes the most obvious case where the tab doesn't integrate visually with the in-content UI when there's a lightweight theme applied. This bug should handle any other case where we don't visually transition nicely between traditional chrome UI and in-content UI.
Assignee | ||
Comment 7•10 years ago
|
||
Well, this bug isn't terribly helpful these days.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•