[css-values] Complete fork.

Author: fantasai

css-values-3/Overview.bs

@@ -20,8 +20,8 @@ Previous Version: https://www.w3.org/TR/2001/WD-css3-values-20010713/
 Editor: Tab Atkins, Google, http://xanthir.com/contact/
 Editor: fantasai, http://fantasai.inkedblade.net/contact
 Former Editor: Håkon Wium Lie, Opera Software, howcome@opera.com
-Abstract: This CSS3 module describes the common values and units that CSS properties accept and the syntax used for describing them in CSS property definitions.
-At Risk: ''toggle()'', ''attr()''
+Abstract: This CSS module describes the common values and units that CSS properties accept and the syntax used for describing them in CSS property definitions.
+At Risk: ''attr()''
 Ignored Terms: <spacing-limit>, containing block
 Ignored Vars: Cn+1, n
 Inline Github Issues: yes
@@ -889,12 +889,6 @@ Relative lengths</h3>
 			<td>1% of viewport's width
 		<tr><td>''vh''
 			<td>1% of viewport's height
-<!--
-		<tr><td>''vi''
-			<td>1% of viewport's size in the root element's <a>inline axis</a>
-		<tr><td>''vb''
-			<td>1% of viewport's size in the root element's <a>block axis</a>
--->
 		<tr><td>''vmin''
 			<td>1% of viewport's smaller dimension
 		<tr><td>''vmax''
@@ -994,7 +988,7 @@ Font-relative lengths: the ''em'', ''ex'', ''ch'', ''rem'' units</h4>
 -->
 
 <h4 id="viewport-relative-lengths">
-Viewport-percentage lengths: the ''vw'', ''vh'', <!-- ''vi'', ''vb'', --> ''vmin'', ''vmax'' units</h4>
+Viewport-percentage lengths: the ''vw'', ''vh'', ''vmin'', ''vmax'' units</h4>
 
 	The <dfn export>viewport-percentage lengths</dfn> are relative to the size of the
 	<a href="https://www.w3.org/TR/CSS21/visudet.html#containing-block-details">initial containing block</a>.
@@ -1023,17 +1017,7 @@ Viewport-percentage lengths: the ''vw'', ''vh'', <!-- ''vi'', ''vb'', --> ''vmin
 		<dt><dfn id="vh" lt="vh">vh unit</dfn>
 		<dd>
 			Equal to 1% of the height of the initial containing block.
-<!--
-		<dt><dfn lt=vi>vi unit</dfn>
-		<dd>
-			Equal to 1% of the size of the initial containing block
-			in the direction of the root element's inline axis.
 
-		<dt><dfn lt=vb>vb unit</dfn>
-		<dd>
-			Equal to 1% of the size of the initial containing block
-			in the direction of the root element's block axis.
--->
 		<dt><dfn id="vmin" lt="vmin">vmin unit</dfn>
 		<dd>
 			Equal to the smaller of ''vw'' or ''vh''.
@@ -1042,13 +1026,7 @@ Viewport-percentage lengths: the ''vw'', ''vh'', <!-- ''vi'', ''vb'', --> ''vmin
 		<dd>
 			Equal to the larger of ''vw'' or ''vh''.
 	</dl>
-<!--
-	In situations where there is no root element
-	or it hasn't yet been styled
-	(such as when evaluating <a>media queries</a>),
-	the ''vi'' and ''vb'' units use the initial value of the 'writing-mode' property
-	to determine which axis they correspond to.
--->
+
 <!--
 ████████  ██     ██       ██ ████████ ████████  ██████
 ██     ██  ██   ██       ██  ██          ██    ██    ██
@@ -1707,186 +1685,7 @@ Range Checking</h4>
 <h4 id='calc-serialize'>
 Serialization</h4>
 
-	To serialize a ''calc()'' value:
-
-	1. Simplify the expression by:
-
-		* Replacing nested ''calc()'' values with parentheses containing their contents
-		* Resolving all multiplications and divisions
-		* Combining identical units
-
-		Note: The value-computation process can transform disparate units into identical ones.
-		For example, ''em'' and ''px'' are obviously different at specified-value time,
-		but at computed-value time they're both absolutized to ''px''.
-
-		The result must be a summation of unique units.
-		(Terms with a value of zero <strong>must</strong> be preserved in this summation.)
-
-	2. If this simplification process results in only a single value
-		(one <<number>>, one <<dimension>>, or one <<percentage>>),
-		and the value being serialized is a <a>computed value</a> or later,
-		serialize it just as that one value,
-		without the ''calc()'' wrapper.
-		If this value is outside the allowed range for the context,
-		it must be clamped to the nearest allowed value.
-
-	3. Otherwise, serialize as a ''calc()'' containing the summation,
-		with the units ordered <a>ASCII case-insensitive</a> alphabetically,
-		the number (if present) coming before all units,
-		and the percentage (if present) coming after all units.
-
-	<div class="example">
-		For example, ''calc(20px + 30px)'' would serialize as ''calc(50px)'' as a specified value,
-		or as ''50px'' as a computed value.
-
-		A value like ''calc(20px + 0%)'' would serialize as ''calc(20px + 0%)'',
-		maintaining both terms in the serialized value.
-		(It's important to maintain zero-valued terms,
-		so the ''calc()'' doesn't suddenly "change shape" in the middle of a transition
-		when one of the values happens to have a zero value temporarily.
-		This also removes the need to "pick a unit" when all the terms are zero.)
-
-		A value like ''calc(20px + 2em)'' would serialize as ''calc(2em + 20px)'' as a specified value
-		(maintaining both units as they're incompatible at specified-value time,
-		but sorting them alphabetically),
-		or as something like ''52px'' as a computed value
-		(''em'' values are converted to absolute lengths at computed-value time,
-		so assuming ''1em'' = ''16px'',
-		they combine into ''52px'',
-		which then drops the ''calc()'' wrapper.)
-	</div>
-
-	See [[!CSSOM]] for further information on serialization.
-
-<!--
-████████  ███████   ██████    ██████   ██       ████████   ███ ███
-   ██    ██     ██ ██    ██  ██    ██  ██       ██        ██     ██
-   ██    ██     ██ ██        ██        ██       ██       ██       ██
-   ██    ██     ██ ██   ████ ██   ████ ██       ██████   ██       ██
-   ██    ██     ██ ██    ██  ██    ██  ██       ██       ██       ██
-   ██    ██     ██ ██    ██  ██    ██  ██       ██        ██     ██
-   ██     ███████   ██████    ██████   ████████ ████████   ███ ███
--->
-
-<h3 id="toggle-notation">
-Toggling Between Values: ''toggle()''</h3>
-
-	The <dfn>toggle()</dfn> expression allows descendant elements
-	to cycle over a list of values instead of inheriting the same value.
-
-	<div class='example'>
-		The following example makes <code>&lt;em></code> elements italic in general,
-		but makes them normal if they're inside something that's italic:
-
-		<pre>em { font-style: toggle(italic, normal); }</pre>
-	</div>
-
-	<div class='example'>
-		The following example cycles markers for nested lists,
-		so that a top level list has ''disc''-shaped markers,
-		but nested lists use ''list-style-type/circle'', then ''square'', then ''box'',
-		and then repeat through the list of marker shapes,
-		starting again (for the 5th list deep) with ''disc''.
-
-		<pre>ul { list-style-type: toggle(disc, circle, square, box); }</pre>
-	</div>
-
-	The syntax of the ''toggle()'' expression is:
-
-	<pre>toggle( <<toggle-value>># )</pre>
-
-	where <dfn>&lt;toggle-value></dfn> is any CSS value
-	that is valid where the expression is placed,
-	and that doesn't contain any top-level commas.
-	If any of the values inside are not valid,
-	then the entire ''toggle()'' expression is invalid.
-	The ''toggle()'' expression may be used as the value of any property,
-	but must be the only component in that property's value.
-
-	The ''toggle()'' notation is not allowed to be nested; nor may it
-	contain ''attr()'' or ''calc()'' notations.
-	Declarations containing such constructs are invalid.
-
-	<div class="example">
-		The following ''toggle()'' examples are all invalid:
-
-		<pre>
-		background-position: 10px toggle(50px, 100px);
-		/* toggle() must be the sole value of the property */
-
-		list-style-type: toggle(disc, 50px);
-		/* ''50px'' isn't a valid value of 'list-style-type' */
-		</pre>
-	</div>
-
-	To determine the computed value of ''toggle()'',
-	first evaluate each argument as if it were the sole value of the property in which ''toggle()'' is placed
-	to determine the computed value that each represents,
-	called <var>C<sub>n</sub></var> for the <var>n</var>-th argument to ''toggle()''.
-	Then, compare the property's <a>inherited value</a>
-	with each <var>C<sub>n</sub></var>.
-	For the earliest <var>C<sub>n</sub></var> that matches the <a>inherited value</a>,
-	the computed value of ''toggle()'' is <var>C<sub>n+1</sub></var>.
-	If the match was the last argument in the list,
-	or there was no match,
-	the computed value of ''toggle()'' is the computed value that the first argument represents.
-
-
-	Note: This means that repeating values in a ''toggle()'' short-circuits the list.
-	For example ''toggle(1em, 2em, 1em, 4em)'' will be equivalent to ''toggle(1em, 2em)''.
-
-	<!-- Issue: Should this short-circuiting affect the computed value? -->
-
-	Note: That ''toggle()'' explicitly looks at the computed value of the parent,
-	so it works even on non-inherited properties.
-	This is similar to the ''inherit'' keyword,
-	which works even on non-inherited properties.
-
-	Note: That the <a href="https://www.w3.org/TR/CSS21/cascade.html#computed-value">computed value</a> of a property is an abstract set of values,
-	not a particular serialization [[!CSS21]],
-	so comparison between computed values should always be unambiguous and have the expected result.
-	For example,
-	a Level 2 <a property spec=css21>background-position</a> computed value
-	is just two offsets, each represented as an absolute length or a percentage,
-	so the declarations ''background-position: top center'' and ''background-position: 50% 0%''
-	produce identical computed values.
-	If the "Computed Value" line of a property definition seems to define something ambiguous or overly strict,
-	please <a href="#status">provide feedback</a> so we can fix it.
-
-	If ''toggle()'' is used on a <a>shorthand property</a>,
-	it sets each of its longhands to a ''toggle()'' value
-	with arguments corresponding to what the longhand would have recieved
-	had each of the original ''toggle()'' arguments been the sole value of the <a>shorthand</a>.
-
-	<div class="example">
-		For example, the following shorthand declaration:
-
-		<pre>margin: toggle(1px 2px, 4px, 1px 5px 3px);</pre>
-
-		is equivalent to the following longhand declarations:
-
-		<pre>
-		margin-top:    toggle(1px, 4px, 1px);
-		margin-right:  toggle(2px, 4px, 5px);
-		margin-bottom: toggle(1px, 4px, 3px);
-		margin-left:   toggle(2px, 4px, 5px);
-		</pre>
-
-		Note that, since ''1px'' appears twice in the top and bottom margins,
-		they will cycle between only two values
-		while the left and right margins cycle through three.
-		In other words, the declarations above will yield the same computed values
-		as the longhand declarations below:
-
-		<pre>
-		margin-top:    toggle(1px, 3px);
-		margin-right:  toggle(2px, 4px, 5px);
-		margin-bottom: toggle(1px, 3px);
-		margin-left:   toggle(2px, 4px, 5px);
-		</pre>
-
-		which may not be what was intended.
-	</div>
+	The serialization of ''calc()'' values is undefined in this level.
 
 <!--
    ███    ████████ ████████ ████████    ███ ███
@@ -1942,10 +1741,6 @@ Ian's proposal:
 	If it's absent,
 	the default value for the given <<type-or-unit>> (from the list below) is implied.
 
-	Note: Unlike <<toggle-value>>s,
-	an ''attr()'' <<attr-fallback>> value may contain top-level commas,
-	as it is always the last argument in the functional notation.
-
 	The attr() expression is only valid if:
 
 	<ul>
@@ -2255,19 +2050,16 @@ Changes</h2>
 	Changes since the <a href="https://www.w3.org/TR/2015/CR-css-values-3-20150611/">11 June 2015 Candidate Recomendation</a> are:
 
 	<ul>
+		<li>Dropped ''toggle()'' for lack of implementations.
 		<li>Allow zero angles to be represented as ''0''.
 		    (Change due to Web-compatibility constraints in transform and gradient syntaxes.)
 		<li>Defined <a href="#local-urls">special handling</a> for fragment URLs.
 		<li>Defined an empty <<url>> resolves to an invalid resource.
-		<li>Defined <a href="#calc-serialize">serialization of <css>calc()</css> values</a>.
 		<li>Defined <a>compatible units</a> and <a>canonical units</a> for serialization.
 		<li>Defined case-sensitivity of ''url()'' attribute argument to match attribute selectors.
 		<li>Added definition of <<ident>> notation to definition of <a>identifiers</a>.
 		<li>Added <<length-percentage>> as a shorthand for <<length>> | <<percentage>>,
 			along with equivalent productions for angles, numbers, times, and frequencies.
-<!--
-		<li>Added the ''vi'' and ''vb'' units.
--->
 		<li>Various clarifications and editorial improvements.
 	</ul>
 

css-values-3/issues-cr-2015.bsi

@@ -82,9 +82,9 @@ Verified:
 Resolved: Sydney 2016 F2F
 ----
 Issue 10.
-Summary:  Is toggle() implemented? Or should we defer to L4?
+Summary:  Defer toggle() due to lack of implementations
 From:     fantasai
-Open:     Needs edits (should be last edit before forking L3 for publication)
+Closed:   Accepted
 Resolved: https://lists.w3.org/Archives/Public/www-style/2016Feb/0183.html
 ----
 Issue 11.

css-values-3/issues-cr-2015.html

@@ -113,11 +113,11 @@ <h1>CSS Values and Units Level 3 Disposition of Comments for 2015-06-11 CR</h1>
 <span class="a">Closed:   Accepted</span>
 <span>Verified:</span>
 <span>Resolved: Sydney 2016 F2F</span></pre>
-<pre class='open ' id='issue-10'>
+<pre class=' a' id='issue-10'>
 <span>Issue 10. <a href='#issue-10'>#</a></span>
-<span>Summary:  Is toggle() implemented? Or should we defer to L4?</span>
+<span>Summary:  Defer toggle() due to lack of implementations</span>
 <span>From:     fantasai</span>
-<span class="">Open:     Needs edits (should be last edit before forking L3 for publication)</span>
+<span class="a">Closed:   Accepted</span>
 <span>Resolved: <a href='https://lists.w3.org/Archives/Public/www-style/2016Feb/0183.html'>https://lists.w3.org/Archives/Public/www-style/2016Feb/0183.html</a></span></pre>
 <pre class=' a' id='issue-11'>
 <span>Issue 11. <a href='#issue-11'>#</a></span>