W3C home > Mailing lists > Public > public-svg-wg@w3.org > April to June 2013

svg2: Tweaks to multiple paints on fill and stroke.

From: SVG Working Group repository <cam+svgwgrepo@mcc.id.au>
Date: Mon, 24 Jun 2013 06:53:44 -0700
Message-Id: <hg.0c60566b6156.1372082024.3034738116371802840@ps58493.dreamhostps.com>
To: public-svg-wg@w3.org
details:   https://svgwg.org/hg/svg2/rev/0c60566b6156
branches:  
changeset: 520:0c60566b6156
user:      tbah <tavmjong@free.fr>
date:      Mon Jun 24 15:51:38 2013 +0200
description:
Tweaks to multiple paints on fill and stroke.

diffstat:

 master/painting.html |  55 +++++++++++++++++++++++++++------------------------
 1 files changed, 29 insertions(+), 26 deletions(-)

diffs (110 lines):

diff --git a/master/painting.html b/master/painting.html
--- a/master/painting.html
+++ b/master/painting.html
@@ -97,45 +97,32 @@ paint servers.</p>
     </tr>
     <tr>
       <th>Owner:</th>
       <td>Tav (<a href="http://www.w3.org/Graphics/SVG/WG/track/actions/3500">ACTION-3500</a>)</td>
     </tr>
   </table>
 </div>
 
-<p>Properties <a>'fill'</a> and <a>'stroke'</a> take on a comma separated list of values of type <a>&lt;paint&gt;</a> with
-the last value optionally taking a space separated solid color fallback.</p>
-
+<p>Properties <a>'fill'</a> and <a>'stroke'</a> take on a comma separated list of values of type <a>&lt;paint&gt;</a>. Each paint is applied to an element in reverse order. Note, only a <a href="pservers.html">paint server</a> in the last position may take an optional fallback color.</p>
+
+<p class="note">The ability to apply more than one paint to an element is new in SVG 2.</p>
 <p class="annotation">The paint order follows that of CSS backgrounds.</p>
 
 <div class="example">
-<pre><![CDATA[
+  <pre><![CDATA[
 <rect width="100" height="100" fill="url(#MyHatch1, #MyHatch2, powderblue)">
-]]></pre>
-<div class="figure">
-  <img
-     alt="An example of applying three paints to a rectangle."
-     src="images/painting/multiple_paints.svg"/>
-  <p class="caption">The rightmost rectangle is filled by stacking the paints shown in the other rectangles.</p>
+  ]]></pre>
+  <div class="figure">
+    <img
+       alt="An example of applying three paints to a rectangle."
+       src="images/painting/multiple_paints.svg"/>
+    <p class="caption">The rightmost rectangle is filled by stacking the paints shown in the other rectangles.</p>
+  </div>
 </div>
-</div>
-
-<div class="example">
-<pre><![CDATA[
-<rect width="100" height="100" fill="url(#MyHatch1, #MyHatch2 powderblue)">
-]]></pre>
-<div class="figure">
-  <img
-     alt="An example with a fallback solid paint fill."
-     src="images/painting/multiple_paints2.svg"/>
-  <p class="caption">The left rectangle shows the expected fill if both MyHatch1  and MyHatch2 are defined. The right rectangle shows the expected fill if MyHatch1 is defined but MyHatch2 is missing.</p>
-</div>
-</div>
-
 
 
 <p>The type <a>&lt;paint&gt;</a> is defined as:</p>
 
 <div class="definition">
   <dfn id="DataTypePaint">&lt;paint&gt;</dfn> =<br/>
   <div style="margin-left: 2em">
     none |<br/>
@@ -184,31 +171,47 @@ the last value optionally taking a space
   (In most cases, the <a>&lt;number&gt;</a>s will be in the range 0 to 1.)
   Note that color interpolation occurs in an RGB color space even if an
   ICC-based color specification is provided (see <a>'color-interpolation'</a>).
   For more on ICC-based colors, refer to <a
   href="color.html#ColorProfileDescriptions">Color profile
   descriptions</a>.</dd>
 
   <dt>[ <a>&lt;funciri&gt;</a> | child | <a>&lt;child-selector&gt;</a> ] [ none | <a>&lt;color&gt;</a> | [ <a>&lt;color&gt;</a>? <a>&lt;icccolor&gt;</a> ] ]?</dt>
-  <dd>A reference to a <a href="pservers.html">paint server</a> element with an
+  <dd>A reference to a <a href="pservers.html">paint server</a> element with, if
+  the paint server is the last paint specified, an
   optional fallback color or <span class="prop-value">none</span>.
   The <a>&lt;funciri&gt;</a>, <span class="prop-value">child</span> keyword,
   or <a>&lt;child-selector&gt;</a> is used to identify a <a>'solidColor'</a>
-  element, <a>gradient element</a> or <a>'pattern'</a> element,
+  element, <a>gradient element</a>, <a>'pattern'</a> element, or <a>'hatch'</a> element,
   which defines the paint to use.
   The <span class="prop-value">child</span> keyword in this instance matches the
   last child <a>paint server element</a> of the element where the paint value
   is specified.
   If the reference is not valid (e.g., it points to an element that
   does not exist, no element was matched, or the element is not a valid paint
   server), then the fallback value is used, if provided; otherwise, the document
   is in error (see <a href="implnote.html#ErrorProcessing">Error
   processing</a>).</dd>
 
+  <div class="example">
+    <pre><![CDATA[
+<rect width="100" height="100" fill="url(#MyHatch1, #MyHatch2 powderblue)">
+    ]]></pre>
+    <div class="figure">
+      <img
+         alt="An example with a fallback solid paint fill."
+         src="images/painting/multiple_paints2.svg"/>
+      <p class="caption">The left rectangle shows the expected fill if both MyHatch1  and MyHatch2 are defined. The right rectangle shows the expected fill if MyHatch1 is defined but MyHatch2 is missing.</p>
+    </div>
+  </div>
+
+  <p class="issue">Should the document be in error if a non-final paint-server reference is invalid? (Only the last paint-server has a fallback.)</p>
+  <p class="issue">How should 'child' behave with allowing multiple paints?</p>
+
   <dt>context-fill</dt>
   <dt>context-stroke</dt>
   <dd>The same paint as the computed value of the <a>'fill'</a> or <a>'stroke'</a>
   property, respectively, of the <a>context element</a>.  If there
   is no context element, then no paint is applied.  If the referenced paint
   is a gradient or a pattern, then the coordinate space to use and the
   object used for any <span class='attr-value'>'objectBoundingBox'</span>-relative
   values are the same as those of the <a>context element</a>.</dd>
Received on Monday, 24 June 2013 13:54:14 UTC

This archive was generated by hypermail 2.3.1 : Monday, 24 June 2013 13:54:14 UTC