Closed npm1 closed 3 years ago
It's possible for a user interaction to change values in a <select> without having one of the events that the spec currently considers for hadRecentInput. See for example https://tamethebots.com/select-recent-input-bug.html, from https://bugs.chromium.org/p/chromium/issues/detail?id=1120282. The popup consumes the click when you select from the dropdown, so we want to consider the change event separately as a way to trigger hadRecentInput.
<select>
It's possible for a user interaction to change values in a
<select>without having one of the events that the spec currently considers for hadRecentInput. See for example https://tamethebots.com/select-recent-input-bug.html, from https://bugs.chromium.org/p/chromium/issues/detail?id=1120282. The popup consumes the click when you select from the dropdown, so we want to consider the change event separately as a way to trigger hadRecentInput.