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: Ryosuke Niwa <rniwa@webkit.org>
Date: Wed, 20 Jun 2012 00:36:27 -0700
Message-ID: <CABNRm62eKaELjAy1Z-aV6MPoiJu=b2ZzXj78uguGZ0SCbhNbTA@mail.gmail.com>
To: olli@pettay.fi
Cc: Adam Klein <adamk@chromium.org>, Jonas Sicking <jonas@sicking.cc>, Rafael Weinstein <rafaelw@google.com>, Mihai Parparita <mihaip@chromium.org>, WebApps WG <public-webapps@w3.org>
On Tue, Jun 19, 2012 at 1:52 PM, Olli Pettay <Olli.Pettay@helsinki.fi>wrote:
>
>   Ojan points out
>
>> that simply using end-of-task could expose low-level implementation
>> detail of the parser to script (such as how much parsing is done in a
>> single task
>> before the parser yields).
>>
>> Does Firefox do anything special here? Or does it simply use the same
>> end-of-task delivery as everywhere else?
>>
>
> 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.
>

That randomness seems undesirable. Can we delay the delivery until
DOMContentLoaded is fired so that we can have more consisnte behavior here?

- Ryosuke
Received on Wednesday, 20 June 2012 07:37:19 GMT

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