Conduitry

Ah! It looks like #6941 just handled the code for one-way binding. And that's all that was originally covered in #3449 and in #4179. So, the two-way binding mentioned here...

Is this an issue about empty elements blocks being added, or about style blocks being added dynamically at all? Svelte needs to be able add some styles dynamically to handle...

This should be fixed in 3.50.0.

Svelte adds the attributes to the element in the order that they are in the original source. If there are some situations (like lazy loading) where the order matters, this...

This is presumably the result of the `elm.setAttribute('width', whatever)` effectively becoming `elm.width = whatever;` when there's an attribute spread present, and the browser is presumably able to handle the normalization...

Fixed in 3.50.0 - https://svelte.dev/repl/a6eddb766f9e474c92e5a23ba0bba362?version=3.50.0

@arxpoetica For now, you can use a [custom `onwarn`](https://github.com/sveltejs/svelte#options) handler to filter out a11y-related warnings, with something like this: ``` { ... onwarn(warning, onwarn) { if (!/A11y:/.test(warning.message)) { onwarn(warning); }...

I don't think there is any issue with collisions between component parameters and existing DOM attributes. The only constraint I know of that we should be enforcing is that in...

That's a bad idea.

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font This element is deprecated, and I don't think we should be going much out of our way trying to support it. https://developer.mozilla.org/en-US/docs/Web/SVG/Element/font However, the SVG version of it is...