You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebDriver key actions don't cover the case of IME inputs, in which multiple composition events end up inserting one or more characters that don't directly map to the keys pressed. This represents a problem for testing web editors which need to handle IME related events specifically.
It makes sense to model this input as actions, because it represents a series of input events that can be interleaved with other input events (e.g. mouse clicks).
Gecko has a couple of test APIs which demonstrate the detailed functional requirements; obviously the details need to change to fit into the WebDriver model, but I propose using those as a guide to what we need to support to be useful for testing web editors.
The text was updated successfully, but these errors were encountered:
WebDriver key actions don't cover the case of IME inputs, in which multiple composition events end up inserting one or more characters that don't directly map to the keys pressed. This represents a problem for testing web editors which need to handle IME related events specifically.
The relevant web specification here is https://w3c.github.io/uievents/#events-compositionevents
It makes sense to model this input as actions, because it represents a series of input events that can be interleaved with other input events (e.g. mouse clicks).
Gecko has a couple of test APIs which demonstrate the detailed functional requirements; obviously the details need to change to fit into the WebDriver model, but I propose using those as a guide to what we need to support to be useful for testing web editors.
The text was updated successfully, but these errors were encountered: