Closed Bug 73889 Opened 25 years ago Closed 24 years ago

Very long <pre> segment not fully rendered, appears with strikethrough

Categories

(Core :: DOM: HTML Parser, defect)

x86
All
defect
Not set
normal

Tracking

()

VERIFIED WONTFIX
mozilla1.0.1

People

(Reporter: jmd, Assigned: harishd)

References

()

Details

(Keywords: compat)

When I load this page in Mozilla 0.8.1, starting at port 48 of the data, it appears with a strikethrough. The data continues this way through port 366, at which point the <pre> ends and the rest of the page is rendered (also with strikethrough!). Note that there is MUCH more data, as can be seen with Netscape 4.7
over to layout.
Assignee: asa → karnaze
Component: Browser-General → Layout
QA Contact: doronr → petersen
Confirming on Windows 2000 with today's build. I'm guessing style on this one.
Assignee: karnaze → pierre
Component: Layout → Style System
OS: Linux → All
QA Contact: petersen → ian
Target Milestone: --- → mozilla1.0
It's been 5 months... just checked with todays build and this is still very broken.
The problem is that this list contains an email address "<S.Kille@isode.com>" which is interpreted as a <S> tag (strikethrough). Reassigned to Parser.
Assignee: pierre → harishd
Component: Style System → Parser
QA Contact: ian → bsharma
QA Contact: bsharma → moied
Entire page seems to load now, and the <pre> doesn't end, but it still has a strikethrough the whole thing, and it's incredibly slow.
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Poor perf on long <pre> sections is another bug I believe. As for the rest, you must escape your email addresses with &lt; for < or they will be interpreted as markup (hence the strikethrough).
Keywords: compat
As the original reporter, seeing this is HTML error, I'm willing to accept WONTFIX, except one thing troubles me. The "tag" causing the strikethrough: <s.Kille@isode.com> Under SGML rules, is <foo.bar> some legal way to start a <foo> tag? How is the period being interpreted?
Per SGML, only name characters are allowed in the generic identifier of an element. So the parser reads in "<s", hits the non-name character ".", closes the generic identifier (making it an "s" element), and probably does some sort of error recovery that puts part or all of the remaining content into a malformed attribute. Again, just escape "<" in all text being converted to HTML into "&lt;" and you should be fine.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Verified wontfix as per Comment #8
Status: RESOLVED → VERIFIED
*** Bug 295886 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.