* 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.

This bug has been sitting in my queue for a couple of weeks. I've just reviewed similar patches for Video and Gallery, which has made me realize that this patch won't be trivial like those were because the Music app has a search feature that needs to have text selection enabled. Dominic: is this a bug you can take? If not, please ask Jim to take it.

Sure, I can take this.

Once we know the possible effort, it would be great if you could update the target milestone. Thanks.

Jim, would you please review this patch? thanks.

(In reply to Kevin Hu [:khu] from comment #5) > Once we know the possible effort, it would be great if you could update the > target milestone. Thanks. After wrote the patch I realized this is a simple fix so should be okay to be landed by this week(If Jim get the review request), and I will just choose the closest milestone, thanks.

Comment on attachment 8540198 [details] patch I'm not quite sure how to test this out, but by inspection, this looks good. rs=me.

Thanks Jim! master: https://github.com/mozilla-b2g/gaia/commit/0db8a38f9fed18ae2abf5ef7e1b6e2a570b07e0e