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:

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.


Reply via email to