brunnerh

How is that a counter argument? This is just string interpolation in exactly the way I expect it to work. (Same as in element text content.)

Sure, it's just a minor thing anyway.

Notes on current Svelte 5 preview ([REPL](https://svelte-5-preview.vercel.app/#H4sIAAAAAAAACkVQwU7EIBD9lZE12d3EhBpvlTbx6N2b9YB02hIpNDBdYwj_LrCaPc28x3szj4ls0gYDa98js3JF1rKXbWMPjH62AsIFDWHGwe1eFUYE5fVG_WAH0uvmPEGEoKRBSDB5t8LxauLkpQ2atLPH56JWzgYC5XZL0MFj0zSVNkgQFveduftAkvA0SRPwnB8Fvy2z4nMnchacVUarry6eztD1_9a7UlP_5ubZoOBXbfXFA0q15JAG7UxL-5cggQygU0kQD3qqcyoaSIz6Arf0bf1dF-O4e1kJeGqalPpXwlXwLK7HiFxPeUDkZV1u8tFWN-pJ48ha8jumj_QL9MaYfG8BAAA=)): Outros have become slower in Firefox, from 300ms. Chromium is still slow in both directions.

It would be convenient, but you already can get pretty close using actions. Something along the lines of: ```js export function focused(node, store) { const onChange = () => store.set(document.activeElement...

I do not think so. You need some way to bridge reactivity between component and non-component code.

I'd say the main reason to have this would be the write access: You can focus the element declaratively *without* using `bind:this` first or using an action.

I highly doubt the "probably legit" part. People adding click handlers on divs, unaware of any problems, is very common. And I would agree with the maintainers that valid cases...

> The problem would surface with a bare minimum of keyboard testing You are just way too optimistic about this. This is assuming that there even is *any* keyboard testing...

I suspect that `untrack` mainly exists for `$effect`, so an entire block of logic, regardless of how many variable references it contains, can be excluded. ```js $effect(() => { //...

I'd say that is somewhat expected if you know how the update sequence works. `$`-notation variables are local to the component, but the change is triggered in a different component...