Permalink
Browse files

Note how the SVG currently implemented in browsers is a mix of SVG 1.…

…1 and SVG Tiny 1.2

Browsers do not currently follow any specifications exactly, for
historical and practical reasons. This attempts to clarify what
features are best avoided, and what features can be relied on.

Discussion: #126
Closes #327.
  • Loading branch information...
1 parent 83c6889 commit 969c45b2478d1d2d3be8564ec85dc316a53c8bcf Taylor Hunt committed with zcorpan Nov 10, 2015
Showing with 42 additions and 5 deletions.
  1. +42 −5 source
View
@@ -37275,16 +37275,52 @@ dictionary <dfn>TrackEventInit</dfn> : <span>EventInit</span> {
</div>
- <p>When the SVG <code data-x="">foreignObject</code> element contains elements from the <span>HTML
- namespace</span>, such elements must all be <span>flow content</span>. <ref spec=SVG></p>
+ <p>When the SVG <code data-x="">foreignObject</code> element contains elements
+ from the <span>HTML namespace</span>, such elements must all be <span>flow content</span>.
+ <ref spec=SVG></p>
- <p>The content model for <code data-x="">title</code> elements in the <span>SVG namespace</span>
- inside <span>HTML documents</span> is <span>phrasing content</span>. (This further constrains the
- requirements given in the SVG specification.)</p>
+ <p>The content model for <code data-x="svg:title">title</code> elements in the
+ <span>SVG namespace</span> inside <span>HTML documents</span> is <span>phrasing content</span>.
+ (This further constrains the requirements given in the SVG specification.)</p>
<p>The semantics of SVG elements are defined by the SVG specification and <span>other applicable
specifications</span>. <ref spec=SVG></p>
+ <p><strong>User agent requirements</strong>: SVG as implemented today follows neither SVG 1.1 nor
+ SVG Tiny 1.2 precisely, instead implementing subsets of each. Although it is hoped that the
+ in-progress SVG 2 specification is a more realistic target for implementations, until that
+ specification is ready, user agents must implement the SVG 1.1 specification with the following
+ willful violations and additions. <ref spec=SVG11> <ref spec=SVGTiny12> <ref spec=SVG2></p>
@foolip
foolip Jan 28, 2016 Member

These three spec refs lead nowhere. Will open an issue.

+
+ <p>The following features from SVG 1.1 must not be implemented:</p>
+
+ <ul>
+ <li>The <code data-x="">tref</code> element</li>
+ <li>The <code data-x="">cursor</code> element (use CSS's <code data-x="">cursor</code> property
+ instead)</li>
+ <li>The font-defining elements: <code data-x="">font</code>, <code data-x="">glyph</code>,
+ <code data-x="">missing-glyph</code>, <code data-x="">hkern</code>,
+ <code data-x="">vkern</code>, <code data-x="">font-face</code>,
+ <code data-x="">font-face-src</code>, <code data-x="">font-face-uri</code>,
+ <code data-x="">font-face-format</code>, and <code data-x="">font-face-name</code> (use
+ CSS's <code data-x="">@font-face</code> instead)</li>
+ <li>The <code data-x="">externalResourcesRequired</code> attribute</li>
+ <li>The <code data-x="">enable-background</code> property</li>
+ <li>The <code data-x="">contentScriptType</code> and <code data-x="">contentStyleType</code>
+ attributes (use the <code data-x="">type</code> attribute on the <code data-x="">script</code>
+ and <code data-x="">style</code> elements instead)</li>
+ </ul>
+
+ <p>The following features from SVG Tiny 1.2 must be implemented:</p>
+
+ <ul>
+ <li>The <code data-x="">non-scaling-stroke</code> value for the
+ <code data-x="">vector-effect</code> property</li>
+ <li>The <code data-x="">class</code> attribute is allowed on all SVG elements</li>
+ <li>The <code data-x="">tabindex</code> attribute is allowed on visible SVG elements</li>
+ <li>The ARIA accessibility attributes are allowed on all SVG elements</li>
+ </ul>
+
<hr>
@@ -118769,6 +118805,7 @@ INSERT INTERFACES HERE
Takeshi Yoshino,
<span data-x="" lang="tr">Tantek &Ccedil;elik</span>,
&#30000;&#26449;&#20581;&#20154; (TAMURA Kent),
+ Taylor Hunt,
Ted Mielczarek,
Terrence Wood,
Tetsuharu OHZEKI,

0 comments on commit 969c45b

Please sign in to comment.