W3C home > Mailing lists > Public > www-style@w3.org > April 2015

[css-ui-4] user-select

From: Florian Rivoal <florian@rivoal.net>
Date: Thu, 2 Apr 2015 16:47:41 +0200
Message-Id: <7B03426A-8E14-46B1-B232-C8F2B4A69039@rivoal.net>
To: www-style list <www-style@w3.org>
Since CSS-UI level 3 is getting increasingly stable and nearing CR,
I've just started a level 4 draft as a diff spec.

I've started by adding 'user-select', which we had deferred from
level 3:

http://dev.w3.org/csswg/css-ui-4/#content-selection

There is general agreement between existing implementations about
which values should exist and what they mean, so I have not tried
to be creative about that.

However, the interop story is less nice when you look into the
details, as browsers disagree on the meaning of auto, computed
values, inheritance, applicability to editable elements...

The specification tries to strike a reasonable middle ground. It
tries to be close as possible to existing implementations when
they agree and make sense. When it diverges from some of the
implementations, I've either included a note saying why, or an
issue highlighting the disagreements.

Also, even though as of today, only IE supports the ''element''
value, I have included it because:

* Even browsers that do not explicitly support it have this
behavior on editable elements (<input>, <textarea>,
contenteditable elements...)

* It influences the overall design of the property in terms of
inheritance and computed values.

* Mozilla[1] and Tab[2] have expressed at least some interest in
having this value with similar semantics to IE.

Feedback most welcome.

 - Florian

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1036853
[2] https://lists.w3.org/Archives/Public/www-style/2014Nov/0541.html
Received on Thursday, 2 April 2015 14:48:05 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:30 UTC