- From: Dominic Cooney <notifications@github.com>
- Date: Thu, 22 Sep 2016 01:59:29 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Thursday, 22 September 2016 08:59:59 UTC
Hmm, I'm not sure about that _copy's_ queue part. There are two elements involved so it is not clear which queue to use. Maybe you enqueue a reaction in *each* queue, and the first one to run cancels the other. We always have edge cases if an author's custom element callback reaches out and messes with the DOM. However this callback is a bit different because we always thought it was OK for an author to change the element's state. So crafty queue handling is trying to preserve that idea. -- 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/176#issuecomment-248847520
Received on Thursday, 22 September 2016 08:59:59 UTC