Closed Bug 915041 Opened 11 years ago Closed 11 years ago

[meta] Update in content CSS (CustomCSS)

Categories

(Developer Documentation Graveyard :: General, defect)

All
Other
defect
Not set
normal

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?
======================================
Blocks: 910513
Component: General → Design / user experience
Depends on: 915046
Depends on: 915050
Depends on: 915057
Depends on: 915087
Depends on: 915109
Depends on: 915185
Depends on: 915627
Blocks: 914828
No longer blocks: 910513
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.
Assignee: nobody → eshepherd
Blocks: 910513
No longer blocks: 914828
Component: Design / user experience → General
Product: Mozilla Developer Network → Developer Documentation
Blocks: 914840
No longer blocks: 910513
Blocks: 910513
No longer blocks: 914840
Blocks: 927438
No longer blocks: 910513
Is this OK now?  Can this be closed?
Usually, we don't close [meta] bugs.
Derp, my bad. Sorry :(
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.