- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 12 Aug 2015 19:19:21 +0200
- To: Wilson Page <wilsonpage@me.com>
- Cc: WebApps WG <public-webapps@w3.org>
On Mon, Aug 10, 2015 at 3:17 PM, Wilson Page <wilsonpage@me.com> wrote: > I was unable to attend the latest F2F so would like clarification on what > the takeaway action items were and who is responsible for pushing them > forward. I don't believe this information was included in the minutes. I think an interesting list of things to do is https://gist.github.com/dglazkov/3a709f3f6768b835dab1 which basically requires some research in implementations. Part of the argument at the F2F was about whether invoking JavaScript during DOM mutations was a lost cause or not. Ryosuke made a good case that it might be, but the Chrome folks were willing to try and disprove that. (I think everyone is agreed that if we don't have, that would be better.) The other argument was about consistency of the world at the time callbacks are invoked. Whether you can observe children and attributes during the "created" callback for instance, which if you rely upon that would result in issues if your component was ever created through createElement(). If you invoke JavaScript during DOM mutations this is not a problem. Otherwise it might be, though https://github.com/w3c/webcomponents/issues/287 is doing some exploring to see if we can "hide" certain things. None of this seems like something we'll have resolved soon though :-/ -- https://annevankesteren.nl/
Received on Wednesday, 12 August 2015 17:19:46 UTC