Further update: I can’t reproduce the issue with "normal" text fields
(tested bing.com and yahoo.com, the issue isn’t present).
Tested again google.com, and I can’t reproduce the issue by only
clearing the field with backspace. For the bug to be observed, I first
have to clear the current uncommitted word with the "X" icon, then type
something else, then erase it with backspace, then hit backspace again
in the empty field, and the first word (that was cleared by "X") is
restored.
It seems there are two issues there, and my guess is that both are in oxide:
- when the field is cleared with the "X" icon, we don’t cancel the current
composition
- when pressing backspace in an empty text field, the event should be ignored
** Summary changed:
- [browser] Clearing text entry with backspace restores the previously
uncommitted word
+ Current composition is not canceled when a text input field is cleared
programmatically
** Changed in: ubuntu-keyboard
Status: New => Invalid
** Changed in: oxide
Status: New => Confirmed
** Changed in: oxide
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384357
Title:
Current composition is not canceled when a text input field is cleared
programmatically
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1384357/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
