[css-ui-4] rename user-select: element to contain

css-ui-4/Overview.bs

@@ -413,7 +413,7 @@ Omitted values are set to their initial values.
 
 	<pre class='propdef'>
 		Name: user-select
-		Value: auto | text | none | element | all
+		Value: auto | text | none | contain | all
 		Initial: auto
 		Inherited: no
 		Applies to: all elements
@@ -431,7 +431,7 @@ Omitted values are set to their initial values.
 	except:
 	<ol>
 		<li>on <a>editable element</a>s
-		where the computed value is always ''user-select/element''
+		where the computed value is always ''user-select/contain''
 		regardless of the specified value
 		<li>when the specified value is ''user-select/auto'',
 		which computes one of the other values as defined below
@@ -455,7 +455,7 @@ Omitted values are set to their initial values.
 		<dd>The computed value of ''user-select/auto'' is determined as follows:
 		<ul>
 			<li>If the element is an <a>editable element</a>,
-			the computed value is ''element''
+			the computed value is ''contain''
 			<li>Otherwise,
 			if the computed value of 'user-select' on the parent of this element is ''all'',
 			the computed value is ''all''
@@ -469,7 +469,7 @@ Omitted values are set to their initial values.
 		whose computed value depends on the parent element
 		makes it possible to create what is effectively selective inheritance.
 		This was initially proposed by Microsoft in IE to introduce a behavior similar to inheritance
-		except that the ''element'' value does not inherit.
+		except that the ''contain'' value does not inherit.
 
 		<dt><dfn>text</dfn>
 		<dd>The element imposes no constraint on the selection.
@@ -539,7 +539,7 @@ Omitted values are set to their initial values.
 		that would hamper usability
 		or violate common user expectations.
 
-		<dt><dfn>element</dfn>
+		<dt><dfn>contain</dfn>
 		<dd>UAs must not allow a selection which is started in this element
 		to be extended outside of this element.
 
@@ -552,12 +552,12 @@ Omitted values are set to their initial values.
 
 		Note: At the time of writing, experimental implementations behave differently from eachother
 		about selections started outside and selections going into the element.
-		The behavior can be observed even on browsers that do not explicitly support ''element''
+		The behavior can be observed even on browsers that do not explicitly support ''contain''
 		by trying to select into a <{textarea}> or a contenteditable element.
 
-		Issue: Not sure the name ''user-select:element'' is particularly clear
-		about what this means.
-		How about something like "contain" or "inside" instead?
+		Note: This was initially introduced
+		as an experimental feature in Internet Explorer,
+		under the name <code>user-select: element</code>.
 
 		<dt><dfn>all</dfn>
 		<dd>The content of the element must be selected atomically: