W3C home > Mailing lists > Public > public-css-commits@w3.org > July 2011

csswg/css-color-correction Overview.html,1.1,1.2 Overview.src.html,1.1,1.2

From: David Baron via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 26 Jul 2011 23:07:41 +0000
To: public-css-commits@w3.org
Message-Id: <E1Qlqiz-00030a-IW@lionel-hutz.w3.org>
Update of /sources/public/csswg/css-color-correction
In directory hutz:/tmp/cvs-serv11550

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Fill out the paragraph I intended to write in the introduction.

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css-color-correction/Overview.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Overview.html	24 Feb 2011 02:34:07 -0000	1.1
+++ Overview.html	26 Jul 2011 23:07:39 -0000	1.2
@@ -23,12 +23,11 @@
 
    <h1>CSS Color Correction Module</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 24 February
-    2011</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 26 July 2011</h2>
 
    <dl>
     <dt>This version:</dt>
-    <!-- <dd><a href="http://www.w3.org/TR/2011/ED-css-color-correction-20110224">http://www.w3.org/TR/2011/ED-css-color-correction-20110224</a></dd> -->
+    <!-- <dd><a href="http://www.w3.org/TR/2011/ED-css-color-correction-20110726/">http://www.w3.org/TR/2011/ED-css-color-correction-20110726/</a></dd> -->
 
     <dd><a
      href="http://dev.w3.org/csswg/css-color-correction/">http://dev.w3.org/csswg/css-color-correction/</a>
@@ -178,7 +177,13 @@
    different displays, therefore, requires care not to cause the worse
    problem of inconsistency of colors on the same display.
 
-  <p class=issue> plan ... future improvements in plugin API ...
+  <p>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.
 
   <h2 id=conformance><span class=secno>2. </span>Conformance</h2>
 
@@ -290,7 +295,8 @@
     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 &lsquo;<code class=property>auto</code>&rsquo; the same as
-    'sRGB'.
+    &lsquo;<a href="#color-correction-value-sRGB"><code
+    class=property>sRGB</code></a>&rsquo;.
   </dl>
 
   <p class=note>The initial value of this property may change in a future
@@ -315,10 +321,10 @@
    <dt id=CSS21>[CSS21]
 
    <dd>Bert Bos; et al. <a
-    href="http://www.w3.org/TR/2010/WD-CSS2-20101207"><cite>Cascading Style
-    Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 7 December
-    2010. W3C Working Draft. (Work in progress.) URL: <a
-    href="http://www.w3.org/TR/2010/WD-CSS2-20101207">http://www.w3.org/TR/2010/WD-CSS2-20101207</a>
+    href="http://www.w3.org/TR/2011/REC-CSS2-20110607"><cite>Cascading Style
+    Sheets Level 2 Revision 1 (CSS&#160;2.1) Specification.</cite></a> 7 June
+    2011. W3C Recommendation. URL: <a
+    href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a>
     </dd>
    <!---->
 
@@ -364,10 +370,9 @@
    <dt id=CSS3COLOR>[CSS3COLOR]
 
    <dd>Tantek &#199;elik; Chris Lilley; L. David Baron. <a
-    href="http://www.w3.org/TR/2010/PR-css3-color-20101028"><cite>CSS Color
-    Module Level 3.</cite></a> 28 October 2010. W3C Proposed Recommendation.
-    (Work in progress.) URL: <a
-    href="http://www.w3.org/TR/2010/PR-css3-color-20101028">http://www.w3.org/TR/2010/PR-css3-color-20101028</a>
+    href="http://www.w3.org/TR/2011/REC-css3-color-20110607"><cite>CSS Color
+    Module Level 3.</cite></a> 7 June 2011. W3C Recommendation. URL: <a
+    href="http://www.w3.org/TR/2011/REC-css3-color-20110607">http://www.w3.org/TR/2011/REC-css3-color-20110607</a>
     </dd>
    <!---->
   </dl>
@@ -428,7 +433,7 @@
      <th>Media
 
    <tbody>
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#color-correction">color-correction</a>
 
      <td>default | sRGB

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css-color-correction/Overview.src.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- Overview.src.html	24 Feb 2011 02:34:07 -0000	1.1
+++ Overview.src.html	26 Jul 2011 23:07:39 -0000	1.2
@@ -90,7 +90,13 @@
 between different displays, therefore, requires care not to cause the
 worse problem of inconsistency of colors on the same display.</p>
 
-<p class="issue"> plan ... future improvements in plugin API ...</p>
+<p>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.</p>
 
 <h2 id="conformance">Conformance</h2>
 
Received on Tuesday, 26 July 2011 23:07:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 26 July 2011 23:07:46 GMT