No need for big dot points here, just use paragraphs.
authorCameron McCormack <cam@mcc.id.au>
Tue, 22 May 2012 13:20:55 +1000
changeset 129 91a87ef66ac2
parent 128 bb7ed0a22b77
child 130 49e177cb6568
No need for big dot points here, just use paragraphs.
master/painting.html
--- a/master/painting.html	Tue May 22 12:22:59 2012 +1000
+++ b/master/painting.html	Tue May 22 13:20:55 2012 +1000
@@ -1152,50 +1152,47 @@
 
 <p>SVG uses two properties, <a>'display'</a> and <a>'visibility'</a>, to
 control the visibility of graphical elements or (in the case of the
-<a>'display'</a> property) container elements.</p>
-
-<p>The differences between the two properties are as follows:</p>
-
-<ul>
-  <li>When applied to a container element, setting <a>'display'</a>
-  to <span class="prop-value">none</span> causes the container and
-  all of its children to be invisible; thus, it acts on groups of
-  elements as a group. <a>'visibility'</a>, however, only applies
-  to individual graphics elements. Setting <a>'visibility'</a>
-  to <span class="prop-value">hidden</span> on a <a>'g'</a>
-  will make its children invisible as long as the children do
-  not specify their own <a>'visibility'</a> properties as <span
-  class="prop-value">visible</span>. Note that <a>'visibility'</a> is
-  <em>not</em> an inheritable property.</li>
+<a>'display'</a> property) container elements.  The differences between the two
+properties are as follows.</p>
 
-  <li>When the <a>'display'</a> property is set to <span
-  class="prop-value">none</span>, then the given element does not
-  become part of the rendering tree. With <a>'visibility'</a> set
-  to <span class="prop-value">hidden</span>, however, processing
-  occurs as if the element were part of the rendering tree and still
-  taking up space, but not actually rendered onto the canvas. This
-  distinction has implications for the <a>'tspan'</a>, <a>'tref'</a> and
-  <a>'altGlyph'</a> elements, <a href="interact.html#UIEvents">event processing</a>,
-  for <a href="coords.html#ObjectBoundingBox">bounding box calculations</a>
-  and for calculation of <a href="masking.html#ClippingPaths">clipping paths</a>.
-  If <a>'display'</a> is set to <span class="prop-value">none</span> on a
-  <a>'tspan'</a>, <a>'tref'</a> or <a>'altGlyph'</a> element, then the
-  text string is ignored for the purposes of text layout; however, if
-  <a>'visibility'</a> is set to <span class="prop-value">hidden</span>,
-  the text string is used for text layout (i.e., it takes up space)
-  even though it is not rendered on the canvas. Regarding events, if
-  <a>'display'</a> is set to <span class="prop-value">none</span>,
-  the element receives no events; however, if <a>'visibility'</a>
-  is set to <span class="prop-value">hidden</span>, the element
-  might still receive events, depending on the value of property
-  <a>'pointer-events'</a>. The geometry of a graphics element with
-  <a>'display'</a> set to <span class="prop-value">none</span> is
-  not included in <a href="coords.html#ObjectBoundingBox">bounding box</a>
-  and <a href="masking.html#ClippingPaths">clipping paths</a>
-  calculations; however, even if <a>'visibility'</a> is to
-  <span class="prop-value">hidden</span>, the geometry of the graphics element
-  still contributes to bounding box and clipping path calculations.</li>
-</ul>
+<p>When applied to a container element, setting <a>'display'</a>
+to <span class="prop-value">none</span> causes the container and
+all of its children to be invisible; thus, it acts on groups of
+elements as a group. <a>'visibility'</a>, however, only applies
+to individual graphics elements. Setting <a>'visibility'</a>
+to <span class="prop-value">hidden</span> on a <a>'g'</a>
+will make its children invisible as long as the children do
+not specify their own <a>'visibility'</a> properties as <span
+class="prop-value">visible</span>. Note that <a>'visibility'</a> is
+<em>not</em> an inheritable property.</p>
+
+<p>When the <a>'display'</a> property is set to <span
+class="prop-value">none</span>, then the given element does not
+become part of the rendering tree. With <a>'visibility'</a> set
+to <span class="prop-value">hidden</span>, however, processing
+occurs as if the element were part of the rendering tree and still
+taking up space, but not actually rendered onto the canvas. This
+distinction has implications for the <a>'tspan'</a>, <a>'tref'</a> and
+<a>'altGlyph'</a> elements, <a href="interact.html#UIEvents">event processing</a>,
+for <a href="coords.html#ObjectBoundingBox">bounding box calculations</a>
+and for calculation of <a href="masking.html#ClippingPaths">clipping paths</a>.
+If <a>'display'</a> is set to <span class="prop-value">none</span> on a
+<a>'tspan'</a>, <a>'tref'</a> or <a>'altGlyph'</a> element, then the
+text string is ignored for the purposes of text layout; however, if
+<a>'visibility'</a> is set to <span class="prop-value">hidden</span>,
+the text string is used for text layout (i.e., it takes up space)
+even though it is not rendered on the canvas. Regarding events, if
+<a>'display'</a> is set to <span class="prop-value">none</span>,
+the element receives no events; however, if <a>'visibility'</a>
+is set to <span class="prop-value">hidden</span>, the element
+might still receive events, depending on the value of property
+<a>'pointer-events'</a>. The geometry of a graphics element with
+<a>'display'</a> set to <span class="prop-value">none</span> is
+not included in <a href="coords.html#ObjectBoundingBox">bounding box</a>
+and <a href="masking.html#ClippingPaths">clipping paths</a>
+calculations; however, even if <a>'visibility'</a> is to
+<span class="prop-value">hidden</span>, the geometry of the graphics element
+still contributes to bounding box and clipping path calculations.</p>
 
     <div class="propdef">
       <dl>