Skip to content

Commit

Permalink
Tidy up language around hasFeature().
Browse files Browse the repository at this point in the history
  • Loading branch information
annevk committed Aug 3, 2015
1 parent e57a716 commit cc5db00
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 15 deletions.
15 changes: 7 additions & 8 deletions dom.bs
Original file line number Diff line number Diff line change
Expand Up @@ -4999,14 +4999,13 @@ method, when invoked, must run these steps:
<li>Return <var>doc</var>.
</ol>

The <dfn method for="DOMImplementation">hasFeature()</dfn> method
must return true.

<p class=note>{{hasFeature()}}
originally would report whether the user agent claimed to support a given DOM
feature, but experience proved it was not nearly as reliable or granular as
simply checking whether the desired objects, attributes, or methods existed.
As such, it should no longer be used, but continues to exist (and simply
The <dfn method for="DOMImplementation"><code>hasFeature()</code></dfn> method, when
invoked, must return true.

<p class="note no-backref">{{hasFeature()}} originally would report whether the user agent
claimed to support a given DOM feature, but experience proved it was not nearly as
reliable or granular as simply checking whether the desired objects, attributes, or
methods existed. As such, it is no longer to be used, but continues to exist (and simply
returns true) so that old pages don't stop working.

</div>
Expand Down
13 changes: 6 additions & 7 deletions dom.html
Original file line number Diff line number Diff line change
Expand Up @@ -6583,15 +6583,14 @@ <h4 class="heading settled" data-level="4.5.1" id="interface-domimplementation">
</ol>


<p>The <dfn class="idl-code" data-dfn-for="DOMImplementation" data-dfn-type="method" data-export="" id="dom-domimplementation-hasfeature">hasFeature()<a class="self-link" href="#dom-domimplementation-hasfeature"></a></dfn> method
must return true.</p>
<p>The <dfn class="idl-code" data-dfn-for="DOMImplementation" data-dfn-type="method" data-export="" id="dom-domimplementation-hasfeature"><code>hasFeature()</code><a class="self-link" href="#dom-domimplementation-hasfeature"></a></dfn> method, when
invoked, must return true.</p>


<p class="note" role="note"><code class="idl"><a data-link-type="idl" href="#dom-domimplementation-hasfeature">hasFeature()</a></code>
originally would report whether the user agent claimed to support a given DOM
feature, but experience proved it was not nearly as reliable or granular as
simply checking whether the desired objects, attributes, or methods existed.
As such, it should no longer be used, but continues to exist (and simply
<p class="note no-backref" role="note"><code class="idl"><a data-link-type="idl" href="#dom-domimplementation-hasfeature">hasFeature()</a></code> originally would report whether the user agent
claimed to support a given DOM feature, but experience proved it was not nearly as
reliable or granular as simply checking whether the desired objects, attributes, or
methods existed. As such, it is no longer to be used, but continues to exist (and simply
returns true) so that old pages don’t stop working.

</p></div>
Expand Down

0 comments on commit cc5db00

Please sign in to comment.