W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: DOM4 not compatible with ACID3 tests

From: Aryeh Gregor <ayg@aryeh.name>
Date: Mon, 12 Sep 2011 15:55:12 -0400
Message-ID: <CAKA+AxkBjpLcC8GoBg76UWaMV4J6CX0ctGb1LS81PUTWK85uFA@mail.gmail.com>
To: Tim Down <timdown@gmail.com>
Cc: Jonas Sicking <jonas@sicking.cc>, Ian Hickson <ian@hixie.ch>, Webapps WG <public-webapps@w3.org>, Olli <Olli@pettay.fi>
On Thu, Sep 8, 2011 at 8:14 PM, Tim Down <timdown@gmail.com> wrote:
> I'd suggest the DOM Range tests in ACID3 could be modified to test
> against the newer WHATWG Range spec, which clears up some ambiguities
> in the DOM 2 Range spec (there's one about what happens to Range
> boundaries after a particular insertNode call that I emailed
> acid3feedback@webstandards.org about over a year ago). There's also
> some attribute node tests in there.

The insertNode issue is noted in the current spec, which has been
merged into DOM4 (formerly known as DOM Core, formerly known as Web
DOM Core):

http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-range-insertnode

DOM 2 Range and Gecko disagree with IE, WebKit, Opera, and old
versions of Acid3.  Apparently this originated as an Acid3 bug that
all non-Gecko engines picked up to pass Acid3, which was later changed
to accept both behaviors.  I've spoken with smaug (Olli) about this
before.  My opinion is that the spec should change to match the
IE/WebKit/Opera behavior unless at least one of them is willing to
change, because that's the behavior that we'll more easily get interop
on.

It's possible you were thinking of a different insertNode issue, though.
Received on Monday, 12 September 2011 19:56:02 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT