Closed
Bug 580502
Opened 14 years ago
Closed 13 years ago
[meta] CSS styling for Console
Categories
(DevTools :: General, defect)
DevTools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pcwalton, Unassigned)
References
Details
(Keywords: meta)
The console needs the final CSS styling for both its HTML and XUL components.
Reporter | ||
Comment 1•14 years ago
|
||
This bug is an important part of the Firefox 4 Console UI. The current UI for the console is simply a placeholder and has not yet been designed from a UX perspective (see bug 559481). Because I am requesting blocking status for the Console UI, and this is a critical part of the Console user experience, I am requesting that this bug block the Firefox 4 release as well.
Reporter | ||
Updated•14 years ago
|
Severity: enhancement → normal
Comment 2•14 years ago
|
||
Yes - it needs to look nicer than it does. betaN+, would prefer an early beta so that we have a chance to get feedback on the style.
blocking2.0: ? → betaN+
Updated•14 years ago
|
Whiteboard: [kd4b5]
Updated•14 years ago
|
Whiteboard: [kd4b5] → [kd4b7]
Updated•14 years ago
|
Severity: normal → blocker
Comment 3•14 years ago
|
||
Reprioritizing bugs. You can filter the mail on the word TEABAGS.
(Side note: I'm moving this into beta 6... post beta 6, I think we should open specific bugs on additional styling changes we want.)
Severity: blocker → normal
Whiteboard: [kd4b7] → [kd4b6]
Comment 4•14 years ago
|
||
Missed that this is a meta bug...
Summary: CSS styling for Console → [meta] CSS styling for Console
Whiteboard: [kd4b6]
Comment 5•14 years ago
|
||
Removing blocking flag from this meta bug. Generally, the styling of the Web Console is in decent shape at this point anyhow.
blocking2.0: betaN+ → ---
Updated•14 years ago
|
Assignee: pwalton → nobody
Comment 6•13 years ago
|
||
this meta bug was for Firefox 4 and all of its dependencies are done.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•