Closed Bug 2031 Opened 26 years ago Closed 26 years ago

compatibility mode: HR should not end PRE

Categories

(Core :: DOM: HTML Parser, defect, P2)

Product:
Core
Component:
DOM: HTML Parser
Platform:
Other
Other
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: dbaron, Assigned: rickg)

References

(
URL
)

Details

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
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
It is fixed in compatibility mode now.
QA Contact: 4110
assigning qa_contact field.
It's also fixed in standard mode. I'm not sure that should be the case.
Status: RESOLVED → VERIFIED
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.