W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2012

Re: [DOM4] Mutation algorithm imposed order on document children

From: Elliott Sprehn <esprehn@gmail.com>
Date: Wed, 13 Jun 2012 10:47:02 -0700
Message-ID: <CAPJYB1jVnf5vNVdAmtrNFa2tJJA9iyoTeerwrryoz_asb5M-Nw@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Ryosuke Niwa <rniwa@webkit.org>, www-dom <www-dom@w3.org>, Ojan Vafai <ojan@chromium.org>, Boris Zbarsky <bzbarsky@mit.edu>
On Wed, Jun 13, 2012 at 1:32 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Tue, Jun 12, 2012 at 10:35 PM, Elliott Sprehn <esprehn@gmail.com>
> wrote:
> > IE9 _does_ expose the doctype node. It's IE8 that doesn't but I've
> ignored
> > that case.
> Did you try multiple doctypes? Or is the only change you want to make
> the one about ordering? Seems kind of arbitrary to me...

That's a good question.

FF, IE9, Webkit: Enforces a single doctype and a single element.
Opera: Enforces a single element, but allows multiple doctypes.

So it seems the one element, one doctype rule is already pretty well

I'd like to change the spec so that instead of requiring a specific
ordering, it requires that the serialization of the document (for example
through XMLSerializer) always reflects the current document state, even if
you removed the doctype node entirely. That ensures that serializing a live
document gets you something that would render the same a second time.

> (Also, changes we make here affect
> http://www.whatwg.org/specs/web-apps/current-work/#serializing-xhtml-fragments
> and may affect other specifications as well that rely on the
> constraints a DOM tree enforces. Given that most browsers don't care
> this does not matter that much, but we should make sure we follow up
> with them.)

Received on Wednesday, 13 June 2012 17:47:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:00 UTC