- From: Anne van Kesteren <notifications@github.com>
- Date: Tue, 29 Mar 2016 01:41:14 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Tuesday, 29 March 2016 08:41:44 UTC
I see. But that means user interface events and such can get in between and we're solving none of the problems we solved with mutation observers. Given such an implementation I think reusing the mutation observer machinery would be better. We could even make it so that there's at most one mutation record of this type in the queue, if that alleviates some concerns. It would make this record a little bit special, but I think that might be okay. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/288#issuecomment-202779633
Received on Tuesday, 29 March 2016 08:41:44 UTC