W3C home > Mailing lists > Public > public-css-commits@w3.org > February 2012

csswg/css3-images Overview.html,1.297,1.298 Overview.src.html,1.307,1.308

From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 28 Feb 2012 00:01:02 +0000
To: public-css-commits@w3.org
Message-Id: <E1S2AV4-00049b-Iw@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-images
In directory hutz:/tmp/cvs-serv15953

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Removed paragraph about inheritance-blocking in element(); replaced it with two paragraphs in Paint Sources about this case, why it's difficult, and a recommendation.

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.html,v
retrieving revision 1.297
retrieving revision 1.298
diff -u -d -r1.297 -r1.298
--- Overview.html	27 Feb 2012 22:09:25 -0000	1.297
+++ Overview.html	28 Feb 2012 00:01:00 -0000	1.298
@@ -16,7 +16,7 @@
 
    <h1>CSS Image Values and Replaced Content Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 27 February
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 28 February
     2012</h2>
 
    <dl>
@@ -24,7 +24,7 @@
 
     <dd><a
      href="http://dev.w3.org/csswg/css3-images/">http://dev.w3.org/csswg/css3-images/</a>
-     <!-- <dd><a href="http://www.w3.org/TR/2012/ED-css3-images-20120227/">http://www.w3.org/TR/2012/WD-css3-images-20120227/</a>-->
+     <!-- <dd><a href="http://www.w3.org/TR/2012/ED-css3-images-20120228/">http://www.w3.org/TR/2012/WD-css3-images-20120228/</a>-->
      
 
     <dt>Latest Version:
@@ -722,16 +722,6 @@
      The host language defines the dimensions and appearance of paint
      sources.</p>
 
-    <p>If any properties on the element would inherit their value from the
-     element's parent, they must instead be set to their initial value.</p>
-
-    <p class=note>Note: even if the property that caused the element to not
-     be rendered was inherited, and switching off that inheritance would
-     cause the element to be rendered again, by this point we're not relying
-     on the rendered appearance of the element, but rather on the paint
-     source it provides, which is layout-independent. Thus, there is no
-     circular dependency created.</p>
-
     <div class=example>
      <p>For example, the &lsquo;<code class=css>element()</code>&rsquo;
       function can reference an SVG &lt;pattern> element in an HTML document:</p>
@@ -905,6 +895,26 @@
     are sized equivalently to the CSS &lsquo;<code class=css>px</code>&rsquo;
     unit.
   </dl>
+
+  <p>Because paint sources have an intrinsic appearance, it's not necessary
+   for the element providing them to be in a document - for example, one can
+   simply create an element with JavaScript and directly assign it to the
+   CSSElementMap in HTML. However, some paint sources (such as an SVG
+   <code>&lt;pattern></code>) depend on style information for their
+   appearance, and it's currently largely undefined how styling information
+   is assigned to an element fragment that's not part of a document. (For
+   example, does the fragment receive styles from the active document? What
+   if it has its own <code>&lt;style></code> or <code>&lt;link
+   rel=stylesheet></code> in it?) This specification explicitly does not
+   define how such a fragment is styled; it is expected that CSS will define
+   it in sufficient detail in the future.
+
+  <p>For now, it is recommended that such fragments be inserted into a
+   document before being referenced. For example, a <code>&lt;pattern></code>
+   element may be placed into a &lsquo;<code
+   class=css>display:none</code>&rsquo; <code>&lt;svg></code> element's
+   <code>&lt;defs></code> element within a document; this has no rendering or
+   layout effects on the document, but the style inheritance is well-defined.</p>
   <!-- ====================================================================== -->
 
   <h4 class=no-num id=element-cycles> Cycle Detection</h4>

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.src.html,v
retrieving revision 1.307
retrieving revision 1.308
diff -u -d -r1.307 -r1.308
--- Overview.src.html	27 Feb 2012 22:09:25 -0000	1.307
+++ Overview.src.html	28 Feb 2012 00:01:00 -0000	1.308
@@ -349,10 +349,6 @@
 		<dd>
 			<p>The function represents an image with the dimensions and appearance of the <i title=paint-source>paint source</i>.  The host language defines the dimensions and appearance of paint sources.</p>
 
-			<p>If any properties on the element would inherit their value from the element's parent, they must instead be set to their initial value.</p>
-
-			<p class='note'>Note: even if the property that caused the element to not be rendered was inherited, and switching off that inheritance would cause the element to be rendered again, by this point we're not relying on the rendered appearance of the element, but rather on the paint source it provides, which is layout-independent.  Thus, there is no circular dependency created.</p>
-
 			<div class='example'>
 				<p>For example, the ''element()'' function can reference an SVG &lt;pattern> element in an HTML document:</p>
 
@@ -475,6 +471,10 @@
 		<dd>The coordinate system has its origin at the top left corner of the <i>concrete object size</i> it's being drawn into, and the same width and height as the <i>concrete object size</i>.  <a href="http://www.w3.org/TR/SVG/coords.html#Units">User coordinates</a> are sized equivalently to the CSS ''px'' unit.</dd>
 	</dl>
 
+	<p>Because paint sources have an intrinsic appearance, it's not necessary for the element providing them to be in a document - for example, one can simply create an element with JavaScript and directly assign it to the CSSElementMap in HTML.  However, some paint sources (such as an SVG <code>&lt;pattern></code>) depend on style information for their appearance, and it's currently largely undefined how styling information is assigned to an element fragment that's not part of a document.  (For example, does the fragment receive styles from the active document? What if it has its own <code>&lt;style></code> or <code>&lt;link rel=stylesheet></code> in it?)  This specification explicitly does not define how such a fragment is styled; it is expected that CSS will define it in sufficient detail in the future.</p>
+
+	<p>For now, it is recommended that such fragments be inserted into a document before being referenced.  For example, a <code>&lt;pattern></code> element may be placed into a ''display:none'' <code>&lt;svg></code> element's <code>&lt;defs></code> element within a document; this has no rendering or layout effects on the document, but the style inheritance is well-defined.</p>
+
 <!-- ====================================================================== -->
 
 <h4 class="no-num" id='element-cycles'>
Received on Tuesday, 28 February 2012 00:01:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:50 UTC