Closed Bug 1092425 Opened 5 years ago Closed 5 years ago
System apps should follow text selection pattern
See System pages of attached spec. * 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 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);
Assignee: nobody → gduan
Hi Alive, could you check if it's ok for system? However, if it's merged and default turn on noneditable selection, user would be hard to hide text selection dialog by tapping -user-select: none , bug 1089979 will fix it.
Attachment #8519653 - Flags: review?(alive)
Attachment #8519653 - Flags: review?(alive) → review+
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.