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
The first question is, should select elements fire click events only when an option is selected, when an option is selected and when the select option menu is opened, only when the select option menu is opened, or never? Additionally, whichever decision is reached, I imagine for accessibility reasons the event should be fired when these events are triggered by the keyboard, but that should also probably be clarified.
The second question is, should option elements fire click events when the option is selected, either with a mouse or with the keyboard, or should they not fire click events?
As you can see by the listed issues above, cross-browser consistency for this does not exist.
This issue was opened at the request of the Firefox devs in the first listed issue.
The text was updated successfully, but these errors were encountered:
Similar, but not the same as #1092. See also https://bugzilla.mozilla.org/show_bug.cgi?id=1767062, https://bugs.webkit.org/show_bug.cgi?id=239964, https://bugs.webkit.org/show_bug.cgi?id=240135, and https://bugs.chromium.org/p/chromium/issues/detail?id=1323015.
The first question is, should select elements fire click events only when an option is selected, when an option is selected and when the select option menu is opened, only when the select option menu is opened, or never? Additionally, whichever decision is reached, I imagine for accessibility reasons the event should be fired when these events are triggered by the keyboard, but that should also probably be clarified.
The second question is, should option elements fire click events when the option is selected, either with a mouse or with the keyboard, or should they not fire click events?
As you can see by the listed issues above, cross-browser consistency for this does not exist.
This issue was opened at the request of the Firefox devs in the first listed issue.
The text was updated successfully, but these errors were encountered: