Closed
Bug 915041
Opened 11 years ago
Closed 11 years ago
[meta] Update in content CSS (CustomCSS)
Categories
(Developer Documentation Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: teoli, Assigned: sheppy)
References
Details
(Whiteboard: [specification][type:bug])
What did you do? ================ This is a meta bug to track updates on our content CSS that need to be done for maximizing the impact of the redesign when we launch (Or if you prefer not to have too many shit^H^H^H^H odd-looking articles) What happened? ============== What should have happened? ========================== Is there anything else we should know? ======================================
Reporter | ||
Updated•11 years ago
|
Component: General → Design / user experience
Updated•11 years ago
|
Comment 1•11 years ago
|
||
Jean-Yves: We will only be releasing a beta at the end of Q3, and can take additional time after that to fix more minor bugs like these. If any of these are so important that you feel they should be corrected before the beta launch, let me know.
Updated•11 years ago
|
Updated•11 years ago
|
Updated•11 years ago
|
Comment 2•11 years ago
|
||
Is this OK now? Can this be closed?
Reporter | ||
Comment 3•11 years ago
|
||
Usually, we don't close [meta] bugs.
Comment 4•11 years ago
|
||
Derp, my bad. Sorry :(
Comment 5•11 years ago
|
||
Actually if the meta bug is empty & all the dependent bugs are closed, we should close it instead of having it hang around forever. I'm closing.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•