Add some issue notes.
--- a/master/painting.html Sun May 20 18:44:40 2012 +1000
+++ b/master/painting.html Sun May 20 18:54:11 2012 +1000
@@ -390,6 +390,10 @@
properties were converted to an equivalent <a>'path'</a> element and
then filled using the given paint server.</p>
+<p class="issue">We should have an algorithm here that computes the
+exact shape of a stroke. This would make it clear how say <a>'stroke-dasharray'</a>
+and <a>'stroke-linejoin'</a> interact.</p>
+
<h3 id="SpecifyingStrokePaint">Specifying stroke paint: the <span class="property">'stroke'</span> property</h3>
<table class="propdef">
--- a/master/shapes.html Sun May 20 18:44:40 2012 +1000
+++ b/master/shapes.html Sun May 20 18:54:11 2012 +1000
@@ -33,6 +33,11 @@
properties available for <a>'path'</a> elements also apply to the basic
shapes.</p>
+<p class="issue">We should define the equivalent path for each shape
+(and for text?). The algorithm that computes the stroke shape for
+an element can then refer to the equivalent path for the element, so
+that it is clear for example where dashing would start.</p>
+
<h2 id="RectElement">The <span class="element-name">'rect'</span> element</h2>
<edit:with element='rect'>
--- a/master/types.html Sun May 20 18:44:40 2012 +1000
+++ b/master/types.html Sun May 20 18:54:11 2012 +1000
@@ -347,6 +347,9 @@
<dt id='DataTypeCoordinate'><coordinate></dt>
<dd>
+ <p class="issue">Do we need this separate data type? Why not just
+ <a><length></a> in all the places we currently use <a><coordinate></a>?</p>
+
<p>A <coordinate> is a length in the user coordinate system that is
the given distance from the origin of the user coordinate system along the
relevant axis (the x-axis for X coordinates, the y-axis for Y