Closed
Bug 113349
Opened 23 years ago
Closed 23 years ago
non-HTML tagnames are stripped out of HTML
Categories
(Core :: DOM: HTML Parser, defect, P2)
Tracking
()
VERIFIED
FIXED
mozilla0.9.9
People
(Reporter: TucsonTester1, Assigned: harishd)
Details
(Keywords: regression)
Attachments
(1 file)
|
2.10 KB,
patch
|
hjtoi-bugzilla
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
Tested using Composer rev. 2001120303 on Win 98
My steps to reproduce:
1. Launch Composer and create a new blank page
2. Click on the "HTML Source" tab at the bottom
3. Inside of the <body> tags, type in <marquee> marquee test </marquee> then
click back to the "Normal" view.
Expected results:
The test should scroll accross the screen
Actual results:
The text will display on the screen without scrolling. When the HTML source is
viewed, the word "marquee" is removed leaving just "<> marquee test </>".
Even though the Netscape browser doesn't support viewing of the Marquee tag, the
previous build of Composer (11/26) did allow for the creation of this feature.
Other custom HTML such as a "blink" tag or form tags are created and function
correctly.
*shrug*
Over to charles for some more experienced triage.
Assignee: syd → cmanske
|
||
Comment 2•23 years ago
|
||
This isn't Composer, it's probably in the parser.
Not just Marquee, but any non-official HTML tagname is stripped out.
This is an important problem and regression! Unrecognized elements are supposed
to be marked with the "_moz-userdefined" attribute and they should retain
the user's tagname.
Assignee: cmanske → harishd
Severity: minor → major
Component: Editor: Composer → Parser
Keywords: regression
QA Contact: sujay → moied
Summary: In Composer, marquee tag is stripped out of HTML → non-HTML tagnames are stripped out of HTML
|
|
||
Comment 3•23 years ago
|
||
Odd, I thought "Strict" DTD was supposed to prevent such tags from going in, but it's a complete mess anyway.
I'm sure this is something to do with jst's change to nsHTMLTags. Investigating.
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla0.9.9
The problem was that we're creating a new node info with |no name| for
userdefined tags ( since HTMLIdToStringTag wasn't able to map userdefined tag to
a string value ).
|
||
Comment 7•23 years ago
|
||
Comment on attachment 66519 [details] [diff] [review]
patch v1.0 [ HTMLIdToStringTag should only be used for known tags ]
sr=jst
Attachment #66519 -
Flags: superreview+
Comment on attachment 66519 [details] [diff] [review]
patch v1.0 [ HTMLIdToStringTag should only be used for known tags ]
r=heikki
Attachment #66519 -
Flags: review+
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•