Bug 4475 - <noscript>, <noframes>, <nolayer> and <noembed> elements should be in the DOM
Summary: <noscript>, <noframes>, <nolayer> and <noembed> elements should be in the DOM
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Anders Carlsson
Depends on:
Reported: 2005-08-17 02:46 PDT by Anders Carlsson
Modified: 2005-08-19 16:56 PDT (History)
0 users

See Also:

Add "no-elements" to the DOM (12.74 KB, patch)
2005-08-17 02:48 PDT, Anders Carlsson
darin: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Carlsson 2005-08-17 02:46:36 PDT
Currently, the HTML parser ignores the above tags, while other browsers put them in the DOM. WinIE, 
MacIE and Opera ignores any child nodes of the elements, while mozilla treats all contents as a single text 
node, for example <noframes><b>Foo</b></noframes> will create a noframes element with a child 
node that has the value "<b>Foo</b>". Some of the HTML element tests are failing because of this.
Comment 1 Anders Carlsson 2005-08-17 02:48:26 PDT
Created attachment 3432 [details]
Add "no-elements" to the DOM

Here's a patch that adds the "no-elements" to the DOM. It doesn't create any
children for them though, but I think this is OK.