- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 18 Aug 2015 11:00:33 +0200
- To: Domenic Denicola <d@domenic.me>
- Cc: public-webapps <public-webapps@w3.org>
Thank you for writing this up. Would be interesting to hear what Maciej and Ryosuke think. On Tue, Aug 18, 2015 at 12:19 AM, Domenic Denicola <d@domenic.me> wrote: > - Use symbols instead of strings for custom element callbacks. So the way this is done is that they are publicly available on the prototype. Does that mean behavior can change during the lifetime? What does that mean for builtin elements that do not have these callbacks on their prototype? Also, we probably need to rename registerElement() due to the different semantics. Also, you want to sort the attributes in some way before calling attributeChanged from upgrades, or we must finally agree on that attributes are sorted in some deterministic way: https://www.w3.org/Bugs/Public/show_bug.cgi?id=17871 I also thought the idea was to pass attached/detached their changed ancestor and perhaps rename them inserted/removed (and no longer scope them to document change). -- https://annevankesteren.nl/
Received on Tuesday, 18 August 2015 09:01:01 UTC