Closed
Bug 12184
Opened 25 years ago
Closed 24 years ago
<plaintext> tag doesn't work
Categories
(Core :: DOM: HTML Parser, defect, P3)
Core
DOM: HTML Parser
Tracking
()
VERIFIED
WORKSFORME
M12
People
(Reporter: brendan, Assigned: harishd)
References
()
Details
(Keywords: verifyme, Whiteboard: [19990909]tried on today's build - not fixed; will try tomorrow's)
I didn't get a chance to debug this, but it seems to produce no text, and the
empty body generation magic happens, whether or not it's closed by </plaintext>.
/be
Digging deeper, I'm seeing odd behavior which appears to be upstream. It looks
like I'm not getting any content in this case, nor do I get content from necko
in the case of file URLS. I'm convinced that my file url is valid (and it works
fine in 4.x). I'll get with warren before proceeding here. The problems may be
related.
Note: the bug appears to be a result of the way the DTD deals with skipped
content. In the case of plaintext, we're looking for the end of the plaintext
element which never comes. The we hit the end of the document and neglect to
emit the skipped content we've encountered thus far. It's and easy kill which
I'll get to soon.
Comment 4•25 years ago
|
||
I tried 'javascript:<plaintext>hi</plaintext>' too and that didn't work, so more
than the end-tag is needed. Beware that while javascript: works in M9, recent
security changes to the trunk have busted it.
/be
Thanks for the feedback. The terse summary of the fix I posted will account both
of your examples. I can test with plain file URL's (which exhibit the same
behavior). It's just a side-effect of the code in the parser that tries to move
content around. While moving content is a useful capability, this is an
oversight in my implementation and needs to be fixed (if not held up to the rest
of the world as an example of how lame the parser is.)
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Generated an end sequence, for open skip target.
PLAINTEXT should work now. Marking bug FIXED.
Updated•25 years ago
|
Whiteboard: [19990909]tried on today's build - not fixed; will try tomorrow's
My bad :o( javascript:'<plaintext> hello' is not working!!! I'll look into it.
Actually, I tested with the following example:
<html>
<head>
<script>
document.write('<plaintext> hello');
</script>
</head>
<body>...
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Updated•25 years ago
|
Resolution: FIXED → ---
Comment 9•25 years ago
|
||
reopening bug
Assignee | ||
Comment 10•25 years ago
|
||
Moving to M12
Assignee | ||
Comment 11•25 years ago
|
||
Tested with Oct 23rd build and it worked fine for me!!
Janc, could you please verify this?? Thanx
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 12•25 years ago
|
||
Marking WORKSFORME
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 13•25 years ago
|
||
works for me too
Comment 14•24 years ago
|
||
Cute. Does anyone think someone fixed this? obviously work was done on it. I
also have a similar bug 46054 that says it doesn't work.
I'm marking verifyme. I would hope that QA would check the dependencies. If you
decide this bug is truely fixed then please include the url for the patch.
Thank you.
Assignee | ||
Comment 15•24 years ago
|
||
46054 is the not the same as this bug. javascript:'<plaintext> hi there' does
work. Marking bug WORKSFORME.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → WORKSFORME
Comment 16•24 years ago
|
||
Verified on linux
Mac?
Win?
Comment 18•23 years ago
|
||
Verified on
build: 2001-05-03-04
Platform: WinNT
Status: RESOLVED → VERIFIED
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•