[css-color-4] Remove the 'color-correction' property per resolution yesterday, but move the parts that should still be specified earlier in the spec.

Author: dbaron

css-color/Overview.bs

@@ -144,6 +144,20 @@ Notes On Using Colors</h3>
 		<li><a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#visual-audio-contrast-without-color"><em>1.4.1 Use of Color:</em> Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element</a>
 	</ul>
 
+<h3 id='sRGB'>Colors in sRGB</h3>
+
+	Colors specified in CSS, HTML, and untagged images are in the sRGB color space ([[!SRGB]]).
+
+	<p class="note">This is not yet reliably implemented across implementations, though it has been shown to be implementable.  Implementing it compatibly may require notifying plugins to treat untagged colors in the same way to avoid issues with colors not matching each other within a page.</p>
+
+	An <dfn export>untagged image</dfn> is an image that is not explicitly assigned a color profile, as defined by the image format.
+
+	Note that this rule does not apply to videos, since untagged video should be presumed to be in CCIR 601.
+
+	<p class="issue">
+		Really?  Shouldn't video be consistent with images?
+		Or do implementations really do this differently?
+	</p>
 
 <h2 id='numeric-rgb'>
 RGB Colors</h2>
@@ -2159,67 +2173,6 @@ Simple alpha compositing</h3>
 	are not implemented or do not apply, implementations must act as though they have their initial values.)
 
 
-<h2 id='color-management'>
-Color Management: the 'color-correction' property</h2>
-
-	CSS Level 1 ([[CSS1]]), CSS Level 2 ([[!CSS21]]), and CSS Color Level 3 ([[CSS3COLOR]])
-	define colors specified in CSS to be in the sRGB color space ([[!SRGB]]).
-	However, most or all existing Web browser implementations do not correct colors specified in HTML, CSS, or untagged images
-	even when the proper correction is known.
-
-	If browsers did so,
-	it would make the colors displayed in Web pages more consistent between different displays and operating systems.
-	However, a more important type of consistency is the consistency of colors in different parts of a page on the same display,
-	such as between colors specified in style sheets and colors in images,
-	or between those colors and colors drawn by plugins.
-	Improving the consistency of colors between different displays, therefore,
-	requires care not to cause the worse problem of inconsistency of colors on the same display.
-
-	In the long run, we hope that it might be possible for implementations to switch to
-	treating CSS colors and colors in untagged images as being in sRGB by default.
-	(This may depend on additions for color management being made to the plugin API and popular plugins using those additions.)
-	Therefore, this specification provides a way to clearly opt in to that correct behavior,
-	but provides an default behavior (initial value) that may be equivalent to this opt-in.
-
-	<pre class='propdef'>
-	Name: color-correction
-	Value: auto | sRGB
-	Initial: auto
-	Applies to: all elements
-	Inherited: yes
-	Percentages: N/A
-	Media: visual
-	Computed value: as specified
-	</pre>
-
-	The 'color-correction' property specifies the color space that colors specified in CSS
-	and colors in <a>untagged images</a> are in.
-	An <dfn export>untagged image</dfn> is an image that is not explicitly assigned a color profile,
-	as defined by the image format.
-	It does not apply to videos, since untagged video should be presumed to be in CCIR 601.
-
-	<p class="issue">
-		Really?  Shouldn't video be consistent with images?
-		Or do implementations really do this differently?
-
-	<dl dfn-type=value dfn-for="color-correction">
-		<dt><dfn>sRGB</dfn>
-		<dd>
-			Colors specified in CSS
-			and colors in <a>untagged images</a>
-			are in the sRGB color space.
-
-		<dt><dfn>auto</dfn>
-		<dd>
-			The color space for colors specified in CSS and colors in <a>untagged images</a> is not defined.
-			However, implementations must use a single color space for such colors so that they match each other.
-			When doing so would not cause color mismatches with content such as plugins,
-			implementations should treat ''auto'' the same as ''sRGB''.
-	</dl>
-
-	Note: The initial value of this property may change in a future level of this specification.
-
-
 <h2 id='color-adjust'>
 Preserving Colors in Different-Capability Devices: the 'color-adjust' property</h2>