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
I fire a change event on my input with datalist. In Chrome and Edge (native behaviour), it fire the event as soon as I press enter on an item. With the polyfill (in Firefox) the item is set to the input on enter, which means I need to press enter one more time in order for the event to fire.
The text was updated successfully, but these errors were encountered:
I've recognized that this seems to be the standard behaviour in Firefox for <datalist> HTML element, independently from the usage of this polyfill. So in general I agree with you that it's bad to have this inconsistency, but I sadly don't know the exact specified behaviour (either one might be incorrect). Have you already done some research on this aspect?
And what would you suggest? I think to remember that triggering an event in this case might be a little problematic, as we both wouldn't want to "browser (version) detect" and as well couldn't feature detect the differences in event handling, and that for should rather get aligned at the browser level than solving it within the polyfill.
@mfranzke I've just noticed that it works differently in Chrome + Edge (native) compared to Firefox (polyfill). I've not investigated it more than that.
You can leave this open or close it depending on if you want / can fix it or not.
I fire a change event on my input with datalist. In Chrome and Edge (native behaviour), it fire the event as soon as I press enter on an item. With the polyfill (in Firefox) the item is set to the input on enter, which means I need to press enter one more time in order for the event to fire.
The text was updated successfully, but these errors were encountered: