Closed Bug 267193 Opened 20 years ago Closed 20 years ago

[quirks] vertical space before and after H1 if inside A NAME tag

Categories

(Core :: Layout: Block and Inline, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: AZurcher, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.7) Gecko/20040803 Firefox/0.9.3

A vertical space appears before and after H1 when this tag is inside a <A
NAME=...> tag.

The style sheet specifies : H1 {
	font-family : "Times New Roman",Times,serif;
	font-size-adjust : 0.45;
	font-size : 24pt;
	font-weight : bold;
	font-style : italic;
	color : #999999;
	margin-bottom : 0.5 em;
}

The MARGIN specified for H1 in the style sheet doesn't seem to be taken into
account when H1 is inside a <A> tag?

This additional space is not specified in the style sheet for A tag either!

Reproducible: Always
Steps to Reproduce:
Compare :
http://chanteur.net/biblio/bug2.htm  (additional space)
with :
http://chanteur.net/biblio/bug2b.htm  (no space)
Actual Results:  
A vertical space appears before and after H1 when this tag is inside a <A
NAME=...> tag.

Expected Results:  
Keep the margins specified in the style sheet for the H1 tag.
Specifying "margin-top : 0;" for H1 in the style sheet resolves the problem.

(Invalid syntax "margin-bottom : 0.5 em" also replaced with "margin-bottom : 0.5em")
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
That's a by-design quirk in quirks.css.

td > h1:-moz-first-node {
  margin-top: 0;
}

When you wrap an <A> tag around the H1, (which is invalid HTML, by the way),
this rule no longer kicks in and the default H1 margins apply.
Summary: vertical space before and after H1 if inside A NAME tag → [quirks] vertical space before and after H1 if inside A NAME tag
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.