You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug sl-change event on <sl-select> is fired right after it was created. This behavior is different from the native <select>change event which is fired only after a user chooses a new value. When using <sl-select multiple> the sl-change event is fired two times on init.
To Reproduce
I prepared example in Lit playground: example
Expected behavior sl-change event on <sl-select> should not be dispatched on init (not once, not twice).
Desktop (please complete the following information):
OS: Windows 10
Browser chrome
Version 91.0.4472.77
The text was updated successfully, but these errors were encountered:
Thanks for reporting this. Since select doesn't map to an actual form control, the sl-change event is simulated and was firing prematurely during init. This fix will be in beta.44.
Describe the bug
sl-change
event on<sl-select>
is fired right after it was created. This behavior is different from the native<select>
change
event which is fired only after a user chooses a new value. When using<sl-select multiple>
thesl-change
event is fired two times on init.To Reproduce
I prepared example in Lit playground: example
Expected behavior
sl-change
event on<sl-select>
should not be dispatched on init (not once, not twice).Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: