Closed
Bug 77145
Opened 25 years ago
Closed 25 years ago
Stray left angle brackets ("<") from tags are left in output around the 4kB mark
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
VERIFIED
FIXED
mozilla0.9.2
People
(Reporter: danp, Assigned: harishd)
References
()
Details
(Whiteboard: [fix in hand])
Attachments
(4 files)
|
1.23 KB,
application/x-zip-compressed
|
Details | |
|
252 bytes,
application/octet-stream
|
Details | |
|
998 bytes,
patch
|
Details | Diff | Splinter Review | |
|
1.73 KB,
patch
|
Details | Diff | Splinter Review |
The gist of this bug is that the parser seems to leave a stray left angle
bracket from any HTML tag as long as it is in just the right place, which seems
to be around the *4096* byte mark. (I smell an off-by one buffer screwup here.)
In the limited time I've had to play with this bug (I found this in the middle
of hurriedly writing some release notes in between fixing bugs for a product
that's due tomorrow), I've managed to whip up two test cases (located at the URL
for this bug), both of which need to be run using the file:// resource type to
most easily reproduce this bug, and need to be left in their original format
(which is CR/LF line endings). *The exact number of characters matters when
reproducing this bug*, as I already mentioned. To ensure the file contents
aren't munged when downloading, the two testcases are in a .zip file.
To see the bug in action, open each test case, and look for an opening angle
bracket at the bottom. Then look at the HTML. It all should become clear then.
| Reporter | ||
Updated•25 years ago
|
Summary: Stray left angle brackets ("<") from tags are left in output when parsing files of certain sizes → Stray left angle brackets ("<") from tags are left in output around the 4kB mark
| Reporter | ||
Comment 1•25 years ago
|
||
Some additional info after playing with the cool test case:
The requirements for reproducing the bug are:
1) You have to cheat/make Moz into thinking that it is dealing with an HTML file
(so Moz will have to parse the content instead of diaplaying it like plain text).
2) File content:
a) First, put a bunch of characters exactly 4095 bytes long.
b) Then, add a retuen (which, in DOS file format, means an CR and LF)
c) Finally, put some other characters (length doesn't matter)
Comment 5•25 years ago
|
||
I see this on Linux build 2001-04-22-21 as well. status to new, adding various
keywords.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
Setting to 1.0 since 0.9.2 hasn't been scheduled yet.
Target Milestone: mozilla0.9.2 → mozilla1.0
Moving to milestone 0.9.2
We'd really like this fix before too long
nsbeta1-, we don't need it immediately, other things are more important right now.
| Assignee | ||
Comment 10•25 years ago
|
||
Comment 11•25 years ago
|
||
r/sr=vidur
r=heikki.
Comment 13•25 years ago
|
||
a= asa@mozilla.org for checkin to the trunk.
(on behalf of drivers)
Blocks: 83989
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 14•25 years ago
|
||
Fix is in.
Comment 15•25 years ago
|
||
Verified on
build: 2001-06-20-04-Trunk
platform: Win NT
Both the test cases load fine.
You need to log in
before you can comment on or make changes to this bug.
Description
•