hide selection handle when start typing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
David Barth | ||
Oxide |
Fix Released
|
High
|
Olivier Tilloy | ||
1.15 |
Fix Released
|
High
|
Olivier Tilloy | ||
1.16 |
Fix Released
|
High
|
Olivier Tilloy | ||
webbrowser-app (Ubuntu) |
Invalid
|
High
|
Olivier Tilloy |
Bug Description
we are showing the selection handle (in addition to the cursor) whenever entering a text field that already has text in it. For example, if you are replying to a Gmail message, you have an annoying blue selection handle blinking where you are trying to type and you can't turn it off. Or on a form, focusing on a field to append text will also show the selection handle. Or a multi line text area, adding a new line and typing at the beginning.
Tested Chrome on Android and it behaves differently, and think we should do similar:
1. Show the selection handle initially, but have it disappear when you press any key (space, character, etc.)
2. Tapping anywhere in the field will cause handle to be shown again
3. Also, can we put the selection handle on the bottom of the cursor instead of the top? This is the behavior on Chrome for Android and the rest of our non-html platform in Ubuntu touch.
Related branches
Changed in webbrowser-app (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Olivier Tilloy (osomon) |
status: | New → Confirmed |
Changed in canonical-devices-system-image: | |
milestone: | none → 12 |
assignee: | nobody → Bill Filler (bfiller) |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in oxide: | |
status: | In Progress → Fix Released |
Changed in canonical-devices-system-image: | |
milestone: | 12 → 13 |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
TouchSelectionC ontrollerClient Aura::EnvPreTar getHandler is relevant: it listens to key, mouse and scroll events, and hides the insertion handle as soon as one of those events is registered.
ui::EventTarget is not used in oxide though, so we’d need to monitor input events at a different level.