Chris Carson

I agree with @dummdidumm: > it's essentially two very separate things Submitting a GET form is just like clicking on a link. The difference between `?search=foobarbaz` and `?page=2` is nil....

> It's way more common for people to use on:event on the exact element the event triggers. We're not going to give up most of the cases we can catch...

> Agree that this is a less common use case What's the common use case? Trying to game the semantics and turn a div into a link? `contenteditable`? I can...

User agents check for `tabindex` to determine whether a semantically non-interactive element (let's just say "div") is in the accessibility tree ("the tree".) By contrast, the Svelte a11y linter considers...

> You are just way too optimistic about this. This is assuming that there even is any keyboard testing to begin with. That's as may be (I haven't been accused...

@oscarhermoso Your [example](https://svelte.dev/repl/00047dfff155430d9be9a14d9fe66855?version=4.1.1) seems to prove my point. The `LogWrapper` component isn't doing any harm. It's not masquerading as a button or a link or some other interactive thing that...

> but accessibility is impacted, because there's an interaction that can be accessed by mouse but not keyboard @oscarhermoso, fair enough. Your point might be better made / more easily...

I don't understand why the callback is called before each run of `$effect`, rather than just when the component is destroyed. Not saying it's wrong to do so -- I...

@MotionlessTrain Thanks, I get it. If in your example `el` was a property of the component (not a bound html element in the component's own markup) we'd have remove the...

> ~~Notably, this seems to occur only when binding arrays (and possibly other special things,) but not pojos.~~ I tried, but failed, to figure out the difference in my repro....