57366 - RFE: Support for the IE DOM.

Status: VERIFIED DUPLICATE of bug 154589

(Core :: DOM: Core & HTML, enhancement, P3)

Description

[Joseph Elwell]

I have been told repeatedly that Mozilla.org would accept outside support of
proprietary standards into their default codebase - if only some contributor
offered a working implementation.

<BLINK> is an example of a proprietary (non-standard) tag that has never been
part of any w3c recommended HTML spec.

<LAYER> is an exmple of a proprietary (non-standard) tag that has not yet been
supported, but - I am told - Mozilla.org would be willing to accept (into the
main distribution) if someone created support for.

Along these lines, Mozilla.org should support the IE DOM; this would allow many
pages already out there to work seamlessly with Mozilla.

Comment 1

[Doron Rosenberg (IBM)]

I am assuming this is not a joke on any kind:

well, the blink is just something netscape people feel they need, like the
about:mozilla or fishcam

The layer tag, however, is something else. it's a bastardisation that netscape
introduced, and there is now the incentive to support it in some way (convert to
divs) so that pages might render.

I heavily doubt we will support the ie DOM, this would mean a lot of work.
Perhaps convert document.all like <layer>, but doubtfull.

Marking helpwanted and settign to [e-mail].

Comment 2

[Joseph Elwell]

Assinging to DOM Level 0 which is apparently:
"This component consists of all functionality related to JavaScript manipulation
of window, document and navigator components that was available in Navigator 4.x
and before, and not defined by the W3C."

DOM Level 0 might be a good place to support all proprietary DOM features.

Comment 3

[Blake Ross]

Someone pointed out to me the other day that <blink> works (and, indeed, it 
does).

Comment 4

[Brian 'netdragon' Bober]

How hard is it to reproduce using normal dom what document.all does? It would 
be a bad idea to support more proprietary html than is needed. Proprietary html 
causes people to actually write web pages using it. innerhtml is another 
example. The only time proprietary html is accepted is when it can't be 
duplicated using another method. Can document.all be duplicated easily?

Comment 5

[timeless]

document.all.foo == document.getElementById("foo") as such there's really no 
justification for someone needing to use the non w3 spec'd form.

Comment 6

[Brian 'netdragon' Bober]

Also, according to the specs, you can do anything for document.all with 
document.getElementById, document.getElementsByTagName and 
document.getElementByName. Using these makes the code easier to read because 
you are being more explicit of what type each object is. document.all is an old 
thing microsoft added and shouldn't be supported. The question is: even if 
someone wrote the code, would it be a good thing to add? The answer is "no" 
because support for proprietary html would make it even harder to get rid of.

Comment 7

[Christopher Aillon (sabbatical, not receiving bugmail)]

Sigh.

*** This bug has been marked as a duplicate of 154589 ***

Comment 8

[Brian 'netdragon' Bober]

Goatified