Closed
Bug 1398056
Opened 7 years ago
Closed 4 years ago
Black h3 background and gray <code> background
Categories
(Developer Documentation Graveyard :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: fs, Assigned: eweyl)
Details
(Keywords: in-triage, Whiteboard: [specification][type:bug])
Attachments
(1 file)
12.92 KB,
image/png
|
Details |
What did you do? ================ Went to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array#Array_instances What happened? ============== Saw <h2><code>Array</code> instances</h2> with both black and gray backgrounds What should have happened? ========================== Not sure having both backgrounds looks great. The gray background box seems also larger than the black background. Is there anything else we should know? ====================================== Thanks for the gray for <code> generally. It's awesome!
Comment 1•7 years ago
|
||
On Mac this is only a problem with Firefox and not with Chrome or Safari. That complicates fixing it :/
Comment 2•7 years ago
|
||
Comment 3•6 years ago
|
||
Since the article page scanability changes this is a problem in h3s instead of h2s now.
Reporter | ||
Comment 4•6 years ago
|
||
We shouldn't use <code> in headlines.
Component: Design → General
Product: developer.mozilla.org → Developer Documentation
Summary: Black h2 background and gray <code> background → Black h3 background and gray <code> background
Comment 5•6 years ago
|
||
I have updated the MDN style guide to say specifically not to use any styles or things like <code> within headings. We need to work on removing these going forward.
Updated•6 years ago
|
Assignee: nobody → eweyl
Status: NEW → ASSIGNED
Comment 6•4 years ago
|
||
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•