Last active
December 28, 2015 09:39
-
-
Save AutomatedTester/7481065 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # HG changeset patch | |
| # User David Burns <dburns@mozilla.com> | |
| # Date 1384513272 0 | |
| # Fri Nov 15 11:01:12 2013 +0000 | |
| # Node ID 4fa452d6af4cf85a783ca17265adb45a09666d7d | |
| # Parent e91efdc2c8ce7f28f3af10f5fec3c7eada7da2f6 | |
| imported patch xml_errors | |
| 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,29 +1,29 @@ | |
| <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 XML //TODO(David) add cite. 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 exception (//TODO(David) Add details of exception thrown</li> | |
| - <li>Attempts to send keys to a node MUST return an exception (//TODO(David) Add details of exception thrown</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 (//TODO(David) Add details of exception thrown</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> | |
| </section> | |
| diff --git a/webdriver-spec.html b/webdriver-spec.html | |
| --- a/webdriver-spec.html | |
| +++ b/webdriver-spec.html | |
| @@ -2242,29 +2242,29 @@ 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 XML //TODO(David) add cite. 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 exception (//TODO(David) Add details of exception thrown</li> | |
| - <li>Attempts to send keys to a node MUST return an exception (//TODO(David) Add details of exception thrown</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 (//TODO(David) Add details of exception thrown</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> | |
| </section> | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment