Closed
Bug 192968
Opened 23 years ago
Closed 23 years ago
(html) -> the renderer seems to break when finds a noscript element inside a textarea element
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
People
(Reporter: igjav, Assigned: harishd)
Details
(Keywords: compat, testcase)
Attachments
(1 file)
|
432 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
<!-- view source of this in mozilla and compare with rendering -->
<textarea cols=80 rows=10>
<noscript>nothing or something</noscript>
<a href="http://www.mozilla.org" title="Go mozilla!">Red</a>
</textarea>
<textarea cols=80 rows=10>
<h1>nothing or something</h1>
<a href="http://www.mozilla.org" title="Go mozilla!">Red</a>
</textarea>
Reproducible: Always
Steps to Reproduce:
1. Open the code that comes in details in a mozilla window.
Actual Results:
The elements that come after noscript element lose reflected attributes
Expected Results:
Respect a textarea content, I would love it ;)
I tested with 1.3beta and same results.
I put this on critical because it can cause data lose on intranet applications,
even it's clear that is not a frequently used structure.
My case: It implied to reprogram the web management software.
| Reporter | ||
Updated•23 years ago
|
Hardware: Other → PC
Comment 1•23 years ago
|
||
Parser. The HTML (using unescaped tags in a <textarea>) is invalid; not sure
what our current attempts to "deal with" such HTML are like...
Assignee: asa → harishd
Component: Browser-General → Parser
QA Contact: asa → dsirnapalli
Comment 2•23 years ago
|
||
Comment 3•23 years ago
|
||
confirming with linux trunk build 20030212, but downgrading severity since this
is invalid markup (should be escaped). critical is mostly reserved for crash/hang.
You need to log in
before you can comment on or make changes to this bug.
Description
•