svg.patch

# HG changeset patch
# User David Burns <dburns@mozilla.com>
# Date 1384513331 0
#      Fri Nov 15 11:02:11 2013 +0000
# Node ID 2ad686ef97d0b711bcc491294a47e13750c0ff0e
# Parent  4fa452d6af4cf85a783ca17265adb45a09666d7d
imported patch svg

diff --git a/17_non_html_content.html b/17_non_html_content.html
--- a/17_non_html_content.html
+++ b/17_non_html_content.html
@@ -1,35 +1,37 @@
 <section>
   <h2>Handling non-HTML Content</h2>
   <p>Non-HTML content MUST be treated in the same manner as HTML if the Non-HTML if the browser 
     creates a DOM object for the content of the document. If a DOM Object is not created then 
     how it handled SHOULD be non-normative</p>
 
   <section>
     <h2>XML</h2>
-    <p>This section describes XML documents as described in [[!XML10]]. For XHTML documents the remote end should treat them as HTML documents 
+    <p>This section describes XML documents as described in [[XML10]]. For XHTML documents the remote end should treat them as HTML documents 
     and not have the caveats, below, applied.</p>
       <p>Since Browsers create a DOM object for XML pages it is expected that we can interogate 
       them as a normal HTML document however the following differences should be noted:</p>
       <ul>
         <li>Visibility Checks MAY be skipped since XML nodes can not be hidden and <code>isDisplayed</code> MUST return true<li>
         <li>Getting computed styles of elements MUST return an empty string</li>
         <li>Position and Size of element MUST return null for elements in the map returned</li>
         <li>Attempts to clear the node MUST return an <code><a href='#status-unsupported-operation'>unsupported operation</a></code> </li>
         <li>Attempts to send keys to a node MUST return an exception <code><a href='#status-unsupported-operation'>unsupported operation</a></code></li>
         <li><code>isEnabled</code> MUST return false</li>
         <li><code>isSelected</code> MUST return false</li>
         <li><code>submit</code> MUST return an exception <code><a href='#status-unsupported-operation'>unsupported operation</a></code></li>
       </ul>
   </section>
   <section>
     <h2>SVG</h2>
-    
-    <p>TODO: describe how the SVG DOM maps to WebElement implementations.</p>
+    <p>This section described SVG documents in a browser as described by [[SVG2]].
+    Since browsers create a DOM tree for SVG documents it is expected that WebDriver 
+    can interrogate the DOM as a normal HTML document.
+    </p>
   </section>
   
   <section>
     <h2>Working with Accessibility APIs</h2>
     
     <p>Many accessibility APIs represent the UI as a series of nested nodes. It is possible to map these nodes to <code>WebElement</code> instances. In order to function properly, it is likely that additional element locating strategies will be required.</p>
     
     <p class="note">This is one way in which it might be possible to test mobile applications that marry a native wrapper around a series of HTML views.</p>
diff --git a/webdriver-spec.html b/webdriver-spec.html
--- a/webdriver-spec.html
+++ b/webdriver-spec.html
@@ -2242,35 +2242,37 @@ assertEquals(style, recovered);
 <section>
   <h2>Handling non-HTML Content</h2>
   <p>Non-HTML content MUST be treated in the same manner as HTML if the Non-HTML if the browser 
     creates a DOM object for the content of the document. If a DOM Object is not created then 
     how it handled SHOULD be non-normative</p>
 
   <section>
     <h2>XML</h2>
-    <p>This section describes XML documents as described in [[!XML10]]. For XHTML documents the remote end should treat them as HTML documents 
+    <p>This section describes XML documents as described in [[XML10]]. For XHTML documents the remote end should treat them as HTML documents 
     and not have the caveats, below, applied.</p>
       <p>Since Browsers create a DOM object for XML pages it is expected that we can interogate 
       them as a normal HTML document however the following differences should be noted:</p>
       <ul>
         <li>Visibility Checks MAY be skipped since XML nodes can not be hidden and <code>isDisplayed</code> MUST return true<li>
         <li>Getting computed styles of elements MUST return an empty string</li>
         <li>Position and Size of element MUST return null for elements in the map returned</li>
         <li>Attempts to clear the node MUST return an <code><a href='#status-unsupported-operation'>unsupported operation</a></code> </li>
         <li>Attempts to send keys to a node MUST return an exception <code><a href='#status-unsupported-operation'>unsupported operation</a></code></li>
         <li><code>isEnabled</code> MUST return false</li>
         <li><code>isSelected</code> MUST return false</li>
         <li><code>submit</code> MUST return an exception <code><a href='#status-unsupported-operation'>unsupported operation</a></code></li>
       </ul>
   </section>
   <section>
     <h2>SVG</h2>
-    
-    <p>TODO: describe how the SVG DOM maps to WebElement implementations.</p>
+    <p>This section described SVG documents in a browser as described by [[SVG2]].
+    Since browsers create a DOM tree for SVG documents it is expected that WebDriver 
+    can interrogate the DOM as a normal HTML document.
+    </p>
   </section>
   
   <section>
     <h2>Working with Accessibility APIs</h2>
     
     <p>Many accessibility APIs represent the UI as a series of nested nodes. It is possible to map these nodes to <code>WebElement</code> instances. In order to function properly, it is likely that additional element locating strategies will be required.</p>
     
     <p class="note">This is one way in which it might be possible to test mobile applications that marry a native wrapper around a series of HTML views.</p>