- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 16 Jul 2015 19:17:33 +0200
- To: Domenic Denicola <d@domenic.me>
- Cc: Olli Pettay <olli@pettay.fi>, Travis Leithead <travis.leithead@microsoft.com>, public-webapps <public-webapps@w3.org>
On Thu, Jul 16, 2015 at 6:49 PM, Domenic Denicola <d@domenic.me> wrote: > Even if it can be specced/implemented, should it? I.e., why would this be OK where MutationEvents are not? Apart from the verbosity and performance issues with mutation events, I think the main problem with mutation events has been the lack of a clear processing model (and that is true to this day), causing crashes in user agents: https://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0779.html In other words, the specification authors invented something, but didn't do the due diligence of writing down how that invention would actually impact the overall model. (This is a problem to this day. E.g., UI events.) So the main problem with custom constructors seems to be the processing model, combined with the work of actually implementing and vetting that. -- https://annevankesteren.nl/
Received on Thursday, 16 July 2015 17:17:59 UTC