adiGuba

> or reference to the instance (which we've resisted thus far, because 99% of the time when someone wants that reference it's to do something inadvisable)? I think this can...

Perhaps we can even use `this` for that, as it's currently undefined : ```svelte console.log(this); // "this" should be the current component instance ```

Hello, > I'd just love a way to be able to do something like this > > ```js > function action(...) { > // clientside only stuff > > return...

#11613 add a partial fix for this, and now these lines will produce a warning **state_proxy_equality_mismatch** : ```js items.findIndex(n => n === item); // WARN state_proxy_equality_mismatch ``` This is fine,...

It seem that the problem come from this check in set_value() : `element.value === value` ```js export function set_value(element, value) { // @ts-expect-error var attributes = (element.__attributes ??= {}); //...

It seem that the change come from #13574 in order to handle minlength/maxlength

Hello, From what I see, apart from innerHTML optimization (which is not used when using a variable on the template), some specific attributes like `value`, `checked` are not added to...

I successfully reproduced the bug with this REPL. I think I found the origin of the problem, I will try to make a PR...

Just in case, I generated the type based on the MDN ```ts export interface HTMLInputButtonAttributes = Omit; export interface HTMLInputCheckboxAttributes = Omit; export interface HTMLInputColorAttributes = Omit; export interface HTMLInputDateAttributes...

This is not about changing the existing `HTMLInputAttributes`, but about adding new and more precise types...