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

[css-ui-4] user-select inheriting into absolutely positioned elements

From: Florian Rivoal <florian@rivoal.net>
Date: Mon, 1 Jun 2015 10:59:22 +0200
Message-Id: <5E3FAE5B-A437-45CE-8BEB-B87169887F54@rivoal.net>
To: www-style list <www-style@w3.org>
The specification for this user-select (http://dev.w3.org/csswg/css-ui-4/#content-selection), drawing inspiration from Mozilla's implementation, made user-select not inherit* into absolutely positioned children.

However, in parallel, Mozilla just changed its implementation, and now does inherit* into absolutely positioned children.

https://bugzilla.mozilla.org/show_bug.cgi?id=1129356

Reading through bugzilla, it seems that the motivation for this fix was a mix of:
a - aligning with other browsers
b - addressing some uses cases (primarily in firefox os)
c - following the old and obsolete http://www.w3.org/TR/2000/WD-css3-userint-20000216#user-select draft

I don't expect absolute positioning of children of a user-select:none element is particularly common, so while 'a' is a valid reason, it's probably not overwhelming. 'c' is not really a relevant reason.

'b' is relevant and a good justification, so I think we should probably change the spec to let user-select inherit* into absolutely positioned children.

At the same time, the old behavior was probably introduced for a reason, and it would be nice to see use cases outside of firefox os to help decide one way or the other. 

Anyone wants to defend the old Mozilla behavior, or should I go ahead and adjust the spec?

 - Florian

* As described in the spec, this isn't technically inheritance, just computed value magic to effectively do selective inheritance, but it is more easily phrased this way.
Received on Monday, 1 June 2015 08:59:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:54 UTC