Permalink
Browse files

Editorial: use implementer instead of implementor

Closes #3231.
  • Loading branch information...
annevk committed Nov 20, 2017
1 parent cc3fcc8 commit f8f9c6c222ce79c2f8df185521aaa291c7301419
Showing with 21 additions and 20 deletions.
  1. +1 −1 FAQ.md
  2. +20 −19 source
View
2 FAQ.md
@@ -24,7 +24,7 @@ The whole standard is more or less stable. There are some parts of it that descr
In practice, implementations all follow the latest standard anyway, not so-called "finished" snapshots. The problem with following a snapshot is that you end up following something that is _known to be wrong_. That's obviously not the way to get interoperability!
This has in fact been a real problem at the W3C, where mistakes are found and fixed in the editors' drafts of specifications, but implementors who aren't fully engaged in the process go and implement obsolete snapshots instead, including those bugs. This has resulted in serious differences between browsers.
This has in fact been a real problem at the W3C, where mistakes are found and fixed in the editors' drafts of specifications, but implementers who aren't fully engaged in the process go and implement obsolete snapshots instead, including those bugs. This has resulted in serious differences between browsers.
For more information on this, see the WHATWG FAQ entry [What does "Living Standard" mean?](https://whatwg.org/faq#living-standard).
View
39 source
@@ -330,7 +330,7 @@
<!-- NON-NORMATIVE SECTION -->
<p>This specification is intended for authors of documents and scripts that use the features
defined in this specification<span w-nodev>, implementors of tools that operate on pages that
defined in this specification<span w-nodev>, implementers of tools that operate on pages that
use the features defined in this specification, and individuals wishing to establish the
correctness of documents or implementations with respect to the requirements of this
specification</span>.</p>
@@ -827,7 +827,7 @@ interface <dfn data-x="">Example</dfn> {
examining the forum sites that they participate in) to determine whether the person should be
prevented from voting in an election.</p>
<p>Since the malevolent purposes can be remarkably evil, user agent implementors are encouraged to
<p>Since the malevolent purposes can be remarkably evil, user agent implementers are encouraged to
consider how to provide their users with tools to minimize leaking information that could be used
to fingerprint a user.</p>
@@ -2206,8 +2206,8 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
<h4>Conformance classes</h4>
<p>This specification describes the conformance criteria for <span w-nodev>user agents
(relevant to implementors) and</span> documents<span w-nodev> (relevant to authors and
authoring tool implementors)</span>.</p>
(relevant to implementers) and</span> documents<span w-nodev> (relevant to authors and
authoring tool implementers)</span>.</p>
<p><dfn>Conforming documents</dfn> are those that comply with all the conformance criteria for
documents. For readability, some of these conformance requirements are phrased as conformance
@@ -9614,7 +9614,7 @@ partial interface <dfn id="document" data-lt="">Document</dfn> {
</div>
<p class="note">This API has fallen out of favor in the implementor and standards community, as
<p class="note">This API has fallen out of favor in the implementer and standards community, as
it globally exposes <code>script</code> or <span>SVG <code>script</code></span> elements. As such,
it is not available in newer contexts, such as when running <span data-x="module script">module
scripts</span> or when running scripts in a <span>shadow tree</span>. We are looking into creating
@@ -15997,7 +15997,7 @@ interface <dfn>HTMLHeadingElement</dfn> : <span>HTMLElement</span> {};</pre>
<!-- http://www.brucelawson.co.uk/2009/html-5-is-a-mess/#comment-618895 -->
<p>How a user agent exposes such multi-level headings in user interfaces (e.g. in tables of
contents or search results) is left open to implementors, as it is a user interface issue. The
contents or search results) is left open to implementers, as it is a user interface issue. The
first example above could be rendered as:</p>
<pre>The reality dysfunction: Space is not the only void</pre>
@@ -16986,7 +16986,7 @@ Space is not the only void</pre>
<p>These default headings ("Untitled document", "Navigation", "Sidebar") are not specified by
this specification, and might vary with the user's language, the page's language, the user's
preferences, the user agent implementor's preferences, etc.</p>
preferences, the user agent implementer's preferences, etc.</p>
</div>
@@ -23250,7 +23250,7 @@ interface <dfn>HTMLHyperlinkElementUtils</dfn> {
(e.g. "<code data-x="">.txt</code>").</p>
<p class="note">This last step would make it impossible to download executables, which might not
be desirable. As always, implementors are forced to balance security and usability in this
be desirable. As always, implementers are forced to balance security and usability in this
matter.</p>
</li>
@@ -29022,7 +29022,7 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
<code>figcaption</code> elements, or the <code data-x="attr-title">title</code> attribute, to
provide the image's caption.</p>
<p>As a last resort, implementors should either set the <code data-x="attr-img-alt">alt</code>
<p>As a last resort, implementers should either set the <code data-x="attr-img-alt">alt</code>
attribute to the empty string, under the assumption that the image is a purely decorative image
that doesn't add any information but is still specific to the surrounding content, or omit the
<code data-x="attr-img-alt">alt</code> attribute altogether, under the assumption that the image is
@@ -38166,7 +38166,7 @@ dictionary <dfn>TrackEventInit</dfn> : <span>EventInit</span> {
<div w-nodev>
<h5>Best practices for implementors of media elements</h5>
<h5>Best practices for implementers of media elements</h5>
<!-- NON-NORMATIVE SECTION -->
@@ -39079,7 +39079,7 @@ interface <dfn>HTMLTableElement</dfn> : <span>HTMLElement</span> {
</div>
<p class="note">Authors <span w-nodev>and implementors</span> are encouraged to consider
<p class="note">Authors <span w-nodev>and implementers</span> are encouraged to consider
using some of the <a href="#table-layout-techniques">table design techniques</a> described below
to make tables easier to navigate for users.</p>
@@ -58497,7 +58497,7 @@ not-slash = %x0000-002E / %x0030-10FFFF
<p>This specification does not define how XSLT interacts with the <code>script</code> element.
However, in the absence of another specification actually defining this, here are some guidelines
for implementors, based on existing implementations:</p>
for implementers, based on existing implementations:</p>
<ul>
@@ -58979,7 +58979,7 @@ interface <dfn>HTMLTemplateElement</dfn> : <span>HTMLElement</span> {
<p>This specification does not define how XSLT and XPath interact with the <code>template</code>
element. However, in the absence of another specification actually defining this, here are some
guidelines for implementors, which are intended to be consistent with other processing described
guidelines for implementers, which are intended to be consistent with other processing described
in this specification:</p>
<ul>
@@ -82435,7 +82435,7 @@ interface <dfn>Location</dfn> { // but see also <a href="#the-location-interface
data-x="concept-navigate-mature">matured</dfn>.</p></li>
<li><p><i>Fragment loop</i>: <span>Spin the event loop</span> for a user-agent-defined amount of
time, as desired by the user agent implementor. (This is intended to allow the user agent to
time, as desired by the user agent implementer. (This is intended to allow the user agent to
optimize the user experience in the face of performance concerns.)</p></li>
<li><p>If the <code>Document</code> object has no parser, or its parser has <span data-x="stop
@@ -85045,7 +85045,7 @@ NETWORK:
"fallback entry", then the user agent may skip this URL.</p>
<p class="note">This is intended to allow user agents to expire resources not listed in the
manifest from the cache. Generally, implementors are urged to use an approach that expires
manifest from the cache. Generally, implementers are urged to use an approach that expires
lesser-used resources first.</p>
</li>
@@ -91638,7 +91638,7 @@ interface <dfn>NavigatorID</dfn> {
<!-- similar paragraph in next section -->
<p class="warning">Any information in this API that varies from user to user can be used to
profile the user. In fact, if enough such information is available, a user can actually be
uniquely identified. For this reason, user agent implementors are strongly urged to include as
uniquely identified. For this reason, user agent implementers are strongly urged to include as
little information in this API as possible.
<!--INSERT FINGERPRINT-->
</p>
@@ -93493,7 +93493,7 @@ source.addEventListener('remove', removeHandler, false);</pre>
<p>Using this API rather than emulating it using <code>XMLHttpRequest</code> or an
<code>iframe</code> allows the user agent to make better use of network resources in cases where
the user agent implementor and the network operator are able to coordinate in advance. Amongst
the user agent implementer and the network operator are able to coordinate in advance. Amongst
other benefits, this can result in significant savings in battery life on portable devices. This
is discussed further in the section below on <a href="#eventsource-push">connectionless
push</a>.</p>
@@ -104426,7 +104426,7 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
<p class="note">The algorithm described below places no limit on the depth of the DOM tree
generated, or on the length of tag names, attribute names, attribute values, <code>Text</code>
nodes, etc. While implementors are encouraged to avoid arbitrary limits, it is recognized that <a
nodes, etc. While implementers are encouraged to avoid arbitrary limits, it is recognized that <a
href="#hardwareLimitations">practical concerns</a> will likely force user agents to impose nesting
depth constraints.</p>
@@ -110278,7 +110278,7 @@ Hello.&lt;/pre></pre>
<p>The suggestions in this section generally assume a visual output medium with a resolution of
96dpi or greater, but HTML is intended to apply to multiple media (it is a
<i>media-independent</i> language). User agent implementors are encouraged to adapt the
<i>media-independent</i> language). User agent implementers are encouraged to adapt the
suggestions in this section to their target media.</p>
<hr>
@@ -120987,6 +120987,7 @@ INSERT INTERFACES HERE
贺师俊 (HE Shi-Jun), <!-- hax on GitHub -->
Shiki Okasaka,
Shivani Sharma,
shreyateeza, <!-- GitHub -->
Shubheksha Jalan,
Sierk Bornemann,
Sigbj&oslash;rn Finne,

0 comments on commit f8f9c6c

Please sign in to comment.