Maybe this is a stupid question, but why does the `slotchange` event exist? A mutation observer can do the one thing slotchange can do, but also much more. #javascript #WebComponents #shadowDOM
@noleli timing is an issue. Mutation observers only fire when something changes. So they won't fire on the initial value (slot change will). Also if you use dynamic slot assignment (change slot but not children) MO wont fire
@noleli I do wish slotchange would tell your WHAT changed. Like how MO has which nodes were added and removed.