compatibility mode: HR should not end PRE

VERIFIED FIXED

Status

()

P2
minor
VERIFIED FIXED
20 years ago
20 years ago

People

(Reporter: dbaron, Assigned: rickg)

Tracking

Trunk
Other
Other
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

In compatibility mode *only* (i.e., DTD below HTML 4.0 strict), you should not
make an HR terminate a PRE element.  (Note:  HRs should not be within PREs.)
See the messed up output above from the Apache server that claims to be HTML
3.2.  (IMGs shouldn't be in PREs either.)
More PRE problems are visible in the (invalid) output of the W3C HTML validator
at, for example,
http://validator.w3.org/check?url=http://misa.ppages.com/main.htm
(Assignee)

Updated

20 years ago
Status: NEW → ASSIGNED
(Assignee)

Updated

20 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

20 years ago
It is fixed in compatibility mode now.

Updated

20 years ago
QA Contact: 4110

Comment 3

20 years ago
assigning qa_contact field.
It's also fixed in standard mode.  I'm not sure that should be the case.

Updated

20 years ago
Status: RESOLVED → VERIFIED

Comment 5

20 years ago
Using 3/29 build, verifying bug fixed. HR no longer ends PRE element tag.
Followup memo sent to assigned engineer for clarification of browser behavior
with illegal nested element.
Well, since HR is not valid inside PRE, the behaviour in strict mode is
undefined, so I don't suppose we can complain either way...
You need to log in before you can comment on or make changes to this bug.