- From: SVG Working Group repository <cam+svgwgrepo@mcc.id.au>
- Date: Thu, 13 Jun 2013 15:30:35 -0700
- To: public-svg-wg@w3.org
details: https://svgwg.org/hg/svg2/rev/ec28c0ac0091
branches:
changeset: 514:ec28c0ac0091
user: Cameron McCormack <cam@mcc.id.au>
date: Fri Jun 14 08:28:48 2013 +1000
description:
Fix broken links.
diffstat:
master/conform.html | 2 +-
master/interact.html | 22 +++++++++++-----------
master/pservers.html | 4 ++--
3 files changed, 14 insertions(+), 14 deletions(-)
diffs (191 lines):
diff --git a/master/conform.html b/master/conform.html
--- a/master/conform.html
+++ b/master/conform.html
@@ -28,17 +28,17 @@ they necessarily reference normative tex
within other related specifications. It is only possible to fully
comprehend the conformance requirements of SVG through a complete
reading of all normative references.</p>
<h2 id="ConformingSVGDocuments">Conforming SVG Document Fragments</h2>
<p>An SVG document fragment is a <em>Conforming SVG Document Fragment</em> if
it adheres to the specification described in this document
-(<a href="index.html">Scalable Vector Graphics (SVG) Specification</a>) and also:</p>
+(<a href="Overview.html">Scalable Vector Graphics (SVG) Specification</a>) and also:</p>
<ul>
<li>is <a href="http://www.w3.org/TR/2008/REC-xml-20081126/#sec-well-formed">XML well-formed</a>
([<a href="refs.html#ref-XML10">XML10</a>], section 2.1),</li>
<li>conforms to the <a href="http://www.w3.org/TR/2006/REC-xml-names-20060816/"><cite>Namespaces in XML</cite></a>
specification [<a href="refs.html#ref-XML-NS">XML-NS</a>],</li>
diff --git a/master/interact.html b/master/interact.html
--- a/master/interact.html
+++ b/master/interact.html
@@ -1166,22 +1166,22 @@ element.
</edit:with>
<h2 id="Focus">Focus</h2>
<div class="impl">
<p>When an element is <i>focused</i>, key events received by the
document must be targeted at that element. There may be no element
focused; when no element is focused, key events received by the
- document must be targeted at the <code><a href="#document">Document</a></code>'s root <code><a href="struct.html#SVGElement">svg</a></code> element, if
+ document must be targeted at the <code>Document</code>'s root <code><a href="struct.html#SVGElement">svg</a></code> element, if
there is one. If there is no root element, key events must not be
fired.</p>
<p>User agents may track focus for each <a href="http://www.w3.org/TR/html5/browsers.html#browsing-context">browsing
- context</a> or <code><a href="#document">Document</a></code> individually, or may support
+ context</a> or <code>Document</code> individually, or may support
only one focused element per <a href="http://www.w3.org/TR/html5/browsers.html#top-level-browsing-context">top-level browsing context</a>
— user agents should follow platform conventions in this
regard.</p>
<p>Which elements within a <a href="http://www.w3.org/TR/html5/browsers.html#top-level-browsing-context">top-level browsing context</a>
currently have focus must be independent of whether or not the
<a href="http://www.w3.org/TR/html5/browsers.html#top-level-browsing-context">top-level browsing context</a> itself has the <i>system
focus</i>.</p>
@@ -1189,17 +1189,17 @@ element.
<p id="bc-focus-ergo-bcc-focus">When a <a href="http://www.w3.org/TR/html5/browsers.html#child-browsing-context">child browsing
context</a> is focused, its <a href="http://www.w3.org/TR/html5/browsers.html#browsing-context-container">browsing conrtext
container</a> must also have focus.</p>
<p class="note">When an element is focused, the element matches the
CSS <code>:focus</code> pseudo-class.</p>
</div>
-<h3 id="sequential-focus-navigation-and-the-tabindex-attribute">Sequential focus navigation and the <code title="attr-tabindex"> <a href="#SVGElementTabindexAttribute">tabindex</a> </code> attribute </h3>
+<h3 id="sequential-focus-navigation-and-the-tabindex-attribute">Sequential focus navigation and the <span class="attr-name">'tabindex'</span> attribute</h3>
<dt>
<table class="propdef attrdef">
<tr>
<th>Name</th>
<th>Value</th>
<th>Lacuna value</th>
<th>Animatable</th>
@@ -1283,17 +1283,17 @@ element.
<ul><li>before any <a href="#focusable">focusable</a> element whose <code><a href="#SVGElementTabindexAttribute">tabindex</a></code> attribute has been omitted
or whose value, when parsed, returns an error,</li>
<li>before any <a href="#focusable">focusable</a> element whose <code><a href="#SVGElementTabindexAttribute">tabindex</a></code> attribute has a value equal
to or less than zero,</li>
<li>after any element whose <code><a href="#SVGElementTabindexAttribute">tabindex</a></code> attribute has a value
- greater than zero but less than the value of the <code title="attr-tabindex"><a href="#attr-tabindex">tabindex</a></code> attribute on the
+ greater than zero but less than the value of the <code><a href="#SVGElementTabindexAttribute">tabindex</a></code> attribute on the
element,</li>
<li>after any element whose <code><a href="#SVGElementTabindexAttribute">tabindex</a></code> attribute has a value equal
to the value of the <code><a href="#SVGElementTabindexAttribute">tabindex</a></code>
attribute on the element but that is earlier in the document in
<a href="http://www.w3.org/TR/html5/infrastructure.html#tree-order">tree order</a> than the element,</li>
<li>before any element whose <code><a href="#SVGElementTabindexAttribute">tabindex</a></code> attribute has a value equal
@@ -1326,31 +1326,31 @@ element.
<h4 id="focus-management">Focus management</h4>
<p class="issue">Need to decide how will replace some of the links pertainig to "in a document", "Document", and "being rendered". This is dependent on Document work that needs to be added wrt. tabindex. Do we define our own definitions vs. what is in HTML5?</p>
<p>An element is <dfn id="focusable">focusable</dfn> if the user agent's default
behavior allows it to be focusable or if the element has its
<a href="#specially-focusable">tabindex focus flag</a> set, but only if the element is
- either <a href="rendering.html#being-rendered">being rendered</a> and only if
+ either <a href="#being-rendered">being rendered</a> and only if
neither the element nor any of its ancestors are <a href="http://www.w3.org/TR/html5/editing.html#inert">inert</a>.</p>
<p>User agents should make the <a href="linking.html#AElement">a</a> element <a href="#focusable">focusable</a> as part of their default behavior, unless
platform conventions dictate otherwise:</p>
<p>Notwithstanding the above, user agents may make <em>any</em> element or part of an element
focusable, especially to aid with accessibility or to better match platform conventions.</p>
<hr/><p>The <dfn id="focusing-steps">focusing steps</dfn> for an element are as follows:</p>
- <ol><li><p>If the element is not <a href="infrastructure.html#in-a-document" title="in a Document">in a
+ <ol><li><p>If the element is not <a href="http://www.w3.org/TR/html5/infrastructure.html#in-a-document" title="in a Document">in a
<code>Document</code></a>, or if the element's
- <code><a href="dom.html#document">Document</a></code> has no <a href="http://www.w3.org/TR/html5/browsers.html#browsing-context">browsing context</a>, or if
- the element's <code><a href="dom.html#document">Document</a></code>'s <a href="http://www.w3.org/TR/html5/browsers.html#browsing-context">browsing context</a>
+ <code>Document</code> has no <a href="http://www.w3.org/TR/html5/browsers.html#browsing-context">browsing context</a>, or if
+ the element's <code>Document</code>'s <a href="http://www.w3.org/TR/html5/browsers.html#browsing-context">browsing context</a>
has no <a href="http://www.w3.org/TR/html5/browsers.html#top-level-browsing-context">top-level browsing context</a>, or if the element
is not <a href="#focusable">focusable</a>, then abort these steps.</p></li>
<li><p>If focusing the element will remove the focus from another
element, then run the <a href="#unfocusing-steps">unfocusing steps</a> for that
element.</p></li>
<li>
@@ -1375,22 +1375,22 @@ element.
</ol><p>When an element that is focused stops being a
<a href="#focusable">focusable</a> element, or stops being focused without
another element being explicitly focused in its stead, the user
agent should synchronously run the <a href="#unfocusing-steps">unfocusing steps</a> for
the affected element only.</p>
<p class="example">For example, this might happen because the
- element is removed from its <code><a href="dom.html#document">Document</a></code>.</p>
+ element is removed from its <code>Document</code>.</p>
</div>
- <hr/><p>An element is <dfn id="being-rendered">being rendered</dfn> if it is <a href="infrastructure.html#in-a-document">in a
+ <hr/><p>An element is <dfn id="being-rendered">being rendered</dfn> if it is <a href="http://www.w3.org/TR/html5/infrastructure.html#in-a-document">in a
<code>Document</code></a>, either its parent node is itself
- <a href="#being-rendered">being rendered</a> or it is the <code><a href="dom.html#document">Document</a></code> node,
+ <a href="#being-rendered">being rendered</a> or it is the <code>Document</code> node,
and it is not explicitly excluded from the rendering using either:</p>
<ul class="brief"><li>the CSS 'display' property's 'none' value, or</li>
<li>the 'visibility' property's 'collapse' value unless it is being treated as equivalent to the 'hidden' value, or</li>
<li>some equivalent in other styling languages.</li>
</ul><p class="note">Just being off-screen does not mean the element is
not <a href="#being-rendered">being rendered</a>.</p>
<hr/>
diff --git a/master/pservers.html b/master/pservers.html
--- a/master/pservers.html
+++ b/master/pservers.html
@@ -2136,17 +2136,17 @@ processed.</p>
<dd>
<p>
Defines a single path in the <a>'hatch'</a>.
</p>
<dl class="attrdef-svg2">
- <dt>Value</dt> <dd><a href="#PathData">Path data</a></dd>
+ <dt>Value</dt> <dd><a href="paths.html#PathData">Path data</a></dd>
<dt><a>Lacuna value</a></dt> <dd>An infinite line, see below</dd>
<dt><a>Animatable</a></dt> <dd>yes</dd>
</dl>
</dd>
<dt id="HatchPathElementOffsetAttribute"><span class="adef">offset</span></dt>
@@ -2165,17 +2165,17 @@ processed.</p>
</dl>
</dd>
</dl>
<h4 id="HatchPathNotes">Notes on hatch paths</h4>
-<p>Hatch paths are defined with the same <a href="#PathData">Path
+<p>Hatch paths are defined with the same <a href="paths.html#PathData">Path
data</a> used in the <a>'d'</a> attribute of the <a>'path'</a>
element. The path is defined relative to the origin of each strip
translated in the <var>x</var> direction by the <a>'offset'</a>
(the <var>y</var> direction is aligned along the infinite axis of the
strip).
</p>
<div class="figure">
Received on Thursday, 13 June 2013 22:31:00 UTC