[🐛 Bug]: selectByIndex doesn't fire the "input" event in Chrome · webdriverio/webdriverio#14831

(4 留言) (0 反應) (1 負責人)JavaScript (6,029 star) (1,793 fork)batch import

Bug 🐛help wanted

描述

Have you read the Contributing Guidelines on issues?

I have read the Contributing Guidelines on issues.

WebdriverIO Version

9.20.0

Node.js Version

24.8

Mode

WDIO Testrunner

Which capabilities are you using?

What happened?

I tried to use the API selectByIndex and realized that the input event wasn't dispatched in Chrome. I tested both chrome stable and canary versions.

It's not clear to me if this is a bug in webdriver.io or a bug in Chrome BiDi implementation, because webdriver.io implementation is finally just a click: https://github.com/webdriverio/webdriverio/blob/e86efccd84e20b01713a43113d166d8deb397edc/packages/webdriverio/src/commands/element/selectByIndex.ts#L33-L70

My understanding is that the Chrome implementation is in https://source.chromium.org/chromium/chromium/src/+/main:chrome/test/chromedriver/element_commands.cc;l=285-297, and ultimately to this minified JS, but it's difficult for me to go beyond that.

What is your expected behavior?

The input event should be triggered and dispatched.

How to reproduce the bug.

Clone the project https://github.com/julienw/webdriver-select-by-index-bug
Run npm install
Run npm test

=> notice this fails in chrome but not in Firefox

Relevant log output

Nothing seems relevant

Code of Conduct

I agree to follow this project's Code of Conduct

Is there an existing issue for this?

I have searched the existing issues

貢獻者指南

技術棧: javascripttypescriptnodejs
領域: testing
議題類型: bug
難度: 3
預計時間: half day
活動狀態: needs maintainer response
清晰度: mostly clear
前置要求: JavaScript basicsWebdriverIO fundamentalsChrome DevTools
新手友善度: 35
研究方向: Investigate the WebdriverIO selectByIndex implementation in packages/webdriverio/src/commands/element/selectByIndex.ts and compare with the ChromeDriver atoms in third party/selenium atoms/atoms.cc. Focus on why the 'input' event is not dispatched in Chrome. Consider adding a synthetic event dispatch after selecting the option or using alternative WebElement methods. Check linked issue for reproduction steps and test in both Chrome and Firefox to confirm behavior.