- From: Domenic Denicola <notifications@github.com>
- Date: Thu, 10 Mar 2016 10:15:43 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Thursday, 10 March 2016 18:17:02 UTC
One result of internal discussion so far is that @esprehn would prefer "no" for the two "unresolved questions" in https://github.com/w3c/webcomponents/issues/419#issuecomment-194640804. Since that's the first concrete implementer preference we've seen I'll change the spec in that direction. And comments like https://github.com/w3c/webcomponents/issues/419#issuecomment-194905641 imply that even though I thought it would be more developer-friendly that way, it might just be confusing, so all evidence is leaning toward that. So---elements created during fragment parsing and during cloning will not auto-upgrade. (Hmm, I'll rename the flag to auto-upgrade, instead of upgradeable.) --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/419#issuecomment-194984109
Received on Thursday, 10 March 2016 18:17:02 UTC