[Problem/Bug]: Dropdown values cannot be selected

[repo-nio]

What happened?

Using latest version 134.0.3124.51, values in a dropdown cannot be selected.

See video and sample html code

NClient4.mp4

<h2>Select a Fruit:</h2>
<select name="fruits" id="fruits">
    <option value="apple">Apple</option>
    <option value="banana">Banana</option>
    <option value="orange">Orange</option>
    <option value="grape">Grape</option>
    <option value="mango">Mango</option>
</select>

<h2>Select a Car Make:</h2>
<select name="cars" id="cars">
    <option value="toyota">Toyota</option>
    <option value="honda">Honda</option>
    <option value="ford">Ford</option>
    <option value="bmw">BMW</option>
</select>

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

134.0.3124.51

SDK Version

No response

Framework

WPF

Operating System

Windows 10

OS Version

No response

Repro steps

1. Use sample code below
2. Click on dropdown
3. Values will show and disappear immediately.

<h2>Select a Fruit:</h2>
<select name="fruits" id="fruits">
    <option value="apple">Apple</option>
    <option value="banana">Banana</option>
    <option value="orange">Orange</option>
    <option value="grape">Grape</option>
    <option value="mango">Mango</option>
</select>

<h2>Select a Car Make:</h2>
<select name="cars" id="cars">
    <option value="toyota">Toyota</option>
    <option value="honda">Honda</option>
    <option value="ford">Ford</option>
    <option value="bmw">BMW</option>
</select>

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in version 134.0.3124.51
Working fine in v133

Last working version (if regression)

133.0.3065.92

[C-Wal]

Same here. Been trying to troubleshoot this all day.

[ambikakunnath]

The issue happens due to focus lose. Resolving as duplicate of [Problem/Bug]: input field of type text and name email loses focus #5144

[gourabkmsft]

On further investigation we have realized this is not the same issue as #5144. We have root caused the issue and are working landing it into v134 right now.

[bansal-mohit]

Update: This should be fixed in 134.0.3124.68 and is rolling out slowly.

[MarkusGit79]

Update: This should be fixed in 134.0.3124.68 and is rolling out slowly.

problem not solved with my device with version 134.0.3124.68.

[cp07451]

Can anyone confirm this works? Does the webview2 and the Edge broswer need to be updated? Or can one use 134.0.3124.68 with the previous Edge?