Dropdown key events handling fix - v5 #30529
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please see #30510 for details. Two new unit tests added. "npm run test" was finished without errors.
It was needed to add following fix from v4: #28912. After this cyclomatic complexity of
dataApiKeydownHandler
was higher than allowed in your ESLint configuration, so I extracted_isDropDownCommand
method.Additionally I fix some by catch error of variables assignment in "should ignore keyboard events for s and <textarea>s within dropdown-menu, except for escape key" test.
Fixes #30510