csswg/css3-images Overview.html,1.298,1.299 Overview.src.html,1.308,1.309 from Tab Atkins Jr.. via cvs-syncmail on 2012-02-28 (public-css-commits@w3.org from February 2012)

From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 28 Feb 2012 00:14:01 +0000
To: public-css-commits@w3.org
Message-Id: <E1S2Ahd-0004Nn-DF@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-images
In directory hutz:/tmp/cvs-serv16833

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Move the previous added text into a note.

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-images/Overview.html,v
retrieving revision 1.298
retrieving revision 1.299
diff -u -d -r1.298 -r1.299
--- Overview.html	28 Feb 2012 00:01:00 -0000	1.298
+++ Overview.html	28 Feb 2012 00:13:59 -0000	1.299
@@ -896,25 +896,28 @@
     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.
+  <div class=note>
+   <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 &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>
+   <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>
+  </div>
   <!-- ====================================================================== -->
 
   <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.308
retrieving revision 1.309
diff -u -d -r1.308 -r1.309
--- Overview.src.html	28 Feb 2012 00:01:00 -0000	1.308
+++ Overview.src.html	28 Feb 2012 00:13:59 -0000	1.309
@@ -471,9 +471,11 @@
 		<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>
+	<div class='note'>
+		<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>
+		<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>
+	</div>
 
 <!-- ====================================================================== -->
Received on Tuesday, 28 February 2012 00:14:03 UTC