If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Tap() wont work in "Test UI > Keyboard Test", but click() works

RESOLVED WORKSFORME

Status

Testing
Marionette
RESOLVED WORKSFORME
5 years ago
3 years ago

People

(Reporter: ypwalter, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [touch])

(Reporter)

Description

5 years ago
This bug is migrate from https://github.com/mozilla/gaia-ui-tests/issues/333 with suggestion of malini.

I was writing testing scripts of keyboard in gaia-ui-test.

However, I found an interesting issue:
STR
1. When you try to automatically testing in "Test UI" app.
2. Enter keyboard tests
3. Switch to keyboard and use the following code.
text = self.marionette.find_element('css selector', "input[type='text']")
textarea = self.marionette.find_element('css selector', 'textarea')

text.click()
textarea.click()
Click() for input column in view would work.

However,
self.marionette.tap(text)
self.marionette.tap(textarea)
Won't work proper. Click() still works, but tap(doesn't work)
Suspect there is an issue to tap/focus the elements here.

I tried to do some changes. I found that WebElement.focus() kind of works but not the behavior we expect.

Please help on investigation if you have a fix or any ideas.
I would also try to contribute to this issue and report the most up-to-date status.
Depends on: 869034
Blocks: 869034
No longer depends on: 869034
I can't seem to locate the text/textarea fields in the 'UI tests' app after selecting the Keyboard tests, can you repeat the STR and see if they still work for you? If not, can you update the STR?
Whiteboard: [touch]
Keywords: ateam-marionette-goal, ateam-marionette-userinput
Keywords: ateam-marionette-goal, ateam-marionette-userinput

Comment 2

3 years ago
Original test case is gone but I checked tap for all textarea fields on the new version of UI Tests and they all work correctly.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.