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)
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
Comment 1•25 years ago
|
||
over to layout.
Assignee: asa → karnaze
Component: Browser-General → Layout
QA Contact: doronr → petersen
Comment 2•25 years ago
|
||
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
| Reporter | ||
Comment 3•25 years ago
|
||
It's been 5 months... just checked with todays build and this is still very broken.
Comment 4•25 years ago
|
||
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
| Reporter | ||
Comment 5•24 years ago
|
||
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.
Comment 6•24 years ago
|
||
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
Comment 7•24 years ago
|
||
Poor perf on long <pre> sections is another bug I believe. As for the rest, you
must escape your email addresses with < for < or they will be interpreted as
markup (hence the strikethrough).
Keywords: compat
| Reporter | ||
Comment 8•24 years ago
|
||
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?
Comment 9•24 years ago
|
||
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 "<" and you should be fine.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Comment 11•21 years ago
|
||
*** 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.
Description
•