On 06/26/2012 11:58 PM, Adam Klein wrote:
On Wed, Jun 20, 2012 at 12:29 AM, Anne van Kesteren <ann...@annevk.nl
On Tue, Jun 19, 2012 at 10:52 PM, Olli Pettay <olli.pet...@helsinki.fi
> 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
> 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 doesn't say anything about this. And because it doesn't special case
parser initiated mutations,
those mutations should be there.
That is, that MutationObservers are not specified to be notified
of actions taken by the parser.
That would be still very odd. The randomness that there is, is visible to
scripts already now.
You can't know the size of network packages, so you can't know exactly now
documents are parsed etc.
It would be also odd for scripts which use mutation observer to start working
document enters into some state (readyState == "complete" or some such).
During page load user initiated events could cause all sorts of mutations but
there wasn't a way to get notified
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 changed.
Anne, Ian, Olli, Jonas, your thoughts?