Originally reported as b/35863435.
Repro steps:
1. Turn off predictive text on Samsung keyboard.
2. Type google.com and go to google.com
3. Type goo
4. The second 'o' does not get typed.
4 out of 100 tries
Samsung did a bit more analysis and found that typing sometimes fails on URL bar because input gets restarted, with the following stack traces:
InputMethodManager.startInputInner(int, IBinder, int, int, int) line: 1612
InputMethodManager.restartInput(View) line: 1587
UrlBar(TextView).setText(CharSequence, TextView$BufferType, boolean, int) line: 4999
UrlBar(TextView).setText(CharSequence, TextView$BufferType) line: 4936
UrlBar(EditText).setText(CharSequence, TextView$BufferType) line: 111
UrlBar.setText(CharSequence, TextView$BufferType) line: 865
UrlBar(TextView).setText(CharSequence) line: 4911
UrlBar.setUrl(String, String) line: 747
UrlBar.setAutocompleteText(CharSequence, CharSequence) line: 779
LocationBarPhone(LocationBarLayout).onSuggestionsReceived(List, String) line: 1985
AutocompleteController.onSuggestionsReceived(List, String, long) line: 212
SystemMessageHandler.nativeDoRunLoopOnce(long, long, long) line: not available [native method]
SystemMessageHandler.handleMessage(Message) line: 41
SystemMessageHandler(Handler).dispatchMessage(Message) line: 102
Looper.loop() line: 154
ActivityThread.main(String[]) line: 6776
Method.invoke(Object, Object...) line: not available [native method]
ZygoteInit$MethodAndArgsCaller.run() line: 1520
ZygoteInit.main(String[]) line: 1410
I can take a look.
Comment 1 by changwan@chromium.org
, Jul 7 2017