* 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);

Take it. Should be a one liner.

This is a 2.2 feature.

Comment on attachment 8525835 [details] mozilla-b2g:master PR#26318 This is the only rules needed for Keyboard Settings page.

Comment on attachment 8525835 [details] mozilla-b2g:master PR#26318 r=me, thanks. I found an issue that when you long press on the bottom blank part of the keyboard settings page, it would still pop up 2 caret handlers in front of the Word suggestion item. But I would suppose this is a platform issue?

master: https://github.com/mozilla-b2g/gaia/commit/b981d2fe67d8de3e83e8b1f2625d2f89c6d1ce2f