- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 31 Aug 2010 16:34:32 -0700
- To: Joćo Eiras <joao.eiras@gmail.com>
- Cc: www-dom@w3.org
On Tue, Aug 31, 2010 at 3:58 PM, Joćo Eiras <joao.eiras@gmail.com> wrote: > On , Anne van Kesteren <annevk@opera.com> wrote: > >> On Mon, 30 Aug 2010 21:15:04 +0200, Ojan Vafai <ojan@chromium.org> wrote: >>> >>> WebKit is changing to match Gecko and not throw WRONG_DOCUMENT_ERR in a >>> number of cases. >>> >>> https://bugs.webkit.org/show_bug.cgi?id=19524 >>> >>> Is there an editor for http://www.w3.org/TR/DOM-Level-3-Core/? These >>> cross-document restrictions cause an unnecessary burden on web developers >>> and soon WebKit and Gecko will not be firing them. Is there any >>> possibility >>> of changing the spec to match? >> >> There's: http://simon.html5.org/specs/web-dom-core >> >> I have a vague plan of working on it once the CSS Value API in CSSOM is >> specified, but it depends on how much time everything else leaves me. > > The spec has always enforced WRONG_DOCUMENT_ERR, but Mozilla has always had > the bug. Hence Opera was forced to implicitly do adoptNode although always > remarked as a temp solution while Mozilla did not fix their issue. > > Although I would personally agree that firing the exception is better from a > strict programming point of view, web compat will probably require the > implicitly adoptNode forever. For what it's worth, we actually tried to remove the implicit adoptNode and implement the WRONG_DOCUMENT_ERR exception. IIRC this was for firefox 3.0 or 3.5. However in the end we had to revert because there were just too many sites breaking. In fact, it was a big enough problem that we weren't even able to get to release candidates, but had to revert before than. I would expect that actually releasing would have uncovered significantly more sites that were breaking. / Jonas
Received on Tuesday, 31 August 2010 23:35:29 UTC