Bug 131642 - [iOS] WebEditorClient::textDidChangeInTextField always thinks that the change is not caused by user typing
Summary: [iOS] WebEditorClient::textDidChangeInTextField always thinks that the change...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit API (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-14 15:34 PDT by mitz
Modified: 2014-04-14 15:34 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mitz 2014-04-14 15:34:22 PDT 
The way text input is handled in the iOS port makes it so that by the time WebEditorClient::textDidChangeInTextField is called, UserTypingGestureIndicator::processingUserTypingGesture() is already returning false. For this reason, the WebKit1 implementation of this client function disables the user-gesture check when targeting iOS.

We should fix handling of typing on iOS so that the client function can distinguish between programmatic changes and user-typing-initiated changes.