Closed Bug 1094009 Opened 7 years ago Closed 7 years ago
Settings 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);
This is a 2.2 feature.
feature-b2g: 2.2? → 2.2+
EJ, could you help review this simple patch? Thanks.
Assignee: nobody → arthur.chen
Comment on attachment 8537082 [details] link to https://github.com/mozilla-b2g/gaia/pull/26814 Arthur, I think we have to whitelist down needed input types instead of make all of them selectable, please check my comments on GitHub, thanks !
Comment on attachment 8537082 [details] link to https://github.com/mozilla-b2g/gaia/pull/26814 Comment addressed. Please help review it again, thanks.
Comment on attachment 8537082 [details] link to https://github.com/mozilla-b2g/gaia/pull/26814 Thanks Arthur ! r+
Attachment #8537082 - Flags: review?(ejchen) → review+
Thanks, EJ! master: 58734e8a48157f99d5b733412b600c2e04c954fe
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.