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

On Wed, Jun 20, 2012 at 1:33 PM, Adam Klein <adamk@chromium.org> wrote:

> On Wed, Jun 20, 2012 at 12:36 AM, Ryosuke Niwa <rniwa@webkit.org> wrote:
>
>> 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?
>>
>
> This doesn't seem very useful to me. Observing during page load will
> clearly have a cost associated with it, and if you aren't notified until
> DOMContentLoaded, you could have just listened for DOMContentLoaded
> yourself, looked through the document for the stuff you care about, and
> then attach an observer.
>

That's a good point. Although my point was so that you don't have to
explicitly wait for DOMContentLoaded yourself. Because if that was script's
intention, you could have just added "differ" or "async" content attribute
to the script element.

On Wed, Jun 20, 2012 at 12:53 AM, Olli Pettay <Olli.Pettay@helsinki.fi>
 wrote:

> On 06/20/2012 10:36 AM, Ryosuke Niwa wrote:
>
>> That randomness seems undesirable. Can we delay the delivery until
>> DOMContentLoaded is fired so that we can have more consisnte behavior here?
>>
>
> That prevents using MutationObserver for certain cases. Like when you
> "stream" data using an iframe.
>
> Also, there are already many cases when networking/parsing handling is
> exposed to the web pages.
> Just put any <img onload=".." onerror="...">. When the handlers run, the
> stuff after the <img> may or may not be in the document.


That's true. Maybe this "randomness" is okay after all.

- Ryosuke