Closed Bug 859941 Opened 11 years ago Closed 11 years ago

Unable to dismiss keyboard on desktop B2G client by tapping another element

Categories

(Remote Protocol :: Marionette, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: davehunt, Assigned: mdas)

References

Details

Attachments

(1 file)

Attached file Reduced test case
The keyboard should be dismissed when tapping another element. For example, after entering a contact name and tapping done. This works manually, and when running tests against a device, but does not work against the desktop build.

I have attached a reduced test case that reproduces this issue. To run it you can use the following command line, replacing the path with the location of a desktop build.

Note that you will need to manually bring the desktop client to the foreground otherwise the keyboard will not be displayed. Also, I recommend backing up your profile as for some reason running the tests puts the profile in an unusable state. Both of these issues will be fixed in the next release of the Marionette client.

$ gaiatest --binary=/Applications/B2G.app/Contents/MacOS/b2g-bin --profile=/Applications/B2G.app/Contents/MacOS/gaia/profile test_dismiss_keyboard.py
Assignee: nobody → mdas
Interesting note, if you replace the tap() on the save-button element with a click(), then the keyboard is dismissed. We're updating what marionette's single_tap will do here Bug 850819 (and eventually what tap() will do here: Bug 845849. I'm going to build with these changes and see if they fix this behaviour
This is fixed by replacing marionette.tap(element) with element.tap()
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Blocks: 869034
No longer depends on: 869034
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: