New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 876221 link

Starred by 1 user
Status: WontFix
Owner:
shend@chromium.org
Closed: Sep 21
Cc:
█ nek...@chromium.org
dmazz...@chromium.org
aboxhall@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

AutomationNode.doDefault doesn't trigger click events

Project Member Reported by shend@chromium.org, Aug 21 
Chrome Version: 70.0.3519.3
OS: ChromeOS

According to the code [1] [2], calling doDefault() on an input field or a textarea doesn't actually simulate click events; it only focuses.

Also can confirm the issue locally with a test extension using the automation API.

[1] https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/html/forms/input_type_view.cc?type=cs&sq=package:chromium&g=0&l=74

[2] https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/html/forms/html_text_area_element.cc?type=cs&sq=package:chromium&g=0&l=566

Comment 1 by nek...@chromium.org, Sep 13 

I don't understand why clicking would be necessary. If I place focus in an edit field using tab or shift+tab, clicking is not involved and the web app should be able to handle that. More importantly, if a platform were to exposes a set_focus API, does that mean it should also click every time it changes the focus?

Comment 2 by shend@chromium.org, Sep 13

Cc: nek...@chromium.org
Sorry for the lack of context in the bug. I was trying to use the automation API to write some UI integration tests for the ChromeOS virtual keyboard. For various reasons (see 642513), invoking the virtual keyboard requires a real click on a textfield.

After some discussion with dmazzoni@, it looks like it's very difficult for the automation API to simulate a "system-level" click that would invoke the virtual keyboard. So I'm probably going to use a different API to do the clicking.

So if you think that the current behaviour (doDefault on textarea does not click) is WAI, then I'm happy to close this bug :)

Comment 3 by shend@chromium.org, Sep 21

Status: WontFix (was: Assigned)
We found a workaround without using the automation API so marking as WontFix.
►

Sign in to add a comment