Re: [webcomponents] Need "slotting changed" event (#288)

@esprehn : That doesn't seem like a great developer ergonomics.  If that's acceptable, and the developers are expected to check whether something has changed for real and/or what has changed, then why don't we just fire an asynchronous event instead?

It just doesn't make sense for browsers to be creating useless mutation record objects for each potential change when the author is going to ignore all those records and check whether something has changed themselves.  It also makes mutation observer API less coherent because no other mutation type does this.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/288#issuecomment-186051279