Closed Bug 269366 Opened 20 years ago Closed 20 years ago

different results if leave out HTML Transitional DTD URL

Categories

(Core :: DOM: HTML Parser, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: pete, Unassigned)

Details

example a)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

example b)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
 "http://www.w3.org/TR/html4/loose.dtd">

If I leave out the URL of the DTD for HTML 4.01 Transitional, as in example a),
headings using <h2>, <h4> etc (I haven't tested the rest) are smaller than those
displayed when including the URL as in example a), when viewed in Firefox 1.0RC2
and Mozilla 1.8a4, but not IE 5.0. In IE 5.0 they're the same larger sizes no
matter whether using example a) or b).

Tables also differ, they have stronger borders and lots more white space when
using example a)
(my tables use border="0" cellspacing="0" cellpadding="0")

This doesn't have any effect if HTML 4.01 Strict is used and it's URL for the
DTD omitted; In that case it looks the way the Transitional does if you leave in
the URL

Mozilla Composer 1.8a4 doesn't add the URL in example a)

Not sure but possibly related to bug 218818

Examples of a page of mine using example a) is at
http://thegoldenear.org/toolbox/windows/software.html
the url switches between quirks and almost standards mode
http://www.mozilla.org/docs/web-developer/quirks/doctypes.html
so I'm seeing my document rendered in quirks mode, which is intended to imitate
Netscape 4, which looks wrong. I should instead use Strict mode and convert old
documents to a strictness I understand now but didn't when they were originally
written

Its a shame I originally copied my DOCTYPE declaration from that used by Mozilla
Composer. I've now voted for bug 92525

Shall I mark this bug a dupe of bug 92525? or INVALID?
marking invalid, better than voting is fixing Daniel will probably be very happy
about new contributors :-)
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.