Closed Bug 1092961 Opened 7 years ago Closed 7 years ago
Clock app to follow text selection pattern
* Input fields (input areas, input dialogs and search fields) are the only Building Blocks with selectable text. * HTML elements like buttons or links, or events like ontouchstart or onclick, should trigger the action when tapped rather than triggering text selection.
The Gecko work is close to completion, the remaining part is to fix test case failures then pref it on in m-c bug 1092888. After the bug landed, text selection and cut/copy/paste can be triggered in apps on both editable and non-editable elements. Gaia per app work in v2.2 is to follow UX guideline and leverage CSS -moz-user-select https://developer.mozilla.org/en-US/docs/Web/CSS/user-select to make certain elements non-selectable. Before Gecko is pref on in m-c, Gaia can manually switch it on by the following two pref to test in advance: pref("selectioncaret.enabled", on); pref("selectioncaret.noneditable", on);
The only selectable field I see in Clock is the "Alarm name" field when creating/editing an alarm and the selection already works there. Is there anything else to be done?
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
That's great, that's it for clock, thanks.
QA Whiteboard: [2.2-feature-qa+] → [2.2-feature-qa+] [textselection]
QA Whiteboard: [2.2-feature-qa+] [textselection] → [2.2-feature-qa+] [COM=Text Selection]
You need to log in before you can comment on or make changes to this bug.