User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36 Edg/88.0.705.81

Steps to reproduce:

1. Navigate to the URL: https://codepen.io/pen/

2. Paste the following code:

    <select>
       <option>hello</option>
       <option>world</option>
    <select> 
   

3. Click on dropdown and verify if it is getting expanded automatically without mouse release.

Actual results:

Drop-down expands before mouse release.

Expected results:

Drop-down shouldn't expand until after release.

Why that expectation?

GTK, macOS, and other browsers on Windows at least seem to expand the list on mousedown as well.

Do you know of equivalent change requests for other browsers?

CCing Jamie and Morgan since this is a sort of A11Y issue I think.

I don't understand this expectation either. Even native Win32 ComboBox dropdowns behave the same way: they drop down on mouse down, not mouse up. I'm also not clear how the current behaviour adversely impacts people with disabilities. Can you please clarify?

Olli told me on Matrix that the behavior depends on OS, indeed on Windows 10, it looks like drop down list opens when releasing mouse button. This is opposed to the behavior Jamie's commented in comment 3, interesting. I am seeing it in Settings > Display settings.

FWIW, Mac and Linux opens it on mouse down.

(In reply to Hiroyuki Ikezoe (:hiro) from comment #4)

Olli told me on Matrix that the behavior depends on OS, indeed on Windows 10, it looks like drop down list opens when releasing mouse button. This is opposed to the behavior Jamie's commented in comment 3, interesting. I am seeing it in Settings > Display settings.

It seems Windows itself is inconsistent. XAML dropdowns (like the one in the new Display Settings) drop down on mouse up as you say. However, Win32 ComboBox controls (such as the "Files of type" dropdown in file open dialogs) drop down on mouse down.

It's unclear to me if there is anything we should be changing here. It sounds like the behavior is reasonable/widespread; should we just close this as INVALID (or WONTFIX), or is there more needed?

@Reporter: could you follow up in the light of the comments above, and clarify if you think there's a reason to make a change here? Thanks.

Given comment 5, I think this should be wontfix unless the reporter can provide a strong argument to the contrary.

I just wanted to acknowldge the research, discussion and conclusion here. We will not provide any argument to fix it.

Alright, thank you for the reply :)