W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: Should MutationObservers be able to observe work done by the HTML parser?

From: Adam Klein <adamk@chromium.org>
Date: Tue, 26 Jun 2012 13:58:44 -0700
Message-ID: <CAEvLGc+z_6htQMw9Pt8R0EfmD97GFiJN4iDdfBkScZrqeBbKKw@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>, Ian Hickson <ian@hixie.ch>, Jonas Sicking <jonas@sicking.cc>, Olli Pettay <Olli.Pettay@helsinki.fi>
Cc: WebApps WG <public-webapps@w3.org>
On Wed, Jun 20, 2012 at 12:29 AM, Anne van Kesteren <annevk@annevk.nl>wrote:

> On Tue, Jun 19, 2012 at 10:52 PM, Olli Pettay <Olli.Pettay@helsinki.fi>
> wrote:
> > end-of-microtask or end-of-task everywhere. And yes, some parsing /
> > networking details may unfortunately be exposed,
> > but in a way which should be quite random. Web devs just can't really
> rely
> > on network packages to be delivered to parser in
> > some exact way.
> I think the original solution we had to not expose parser mutations
> was better. Exposing this can lead to all kinds of subtle bugs that
> are hard to detect for developers.

I take it from your reply that you and I had the same view of what's
specced in DOM4. That is, that MutationObservers are not specified to be
notified of actions taken by the parser. Given that fact, it seems that
either the spec should be changed (and by "spec" here I think the required
changes are in HTML, not DOM), or Firefox's implementation ought to be

Anne, Ian, Olli, Jonas, your thoughts?

- Adam
Received on Tuesday, 26 June 2012 20:59:13 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:41 UTC