Closed
Bug 7660
Opened 25 years ago
Closed 25 years ago
<map> causes extra whitespace; shouldn't be displayed
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Core
CSS Parsing and Computation
Tracking
()
VERIFIED
FIXED
M8
People
(Reporter: allen.sam, Assigned: peterl-retired)
References
()
Details
(Whiteboard: simple fix included)
The <map> tag at the top of http://www.mozilla.org/ is causing there to be extra whitespace at the top of the page. The fix for this is very easy. Add, to ua.css, map {display: none; } Voila! Whitespace is gone, on mozilla.org and the other pages that exhibit this flaw. This does not cause any functionality of the tag to be lost. Someone check this in, that whitespace has been bothering me for a long time.
Kipp -- this looks to be a box/line collapsing bug. Note the first blank line that preceeds the map (at the very top of the page).
Updated•25 years ago
|
Component: Layout → Style System
Comment 2•25 years ago
|
||
The problem is actually that MAP is currently not mentioned in ua.css, so it defaults to being an inline element. It thus creates an anonymous block box around itself, takes note of itself because it is empty, and leaves a blank line. This is correct as per CSS. To follow HTML4, it should be declared like this: MAP { display: block; } It would be wrong to say "map { display: none; }", because otherwise block-level content in MAP elements would dissapear. See HTML4, section 13.6.1. I am reassigning this to Style System. Peter: The fix for this is really simple, just add the line mentioned above to ua.css, near the AREA rule.
Updated•25 years ago
|
Assignee: kipp → peterl
Comment 3•25 years ago
|
||
Reassigning...
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M8
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 4•25 years ago
|
||
OK.Checked with the 6/23 build. Marking as verified fixed.
*** Bug 9273 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•