W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2014

Re: Extending Mutation Observers to address use cases of

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Wed, 12 Feb 2014 03:52:43 +0200
Message-ID: <52FAD3EB.6090708@helsinki.fi>
To: Ryosuke Niwa <rniwa@apple.com>, "public-webapps@w3.org WG" <public-webapps@w3.org>
CC: Erik Arvidsson <arv@google.com>, Anne van Kesteren <annevk@annevk.nl>, Jonas Sicking <jonas@sicking.cc>
On 02/12/2014 03:41 AM, Ryosuke Niwa wrote:
> Hi,
>
> Iím bringing this up out of:
>
> [Custom]: enteredView and leftView callbacks are still confusing
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=24314
>
> Could someone clarify exactly why mutation observers canít satisfy use cases for custom elements?
>
> I strongly believe that we should extend mutation observers (e.g. add some flag to fire more eagerly) so that we could *explain* these callbacks in terms of mutation observers.
>
> - R. Niwa
>
>


Doesn't the web component stuff want to be notified way before mutation observer callbacks are called (end of microtask)
This new stuff would be called right before some dom method call returns (I think someone mentioned 'nanotask').


We could add some scheduling thing to mutation observers. By default we'd use microtask, since that tends to be good
for various performance reasons, but normal tasks or nanotasks could be possible too.



-Olli
Received on Wednesday, 12 February 2014 01:53:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:21 UTC