[html5] r8876 - [e] (0) Fix language to be more consistent (behavior->behaviour) Affected topics [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Jan 6 17:02:47 PST 2015
Author: ianh
Date: 2015-01-06 17:02:44 -0800 (Tue, 06 Jan 2015)
New Revision: 8876
Modified:
complete.html
index
source
Log:
[e] (0) Fix language to be more consistent (behavior->behaviour)
Affected topics: CSS, Canvas, DOM APIs, HTML, HTML Syntax and Parsing, Microdata, Rendering, Security, Video and Audio
Modified: complete.html
===================================================================
--- complete.html 2015-01-07 00:52:49 UTC (rev 8875)
+++ complete.html 2015-01-07 01:02:44 UTC (rev 8876)
@@ -375,7 +375,7 @@
<h2 id=contents class="no-num no-toc">Full table of contents</h2>
<ol class=toc><li id=toc-introduction><a href=#introduction>1 Introduction</a><ol><li><a href=#abstract>1.1 Where does this specification fit?</a><li><a href=#is-this-html5?>1.2 Is this HTML5?</a><li><a href=#background>1.3 Background</a><li><a href=#audience>1.4 Audience</a><li><a href=#scope>1.5 Scope</a><li><a href=#history-2>1.6 History</a><li><a href=#design-notes>1.7 Design notes</a><ol><li><a href=#serialisability-of-script-execution>1.7.1 Serialisability of script execution</a><li><a href=#compliance-with-other-specifications>1.7.2 Compliance with other specifications</a><li><a href=#extensibility>1.7.3 Extensibility</a></ol><li><a href=#html-vs-xhtml>1.8 HTML vs XHTML</a><li><a href=#structure-of-this-specification>1.9 Structure of this specification</a><ol><li><a href=#how-to-read-this-specification>1.9.1 How to read this specification</a><li><a href=#typographic-conventions>1.9.2 Typographic conventions</a></ol><li><a href=#fingerprint>1.10 Privacy concerns</a><
ol><li><a href=#fingerprint-postMessage>1.10.1 Cross-site communication</a></ol><li><a href=#a-quick-introduction-to-html>1.11 A quick introduction to HTML</a><ol><li><a href=#writing-secure-applications-with-html>1.11.1 Writing secure applications with HTML</a><li><a href=#common-pitfalls-to-avoid-when-using-the-scripting-apis>1.11.2 Common pitfalls to avoid when using the scripting APIs</a><li><a href=#how-to-catch-mistakes-when-writing-html:-validators-and-conformance-checkers>1.11.3 How to catch mistakes when writing HTML: validators and conformance checkers</a></ol><li><a href=#conformance-requirements-for-authors>1.12 Conformance requirements for authors</a><ol><li><a href=#presentational-markup>1.12.1 Presentational markup</a><li><a href=#syntax-errors>1.12.2 Syntax errors</a><li><a href=#restrictions-on-content-models-and-on-attribute-values>1.12.3 Restrictions on content models and on attribute values</a></ol><li><a href=#suggested-reading>1.13 Suggested reading</a>
</ol><li id=toc-infrastructure><a href=#infrastructure>2 Common infrastructure</a><ol><li><a href=#terminology>2.1 Terminology</a><ol><li><a href=#resources>2.1.1 Resources</a><li><a href=#xml>2.1.2 XML</a><li><a href=#dom-trees>2.1.3 DOM trees</a><li><a href=#scripting-2>2.1.4 Scripting</a><li><a href=#plugins>2.1.5 Plugins</a><li><a href=#encoding-terminology>2.1.6 Character encodings</a></ol><li><a href=#conformance-requirements>2.2 Conformance requirements</a><ol><li><a href=#conformance-classes>2.2.1 Conformance classes</a><li><a href=#dependencies>2.2.2 Dependencies</a><li><a href=#extensibility-2>2.2.3 Extensibility</a><li><a href=#interactions-with-xpath-and-xslt>2.2.4 Interactions with XPath and XSLT</a></ol><li><a href=#case-sensitivity-and-string-comparison>2.3 Case-sensitivity and string comparison</a><li><a href=#common-microsyntaxes>2.4 Common microsyntaxes</a><ol><li><a href=#common-parser-idioms>2.4.1 Common parser idioms</a><li><a href=#boolean-attributes>2.
4.2 Boolean attributes</a><li><a href=#keywords-and-enumerated-attributes>2.4.3 Keywords and enumerated attributes</a><li><a href=#numbers>2.4.4 Numbers</a><ol><li><a href=#signed-integers>2.4.4.1 Signed integers</a><li><a href=#non-negative-integers>2.4.4.2 Non-negative integers</a><li><a href=#floating-point-numbers>2.4.4.3 Floating-point numbers</a><li><a href=#percentages-and-dimensions>2.4.4.4 Percentages and lengths</a><li><a href=#lists-of-integers>2.4.4.5 Lists of integers</a><li><a href=#lists-of-dimensions>2.4.4.6 Lists of dimensions</a></ol><li><a href=#dates-and-times>2.4.5 Dates and times</a><ol><li><a href=#months>2.4.5.1 Months</a><li><a href=#dates>2.4.5.2 Dates</a><li><a href=#yearless-dates>2.4.5.3 Yearless dates</a><li><a href=#times>2.4.5.4 Times</a><li><a href=#local-dates-and-times>2.4.5.5 Local dates and times</a><li><a href=#time-zones>2.4.5.6 Time zones</a><li><a href=#global-dates-and-times>2.4.5.7 Global dates and times</a><li><a href=#weeks>2.4.5.
8 Weeks</a><li><a href=#durations>2.4.5.9 Durations</a><li><a href=#vaguer-moments-in-time>2.4.5.10 Vaguer moments in time</a></ol><li><a href=#colours>2.4.6 Colours</a><li><a href=#space-separated-tokens>2.4.7 Space-separated tokens</a><li><a href=#comma-separated-tokens>2.4.8 Comma-separated tokens</a><li><a href=#syntax-references>2.4.9 References</a><li><a href=#mq>2.4.10 Media queries</a></ol><li><a href=#urls>2.5 URLs</a><ol><li><a href=#terminology-2>2.5.1 Terminology</a><li><a href=#resolving-urls>2.5.2 Resolving URLs</a><li><a href=#dynamic-changes-to-base-urls>2.5.3 Dynamic changes to base URLs</a></ol><li><a href=#fetching-resources>2.6 Fetching resources</a><ol><li><a href=#terminology-3>2.6.1 Terminology</a><li><a href=#processing-model>2.6.2 Processing model</a><li><a href=#encrypted-http-and-related-security-concerns>2.6.3 Encrypted HTTP and related security concerns</a><li><a href=#content-type-sniffing>2.6.4 Determining the type of a resource</a><li><a href=
#extracting-character-encodings-from-meta-elements>2.6.5 Extracting character encodings from <code>meta</code> elements</a><li><a href=#cors-settings-attributes>2.6.6 CORS settings attributes</a><li><a href=#cors-enabled-fetch>2.6.7 CORS-enabled fetch</a></ol><li><a href=#common-dom-interfaces>2.7 Common DOM interfaces</a><ol><li><a href=#reflecting-content-attributes-in-idl-attributes>2.7.1 Reflecting content attributes in IDL attributes</a><li><a href=#collections-2>2.7.2 Collections</a><ol><li><a href=#the-htmlallcollection-interface>2.7.2.1 The <code>HTMLAllCollection</code> interface</a><li><a href=#the-htmlformcontrolscollection-interface>2.7.2.2 The <code>HTMLFormControlsCollection</code> interface</a><li><a href=#the-htmloptionscollection-interface>2.7.2.3 The <code>HTMLOptionsCollection</code> interface</a><li><a href=#the-htmlpropertiescollection-interface>2.7.2.4 The <code>HTMLPropertiesCollection</code> interface</a></ol><li><a href=#the-domstringmap-interface>2.
7.3 The <code>DOMStringMap</code> interface</a><li><a href=#domelementmap>2.7.4 DOMElementMap</a><li><a href=#transferable-objects>2.7.5 Transferable objects</a><li><a href=#safe-passing-of-structured-data>2.7.6 Safe passing of structured data</a><li><a href=#callbacks>2.7.7 Callbacks</a><li><a href=#garbage-collection>2.7.8 Garbage collection</a></ol><li><a href=#namespaces>2.8 Namespaces</a></ol><li id=toc-dom><a href=#dom>3 Semantics, structure, and APIs of HTML documents</a><ol><li><a href=#documents>3.1 Documents</a><ol><li><a href=#the-document-object>3.1.1 The <code>Document</code> object</a><li><a href=#resource-metadata-management>3.1.2 Resource metadata management</a><li><a href=#dom-tree-accessors>3.1.3 DOM tree accessors</a><li><a href=#loading-xml-documents>3.1.4 Loading XML documents</a></ol><li><a href=#elements>3.2 Elements</a><ol><li><a href=#semantics-2>3.2.1 Semantics</a><li><a href=#elements-in-the-dom>3.2.2 Elements in the DOM</a><li><a href=#element-def
initions>3.2.3 Element definitions</a><ol><li><a href=#attributes>3.2.3.1 Attributes</a></ol><li><a href=#content-models>3.2.4 Content models</a><ol><li><a href=#the-nothing-content-model>3.2.4.1 The "nothing" content model</a><li><a href=#kinds-of-content>3.2.4.2 Kinds of content</a><ol><li><a href=#metadata-content>3.2.4.2.1 Metadata content</a><li><a href=#flow-content>3.2.4.2.2 Flow content</a><li><a href=#sectioning-content>3.2.4.2.3 Sectioning content</a><li><a href=#heading-content>3.2.4.2.4 Heading content</a><li><a href=#phrasing-content>3.2.4.2.5 Phrasing content</a><li><a href=#embedded-content-2>3.2.4.2.6 Embedded content</a><li><a href=#interactive-content>3.2.4.2.7 Interactive content</a><li><a href=#palpable-content>3.2.4.2.8 Palpable content</a><li><a href=#script-supporting-elements>3.2.4.2.9 Script-supporting elements</a></ol><li><a href=#transparent-content-models>3.2.4.3 Transparent content models</a><li><a href=#paragraphs>3.2.4.4 Paragraphs</a></ol><li>
<a href=#global-attributes>3.2.5 Global attributes</a><ol><li><a href=#the-id-attribute>3.2.5.1 The <code>id</code> attribute</a><li><a href=#the-title-attribute>3.2.5.2 The <code>title</code> attribute</a><li><a href=#the-lang-and-xml:lang-attributes>3.2.5.3 The <code>lang</code> and <code>xml:lang</code> attributes</a><li><a href=#the-translate-attribute>3.2.5.4 The <code>translate</code> attribute</a><li><a href=#the-xml:base-attribute-(xml-only)>3.2.5.5 The <code>xml:base</code> attribute (XML only)</a><li><a href=#the-dir-attribute>3.2.5.6 The <code>dir</code> attribute</a><li><a href=#classes>3.2.5.7 The <code>class</code> attribute</a><li><a href=#the-style-attribute>3.2.5.8 The <code>style</code> attribute</a><li><a href=#embedding-custom-non-visible-data-with-the-data-*-attributes>3.2.5.9 Embedding custom non-visible data with the <code>data-*</code> attributes</a></ol><li><a href=#requirements-relating-to-the-bidirectional-algorithm>3.2.6 Requirements relating to t
he bidirectional algorithm</a><ol><li><a href=#authoring-conformance-criteria-for-bidirectional-algorithm-formatting-characters>3.2.6.1 Authoring conformance criteria for bidirectional-algorithm formatting characters</a><li><a href=#user-agent-conformance-criteria>3.2.6.2 User agent conformance criteria</a></ol><li><a href=#wai-aria>3.2.7 Annotations for assistive technology products (ARIA)</a></ol></ol><li id=toc-semantics><a href=#semantics>4 The elements of HTML</a><ol><li><a href=#the-root-element>4.1 The root element</a><ol><li><a href=#the-html-element>4.1.1 The <code>html</code> element</a></ol><li><a href=#document-metadata>4.2 Document metadata</a><ol><li><a href=#the-head-element>4.2.1 The <code>head</code> element</a><li><a href=#the-title-element>4.2.2 The <code>title</code> element</a><li><a href=#the-base-element>4.2.3 The <code>base</code> element</a><li><a href=#the-link-element>4.2.4 The <code>link</code> element</a><li><a href=#the-meta-element>4.2.5 The <c
ode>meta</code> element</a><ol><li><a href=#standard-metadata-names>4.2.5.1 Standard metadata names</a><li><a href=#other-metadata-names>4.2.5.2 Other metadata names</a><li><a href=#pragma-directives>4.2.5.3 Pragma directives</a><li><a href=#other-pragma-directives>4.2.5.4 Other pragma directives</a><li><a href=#charset>4.2.5.5 Specifying the document's character encoding</a></ol><li><a href=#the-style-element>4.2.6 The <code>style</code> element</a><li><a href=#interactions-of-styling-and-scripting>4.2.7 Interactions of styling and scripting</a></ol><li><a href=#sections>4.3 Sections</a><ol><li><a href=#the-body-element>4.3.1 The <code>body</code> element</a><li><a href=#the-article-element>4.3.2 The <code>article</code> element</a><li><a href=#the-section-element>4.3.3 The <code>section</code> element</a><li><a href=#the-nav-element>4.3.4 The <code>nav</code> element</a><li><a href=#the-aside-element>4.3.5 The <code>aside</code> element</a><li><a href=#the-h1,-h2,-h3,-h4,-
h5,-and-h6-elements>4.3.6 The <code>h1</code>, <code>h2</code>, <code>h3</code>, <code>h4</code>, <code>h5</code>, and
- <code>h6</code> elements</a><li><a href=#the-hgroup-element>4.3.7 The <code>hgroup</code> element</a><li><a href=#the-header-element>4.3.8 The <code>header</code> element</a><li><a href=#the-footer-element>4.3.9 The <code>footer</code> element</a><li><a href=#the-address-element>4.3.10 The <code>address</code> element</a><li><a href=#headings-and-sections>4.3.11 Headings and sections</a><ol><li><a href=#outlines>4.3.11.1 Creating an outline</a><li><a href=#sample-outlines>4.3.11.2 Sample outlines</a><li><a href=#exposing-outlines-to-users>4.3.11.3 Exposing outlines to users</a></ol><li><a href=#usage-summary-2>4.3.12 Usage summary</a><ol><li><a href=#article-or-section>4.3.12.1 Article or section?</a></ol></ol><li><a href=#grouping-content>4.4 Grouping content</a><ol><li><a href=#the-p-element>4.4.1 The <code>p</code> element</a><li><a href=#the-hr-element>4.4.2 The <code>hr</code> element</a><li><a href=#the-pre-element>4.4.3 The <code>pre</code> element</a><li><a href=#t
he-blockquote-element>4.4.4 The <code>blockquote</code> element</a><li><a href=#the-ol-element>4.4.5 The <code>ol</code> element</a><li><a href=#the-ul-element>4.4.6 The <code>ul</code> element</a><li><a href=#the-li-element>4.4.7 The <code>li</code> element</a><li><a href=#the-dl-element>4.4.8 The <code>dl</code> element</a><li><a href=#the-dt-element>4.4.9 The <code>dt</code> element</a><li><a href=#the-dd-element>4.4.10 The <code>dd</code> element</a><li><a href=#the-figure-element>4.4.11 The <code>figure</code> element</a><li><a href=#the-figcaption-element>4.4.12 The <code>figcaption</code> element</a><li><a href=#the-main-element>4.4.13 The <code>main</code> element</a><li><a href=#the-div-element>4.4.14 The <code>div</code> element</a></ol><li><a href=#text-level-semantics>4.5 Text-level semantics</a><ol><li><a href=#the-a-element>4.5.1 The <code>a</code> element</a><li><a href=#the-em-element>4.5.2 The <code>em</code> element</a><li><a href=#the-strong-element>4.5.3
The <code>strong</code> element</a><li><a href=#the-small-element>4.5.4 The <code>small</code> element</a><li><a href=#the-s-element>4.5.5 The <code>s</code> element</a><li><a href=#the-cite-element>4.5.6 The <code>cite</code> element</a><li><a href=#the-q-element>4.5.7 The <code>q</code> element</a><li><a href=#the-dfn-element>4.5.8 The <code>dfn</code> element</a><li><a href=#the-abbr-element>4.5.9 The <code>abbr</code> element</a><li><a href=#the-ruby-element>4.5.10 The <code>ruby</code> element</a><li><a href=#the-rt-element>4.5.11 The <code>rt</code> element</a><li><a href=#the-rp-element>4.5.12 The <code>rp</code> element</a><li><a href=#the-data-element>4.5.13 The <code>data</code> element</a><li><a href=#the-time-element>4.5.14 The <code>time</code> element</a><li><a href=#the-code-element>4.5.15 The <code>code</code> element</a><li><a href=#the-var-element>4.5.16 The <code>var</code> element</a><li><a href=#the-samp-element>4.5.17 The <code>samp</code> element</a><l
i><a href=#the-kbd-element>4.5.18 The <code>kbd</code> element</a><li><a href=#the-sub-and-sup-elements>4.5.19 The <code>sub</code> and <code>sup</code> elements</a><li><a href=#the-i-element>4.5.20 The <code>i</code> element</a><li><a href=#the-b-element>4.5.21 The <code>b</code> element</a><li><a href=#the-u-element>4.5.22 The <code>u</code> element</a><li><a href=#the-mark-element>4.5.23 The <code>mark</code> element</a><li><a href=#the-bdi-element>4.5.24 The <code>bdi</code> element</a><li><a href=#the-bdo-element>4.5.25 The <code>bdo</code> element</a><li><a href=#the-span-element>4.5.26 The <code>span</code> element</a><li><a href=#the-br-element>4.5.27 The <code>br</code> element</a><li><a href=#the-wbr-element>4.5.28 The <code>wbr</code> element</a><li><a href=#usage-summary>4.5.29 Usage summary</a></ol><li><a href=#links>4.6 Links</a><ol><li><a href=#introduction-2>4.6.1 Introduction</a><li><a href=#links-created-by-a-and-area-elements>4.6.2 Links created by <code>a
</code> and <code>area</code> elements</a><li><a href=#following-hyperlinks>4.6.3 Following hyperlinks</a><li><a href=#downloading-resources>4.6.4 Downloading resources</a><ol><li><a href=#hyperlink-auditing>4.6.4.1 Hyperlink auditing</a></ol><li><a href=#linkTypes>4.6.5 Link types</a><ol><li><a href=#rel-alternate>4.6.5.1 Link type "<code>alternate</code>"</a><li><a href=#link-type-author>4.6.5.2 Link type "<code>author</code>"</a><li><a href=#link-type-bookmark>4.6.5.3 Link type "<code>bookmark</code>"</a><li><a href=#link-type-external>4.6.5.4 Link type "<code>external</code>"</a><li><a href=#link-type-help>4.6.5.5 Link type "<code>help</code>"</a><li><a href=#rel-icon>4.6.5.6 Link type "<code>icon</code>"</a><li><a href=#link-type-license>4.6.5.7 Link type "<code>license</code>"</a><li><a href=#link-type-nofollow>4.6.5.8 Link type "<code>nofollow</code>"</a><li><a href=#link-type-noreferrer>4.6.5.9 Link type "<code>noreferrer</code>"</a><li><a href=#link-type-pingback>4.
6.5.10 Link type "<code>pingback</code>"</a><li><a href=#link-type-prefetch>4.6.5.11 Link type "<code>prefetch</code>"</a><li><a href=#link-type-search>4.6.5.12 Link type "<code>search</code>"</a><li><a href=#link-type-sidebar>4.6.5.13 Link type "<code>sidebar</code>"</a><li><a href=#link-type-stylesheet>4.6.5.14 Link type "<code>stylesheet</code>"</a><li><a href=#link-type-tag>4.6.5.15 Link type "<code>tag</code>"</a><li><a href=#sequential-link-types>4.6.5.16 Sequential link types</a><ol><li><a href=#link-type-next>4.6.5.16.1 Link type "<code>next</code>"</a><li><a href=#link-type-prev>4.6.5.16.2 Link type "<code>prev</code>"</a></ol><li><a href=#other-link-types>4.6.5.17 Other link types</a></ol></ol><li><a href=#edits>4.7 Edits</a><ol><li><a href=#the-ins-element>4.7.1 The <code>ins</code> element</a><li><a href=#the-del-element>4.7.2 The <code>del</code> element</a><li><a href=#attributes-common-to-ins-and-del-elements>4.7.3 Attributes common to <code>ins</code> and <co
de>del</code> elements</a><li><a href=#edits-and-paragraphs>4.7.4 Edits and paragraphs</a><li><a href=#edits-and-lists>4.7.5 Edits and lists</a><li><a href=#edits-and-tables>4.7.6 Edits and tables</a></ol><li><a href=#embedded-content>4.8 Embedded content</a><ol><li><a href=#introduction-3>4.8.1 Introduction</a><ol><li><a href=#adaptive-images>4.8.1.1 Adaptive images</a></ol><li><a href=#dependencies-2>4.8.2 Dependencies</a><li><a href=#the-picture-element>4.8.3 The <code>picture</code> element</a><li><a href=#the-source-element-when-used-with-the-picture-element>4.8.4 The <code>source</code> element when used with the <code>picture</code> element</a><li><a href=#the-img-element>4.8.5 The <code>img</code> element</a><ol><li><a href=#alt>4.8.5.1 Requirements for providing text to act as an alternative for images</a><ol><li><a href=#general-guidelines>4.8.5.1.1 General guidelines</a><li><a href=#a-link-or-button-containing-nothing-but-the-image>4.8.5.1.2 A link or button conta
ining nothing but the image</a><li><a href=#a-phrase-or-paragraph-with-an-alternative-graphical-representation:-charts,-diagrams,-graphs,-maps,-illustrations>4.8.5.1.3 A phrase or paragraph with an alternative graphical representation: charts, diagrams, graphs, maps, illustrations</a><li><a href=#a-short-phrase-or-label-with-an-alternative-graphical-representation:-icons,-logos>4.8.5.1.4 A short phrase or label with an alternative graphical representation: icons, logos</a><li><a href=#text-that-has-been-rendered-to-a-graphic-for-typographical-effect>4.8.5.1.5 Text that has been rendered to a graphic for typographical effect</a><li><a href=#a-graphical-representation-of-some-of-the-surrounding-text>4.8.5.1.6 A graphical representation of some of the surrounding text</a><li><a href=#ancillary-images>4.8.5.1.7 Ancillary images</a><li><a href="#a-purely-decorative-image-that-doesn't-add-any-information">4.8.5.1.8 A purely decorative image that doesn't add any information</a><li>
<a href=#a-group-of-images-that-form-a-single-larger-picture-with-no-links>4.8.5.1.9 A group of images that form a single larger picture with no links</a><li><a href=#a-group-of-images-that-form-a-single-larger-picture-with-links>4.8.5.1.10 A group of images that form a single larger picture with links</a><li><a href=#a-key-part-of-the-content>4.8.5.1.11 A key part of the content</a><li><a href=#an-image-not-intended-for-the-user>4.8.5.1.12 An image not intended for the user</a><li><a href=#an-image-in-an-e-mail-or-private-document-intended-for-a-specific-person-who-is-known-to-be-able-to-view-images>4.8.5.1.13 An image in an e-mail or private document intended for a specific person who is known to be able to view images</a><li><a href=#guidance-for-markup-generators>4.8.5.1.14 Guidance for markup generators</a><li><a href=#guidance-for-conformance-checkers>4.8.5.1.15 Guidance for conformance checkers</a></ol></ol><li><a href=#the-iframe-element>4.8.6 The <code>iframe</code>
element</a><li><a href=#the-embed-element>4.8.7 The <code>embed</code> element</a><li><a href=#the-object-element>4.8.8 The <code>object</code> element</a><li><a href=#the-param-element>4.8.9 The <code>param</code> element</a><li><a href=#the-video-element>4.8.10 The <code>video</code> element</a><li><a href=#the-audio-element>4.8.11 The <code>audio</code> element</a><li><a href=#the-source-element>4.8.12 The <code>source</code> element</a><li><a href=#the-track-element>4.8.13 The <code>track</code> element</a><li><a href=#media-elements>4.8.14 Media elements</a><ol><li><a href=#error-codes>4.8.14.1 Error codes</a><li><a href=#location-of-the-media-resource>4.8.14.2 Location of the media resource</a><li><a href=#mime-types>4.8.14.3 MIME types</a><li><a href=#network-states>4.8.14.4 Network states</a><li><a href=#loading-the-media-resource>4.8.14.5 Loading the media resource</a><li><a href=#offsets-into-the-media-resource>4.8.14.6 Offsets into the media resource</a><li><a hr
ef=#ready-states>4.8.14.7 Ready states</a><li><a href=#playing-the-media-resource>4.8.14.8 Playing the media resource</a><li><a href=#seeking>4.8.14.9 Seeking</a><li><a href=#media-resources-with-multiple-media-tracks>4.8.14.10 Media resources with multiple media tracks</a><ol><li><a href=#audiotracklist-and-videotracklist-objects>4.8.14.10.1 <code>AudioTrackList</code> and <code>VideoTrackList</code> objects</a><li><a href=#selecting-specific-audio-and-video-tracks-declaratively>4.8.14.10.2 Selecting specific audio and video tracks declaratively</a></ol><li><a href=#synchronising-multiple-media-elements>4.8.14.11 Synchronising multiple media elements</a><ol><li><a href=#introduction-4>4.8.14.11.1 Introduction</a><li><a href=#media-controllers>4.8.14.11.2 Media controllers</a><li><a href=#assigning-a-media-controller-declaratively>4.8.14.11.3 Assigning a media controller declaratively</a></ol><li><a href=#timed-text-tracks>4.8.14.12 Timed text tracks</a><ol><li><a href=#text
-track-model>4.8.14.12.1 Text track model</a><li><a href=#sourcing-in-band-text-tracks>4.8.14.12.2 Sourcing in-band text tracks</a><li><a href=#sourcing-out-of-band-text-tracks>4.8.14.12.3 Sourcing out-of-band text tracks</a><li><a href=#guidelines-for-exposing-cues-in-various-formats-as-text-track-cues>4.8.14.12.4 Guidelines for exposing cues in various formats as text track cues</a><li><a href=#text-track-api>4.8.14.12.5 Text track API</a><li><a href=#text-tracks-describing-chapters>4.8.14.12.6 Text tracks describing chapters</a><li><a href=#cue-events>4.8.14.12.7 Event handlers for objects of the text track APIs</a><li><a href=#best-practices-for-metadata-text-tracks>4.8.14.12.8 Best practices for metadata text tracks</a></ol><li><a href=#user-interface>4.8.14.13 User interface</a><li><a href=#time-ranges>4.8.14.14 Time ranges</a><li><a href=#the-trackevent-interface>4.8.14.15 The <code>TrackEvent</code> interface</a><li><a href=#mediaevents>4.8.14.16 Event summary</a><li
><a href=#security-and-privacy-considerations>4.8.14.17 Security and privacy considerations</a><li><a href=#best-practices-for-authors-using-media-elements>4.8.14.18 Best practices for authors using media elements</a><li><a href=#best-practices-for-implementors-of-media-elements>4.8.14.19 Best practices for implementors of media elements</a></ol><li><a href=#the-map-element>4.8.15 The <code>map</code> element</a><li><a href=#the-area-element>4.8.16 The <code>area</code> element</a><li><a href=#image-maps>4.8.17 Image maps</a><ol><li><a href=#authoring>4.8.17.1 Authoring</a><li><a href=#processing-model-2>4.8.17.2 Processing model</a></ol><li><a href=#mathml>4.8.18 MathML</a><li><a href=#svg-0>4.8.19 SVG</a><li><a href=#dimension-attributes>4.8.20 Dimension attributes</a></ol><li><a href=#tables>4.9 Tabular data</a><ol><li><a href=#the-table-element>4.9.1 The <code>table</code> element</a><ol><li><a href=#table-descriptions-techniques>4.9.1.1 Techniques for describing tables<
/a><li><a href=#table-layout-techniques>4.9.1.2 Techniques for table design</a></ol><li><a href=#the-caption-element>4.9.2 The <code>caption</code> element</a><li><a href=#the-colgroup-element>4.9.3 The <code>colgroup</code> element</a><li><a href=#the-col-element>4.9.4 The <code>col</code> element</a><li><a href=#the-tbody-element>4.9.5 The <code>tbody</code> element</a><li><a href=#the-thead-element>4.9.6 The <code>thead</code> element</a><li><a href=#the-tfoot-element>4.9.7 The <code>tfoot</code> element</a><li><a href=#the-tr-element>4.9.8 The <code>tr</code> element</a><li><a href=#the-td-element>4.9.9 The <code>td</code> element</a><li><a href=#the-th-element>4.9.10 The <code>th</code> element</a><li><a href=#attributes-common-to-td-and-th-elements>4.9.11 Attributes common to <code>td</code> and <code>th</code> elements</a><li><a href=#processing-model-3>4.9.12 Processing model</a><ol><li><a href=#forming-a-table>4.9.12.1 Forming a table</a><li><a href=#header-and-data
-cell-semantics>4.9.12.2 Forming relationships between data cells and header cells</a></ol><li><a href=#table-sorting-model>4.9.13 Table sorting model</a><li><a href=#table-examples>4.9.14 Examples</a></ol><li><a href=#forms>4.10 Forms</a><ol><li><a href=#introduction-5>4.10.1 Introduction</a><ol><li><a href="#writing-a-form's-user-interface">4.10.1.1 Writing a form's user interface</a><li><a href=#implementing-the-server-side-processing-for-a-form>4.10.1.2 Implementing the server-side processing for a form</a><li><a href=#configuring-a-form-to-communicate-with-a-server>4.10.1.3 Configuring a form to communicate with a server</a><li><a href=#client-side-form-validation>4.10.1.4 Client-side form validation</a><li><a href=#enabling-client-side-automatic-filling-of-form-controls>4.10.1.5 Enabling client-side automatic filling of form controls</a><li><a href=#improving-the-user-experience-on-mobile-devices>4.10.1.6 Improving the user experience on mobile devices</a><li><a href=#
the-difference-between-the-field-type,-the-autofill-field-name,-and-the-input-modality>4.10.1.7 The difference between the field type, the autofill field name, and the input modality</a><li><a href=#input-author-notes>4.10.1.8 Date, time, and number formats</a></ol><li><a href=#categories>4.10.2 Categories</a><li><a href=#the-form-element>4.10.3 The <code>form</code> element</a><li><a href=#the-label-element>4.10.4 The <code>label</code> element</a><li><a href=#the-input-element>4.10.5 The <code>input</code> element</a><ol><li><a href=#states-of-the-type-attribute>4.10.5.1 States of the <code>type</code> attribute</a><ol><li><a href="#hidden-state-(type=hidden)">4.10.5.1.1 Hidden state (<code>type=hidden</code>)</a><li><a href="#text-(type=text)-state-and-search-state-(type=search)">4.10.5.1.2 Text (<code>type=text</code>) state and Search state (<code>type=search</code>)</a><li><a href="#telephone-state-(type=tel)">4.10.5.1.3 Telephone state (<code>type=tel</code>)</a><li><
a href="#url-state-(type=url)">4.10.5.1.4 URL state (<code>type=url</code>)</a><li><a href="#e-mail-state-(type=email)">4.10.5.1.5 E-mail state (<code>type=email</code>)</a><li><a href="#password-state-(type=password)">4.10.5.1.6 Password state (<code>type=password</code>)</a><li><a href="#date-and-time-state-(type=datetime)">4.10.5.1.7 Date and Time state (<code>type=datetime</code>)</a><li><a href="#date-state-(type=date)">4.10.5.1.8 Date state (<code>type=date</code>)</a><li><a href="#month-state-(type=month)">4.10.5.1.9 Month state (<code>type=month</code>)</a><li><a href="#week-state-(type=week)">4.10.5.1.10 Week state (<code>type=week</code>)</a><li><a href="#time-state-(type=time)">4.10.5.1.11 Time state (<code>type=time</code>)</a><li><a href="#local-date-and-time-state-(type=datetime-local)">4.10.5.1.12 Local Date and Time state (<code>type=datetime-local</code>)</a><li><a href="#number-state-(type=number)">4.10.5.1.13 Number state (<code>type=number</code>)</a><li>
<a href="#range-state-(type=range)">4.10.5.1.14 Range state (<code>type=range</code>)</a><li><a href="#color-state-(type=color)">4.10.5.1.15 Colour state (<code>type=color</code>)</a><li><a href="#checkbox-state-(type=checkbox)">4.10.5.1.16 Checkbox state (<code>type=checkbox</code>)</a><li><a href="#radio-button-state-(type=radio)">4.10.5.1.17 Radio Button state (<code>type=radio</code>)</a><li><a href="#file-upload-state-(type=file)">4.10.5.1.18 File Upload state (<code>type=file</code>)</a><li><a href="#submit-button-state-(type=submit)">4.10.5.1.19 Submit Button state (<code>type=submit</code>)</a><li><a href="#image-button-state-(type=image)">4.10.5.1.20 Image Button state (<code>type=image</code>)</a><li><a href="#reset-button-state-(type=reset)">4.10.5.1.21 Reset Button state (<code>type=reset</code>)</a><li><a href="#button-state-(type=button)">4.10.5.1.22 Button state (<code>type=button</code>)</a></ol><li><a href=#input-impl-notes>4.10.5.2 Implemention notes regard
ing localization of form controls</a><li><a href=#common-input-element-attributes>4.10.5.3 Common <code>input</code> element attributes</a><ol><li><a href=#the-maxlength-and-minlength-attributes>4.10.5.3.1 The <code>maxlength</code> and <code>minlength</code> attributes</a><li><a href=#the-size-attribute>4.10.5.3.2 The <code>size</code> attribute</a><li><a href=#the-readonly-attribute>4.10.5.3.3 The <code>readonly</code> attribute</a><li><a href=#the-required-attribute>4.10.5.3.4 The <code>required</code> attribute</a><li><a href=#the-multiple-attribute>4.10.5.3.5 The <code>multiple</code> attribute</a><li><a href=#the-pattern-attribute>4.10.5.3.6 The <code>pattern</code> attribute</a><li><a href=#the-min-and-max-attributes>4.10.5.3.7 The <code>min</code> and <code>max</code> attributes</a><li><a href=#the-step-attribute>4.10.5.3.8 The <code>step</code> attribute</a><li><a href=#the-list-attribute>4.10.5.3.9 The <code>list</code> attribute</a><li><a href=#the-placeholder-att
ribute>4.10.5.3.10 The <code>placeholder</code> attribute</a></ol><li><a href=#common-input-element-apis>4.10.5.4 Common <code>input</code> element APIs</a><li><a href=#common-input-element-events>4.10.5.5 Common event behaviors</a></ol><li><a href=#the-button-element>4.10.6 The <code>button</code> element</a><li><a href=#the-select-element>4.10.7 The <code>select</code> element</a><li><a href=#the-datalist-element>4.10.8 The <code>datalist</code> element</a><li><a href=#the-optgroup-element>4.10.9 The <code>optgroup</code> element</a><li><a href=#the-option-element>4.10.10 The <code>option</code> element</a><li><a href=#the-textarea-element>4.10.11 The <code>textarea</code> element</a><li><a href=#the-keygen-element>4.10.12 The <code>keygen</code> element</a><li><a href=#the-output-element>4.10.13 The <code>output</code> element</a><li><a href=#the-progress-element>4.10.14 The <code>progress</code> element</a><li><a href=#the-meter-element>4.10.15 The <code>meter</code> ele
ment</a><li><a href=#the-fieldset-element>4.10.16 The <code>fieldset</code> element</a><li><a href=#the-legend-element>4.10.17 The <code>legend</code> element</a><li><a href=#form-control-infrastructure>4.10.18 Form control infrastructure</a><ol><li><a href="#a-form-control's-value">4.10.18.1 A form control's value</a><li><a href=#mutability>4.10.18.2 Mutability</a><li><a href=#association-of-controls-and-forms>4.10.18.3 Association of controls and forms</a></ol><li><a href=#attributes-common-to-form-controls>4.10.19 Attributes common to form controls</a><ol><li><a href=#naming-form-controls:-the-name-attribute>4.10.19.1 Naming form controls: the <code>name</code> attribute</a><li><a href=#submitting-element-directionality:-the-dirname-attribute>4.10.19.2 Submitting element directionality: the <code>dirname</code> attribute</a><li><a href=#limiting-user-input-length:-the-maxlength-attribute>4.10.19.3 Limiting user input length: the <code>maxlength</code> attribute</a><li><a
href=#setting-minimum-input-length-requirements:-the-minlength-attribute>4.10.19.4 Setting minimum input length requirements: the <code>minlength</code> attribute</a><li><a href=#enabling-and-disabling-form-controls:-the-disabled-attribute>4.10.19.5 Enabling and disabling form controls: the <code>disabled</code> attribute</a><li><a href=#form-submission>4.10.19.6 Form submission</a><ol><li><a href=#autofocusing-a-form-control:-the-autofocus-attribute>4.10.19.6.1 Autofocusing a form control: the <code>autofocus</code> attribute</a></ol><li><a href=#input-modalities:-the-inputmode-attribute>4.10.19.7 Input modalities: the <code>inputmode</code> attribute</a><li><a href=#autofill>4.10.19.8 Autofill</a><ol><li><a href=#autofilling-form-controls:-the-autocomplete-attribute>4.10.19.8.1 Autofilling form controls: the <code>autocomplete</code> attribute</a><li><a href=#processing-model-4>4.10.19.8.2 Processing model</a><li><a href=#user-interface-for-bulk-autofill>4.10.19.8.3 User i
nterface for bulk autofill</a><li><a href=#the-autocompleteerrorevent-interface>4.10.19.8.4 The <code>AutocompleteErrorEvent</code> interface</a></ol></ol><li><a href=#textFieldSelection>4.10.20 APIs for the text field selections</a><li><a href=#constraints>4.10.21 Constraints</a><ol><li><a href=#definitions>4.10.21.1 Definitions</a><li><a href=#constraint-validation>4.10.21.2 Constraint validation</a><li><a href=#the-constraint-validation-api>4.10.21.3 The constraint validation API</a><li><a href=#security-forms>4.10.21.4 Security</a></ol><li><a href=#form-submission-2>4.10.22 Form submission</a><ol><li><a href=#introduction-6>4.10.22.1 Introduction</a><li><a href=#implicit-submission>4.10.22.2 Implicit submission</a><li><a href=#form-submission-algorithm>4.10.22.3 Form submission algorithm</a><li><a href=#constructing-form-data-set>4.10.22.4 Constructing the form data set</a><li><a href=#selecting-a-form-submission-encoding>4.10.22.5 Selecting a form submission encoding</a
><li><a href=#url-encoded-form-data>4.10.22.6 URL-encoded form data</a><li><a href=#multipart-form-data>4.10.22.7 Multipart form data</a><li><a href=#plain-text-form-data>4.10.22.8 Plain text form data</a></ol><li><a href=#resetting-a-form>4.10.23 Resetting a form</a></ol><li><a href=#interactive-elements>4.11 Interactive elements</a><ol><li><a href=#the-details-element>4.11.1 The <code>details</code> element</a><li><a href=#the-summary-element>4.11.2 The <code>summary</code> element</a><li><a href=#the-menu-element>4.11.3 The <code>menu</code> element</a><li><a href=#the-menuitem-element>4.11.4 The <code>menuitem</code> element</a><li><a href=#context-menus>4.11.5 Context menus</a><ol><li><a href=#declaring-a-context-menu>4.11.5.1 Declaring a context menu</a><li><a href=#processing-model-5>4.11.5.2 Processing model</a><li><a href=#the-relatedevent-interfaces>4.11.5.3 The <code>RelatedEvent</code> interfaces</a></ol><li><a href=#commands>4.11.6 Commands</a><ol><li><a href=#f
acets-2>4.11.6.1 Facets</a><li><a href=#using-the-a-element-to-define-a-command>4.11.6.2 Using the <code>a</code> element to define a command</a><li><a href=#using-the-button-element-to-define-a-command>4.11.6.3 Using the <code>button</code> element to define a command</a><li><a href=#using-the-input-element-to-define-a-command>4.11.6.4 Using the <code>input</code> element to define a command</a><li><a href=#using-the-option-element-to-define-a-command>4.11.6.5 Using the <code>option</code> element to define a command</a><li><a href=#using-the-menuitem-element-to-define-a-command>4.11.6.6 Using the <code>menuitem</code> element to define a
+ <code>h6</code> elements</a><li><a href=#the-hgroup-element>4.3.7 The <code>hgroup</code> element</a><li><a href=#the-header-element>4.3.8 The <code>header</code> element</a><li><a href=#the-footer-element>4.3.9 The <code>footer</code> element</a><li><a href=#the-address-element>4.3.10 The <code>address</code> element</a><li><a href=#headings-and-sections>4.3.11 Headings and sections</a><ol><li><a href=#outlines>4.3.11.1 Creating an outline</a><li><a href=#sample-outlines>4.3.11.2 Sample outlines</a><li><a href=#exposing-outlines-to-users>4.3.11.3 Exposing outlines to users</a></ol><li><a href=#usage-summary-2>4.3.12 Usage summary</a><ol><li><a href=#article-or-section>4.3.12.1 Article or section?</a></ol></ol><li><a href=#grouping-content>4.4 Grouping content</a><ol><li><a href=#the-p-element>4.4.1 The <code>p</code> element</a><li><a href=#the-hr-element>4.4.2 The <code>hr</code> element</a><li><a href=#the-pre-element>4.4.3 The <code>pre</code> element</a><li><a href=#t
he-blockquote-element>4.4.4 The <code>blockquote</code> element</a><li><a href=#the-ol-element>4.4.5 The <code>ol</code> element</a><li><a href=#the-ul-element>4.4.6 The <code>ul</code> element</a><li><a href=#the-li-element>4.4.7 The <code>li</code> element</a><li><a href=#the-dl-element>4.4.8 The <code>dl</code> element</a><li><a href=#the-dt-element>4.4.9 The <code>dt</code> element</a><li><a href=#the-dd-element>4.4.10 The <code>dd</code> element</a><li><a href=#the-figure-element>4.4.11 The <code>figure</code> element</a><li><a href=#the-figcaption-element>4.4.12 The <code>figcaption</code> element</a><li><a href=#the-main-element>4.4.13 The <code>main</code> element</a><li><a href=#the-div-element>4.4.14 The <code>div</code> element</a></ol><li><a href=#text-level-semantics>4.5 Text-level semantics</a><ol><li><a href=#the-a-element>4.5.1 The <code>a</code> element</a><li><a href=#the-em-element>4.5.2 The <code>em</code> element</a><li><a href=#the-strong-element>4.5.3
The <code>strong</code> element</a><li><a href=#the-small-element>4.5.4 The <code>small</code> element</a><li><a href=#the-s-element>4.5.5 The <code>s</code> element</a><li><a href=#the-cite-element>4.5.6 The <code>cite</code> element</a><li><a href=#the-q-element>4.5.7 The <code>q</code> element</a><li><a href=#the-dfn-element>4.5.8 The <code>dfn</code> element</a><li><a href=#the-abbr-element>4.5.9 The <code>abbr</code> element</a><li><a href=#the-ruby-element>4.5.10 The <code>ruby</code> element</a><li><a href=#the-rt-element>4.5.11 The <code>rt</code> element</a><li><a href=#the-rp-element>4.5.12 The <code>rp</code> element</a><li><a href=#the-data-element>4.5.13 The <code>data</code> element</a><li><a href=#the-time-element>4.5.14 The <code>time</code> element</a><li><a href=#the-code-element>4.5.15 The <code>code</code> element</a><li><a href=#the-var-element>4.5.16 The <code>var</code> element</a><li><a href=#the-samp-element>4.5.17 The <code>samp</code> element</a><l
i><a href=#the-kbd-element>4.5.18 The <code>kbd</code> element</a><li><a href=#the-sub-and-sup-elements>4.5.19 The <code>sub</code> and <code>sup</code> elements</a><li><a href=#the-i-element>4.5.20 The <code>i</code> element</a><li><a href=#the-b-element>4.5.21 The <code>b</code> element</a><li><a href=#the-u-element>4.5.22 The <code>u</code> element</a><li><a href=#the-mark-element>4.5.23 The <code>mark</code> element</a><li><a href=#the-bdi-element>4.5.24 The <code>bdi</code> element</a><li><a href=#the-bdo-element>4.5.25 The <code>bdo</code> element</a><li><a href=#the-span-element>4.5.26 The <code>span</code> element</a><li><a href=#the-br-element>4.5.27 The <code>br</code> element</a><li><a href=#the-wbr-element>4.5.28 The <code>wbr</code> element</a><li><a href=#usage-summary>4.5.29 Usage summary</a></ol><li><a href=#links>4.6 Links</a><ol><li><a href=#introduction-2>4.6.1 Introduction</a><li><a href=#links-created-by-a-and-area-elements>4.6.2 Links created by <code>a
</code> and <code>area</code> elements</a><li><a href=#following-hyperlinks>4.6.3 Following hyperlinks</a><li><a href=#downloading-resources>4.6.4 Downloading resources</a><ol><li><a href=#hyperlink-auditing>4.6.4.1 Hyperlink auditing</a></ol><li><a href=#linkTypes>4.6.5 Link types</a><ol><li><a href=#rel-alternate>4.6.5.1 Link type "<code>alternate</code>"</a><li><a href=#link-type-author>4.6.5.2 Link type "<code>author</code>"</a><li><a href=#link-type-bookmark>4.6.5.3 Link type "<code>bookmark</code>"</a><li><a href=#link-type-external>4.6.5.4 Link type "<code>external</code>"</a><li><a href=#link-type-help>4.6.5.5 Link type "<code>help</code>"</a><li><a href=#rel-icon>4.6.5.6 Link type "<code>icon</code>"</a><li><a href=#link-type-license>4.6.5.7 Link type "<code>license</code>"</a><li><a href=#link-type-nofollow>4.6.5.8 Link type "<code>nofollow</code>"</a><li><a href=#link-type-noreferrer>4.6.5.9 Link type "<code>noreferrer</code>"</a><li><a href=#link-type-pingback>4.
6.5.10 Link type "<code>pingback</code>"</a><li><a href=#link-type-prefetch>4.6.5.11 Link type "<code>prefetch</code>"</a><li><a href=#link-type-search>4.6.5.12 Link type "<code>search</code>"</a><li><a href=#link-type-sidebar>4.6.5.13 Link type "<code>sidebar</code>"</a><li><a href=#link-type-stylesheet>4.6.5.14 Link type "<code>stylesheet</code>"</a><li><a href=#link-type-tag>4.6.5.15 Link type "<code>tag</code>"</a><li><a href=#sequential-link-types>4.6.5.16 Sequential link types</a><ol><li><a href=#link-type-next>4.6.5.16.1 Link type "<code>next</code>"</a><li><a href=#link-type-prev>4.6.5.16.2 Link type "<code>prev</code>"</a></ol><li><a href=#other-link-types>4.6.5.17 Other link types</a></ol></ol><li><a href=#edits>4.7 Edits</a><ol><li><a href=#the-ins-element>4.7.1 The <code>ins</code> element</a><li><a href=#the-del-element>4.7.2 The <code>del</code> element</a><li><a href=#attributes-common-to-ins-and-del-elements>4.7.3 Attributes common to <code>ins</code> and <co
de>del</code> elements</a><li><a href=#edits-and-paragraphs>4.7.4 Edits and paragraphs</a><li><a href=#edits-and-lists>4.7.5 Edits and lists</a><li><a href=#edits-and-tables>4.7.6 Edits and tables</a></ol><li><a href=#embedded-content>4.8 Embedded content</a><ol><li><a href=#introduction-3>4.8.1 Introduction</a><ol><li><a href=#adaptive-images>4.8.1.1 Adaptive images</a></ol><li><a href=#dependencies-2>4.8.2 Dependencies</a><li><a href=#the-picture-element>4.8.3 The <code>picture</code> element</a><li><a href=#the-source-element-when-used-with-the-picture-element>4.8.4 The <code>source</code> element when used with the <code>picture</code> element</a><li><a href=#the-img-element>4.8.5 The <code>img</code> element</a><ol><li><a href=#alt>4.8.5.1 Requirements for providing text to act as an alternative for images</a><ol><li><a href=#general-guidelines>4.8.5.1.1 General guidelines</a><li><a href=#a-link-or-button-containing-nothing-but-the-image>4.8.5.1.2 A link or button conta
ining nothing but the image</a><li><a href=#a-phrase-or-paragraph-with-an-alternative-graphical-representation:-charts,-diagrams,-graphs,-maps,-illustrations>4.8.5.1.3 A phrase or paragraph with an alternative graphical representation: charts, diagrams, graphs, maps, illustrations</a><li><a href=#a-short-phrase-or-label-with-an-alternative-graphical-representation:-icons,-logos>4.8.5.1.4 A short phrase or label with an alternative graphical representation: icons, logos</a><li><a href=#text-that-has-been-rendered-to-a-graphic-for-typographical-effect>4.8.5.1.5 Text that has been rendered to a graphic for typographical effect</a><li><a href=#a-graphical-representation-of-some-of-the-surrounding-text>4.8.5.1.6 A graphical representation of some of the surrounding text</a><li><a href=#ancillary-images>4.8.5.1.7 Ancillary images</a><li><a href="#a-purely-decorative-image-that-doesn't-add-any-information">4.8.5.1.8 A purely decorative image that doesn't add any information</a><li>
<a href=#a-group-of-images-that-form-a-single-larger-picture-with-no-links>4.8.5.1.9 A group of images that form a single larger picture with no links</a><li><a href=#a-group-of-images-that-form-a-single-larger-picture-with-links>4.8.5.1.10 A group of images that form a single larger picture with links</a><li><a href=#a-key-part-of-the-content>4.8.5.1.11 A key part of the content</a><li><a href=#an-image-not-intended-for-the-user>4.8.5.1.12 An image not intended for the user</a><li><a href=#an-image-in-an-e-mail-or-private-document-intended-for-a-specific-person-who-is-known-to-be-able-to-view-images>4.8.5.1.13 An image in an e-mail or private document intended for a specific person who is known to be able to view images</a><li><a href=#guidance-for-markup-generators>4.8.5.1.14 Guidance for markup generators</a><li><a href=#guidance-for-conformance-checkers>4.8.5.1.15 Guidance for conformance checkers</a></ol></ol><li><a href=#the-iframe-element>4.8.6 The <code>iframe</code>
element</a><li><a href=#the-embed-element>4.8.7 The <code>embed</code> element</a><li><a href=#the-object-element>4.8.8 The <code>object</code> element</a><li><a href=#the-param-element>4.8.9 The <code>param</code> element</a><li><a href=#the-video-element>4.8.10 The <code>video</code> element</a><li><a href=#the-audio-element>4.8.11 The <code>audio</code> element</a><li><a href=#the-source-element>4.8.12 The <code>source</code> element</a><li><a href=#the-track-element>4.8.13 The <code>track</code> element</a><li><a href=#media-elements>4.8.14 Media elements</a><ol><li><a href=#error-codes>4.8.14.1 Error codes</a><li><a href=#location-of-the-media-resource>4.8.14.2 Location of the media resource</a><li><a href=#mime-types>4.8.14.3 MIME types</a><li><a href=#network-states>4.8.14.4 Network states</a><li><a href=#loading-the-media-resource>4.8.14.5 Loading the media resource</a><li><a href=#offsets-into-the-media-resource>4.8.14.6 Offsets into the media resource</a><li><a hr
ef=#ready-states>4.8.14.7 Ready states</a><li><a href=#playing-the-media-resource>4.8.14.8 Playing the media resource</a><li><a href=#seeking>4.8.14.9 Seeking</a><li><a href=#media-resources-with-multiple-media-tracks>4.8.14.10 Media resources with multiple media tracks</a><ol><li><a href=#audiotracklist-and-videotracklist-objects>4.8.14.10.1 <code>AudioTrackList</code> and <code>VideoTrackList</code> objects</a><li><a href=#selecting-specific-audio-and-video-tracks-declaratively>4.8.14.10.2 Selecting specific audio and video tracks declaratively</a></ol><li><a href=#synchronising-multiple-media-elements>4.8.14.11 Synchronising multiple media elements</a><ol><li><a href=#introduction-4>4.8.14.11.1 Introduction</a><li><a href=#media-controllers>4.8.14.11.2 Media controllers</a><li><a href=#assigning-a-media-controller-declaratively>4.8.14.11.3 Assigning a media controller declaratively</a></ol><li><a href=#timed-text-tracks>4.8.14.12 Timed text tracks</a><ol><li><a href=#text
-track-model>4.8.14.12.1 Text track model</a><li><a href=#sourcing-in-band-text-tracks>4.8.14.12.2 Sourcing in-band text tracks</a><li><a href=#sourcing-out-of-band-text-tracks>4.8.14.12.3 Sourcing out-of-band text tracks</a><li><a href=#guidelines-for-exposing-cues-in-various-formats-as-text-track-cues>4.8.14.12.4 Guidelines for exposing cues in various formats as text track cues</a><li><a href=#text-track-api>4.8.14.12.5 Text track API</a><li><a href=#text-tracks-describing-chapters>4.8.14.12.6 Text tracks describing chapters</a><li><a href=#cue-events>4.8.14.12.7 Event handlers for objects of the text track APIs</a><li><a href=#best-practices-for-metadata-text-tracks>4.8.14.12.8 Best practices for metadata text tracks</a></ol><li><a href=#user-interface>4.8.14.13 User interface</a><li><a href=#time-ranges>4.8.14.14 Time ranges</a><li><a href=#the-trackevent-interface>4.8.14.15 The <code>TrackEvent</code> interface</a><li><a href=#mediaevents>4.8.14.16 Event summary</a><li
><a href=#security-and-privacy-considerations>4.8.14.17 Security and privacy considerations</a><li><a href=#best-practices-for-authors-using-media-elements>4.8.14.18 Best practices for authors using media elements</a><li><a href=#best-practices-for-implementors-of-media-elements>4.8.14.19 Best practices for implementors of media elements</a></ol><li><a href=#the-map-element>4.8.15 The <code>map</code> element</a><li><a href=#the-area-element>4.8.16 The <code>area</code> element</a><li><a href=#image-maps>4.8.17 Image maps</a><ol><li><a href=#authoring>4.8.17.1 Authoring</a><li><a href=#processing-model-2>4.8.17.2 Processing model</a></ol><li><a href=#mathml>4.8.18 MathML</a><li><a href=#svg-0>4.8.19 SVG</a><li><a href=#dimension-attributes>4.8.20 Dimension attributes</a></ol><li><a href=#tables>4.9 Tabular data</a><ol><li><a href=#the-table-element>4.9.1 The <code>table</code> element</a><ol><li><a href=#table-descriptions-techniques>4.9.1.1 Techniques for describing tables<
/a><li><a href=#table-layout-techniques>4.9.1.2 Techniques for table design</a></ol><li><a href=#the-caption-element>4.9.2 The <code>caption</code> element</a><li><a href=#the-colgroup-element>4.9.3 The <code>colgroup</code> element</a><li><a href=#the-col-element>4.9.4 The <code>col</code> element</a><li><a href=#the-tbody-element>4.9.5 The <code>tbody</code> element</a><li><a href=#the-thead-element>4.9.6 The <code>thead</code> element</a><li><a href=#the-tfoot-element>4.9.7 The <code>tfoot</code> element</a><li><a href=#the-tr-element>4.9.8 The <code>tr</code> element</a><li><a href=#the-td-element>4.9.9 The <code>td</code> element</a><li><a href=#the-th-element>4.9.10 The <code>th</code> element</a><li><a href=#attributes-common-to-td-and-th-elements>4.9.11 Attributes common to <code>td</code> and <code>th</code> elements</a><li><a href=#processing-model-3>4.9.12 Processing model</a><ol><li><a href=#forming-a-table>4.9.12.1 Forming a table</a><li><a href=#header-and-data
-cell-semantics>4.9.12.2 Forming relationships between data cells and header cells</a></ol><li><a href=#table-sorting-model>4.9.13 Table sorting model</a><li><a href=#table-examples>4.9.14 Examples</a></ol><li><a href=#forms>4.10 Forms</a><ol><li><a href=#introduction-5>4.10.1 Introduction</a><ol><li><a href="#writing-a-form's-user-interface">4.10.1.1 Writing a form's user interface</a><li><a href=#implementing-the-server-side-processing-for-a-form>4.10.1.2 Implementing the server-side processing for a form</a><li><a href=#configuring-a-form-to-communicate-with-a-server>4.10.1.3 Configuring a form to communicate with a server</a><li><a href=#client-side-form-validation>4.10.1.4 Client-side form validation</a><li><a href=#enabling-client-side-automatic-filling-of-form-controls>4.10.1.5 Enabling client-side automatic filling of form controls</a><li><a href=#improving-the-user-experience-on-mobile-devices>4.10.1.6 Improving the user experience on mobile devices</a><li><a href=#
the-difference-between-the-field-type,-the-autofill-field-name,-and-the-input-modality>4.10.1.7 The difference between the field type, the autofill field name, and the input modality</a><li><a href=#input-author-notes>4.10.1.8 Date, time, and number formats</a></ol><li><a href=#categories>4.10.2 Categories</a><li><a href=#the-form-element>4.10.3 The <code>form</code> element</a><li><a href=#the-label-element>4.10.4 The <code>label</code> element</a><li><a href=#the-input-element>4.10.5 The <code>input</code> element</a><ol><li><a href=#states-of-the-type-attribute>4.10.5.1 States of the <code>type</code> attribute</a><ol><li><a href="#hidden-state-(type=hidden)">4.10.5.1.1 Hidden state (<code>type=hidden</code>)</a><li><a href="#text-(type=text)-state-and-search-state-(type=search)">4.10.5.1.2 Text (<code>type=text</code>) state and Search state (<code>type=search</code>)</a><li><a href="#telephone-state-(type=tel)">4.10.5.1.3 Telephone state (<code>type=tel</code>)</a><li><
a href="#url-state-(type=url)">4.10.5.1.4 URL state (<code>type=url</code>)</a><li><a href="#e-mail-state-(type=email)">4.10.5.1.5 E-mail state (<code>type=email</code>)</a><li><a href="#password-state-(type=password)">4.10.5.1.6 Password state (<code>type=password</code>)</a><li><a href="#date-and-time-state-(type=datetime)">4.10.5.1.7 Date and Time state (<code>type=datetime</code>)</a><li><a href="#date-state-(type=date)">4.10.5.1.8 Date state (<code>type=date</code>)</a><li><a href="#month-state-(type=month)">4.10.5.1.9 Month state (<code>type=month</code>)</a><li><a href="#week-state-(type=week)">4.10.5.1.10 Week state (<code>type=week</code>)</a><li><a href="#time-state-(type=time)">4.10.5.1.11 Time state (<code>type=time</code>)</a><li><a href="#local-date-and-time-state-(type=datetime-local)">4.10.5.1.12 Local Date and Time state (<code>type=datetime-local</code>)</a><li><a href="#number-state-(type=number)">4.10.5.1.13 Number state (<code>type=number</code>)</a><li>
<a href="#range-state-(type=range)">4.10.5.1.14 Range state (<code>type=range</code>)</a><li><a href="#color-state-(type=color)">4.10.5.1.15 Colour state (<code>type=color</code>)</a><li><a href="#checkbox-state-(type=checkbox)">4.10.5.1.16 Checkbox state (<code>type=checkbox</code>)</a><li><a href="#radio-button-state-(type=radio)">4.10.5.1.17 Radio Button state (<code>type=radio</code>)</a><li><a href="#file-upload-state-(type=file)">4.10.5.1.18 File Upload state (<code>type=file</code>)</a><li><a href="#submit-button-state-(type=submit)">4.10.5.1.19 Submit Button state (<code>type=submit</code>)</a><li><a href="#image-button-state-(type=image)">4.10.5.1.20 Image Button state (<code>type=image</code>)</a><li><a href="#reset-button-state-(type=reset)">4.10.5.1.21 Reset Button state (<code>type=reset</code>)</a><li><a href="#button-state-(type=button)">4.10.5.1.22 Button state (<code>type=button</code>)</a></ol><li><a href=#input-impl-notes>4.10.5.2 Implemention notes regard
ing localization of form controls</a><li><a href=#common-input-element-attributes>4.10.5.3 Common <code>input</code> element attributes</a><ol><li><a href=#the-maxlength-and-minlength-attributes>4.10.5.3.1 The <code>maxlength</code> and <code>minlength</code> attributes</a><li><a href=#the-size-attribute>4.10.5.3.2 The <code>size</code> attribute</a><li><a href=#the-readonly-attribute>4.10.5.3.3 The <code>readonly</code> attribute</a><li><a href=#the-required-attribute>4.10.5.3.4 The <code>required</code> attribute</a><li><a href=#the-multiple-attribute>4.10.5.3.5 The <code>multiple</code> attribute</a><li><a href=#the-pattern-attribute>4.10.5.3.6 The <code>pattern</code> attribute</a><li><a href=#the-min-and-max-attributes>4.10.5.3.7 The <code>min</code> and <code>max</code> attributes</a><li><a href=#the-step-attribute>4.10.5.3.8 The <code>step</code> attribute</a><li><a href=#the-list-attribute>4.10.5.3.9 The <code>list</code> attribute</a><li><a href=#the-placeholder-att
ribute>4.10.5.3.10 The <code>placeholder</code> attribute</a></ol><li><a href=#common-input-element-apis>4.10.5.4 Common <code>input</code> element APIs</a><li><a href=#common-input-element-events>4.10.5.5 Common event behaviours</a></ol><li><a href=#the-button-element>4.10.6 The <code>button</code> element</a><li><a href=#the-select-element>4.10.7 The <code>select</code> element</a><li><a href=#the-datalist-element>4.10.8 The <code>datalist</code> element</a><li><a href=#the-optgroup-element>4.10.9 The <code>optgroup</code> element</a><li><a href=#the-option-element>4.10.10 The <code>option</code> element</a><li><a href=#the-textarea-element>4.10.11 The <code>textarea</code> element</a><li><a href=#the-keygen-element>4.10.12 The <code>keygen</code> element</a><li><a href=#the-output-element>4.10.13 The <code>output</code> element</a><li><a href=#the-progress-element>4.10.14 The <code>progress</code> element</a><li><a href=#the-meter-element>4.10.15 The <code>meter</code> el
ement</a><li><a href=#the-fieldset-element>4.10.16 The <code>fieldset</code> element</a><li><a href=#the-legend-element>4.10.17 The <code>legend</code> element</a><li><a href=#form-control-infrastructure>4.10.18 Form control infrastructure</a><ol><li><a href="#a-form-control's-value">4.10.18.1 A form control's value</a><li><a href=#mutability>4.10.18.2 Mutability</a><li><a href=#association-of-controls-and-forms>4.10.18.3 Association of controls and forms</a></ol><li><a href=#attributes-common-to-form-controls>4.10.19 Attributes common to form controls</a><ol><li><a href=#naming-form-controls:-the-name-attribute>4.10.19.1 Naming form controls: the <code>name</code> attribute</a><li><a href=#submitting-element-directionality:-the-dirname-attribute>4.10.19.2 Submitting element directionality: the <code>dirname</code> attribute</a><li><a href=#limiting-user-input-length:-the-maxlength-attribute>4.10.19.3 Limiting user input length: the <code>maxlength</code> attribute</a><li><a
href=#setting-minimum-input-length-requirements:-the-minlength-attribute>4.10.19.4 Setting minimum input length requirements: the <code>minlength</code> attribute</a><li><a href=#enabling-and-disabling-form-controls:-the-disabled-attribute>4.10.19.5 Enabling and disabling form controls: the <code>disabled</code> attribute</a><li><a href=#form-submission>4.10.19.6 Form submission</a><ol><li><a href=#autofocusing-a-form-control:-the-autofocus-attribute>4.10.19.6.1 Autofocusing a form control: the <code>autofocus</code> attribute</a></ol><li><a href=#input-modalities:-the-inputmode-attribute>4.10.19.7 Input modalities: the <code>inputmode</code> attribute</a><li><a href=#autofill>4.10.19.8 Autofill</a><ol><li><a href=#autofilling-form-controls:-the-autocomplete-attribute>4.10.19.8.1 Autofilling form controls: the <code>autocomplete</code> attribute</a><li><a href=#processing-model-4>4.10.19.8.2 Processing model</a><li><a href=#user-interface-for-bulk-autofill>4.10.19.8.3 User
interface for bulk autofill</a><li><a href=#the-autocompleteerrorevent-interface>4.10.19.8.4 The <code>AutocompleteErrorEvent</code> interface</a></ol></ol><li><a href=#textFieldSelection>4.10.20 APIs for the text field selections</a><li><a href=#constraints>4.10.21 Constraints</a><ol><li><a href=#definitions>4.10.21.1 Definitions</a><li><a href=#constraint-validation>4.10.21.2 Constraint validation</a><li><a href=#the-constraint-validation-api>4.10.21.3 The constraint validation API</a><li><a href=#security-forms>4.10.21.4 Security</a></ol><li><a href=#form-submission-2>4.10.22 Form submission</a><ol><li><a href=#introduction-6>4.10.22.1 Introduction</a><li><a href=#implicit-submission>4.10.22.2 Implicit submission</a><li><a href=#form-submission-algorithm>4.10.22.3 Form submission algorithm</a><li><a href=#constructing-form-data-set>4.10.22.4 Constructing the form data set</a><li><a href=#selecting-a-form-submission-encoding>4.10.22.5 Selecting a form submission encoding</
a><li><a href=#url-encoded-form-data>4.10.22.6 URL-encoded form data</a><li><a href=#multipart-form-data>4.10.22.7 Multipart form data</a><li><a href=#plain-text-form-data>4.10.22.8 Plain text form data</a></ol><li><a href=#resetting-a-form>4.10.23 Resetting a form</a></ol><li><a href=#interactive-elements>4.11 Interactive elements</a><ol><li><a href=#the-details-element>4.11.1 The <code>details</code> element</a><li><a href=#the-summary-element>4.11.2 The <code>summary</code> element</a><li><a href=#the-menu-element>4.11.3 The <code>menu</code> element</a><li><a href=#the-menuitem-element>4.11.4 The <code>menuitem</code> element</a><li><a href=#context-menus>4.11.5 Context menus</a><ol><li><a href=#declaring-a-context-menu>4.11.5.1 Declaring a context menu</a><li><a href=#processing-model-5>4.11.5.2 Processing model</a><li><a href=#the-relatedevent-interfaces>4.11.5.3 The <code>RelatedEvent</code> interfaces</a></ol><li><a href=#commands>4.11.6 Commands</a><ol><li><a href=#
facets-2>4.11.6.1 Facets</a><li><a href=#using-the-a-element-to-define-a-command>4.11.6.2 Using the <code>a</code> element to define a command</a><li><a href=#using-the-button-element-to-define-a-command>4.11.6.3 Using the <code>button</code> element to define a command</a><li><a href=#using-the-input-element-to-define-a-command>4.11.6.4 Using the <code>input</code> element to define a command</a><li><a href=#using-the-option-element-to-define-a-command>4.11.6.5 Using the <code>option</code> element to define a command</a><li><a href=#using-the-menuitem-element-to-define-a-command>4.11.6.6 Using the <code>menuitem</code> element to define a
command</a><li><a href=#using-the-command-attribute-on-menuitem-elements-to-define-a-command-indirectly>4.11.6.7 Using the <code>command</code> attribute on <code>menuitem</code> elements to define
a command indirectly</a><li><a href=#using-the-accesskey-attribute-on-a-label-element-to-define-a-command>4.11.6.8 Using the <code>accesskey</code> attribute
on a <code>label</code> element to define a command</a><li><a href=#using-the-accesskey-attribute-on-a-legend-element-to-define-a-command>4.11.6.9 Using the <code>accesskey</code> attribute
@@ -600,7 +600,7 @@
<p>To avoid exposing Web authors to the complexities of multithreading, the HTML and DOM APIs are
designed such that no script can ever detect the simultaneous execution of other scripts. Even
- with <a href=#worker id=serialisability-of-script-execution:worker>workers</a>, the intent is that the behavior of implementations can
+ with <a href=#worker id=serialisability-of-script-execution:worker>workers</a>, the intent is that the behaviour of implementations can
be thought of as completely serialising the execution of all scripts in all <a href=#browsing-context id=serialisability-of-script-execution:browsing-context>browsing contexts</a>.</p>
<p class=note>The <code id=serialisability-of-script-execution:dom-navigator-yieldforstorageupdates><a href=#dom-navigator-yieldforstorageupdates>navigator.yieldForStorageUpdates()</a></code> method, in
@@ -1264,7 +1264,7 @@
<p>The syntax of HTML is constrained to avoid a wide variety of problems.</p>
- <dl><dt>Unintuitive error-handling behavior<dd>
+ <dl><dt>Unintuitive error-handling behaviour<dd>
<p>Certain invalid syntax constructs, when parsed, result in DOM trees that are highly
unintuitive.</p>
@@ -1284,11 +1284,11 @@
more bizarre and convoluted error handling rules, user agents are permitted to fail whenever
encountering a <a href=#parse-error id=syntax-errors:parse-error>parse error</a>.</p>
- <dt>Errors where the error-handling behavior is not compatible with streaming user agents<dd>
+ <dt>Errors where the error-handling behaviour is not compatible with streaming user agents<dd>
- <p>Some error-handling behavior, such as the behavior for the <code><table><hr>...</code> example mentioned above, are incompatible with streaming
+ <p>Some error-handling behaviour, such as the behaviour for the <code><table><hr>...</code> example mentioned above, are incompatible with streaming
user agents (user agents that process HTML files in one pass, without storing state). To avoid
- interoperability problems with such user agents, any syntax resulting in such behavior is
+ interoperability problems with such user agents, any syntax resulting in such behaviour is
considered invalid.</p>
<dt>Errors that can result in infoset coercion<dd>
@@ -1372,7 +1372,7 @@
<div class=example>
<p>Another example of this is the DOCTYPE, which is required to trigger <a href=#no-quirks-mode id=syntax-errors:no-quirks-mode>no-quirks
- mode</a>, because the behavior of legacy user agents in <a href=#quirks-mode id=syntax-errors:quirks-mode>quirks mode</a> is often
+ mode</a>, because the behaviour of legacy user agents in <a href=#quirks-mode id=syntax-errors:quirks-mode>quirks mode</a> is often
largely undocumented.</p>
</div>
@@ -1477,7 +1477,7 @@
<dt>Cases where the default styles are likely to lead to confusion<dd>
- <p>Certain elements have default styles or behaviors that make certain combinations likely to
+ <p>Certain elements have default styles or behaviours that make certain combinations likely to
lead to confusion. Where these have equivalent alternatives without this problem, the confusing
combinations are disallowed.</p>
@@ -1491,7 +1491,7 @@
<p class=example>Another example would be the way <a href=#interactive-content-2 id=restrictions-on-content-models-and-on-attribute-values:interactive-content-2>interactive content</a> cannot be
nested. For example, a <code id=restrictions-on-content-models-and-on-attribute-values:the-button-element><a href=#the-button-element>button</a></code> element cannot contain a <code id=restrictions-on-content-models-and-on-attribute-values:the-textarea-element><a href=#the-textarea-element>textarea</a></code>
- element. This is because the default behavior of such nesting interactive elements would be
+ element. This is because the default behaviour of such nesting interactive elements would be
highly confusing to users. Instead of nesting these elements, they can be placed side by
side.</p>
@@ -2053,7 +2053,7 @@
<p>User agents that are designated as supporting the suggested default rendering must, while so
designated, implement the rules in <a href=#rendering>the rendering section</a> that that
- section defines as the behavior that user agents are <em>expected</em> to implement.</p>
+ section defines as the behaviour that user agents are <em>expected</em> to implement.</p>
<dt id=non-scripted>User agents with no scripting support<dd>
@@ -2173,7 +2173,7 @@
<p>Some conformance requirements are phrased as requirements on elements, attributes, methods or
objects. Such requirements fall into two categories: those describing content model restrictions,
- and those describing implementation behavior. Those in the former category are requirements on
+ and those describing implementation behaviour. Those in the former category are requirements on
documents and authoring tools. Those in the second category are requirements on user agents.
Similarly, some conformance requirements are phrased as requirements on authors; such requirements
are to be interpreted as conformance requirements on the documents that authors produce. (In other
@@ -2936,8 +2936,8 @@
<p class=note>Implementors are strongly urged to carefully examine any third-party libraries
they might consider using to implement the parsing of syntaxes described below. For example, date
- libraries are likely to implement error handling behavior that differs from what is required in
- this specification, since error-handling behavior is often not defined in specifications that
+ libraries are likely to implement error handling behaviour that differs from what is required in
+ this specification, since error-handling behaviour is often not defined in specifications that
describe date syntaxes similar to those used in this specification, and thus implementations tend
to vary greatly in how they handle errors.</p>
@@ -4520,7 +4520,7 @@
<h4 id=terminology-3>2.6.1 Terminology</h4>
<p id=concept-http-equivalent>User agents can implement a variety of transfer protocols, but
- this specification mostly defines behavior in terms of HTTP. <a href=#refsHTTP>[HTTP]</a></p>
+ this specification mostly defines behaviour in terms of HTTP. <a href=#refsHTTP>[HTTP]</a></p>
<p>The <dfn id=concept-http-equivalent-get>HTTP GET method</dfn> is equivalent to the default
retrieval action of the protocol. For example, RETR in FTP. Such actions are idempotent and safe,
@@ -5022,7 +5022,7 @@
<p>If a reflecting IDL attribute has an unsigned integer type (<code id=reflecting-content-attributes-in-idl-attributes:idl-unsigned-long-2><a href=#idl-unsigned-long>unsigned long</a></code>) that is <dfn id=limited-to-only-non-negative-numbers-greater-than-zero>limited to only non-negative numbers
- greater than zero</dfn>, then the behavior is similar to the previous case, but zero is not
+ greater than zero</dfn>, then the behaviour is similar to the previous case, but zero is not
allowed. On getting, the content attribute must first be parsed according to the <a href=#rules-for-parsing-non-negative-integers id=reflecting-content-attributes-in-idl-attributes:rules-for-parsing-non-negative-integers-3>rules for
parsing non-negative integers</a>, and if that is successful, and the value is in the range 1
to 2147483647 inclusive, the resulting value must be returned. If, on the other hand, it fails or
@@ -5043,7 +5043,7 @@
number</a> and then that string must be used as the new content attribute value.</p>
<p>If a reflecting IDL attribute has a floating-point number type (<code id=reflecting-content-attributes-in-idl-attributes:idl-double-2><a href=#idl-double>double</a></code> or <code id=reflecting-content-attributes-in-idl-attributes:idl-unrestricted-double-2><a href=#idl-unrestricted-double>unrestricted
- double</a></code>) that is <dfn id=limited-to-numbers-greater-than-zero>limited to numbers greater than zero</dfn>, then the behavior is
+ double</a></code>) that is <dfn id=limited-to-numbers-greater-than-zero>limited to numbers greater than zero</dfn>, then the behaviour is
similar to the previous case, but zero and negative values are not allowed. On getting, the
content attribute must be parsed according to the <a href=#rules-for-parsing-floating-point-number-values id=reflecting-content-attributes-in-idl-attributes:rules-for-parsing-floating-point-number-values-2>rules for parsing floating-point number
values</a>, and if that is successful and the value is greater than 0.0, the resulting value
@@ -5310,7 +5310,7 @@
<p>On getting, the <dfn id=dom-htmloptionscollection-length><code>length</code></dfn>
attribute must return the number of nodes <a href=#represented-by-the-collection id=the-htmloptionscollection-interface:represented-by-the-collection>represented by the collection</a>.</p>
- <p>On setting, the behavior depends on whether the new value is equal to, greater than, or less
+ <p>On setting, the behaviour depends on whether the new value is equal to, greater than, or less
than the number of nodes <a href=#represented-by-the-collection id=the-htmloptionscollection-interface:represented-by-the-collection-2>represented by the collection</a> at that time. If the number is
the same, then setting the attribute must do nothing. If the new value is greater, then <var>n</var> new <code id=the-htmloptionscollection-interface:the-option-element-4><a href=#the-option-element>option</a></code> elements with no attributes and no child nodes must be
appended to the <code id=the-htmloptionscollection-interface:the-select-element-2><a href=#the-select-element>select</a></code> element on which the <code id=the-htmloptionscollection-interface:htmloptionscollection-3><a href=#htmloptionscollection>HTMLOptionsCollection</a></code> is
@@ -5614,7 +5614,7 @@
<var>memory</var> as the "<var>memory</var>" argument.<li><p>Return <var>output</var>.</ol>
<p>The <dfn id=internal-structured-cloning-algorithm>internal structured cloning algorithm</dfn> is always called with two arguments,
- <var>input</var> and <var>memory</var>, and its behavior is as follows:</p>
+ <var>input</var> and <var>memory</var>, and its behaviour is as follows:</p>
<ol><li><p>If <var>input</var> is the source object of a pair of objects in <var>memory</var>, then
return the destination object in that pair of objects and abort these steps.<li><p>If <var>input</var> is a primitive value, then return that value and abort these
@@ -6831,7 +6831,7 @@
<h6 id=metadata-content>3.2.4.2.1 Metadata content</h6>
- <p><dfn id=metadata-content-2>Metadata content</dfn> is content that sets up the presentation or behavior of the rest of
+ <p><dfn id=metadata-content-2>Metadata content</dfn> is content that sets up the presentation or behaviour of the rest of
the content, or that sets up the relationship of the document with other documents, or that
conveys other "out of band" information.</p>
@@ -7279,7 +7279,7 @@
<p>The XML specification also allows the use of the <code id=global-attributes:attr-xml-space><a href=#attr-xml-space>xml:space</a></code>
attribute in the <a href=#xml-namespace id=global-attributes:xml-namespace>XML namespace</a> on any element in an <a href=#xml-documents id=global-attributes:xml-documents-2>XML
document</a>. This attribute has no effect on <a href=#html-elements id=global-attributes:html-elements-5>HTML elements</a>, as the default
- behavior in HTML is to preserve whitespace. <a href=#refsXML>[XML]</a></p>
+ behaviour in HTML is to preserve whitespace. <a href=#refsXML>[XML]</a></p>
<p class=note>There is no way to serialise the <code id=global-attributes:attr-xml-space-2><a href=#attr-xml-space>xml:space</a></code>
attribute on <a href=#html-elements id=global-attributes:html-elements-6>HTML elements</a> in the <code id=global-attributes:text/html><a href=#text/html>text/html</a></code> syntax.</p>
@@ -7970,7 +7970,7 @@
- <p>User agents must not derive any implementation behavior from these attributes or values.
+ <p>User agents must not derive any implementation behaviour from these attributes or values.
Specifications intended for user agents must not define these attributes to have any meaningful
values.</p>
@@ -9195,7 +9195,7 @@
<p>The <dfn id=attr-link-crossorigin><code>crossorigin</code></dfn> attribute is a <a href=#cors-settings-attribute id=the-link-element:cors-settings-attribute>CORS
settings attribute</a>. It is intended for use with external resource links.</p>
- <p>The exact behavior for links to external resources depends on the exact relationship, as
+ <p>The exact behaviour for links to external resources depends on the exact relationship, as
defined for the relevant link type. Some of the attributes control whether or not the external
resource is to be applied (as defined below).</p>
@@ -9381,7 +9381,7 @@
- <p>The <a href=#activation-behavior id=the-link-element:activation-behavior>activation behavior</a> of <code id=the-link-element:the-link-element-18><a href=#the-link-element>link</a></code> elements that create <a href=#hyperlink id=the-link-element:hyperlink-5>hyperlinks</a> is to run the following steps:</p>
+ <p>The <a href=#activation-behaviour id=the-link-element:activation-behaviour>activation behaviour</a> of <code id=the-link-element:the-link-element-18><a href=#the-link-element>link</a></code> elements that create <a href=#hyperlink id=the-link-element:hyperlink-5>hyperlinks</a> is to run the following steps:</p>
<ol><li><p>If the <code id=the-link-element:the-link-element-19><a href=#the-link-element>link</a></code> element's <a id=the-link-element:node-document-3 href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is not <a href=#fully-active id=the-link-element:fully-active>fully active</a>,
then abort these steps.<li><p><a href=#following-hyperlinks-2 id=the-link-element:following-hyperlinks-2-2>Follow the hyperlink</a> created by the
@@ -9953,13 +9953,13 @@
directives</dfn> may, under certain conditions, be registered in the <a href=https://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki PragmaExtensions page</a>. <a href=#refsWHATWGWIKI>[WHATWGWIKI]</a></p>
<p>Such extensions must use a name that is identical to an HTTP header registered in the Permanent
- Message Header Field Registry, and must have behavior identical to that described for the HTTP
+ Message Header Field Registry, and must have behaviour identical to that described for the HTTP
header. <a href=#refsIANAPERMHEADERS>[IANAPERMHEADERS]</a></p>
<p>Pragma directives corresponding to headers describing metadata, or not requiring specific user
agent processing, must not be registered; instead, use <a href=#concept-meta-extensions id=other-pragma-directives:concept-meta-extensions>metadata names</a>. Pragma directives corresponding to headers
that affect the HTTP processing model (e.g. caching) must not be registered, as they would result
- in HTTP-level behavior being different for user agents that implement HTML than for user agents
+ in HTTP-level behaviour being different for user agents that implement HTML than for user agents
that do not.</p>
<p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at any time to add a pragma
@@ -13615,7 +13615,7 @@
<pre><article lang="en-US">
<h1>My use of language and my cats</h1>
- <p>My cat's behavior hasn't changed much since her absence, except
+ <p>My cat's behaviour hasn't changed much since her absence, except
that she plays her new physique to the neighbors regularly, in an
attempt to get pets.</p>
<div lang="en-GB">
@@ -13697,7 +13697,7 @@
attributes may be used to indicate to the user the likely nature of the target resource before the
user follows the link.</p>
- <p>The <a href=#activation-behavior id=the-a-element:activation-behavior>activation behavior</a> of <code id=the-a-element:the-a-element-6><a href=#the-a-element>a</a></code> elements that create <a href=#hyperlink id=the-a-element:hyperlink-4>hyperlinks</a> is to run the following steps:</p>
+ <p>The <a href=#activation-behaviour id=the-a-element:activation-behaviour>activation behaviour</a> of <code id=the-a-element:the-a-element-6><a href=#the-a-element>a</a></code> elements that create <a href=#hyperlink id=the-a-element:hyperlink-4>hyperlinks</a> is to run the following steps:</p>
<ol><li><p>If the <code id=the-a-element:the-a-element-7><a href=#the-a-element>a</a></code> element's <a id=the-a-element:node-document href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is not <a href=#fully-active id=the-a-element:fully-active>fully active</a>, then abort these steps.<li>
@@ -15973,7 +15973,7 @@
context</a> that will be used. User agents use this name when
<a href=#following-hyperlinks-2 id=links-created-by-a-and-area-elements:following-hyperlinks-2>following hyperlinks</a>.</p>
- <p>When an <code id=links-created-by-a-and-area-elements:the-a-element-4><a href=#the-a-element>a</a></code> or <code id=links-created-by-a-and-area-elements:the-area-element-4><a href=#the-area-element>area</a></code> element's <a href=#activation-behavior id=links-created-by-a-and-area-elements:activation-behavior>activation behavior</a> is
+ <p>When an <code id=links-created-by-a-and-area-elements:the-a-element-4><a href=#the-a-element>a</a></code> or <code id=links-created-by-a-and-area-elements:the-area-element-4><a href=#the-area-element>area</a></code> element's <a href=#activation-behaviour id=links-created-by-a-and-area-elements:activation-behaviour>activation behaviour</a> is
invoked, the user agent may allow the user to indicate a preference regarding whether the
hyperlink is to be used for <a href=#navigate id=links-created-by-a-and-area-elements:navigate>navigation</a> or whether the resource it
specifies is to be downloaded.</p>
@@ -16249,7 +16249,7 @@
<code id=hyperlink-auditing:document><a href=#document>Document</a></code> containing the <a href=#hyperlink id=hyperlink-auditing:hyperlink-2>hyperlink</a> (as described below). (Tokens that fail to resolve are ignored.) This may be done in parallel
with the primary request, and is independent of the result of that request.</p>
- <p>User agents should allow the user to adjust this behavior, for example in conjunction with a
+ <p>User agents should allow the user to adjust this behaviour, for example in conjunction with a
setting that disables the sending of HTTP <code id=hyperlink-auditing:http-referer><a href=#http-referer>Referer</a></code> (sic)
headers. Based on the user's preferences, UAs may either <a href=#ignore id=hyperlink-auditing:ignore>ignore</a> the <code id=hyperlink-auditing:ping-3><a href=#ping>ping</a></code> attribute altogether, or selectively ignore URLs in the
list (e.g. ignoring any third-party URLs).</p>
@@ -20815,8 +20815,8 @@
<p>The <code id=the-embed-element:htmlembedelement><a href=#htmlembedelement>HTMLEmbedElement</a></code> object representing the element must expose the scriptable
interface of the <a href=#plugin id=the-embed-element:plugin-18>plugin</a> instantiated for the <code id=the-embed-element:the-embed-element-25><a href=#the-embed-element>embed</a></code> element, if any. At a
minimum, this interface must implement the <dfn id=dom-embed-caller>legacy caller
- operation</dfn>. (It is suggested that the default behavior of this legacy caller operation, e.g.
- the behavior of the default plugin's legacy caller operation, be to throw a
+ operation</dfn>. (It is suggested that the default behaviour of this legacy caller operation, e.g.
+ the behaviour of the default plugin's legacy caller operation, be to throw a
<code id=the-embed-element:notsupportederror><a href=#notsupportederror>NotSupportedError</a></code> exception.)</p>
@@ -20961,7 +20961,7 @@
<ol><li>
<p>If the user has indicated a preference that this <code id=the-object-element:the-object-element-6><a href=#the-object-element>object</a></code> element's <a href=#fallback-content id=the-object-element:fallback-content-2>fallback
- content</a> be shown instead of the element's usual behavior, then jump to the step below
+ content</a> be shown instead of the element's usual behaviour, then jump to the step below
labeled <i>fallback</i>.</p>
<p class=note>For example, a user could ask for the element's <a href=#fallback-content id=the-object-element:fallback-content-3>fallback content</a> to
@@ -21335,7 +21335,7 @@
<p>All <code id=the-object-element:the-object-element-42><a href=#the-object-element>object</a></code> elements have a <dfn id=dom-object-caller>legacy caller
operation</dfn>. If the <code id=the-object-element:the-object-element-43><a href=#the-object-element>object</a></code> element has an instantiated <a href=#plugin id=the-object-element:plugin-25>plugin</a> that
supports a scriptable interface that defines a legacy caller operation, then that must be the
- behavior of the object's legacy caller operation. Otherwise, the object's legacy caller operation
+ behaviour of the object's legacy caller operation. Otherwise, the object's legacy caller operation
must be to throw a <code id=the-object-element:notsupportederror><a href=#notsupportederror>NotSupportedError</a></code> exception.</p>
@@ -21850,7 +21850,7 @@
<p>If the author isn't sure if user agents will all be able to render the media resources
provided, the author can listen to the <code id=the-source-element:event-error><a href=#event-error>error</a></code> event on the last
- <code id=the-source-element:the-source-element-5><a href=#the-source-element>source</a></code> element and trigger fallback behavior:</p>
+ <code id=the-source-element:the-source-element-5><a href=#the-source-element>source</a></code> element and trigger fallback behaviour:</p>
<pre><script>
function fallback(video) {
@@ -22639,7 +22639,7 @@
<ol><li>
- <p>Optionally, run the following substeps. This is the expected behavior if the user agent
+ <p>Optionally, run the following substeps. This is the expected behaviour if the user agent
intends to not attempt to fetch the resource until the user requests it explicitly (e.g. as
a way to implement the <code id=loading-the-media-resource:attr-media-preload><a href=#attr-media-preload>preload</a></code> attribute's <code id=loading-the-media-resource:attr-media-preload-none><a href=#attr-media-preload-none>none</a></code> keyword).</p>
@@ -23446,7 +23446,7 @@
<p class=note>User agents do not need to support autoplay, and it is suggested that user
agents honor user preferences on the matter. Authors are urged to use the <code id=ready-states:attr-media-autoplay-2><a href=#attr-media-autoplay>autoplay</a></code> attribute rather than using script to force the
- video to play, so as to allow the user to override the behavior if so desired.</p>
+ video to play, so as to allow the user to override the behaviour if so desired.</p>
<p>In any case, the user agent must finally <a href=#queue-a-task id=ready-states:queue-a-task-11>queue a task</a> to <a href=#fire-a-simple-event id=ready-states:fire-a-simple-event-11>fire a simple
event</a> named <code id=ready-states:event-media-canplaythrough><a href=#event-media-canplaythrough>canplaythrough</a></code> at the element.</p>
@@ -23478,7 +23478,7 @@
<p class=note>Authors are urged to use the <code id=ready-states:attr-media-autoplay-3><a href=#attr-media-autoplay>autoplay</a></code>
attribute rather than using script to trigger automatic playback, as this allows the user to
override the automatic playback when it is not desired, e.g. when using a screen reader. Authors
- are also encouraged to consider not using the automatic playback behavior at all, and instead to
+ are also encouraged to consider not using the automatic playback behaviour at all, and instead to
let the user agent wait for the user to start playback explicitly.</p>
@@ -24061,7 +24061,7 @@
value (which would equal the time of the last frame, and might be positive Infinity).</p>
<p class=note>The range might be continuously changing, e.g. if the user agent is buffering a
- sliding window on an infinite stream. This is the behavior seen with DVRs viewing live TV, for
+ sliding window on an infinite stream. This is the behaviour seen with DVRs viewing live TV, for
instance.</p>
<p>User agents should adopt adopt a very liberal and optimistic view of what is seekable. User
@@ -26455,7 +26455,7 @@
element</a> without affecting the <code id=user-interface:mediacontroller-6><a href=#mediacontroller>MediaController</a></code>, but such features are
considered relatively advanced and unlikely to be useful to most users.</p>
- <p>The <a href=#activation-behavior id=user-interface:activation-behavior>activation behavior</a> of a <a href=#media-element id=user-interface:media-element-16>media element</a> that is <a href=#expose-a-user-interface-to-the-user id=user-interface:expose-a-user-interface-to-the-user-3>exposing a user interface to the user</a> must be
+ <p>The <a href=#activation-behaviour id=user-interface:activation-behaviour>activation behaviour</a> of a <a href=#media-element id=user-interface:media-element-16>media element</a> that is <a href=#expose-a-user-interface-to-the-user id=user-interface:expose-a-user-interface-to-the-user-3>exposing a user interface to the user</a> must be
to run the following steps:</p>
<ol><li><p>If the <a href=#media-element id=user-interface:media-element-17>media element</a> has a <a href=#current-media-controller id=user-interface:current-media-controller-9>current media controller</a>, and that
@@ -27408,7 +27408,7 @@
- <p>The <a href=#activation-behavior id=the-area-element:activation-behavior>activation behavior</a> of <code id=the-area-element:the-area-element-13><a href=#the-area-element>area</a></code> elements is to run the following
+ <p>The <a href=#activation-behaviour id=the-area-element:activation-behaviour>activation behaviour</a> of <code id=the-area-element:the-area-element-13><a href=#the-area-element>area</a></code> elements is to run the following
steps:</p>
<ol><li><p>If the <code id=the-area-element:the-area-element-14><a href=#the-area-element>area</a></code> element's <a id=the-area-element:node-document href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is not <a href=#fully-active id=the-area-element:fully-active>fully active</a>,
@@ -27831,7 +27831,7 @@
<p class=note>The corresponding IDL attributes for <code id=dimension-attributes:dom-img-height><a href=#dom-img-height>img</a></code> and
<code id=dimension-attributes:dom-input-height><a href=#dom-input-height>input</a></code> elements are defined in those respective elements'
- sections, as they are slightly more specific to those elements' other behaviors.</p>
+ sections, as they are slightly more specific to those elements' other behaviours.</p>
@@ -28113,7 +28113,7 @@
element, again in <a href=#tree-order id=the-table-element:tree-order-2>tree order</a>, followed finally by those elements whose parent is a
<code id=the-table-element:the-tfoot-element-17><a href=#the-tfoot-element>tfoot</a></code> element, still in <a href=#tree-order id=the-table-element:tree-order-3>tree order</a>.</p>
- <p>The behavior of the <dfn id=dom-table-insertrow><code>insertRow(<var>index</var>)</code></dfn> method depends on the state of the table. When it is called,
+ <p>The behaviour of the <dfn id=dom-table-insertrow><code>insertRow(<var>index</var>)</code></dfn> method depends on the state of the table. When it is called,
the method must act as required by the first item in the following list of conditions that
describes the state of the table and the <var>index</var> argument:</p>
@@ -30627,7 +30627,7 @@
<hr>
- <p>The <a href=#activation-behavior id=table-sorting-model:activation-behavior>activation behavior</a> of a <a href=#sorting-interface-th-element id=table-sorting-model:sorting-interface-th-element>sorting interface <code>th</code>
+ <p>The <a href=#activation-behaviour id=table-sorting-model:activation-behaviour>activation behaviour</a> of a <a href=#sorting-interface-th-element id=table-sorting-model:sorting-interface-th-element>sorting interface <code>th</code>
element</a> is to <a href=#set-the-sort-key id=table-sorting-model:set-the-sort-key>set the sort key</a> to the <code id=table-sorting-model:the-th-element-20><a href=#the-th-element>th</a></code> element.</p>
<p class=note>The <code id=table-sorting-model:the-table-element-20><a href=#the-table-element>table</a></code> will be sorted the next time the user agent <a href=#perform-a-microtask-checkpoint id=table-sorting-model:perform-a-microtask-checkpoint>performs a microtask checkpoint</a>.</p>
@@ -31753,9 +31753,9 @@
then the first such descendant in <a href=#tree-order id=the-label-element:tree-order>tree order</a> is the <code id=the-label-element:the-label-element-9><a href=#the-label-element>label</a></code> element's
<a href=#labeled-control id=the-label-element:labeled-control-4>labeled control</a>.</p>
- <p>The <code id=the-label-element:the-label-element-10><a href=#the-label-element>label</a></code> element's exact default presentation and behavior, in particular what
- its <a href=#activation-behavior id=the-label-element:activation-behavior>activation behavior</a> might be, if anything, should match the platform's label
- behavior. The <a href=#activation-behavior id=the-label-element:activation-behavior-2>activation behavior</a> of a <code id=the-label-element:the-label-element-11><a href=#the-label-element>label</a></code> element for events targeted
+ <p>The <code id=the-label-element:the-label-element-10><a href=#the-label-element>label</a></code> element's exact default presentation and behaviour, in particular what
+ its <a href=#activation-behaviour id=the-label-element:activation-behaviour>activation behaviour</a> might be, if anything, should match the platform's label
+ behaviour. The <a href=#activation-behaviour id=the-label-element:activation-behaviour-2>activation behaviour</a> of a <code id=the-label-element:the-label-element-11><a href=#the-label-element>label</a></code> element for events targeted
at <a href=#interactive-content-2 id=the-label-element:interactive-content-2-2>interactive content</a> descendants of a <code id=the-label-element:the-label-element-12><a href=#the-label-element>label</a></code> element, and any
descendants of those <a href=#interactive-content-2 id=the-label-element:interactive-content-2-3>interactive content</a> descendants, must be to do nothing.</p>
@@ -31770,7 +31770,7 @@
<pre><label><input type=checkbox name=lost> Lost</label></pre>
- <p>On other platforms, the behavior might be just to focus the control, or do nothing.</p>
+ <p>On other platforms, the behaviour might be just to focus the control, or do nothing.</p>
</div>
@@ -32056,7 +32056,7 @@
<code id=the-input-element:the-input-element-2><a href=#the-input-element>input</a></code> element depends on the state of its
<code id=the-input-element:attr-input-type-6><a href=#attr-input-type>type</a></code> attribute.
The subsections that define each type also clearly define in normative "bookkeeping" sections
- which of these feature apply, and which <dfn id=do-not-apply>do not apply</dfn>, to each type. The behavior of
+ which of these feature apply, and which <dfn id=do-not-apply>do not apply</dfn>, to each type. The behaviour of
these features depends on whether they apply or not, as defined in their various sections (q.v.
for <a href=#common-input-element-attributes>content attributes</a>, for <a href=#common-input-element-apis>APIs</a>, for <a href=#common-input-element-events>events</a>).</p>
@@ -33239,8 +33239,8 @@
<hr>
- <p>When an <code id=the-input-element:the-input-element-15><a href=#the-input-element>input</a></code> element is first created, the element's rendering and behavior must
- be set to the rendering and behavior defined for the <code id=the-input-element:attr-input-type-9><a href=#attr-input-type>type</a></code>
+ <p>When an <code id=the-input-element:the-input-element-15><a href=#the-input-element>input</a></code> element is first created, the element's rendering and behaviour must
+ be set to the rendering and behaviour defined for the <code id=the-input-element:attr-input-type-9><a href=#attr-input-type>type</a></code>
attribute's state, and the <a href=#value-sanitization-algorithm id=the-input-element:value-sanitization-algorithm-3>value sanitization algorithm</a>, if one is defined for the
<code id=the-input-element:attr-input-type-10><a href=#attr-input-type>type</a></code> attribute's state, must be invoked.</p>
@@ -33257,7 +33257,7 @@
IDL attribute in any mode other than the <i id=the-input-element:dom-input-value-value-11><a href=#dom-input-value-value>value</a></i> mode, and the
new state of the element's <code id=the-input-element:attr-input-type-15><a href=#attr-input-type>type</a></code> attribute puts the <code id=the-input-element:dom-input-value-8><a href=#dom-input-value>value</a></code> IDL attribute in the <i id=the-input-element:dom-input-value-value-12><a href=#dom-input-value-value>value</a></i> mode, then set the <a href=#concept-fe-value id=the-input-element:concept-fe-value-10>value</a> of the element to the value of the <code id=the-input-element:attr-input-value-6><a href=#attr-input-value>value</a></code> content attribute, if there is one, or the empty string
otherwise, and then set the control's <a href=#concept-input-value-dirty-flag id=the-input-element:concept-input-value-dirty-flag-5>dirty value
- flag</a> to false.<li><p>Update the element's rendering and behavior to the new state's.<li><p><dfn id=signal-a-type-change>Signal a type change</dfn> for the element. (The <a href="#radio-button-state-(type=radio)" id="the-input-element:radio-button-state-(type=radio)-3">Radio Button</a> state uses this, in particular.)<li><p>Invoke the <a href=#value-sanitization-algorithm id=the-input-element:value-sanitization-algorithm-4>value sanitization algorithm</a>, if one is defined for the <code id=the-input-element:attr-input-type-16><a href=#attr-input-type>type</a></code> attribute's new state.</ol>
+ flag</a> to false.<li><p>Update the element's rendering and behaviour to the new state's.<li><p><dfn id=signal-a-type-change>Signal a type change</dfn> for the element. (The <a href="#radio-button-state-(type=radio)" id="the-input-element:radio-button-state-(type=radio)-3">Radio Button</a> state uses this, in particular.)<li><p>Invoke the <a href=#value-sanitization-algorithm id=the-input-element:value-sanitization-algorithm-4>value sanitization algorithm</a>, if one is defined for the <code id=the-input-element:attr-input-type-16><a href=#attr-input-type>type</a></code> attribute's new state.</ol>
</div>
@@ -33270,7 +33270,7 @@
The <code id=the-input-element:attr-fae-form-2><a href=#attr-fae-form>form</a></code> attribute is used to explicitly associate the <code id=the-input-element:the-input-element-17><a href=#the-input-element>input</a></code> element with its <a href=#form-owner id=the-input-element:form-owner>form owner</a>.
The <code id=the-input-element:attr-fe-autofocus-2><a href=#attr-fe-autofocus>autofocus</a></code> attribute controls focus.
The <code id=the-input-element:attr-fe-inputmode-4><a href=#attr-fe-inputmode>inputmode</a></code> attribute controls the user interface's input modality for the control.
- The <code id=the-input-element:attr-fe-autocomplete-4><a href=#attr-fe-autocomplete>autocomplete</a></code> attribute controls how the user agent provides autofill behavior.
+ The <code id=the-input-element:attr-fe-autocomplete-4><a href=#attr-fe-autocomplete>autocomplete</a></code> attribute controls how the user agent provides autofill behaviour.
</p>
@@ -35591,12 +35591,12 @@
activation steps</a> consist of setting the element's <a href=#concept-fe-checked id="checkbox-state-(type=checkbox):concept-fe-checked-3">checkedness</a> to its opposite value (i.e. true if it is false,
false if it is true), and of setting the element's <code id="checkbox-state-(type=checkbox):dom-input-indeterminate-4"><a href=#dom-input-indeterminate>indeterminate</a></code> IDL attribute to false. The <a href=#canceled-activation-steps id="checkbox-state-(type=checkbox):canceled-activation-steps">canceled
activation steps</a> consist of setting the <a href=#concept-fe-checked id="checkbox-state-(type=checkbox):concept-fe-checked-4">checkedness</a> and the element's <code id="checkbox-state-(type=checkbox):dom-input-indeterminate-5"><a href=#dom-input-indeterminate>indeterminate</a></code> IDL attribute back to the values they had
- before the <a href=#pre-click-activation-steps id="checkbox-state-(type=checkbox):pre-click-activation-steps-2">pre-click activation steps</a> were run. The <a href=#activation-behavior id="checkbox-state-(type=checkbox):activation-behavior">activation behavior</a>
+ before the <a href=#pre-click-activation-steps id="checkbox-state-(type=checkbox):pre-click-activation-steps-2">pre-click activation steps</a> were run. The <a href=#activation-behaviour id="checkbox-state-(type=checkbox):activation-behaviour">activation behaviour</a>
is to <a href=#fire-a-simple-event id="checkbox-state-(type=checkbox):fire-a-simple-event">fire a simple event</a> that bubbles named <code id="checkbox-state-(type=checkbox):event-input-input"><a href=#event-input-input>input</a></code> at the element and then <a href=#fire-a-simple-event id="checkbox-state-(type=checkbox):fire-a-simple-event-2">fire a simple event</a>
that bubbles named <code id="checkbox-state-(type=checkbox):event-input-change"><a href=#event-input-change>change</a></code> at the element. </p>
- <p>If the element is not <i id="checkbox-state-(type=checkbox):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="checkbox-state-(type=checkbox):activation-behavior-2">activation
- behavior</a>.</p>
+ <p>If the element is not <i id="checkbox-state-(type=checkbox):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="checkbox-state-(type=checkbox):activation-behaviour-2">activation
+ behaviour</a>.</p>
<p><strong>Constraint validation</strong>: If the element is <i id="checkbox-state-(type=checkbox):concept-input-required"><a href=#concept-input-required>required</a></i> and its <a href=#concept-fe-checked id="checkbox-state-(type=checkbox):concept-fe-checked-5">checkedness</a> is false, then the element is <a href=#suffering-from-being-missing id="checkbox-state-(type=checkbox):suffering-from-being-missing">suffering from
being missing</a>.</p>
@@ -35719,14 +35719,14 @@
<var>R</var>'s <a href=#radio-button-group id="radio-button-state-(type=radio):radio-button-group-5">radio button group</a>, if it still has one, and if so, setting that
element's <a href=#concept-fe-checked id="radio-button-state-(type=radio):concept-fe-checked-8">checkedness</a> to true; or else, if there was no
such element, or that element is no longer in <var>R</var>'s <a href=#radio-button-group id="radio-button-state-(type=radio):radio-button-group-6">radio button group</a>, or
- if <var>R</var> no longer has a <a href=#radio-button-group id="radio-button-state-(type=radio):radio-button-group-7">radio button group</a>, setting <var>R</var>'s <a href=#concept-fe-checked id="radio-button-state-(type=radio):concept-fe-checked-9">checkedness</a> to false. The <a href=#activation-behavior id="radio-button-state-(type=radio):activation-behavior">activation behavior</a> for
+ if <var>R</var> no longer has a <a href=#radio-button-group id="radio-button-state-(type=radio):radio-button-group-7">radio button group</a>, setting <var>R</var>'s <a href=#concept-fe-checked id="radio-button-state-(type=radio):concept-fe-checked-9">checkedness</a> to false. The <a href=#activation-behaviour id="radio-button-state-(type=radio):activation-behaviour">activation behaviour</a> for
<var>R</var> is to <a href=#fire-a-simple-event id="radio-button-state-(type=radio):fire-a-simple-event">fire a simple event</a> that bubbles named <code id="radio-button-state-(type=radio):event-input-input"><a href=#event-input-input>input</a></code> at <var>R</var> and then <a href=#fire-a-simple-event id="radio-button-state-(type=radio):fire-a-simple-event-2">fire a simple event</a>
that bubbles named <code id="radio-button-state-(type=radio):event-input-change"><a href=#event-input-change>change</a></code> at <var>R</var>. </p>
- <p>If the element is not <i id="radio-button-state-(type=radio):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="radio-button-state-(type=radio):activation-behavior-2">activation
- behavior</a>.</p>
+ <p>If the element is not <i id="radio-button-state-(type=radio):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="radio-button-state-(type=radio):activation-behaviour-2">activation
+ behaviour</a>.</p>
<p><strong>Constraint validation</strong>: If an element in the <i id="radio-button-state-(type=radio):radio-button-group-8"><a href=#radio-button-group>radio button group</a></i> is <i id="radio-button-state-(type=radio):concept-input-required"><a href=#concept-input-required>required</a></i>, and all of the <code id="radio-button-state-(type=radio):the-input-element-8"><a href=#the-input-element>input</a></code> elements in the
<i id="radio-button-state-(type=radio):radio-button-group-9"><a href=#radio-button-group>radio button group</a></i> have a <a href=#concept-fe-checked id="radio-button-state-(type=radio):concept-fe-checked-10">checkedness</a> that is
@@ -35825,7 +35825,7 @@
files</a>.</p>
<p>If the element is <i id="file-upload-state-(type=file):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, then the element's
- <a href=#activation-behavior id="file-upload-state-(type=file):activation-behavior">activation behavior</a> is to run the following steps:</p>
+ <a href=#activation-behaviour id="file-upload-state-(type=file):activation-behaviour">activation behaviour</a> is to run the following steps:</p>
<ol><li><p>If the algorithm is not <a href=#allowed-to-show-a-popup id="file-upload-state-(type=file):allowed-to-show-a-popup">allowed to show a popup</a>, then abort these steps
without doing anything else.<li><p>Return, but continue running these steps <a href=#in-parallel id="file-upload-state-(type=file):in-parallel">in parallel</a>.<li><p>Optionally, wait until any prior execution of this algorithm has terminated.</p>
@@ -35847,8 +35847,8 @@
<code id="file-upload-state-(type=file):event-input-input-2"><a href=#event-input-input>input</a></code> at the <code id="file-upload-state-(type=file):the-input-element-5"><a href=#the-input-element>input</a></code> element, and finally
<a href=#fire-a-simple-event id="file-upload-state-(type=file):fire-a-simple-event-4">fire a simple event</a> that bubbles named <code id="file-upload-state-(type=file):event-input-change-2"><a href=#event-input-change>change</a></code> at the <code id="file-upload-state-(type=file):the-input-element-6"><a href=#the-input-element>input</a></code> element.</p>
- <p>If the element is not <i id="file-upload-state-(type=file):concept-fe-mutable-3"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="file-upload-state-(type=file):activation-behavior-2">activation
- behavior</a> and the user agent must not allow the user to change the element's selection.</p>
+ <p>If the element is not <i id="file-upload-state-(type=file):concept-fe-mutable-3"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="file-upload-state-(type=file):activation-behaviour-2">activation
+ behaviour</a> and the user agent must not allow the user to change the element's selection.</p>
<p><strong>Constraint validation</strong>: If the element is <i id="file-upload-state-(type=file):concept-input-required"><a href=#concept-input-required>required</a></i> and the list of <a href=#concept-input-type-file-selected id="file-upload-state-(type=file):concept-input-type-file-selected-4">selected files</a> is empty, then the element is
<a href=#suffering-from-being-missing id="file-upload-state-(type=file):suffering-from-being-missing">suffering from being missing</a>.</p>
@@ -36039,13 +36039,13 @@
<p>If the element is <i id="submit-button-state-(type=submit):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, then the element's
- <a href=#activation-behavior id="submit-button-state-(type=submit):activation-behavior">activation behavior</a> is as follows: if the element has a <a href=#form-owner id="submit-button-state-(type=submit):form-owner">form owner</a>,
+ <a href=#activation-behaviour id="submit-button-state-(type=submit):activation-behaviour">activation behaviour</a> is as follows: if the element has a <a href=#form-owner id="submit-button-state-(type=submit):form-owner">form owner</a>,
and the element's <a id="submit-button-state-(type=submit):node-document" href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is <a href=#fully-active id="submit-button-state-(type=submit):fully-active">fully active</a>,
<a href=#concept-form-submit id="submit-button-state-(type=submit):concept-form-submit">submit</a> the <a href=#form-owner id="submit-button-state-(type=submit):form-owner-2">form owner</a> from the
<code id="submit-button-state-(type=submit):the-input-element-3"><a href=#the-input-element>input</a></code> element; otherwise, do nothing.</p>
- <p>If the element is not <i id="submit-button-state-(type=submit):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="submit-button-state-(type=submit):activation-behavior-2">activation
- behavior</a>.</p>
+ <p>If the element is not <i id="submit-button-state-(type=submit):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="submit-button-state-(type=submit):activation-behaviour-2">activation
+ behaviour</a>.</p>
@@ -36200,14 +36200,14 @@
<p>If the <code id="image-button-state-(type=image):attr-input-src-7"><a href=#attr-input-src>src</a></code> attribute is set, and the image is <i id="image-button-state-(type=image):input-img-available-2"><a href=#input-img-available>available</a></i> and the user agent is configured to display that image,
then: The element <a href=#represents id="image-button-state-(type=image):represents-2">represents</a> a control for selecting a <a href=#concept-input-type-image-coordinate id="image-button-state-(type=image):concept-input-type-image-coordinate">coordinate</a> from the image specified by the
- <code id="image-button-state-(type=image):attr-input-src-8"><a href=#attr-input-src>src</a></code> attribute; if the element is <i id="image-button-state-(type=image):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, the user agent should allow the user to select this <a href=#concept-input-type-image-coordinate id="image-button-state-(type=image):concept-input-type-image-coordinate-2">coordinate</a>, and the element's <a href=#activation-behavior id="image-button-state-(type=image):activation-behavior">activation
- behavior</a> is as follows: if the element has a <a href=#form-owner id="image-button-state-(type=image):form-owner">form owner</a>, and the element's
+ <code id="image-button-state-(type=image):attr-input-src-8"><a href=#attr-input-src>src</a></code> attribute; if the element is <i id="image-button-state-(type=image):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, the user agent should allow the user to select this <a href=#concept-input-type-image-coordinate id="image-button-state-(type=image):concept-input-type-image-coordinate-2">coordinate</a>, and the element's <a href=#activation-behaviour id="image-button-state-(type=image):activation-behaviour">activation
+ behaviour</a> is as follows: if the element has a <a href=#form-owner id="image-button-state-(type=image):form-owner">form owner</a>, and the element's
<a id="image-button-state-(type=image):node-document-2" href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is <a href=#fully-active id="image-button-state-(type=image):fully-active">fully active</a>, take the user's selected <a href=#concept-input-type-image-coordinate id="image-button-state-(type=image):concept-input-type-image-coordinate-3">coordinate</a>, and <a href=#concept-form-submit id="image-button-state-(type=image):concept-form-submit">submit</a> the <code id="image-button-state-(type=image):the-input-element-10"><a href=#the-input-element>input</a></code> element's <a href=#form-owner id="image-button-state-(type=image):form-owner-2">form owner</a>
from the <code id="image-button-state-(type=image):the-input-element-11"><a href=#the-input-element>input</a></code> element. If the user activates the control without explicitly
selecting a coordinate, then the coordinate (0,0) must be assumed.</p>
<p>Otherwise, the element <a href=#represents id="image-button-state-(type=image):represents-3">represents</a> a submit button whose label is given by the
- value of the <code id="image-button-state-(type=image):attr-input-alt-2"><a href=#attr-input-alt>alt</a></code> attribute; if the element is <i id="image-button-state-(type=image):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, then the element's <a href=#activation-behavior id="image-button-state-(type=image):activation-behavior-2">activation behavior</a> is as
+ value of the <code id="image-button-state-(type=image):attr-input-alt-2"><a href=#attr-input-alt>alt</a></code> attribute; if the element is <i id="image-button-state-(type=image):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, then the element's <a href=#activation-behaviour id="image-button-state-(type=image):activation-behaviour-2">activation behaviour</a> is as
follows: if the element has a <a href=#form-owner id="image-button-state-(type=image):form-owner-3">form owner</a>, and the element's <a id="image-button-state-(type=image):node-document-3" href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is
<a href=#fully-active id="image-button-state-(type=image):fully-active-2">fully active</a>, set the <a href=#concept-input-type-image-coordinate id="image-button-state-(type=image):concept-input-type-image-coordinate-4">selected
coordinate</a> to (0,0), and <a href=#concept-form-submit id="image-button-state-(type=image):concept-form-submit-2">submit</a> the
@@ -36215,7 +36215,7 @@
<p>In either case, if the element is <i id="image-button-state-(type=image):concept-fe-mutable-3"><a href=#concept-fe-mutable>mutable</a></i> but has no
<a href=#form-owner id="image-button-state-(type=image):form-owner-5">form owner</a> or the element's <a id="image-button-state-(type=image):node-document-4" href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is not <a href=#fully-active id="image-button-state-(type=image):fully-active-3">fully active</a>,
- then its <a href=#activation-behavior id="image-button-state-(type=image):activation-behavior-3">activation behavior</a> must be to do nothing. If the element is not <i id="image-button-state-(type=image):concept-fe-mutable-4"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="image-button-state-(type=image):activation-behavior-4">activation behavior</a>.</p>
+ then its <a href=#activation-behaviour id="image-button-state-(type=image):activation-behaviour-3">activation behaviour</a> must be to do nothing. If the element is not <i id="image-button-state-(type=image):concept-fe-mutable-4"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="image-button-state-(type=image):activation-behaviour-4">activation behaviour</a>.</p>
<p>The <dfn id=concept-input-type-image-coordinate>selected coordinate</dfn> must consist of
an <var>x</var>-component and a <var>y</var>-component. The coordinates
@@ -36313,7 +36313,7 @@
</div>
- <p class=note>Many aspects of this state's behavior are similar to the behavior of the
+ <p class=note>Many aspects of this state's behaviour are similar to the behaviour of the
<code id="image-button-state-(type=image):the-img-element"><a href=#the-img-element>img</a></code> element. Readers are encouraged to read that section, where many of the same
requirements are described in more detail.</p>
@@ -36361,12 +36361,12 @@
<p>If the element is <i id="reset-button-state-(type=reset):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, then the element's
- <a href=#activation-behavior id="reset-button-state-(type=reset):activation-behavior">activation behavior</a>, if the element has a <a href=#form-owner id="reset-button-state-(type=reset):form-owner">form owner</a> and the element's
+ <a href=#activation-behaviour id="reset-button-state-(type=reset):activation-behaviour">activation behaviour</a>, if the element has a <a href=#form-owner id="reset-button-state-(type=reset):form-owner">form owner</a> and the element's
<a id="reset-button-state-(type=reset):node-document" href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is <a href=#fully-active id="reset-button-state-(type=reset):fully-active">fully active</a>, is to <a href=#concept-form-reset id="reset-button-state-(type=reset):concept-form-reset">reset</a> the <a href=#form-owner id="reset-button-state-(type=reset):form-owner-2">form owner</a>; otherwise, it is to do
nothing.</p>
- <p>If the element is not <i id="reset-button-state-(type=reset):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="reset-button-state-(type=reset):activation-behavior-2">activation
- behavior</a>.</p>
+ <p>If the element is not <i id="reset-button-state-(type=reset):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="reset-button-state-(type=reset):activation-behaviour-2">activation
+ behaviour</a>.</p>
<p><strong>Constraint validation</strong>: The element is <a href=#barred-from-constraint-validation id="reset-button-state-(type=reset):barred-from-constraint-validation">barred from constraint
validation</a>.</p>
@@ -36437,18 +36437,18 @@
- <p>The <code id="button-state-(type=button):the-input-element-2"><a href=#the-input-element>input</a></code> element <a href=#represents id="button-state-(type=button):represents">represents</a> a button with no default behavior. A
+ <p>The <code id="button-state-(type=button):the-input-element-2"><a href=#the-input-element>input</a></code> element <a href=#represents id="button-state-(type=button):represents">represents</a> a button with no default behaviour. A
label for the button must be provided in the <code id="button-state-(type=button):attr-input-value"><a href=#attr-input-value>value</a></code>
attribute, though it may be the empty string. If the element has a <code id="button-state-(type=button):attr-input-value-2"><a href=#attr-input-value>value</a></code> attribute, the button's label must be the value of that
attribute; otherwise, it must be the empty string. The element is a <a href=#concept-button id="button-state-(type=button):concept-button">button</a>.</p>
- <p>If the element is <i id="button-state-(type=button):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, the element's <a href=#activation-behavior id="button-state-(type=button):activation-behavior">activation
- behavior</a> is to do nothing.</p>
+ <p>If the element is <i id="button-state-(type=button):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, the element's <a href=#activation-behaviour id="button-state-(type=button):activation-behaviour">activation
+ behaviour</a> is to do nothing.</p>
- <p>If the element is not <i id="button-state-(type=button):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="button-state-(type=button):activation-behavior-2">activation
- behavior</a>.</p>
+ <p>If the element is not <i id="button-state-(type=button):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="button-state-(type=button):activation-behaviour-2">activation
+ behaviour</a>.</p>
<p><strong>Constraint validation</strong>: The element is <a href=#barred-from-constraint-validation id="button-state-(type=button):barred-from-constraint-validation">barred from constraint
validation</a>.</p>
@@ -37119,7 +37119,7 @@
is the selected suggestion's <a href=#concept-option-value id=the-list-attribute:concept-option-value-3>value</a>, or change an
existing entry in the <code id=the-list-attribute:the-input-element-4><a href=#the-input-element>input</a></code> element's <a href=#concept-fe-values id=the-list-attribute:concept-fe-values-4>values</a> to have the value given by the selected
suggestion's <a href=#concept-option-value id=the-list-attribute:concept-option-value-4>value</a>, as if the user had himself added
- an entry with that value, or edited an existing entry to be that value. Which behavior is to be
+ an entry with that value, or edited an existing entry to be that value. Which behaviour is to be
applied depends on the user interface in a user-agent-defined manner.</p>
</dl>
@@ -37339,7 +37339,7 @@
<p>The <dfn id=dom-input-value><code>value</code></dfn> IDL attribute allows scripts to
manipulate the <a href=#concept-fe-value id=common-input-element-apis:concept-fe-value-6>value</a> of an <code id=common-input-element-apis:the-input-element-2><a href=#the-input-element>input</a></code> element. The
- attribute is in one of the following modes, which define its behavior:</p>
+ attribute is in one of the following modes, which define its behaviour:</p>
<dl><dt><dfn id=dom-input-value-value>value</dfn>
@@ -37534,7 +37534,7 @@
- <h5 id=common-input-element-events>4.10.5.5 Common event behaviors</h5>
+ <h5 id=common-input-element-events>4.10.5.5 Common event behaviours</h5>
<p>When the <code id=common-input-element-events:event-input-input><a href=#event-input-input>input</a></code> and <code id=common-input-element-events:event-input-change><a href=#event-input-change>change</a></code> events <a href=#concept-input-apply id=common-input-element-events:concept-input-apply>apply</a>
(which is the case for all <code id=common-input-element-events:the-input-element><a href=#the-input-element>input</a></code> controls other than <a href=#concept-button id=common-input-element-events:concept-button>buttons</a> and those with the <code id=common-input-element-events:attr-input-type><a href=#attr-input-type>type</a></code> attribute in the <a href="#hidden-state-(type=hidden)" id="common-input-element-events:hidden-state-(type=hidden)">Hidden</a> state), the events are fired to indicate that the
@@ -37542,12 +37542,12 @@
event fires whenever the user has modified the data of the control. The <dfn id=event-input-change><code>change</code></dfn> event fires when the value is committed, if
that makes sense for the control, or else when the control <a href=#unfocus-causes-change-event>loses focus</a>. In all cases, the <code id=common-input-element-events:event-input-input-2><a href=#event-input-input>input</a></code> event comes before the corresponding <code id=common-input-element-events:event-input-change-2><a href=#event-input-change>change</a></code> event (if any).</p>
- <p>When an <code id=common-input-element-events:the-input-element-2><a href=#the-input-element>input</a></code> element has a defined <a href=#activation-behavior id=common-input-element-events:activation-behavior>activation behavior</a>, the rules
+ <p>When an <code id=common-input-element-events:the-input-element-2><a href=#the-input-element>input</a></code> element has a defined <a href=#activation-behaviour id=common-input-element-events:activation-behaviour>activation behaviour</a>, the rules
for dispatching these events, if they <a href=#concept-input-apply id=common-input-element-events:concept-input-apply-2>apply</a>, are given
in the section above that defines the <code id=common-input-element-events:attr-input-type-2><a href=#attr-input-type>type</a></code> attribute's
state. (This is the case for all <code id=common-input-element-events:the-input-element-3><a href=#the-input-element>input</a></code> controls with the <code id=common-input-element-events:attr-input-type-3><a href=#attr-input-type>type</a></code> attribute in the <a href="#checkbox-state-(type=checkbox)" id="common-input-element-events:checkbox-state-(type=checkbox)">Checkbox</a> state, the <a href="#radio-button-state-(type=radio)" id="common-input-element-events:radio-button-state-(type=radio)">Radio Button</a> state, or the <a href="#file-upload-state-(type=file)" id="common-input-element-events:file-upload-state-(type=file)">File Upload</a> state.)</p>
- <p>For <code id=common-input-element-events:the-input-element-4><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behavior id=common-input-element-events:activation-behavior-2>activation behavior</a>, but to
+ <p>For <code id=common-input-element-events:the-input-element-4><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behaviour id=common-input-element-events:activation-behaviour-2>activation behaviour</a>, but to
which these events <a href=#concept-input-apply id=common-input-element-events:concept-input-apply-3>apply</a>, and for which the user
interface involves both interactive manipulation and an explicit commit action, then when the user
changes the element's <a href=#concept-fe-value id=common-input-element-events:concept-fe-value>value</a>, the user agent must
@@ -37563,7 +37563,7 @@
whereas the <code id=common-input-element-events:event-input-change-4><a href=#event-input-change>change</a></code> event would only fire when the user
let go of the knob, committing to a specific value.</p>
- <p>For <code id=common-input-element-events:the-input-element-7><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behavior id=common-input-element-events:activation-behavior-3>activation behavior</a>, but to
+ <p>For <code id=common-input-element-events:the-input-element-7><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behaviour id=common-input-element-events:activation-behaviour-3>activation behaviour</a>, but to
which these events <a href=#concept-input-apply id=common-input-element-events:concept-input-apply-4>apply</a>, and for which the user
interface involves an explicit commit action but no intermediate manipulation, then any time the
user commits a change to the element's <a href=#concept-fe-value id=common-input-element-events:concept-fe-value-2>value</a>, the user
@@ -37581,7 +37581,7 @@
selecting a date from the drop down calendar and then dismissing the drop down would be a commit
action.</p>
- <p>For <code id=common-input-element-events:the-input-element-10><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behavior id=common-input-element-events:activation-behavior-4>activation behavior</a>, but to
+ <p>For <code id=common-input-element-events:the-input-element-10><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behaviour id=common-input-element-events:activation-behaviour-4>activation behaviour</a>, but to
which these events <a href=#concept-input-apply id=common-input-element-events:concept-input-apply-5>apply</a>, any time the user causes the
element's <a href=#concept-fe-value id=common-input-element-events:concept-fe-value-4>value</a> to change without an explicit commit
action, the user agent must <a href=#queue-a-task id=common-input-element-events:queue-a-task-4>queue a task</a> to <a href=#fire-a-simple-event id=common-input-element-events:fire-a-simple-event-5>fire a simple event</a> that
@@ -37653,7 +37653,7 @@
<p>The element is a <a href=#concept-button id=the-button-element:concept-button>button</a>.</p>
- <p>The <dfn id=attr-button-type><code>type</code></dfn> attribute controls the behavior of
+ <p>The <dfn id=attr-button-type><code>type</code></dfn> attribute controls the behaviour of
the button when it is activated. It is an <a href=#enumerated-attribute id=the-button-element:enumerated-attribute>enumerated attribute</a>. The following table
lists the keywords and states for the attribute — the keywords in the left column map to the
states in the cell in the second column on the same row as the keyword.</p>
@@ -37689,7 +37689,7 @@
validation</a>.</p>
<p>When a <code id=the-button-element:the-button-element-2><a href=#the-button-element>button</a></code> element is not <a href=#concept-fe-disabled id=the-button-element:concept-fe-disabled>disabled</a>,
- its <a href=#activation-behavior id=the-button-element:activation-behavior>activation behavior</a> element is to run the steps defined in the following list for
+ its <a href=#activation-behaviour id=the-button-element:activation-behaviour>activation behaviour</a> element is to run the steps defined in the following list for
the current state of the element's <code id=the-button-element:attr-button-type-4><a href=#attr-button-type>type</a></code> attribute:</p>
<dl><dt> <dfn id=attr-button-type-submit-state>Submit Button</dfn> <dd><p>If the element has a <a href=#form-owner id=the-button-element:form-owner>form owner</a> and the element's <a id=the-button-element:node-document href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is
@@ -37948,7 +37948,7 @@
The <code id=the-select-element:attr-fe-name-2><a href=#attr-fe-name>name</a></code> attribute represents the element's name.
The <code id=the-select-element:attr-fe-disabled-2><a href=#attr-fe-disabled>disabled</a></code> attribute is used to make the control non-interactive and to prevent its value from being submitted.
The <code id=the-select-element:attr-fe-autofocus-2><a href=#attr-fe-autofocus>autofocus</a></code> attribute controls focus.
- The <code id=the-select-element:attr-fe-autocomplete-2><a href=#attr-fe-autocomplete>autocomplete</a></code> attribute controls how the user agent provides autofill behavior.
+ The <code id=the-select-element:attr-fe-autocomplete-2><a href=#attr-fe-autocomplete>autocomplete</a></code> attribute controls how the user agent provides autofill behaviour.
</p>
<p>A <code id=the-select-element:the-select-element-26><a href=#the-select-element>select</a></code> element that is not <a href=#concept-fe-disabled id=the-select-element:concept-fe-disabled-3>disabled</a> is
@@ -38509,7 +38509,7 @@
<p>On setting, the <code id=the-option-element:dom-option-text-5><a href=#dom-option-text>text</a></code> attribute must act as if the
<code id=the-option-element:textcontent-2><a href=#textcontent>textContent</a></code> IDL attribute on the element had been set to the new value.</p>
- <p>The <dfn id=dom-option-form><code>form</code></dfn> IDL attribute's behavior depends on
+ <p>The <dfn id=dom-option-form><code>form</code></dfn> IDL attribute's behaviour depends on
whether the <code id=the-option-element:the-option-element-22><a href=#the-option-element>option</a></code> element is in a <code id=the-option-element:the-select-element-8><a href=#the-select-element>select</a></code> element or not. If the
<code id=the-option-element:the-option-element-23><a href=#the-option-element>option</a></code> has a <code id=the-option-element:the-select-element-9><a href=#the-select-element>select</a></code> element as its parent, or has an
<code id=the-option-element:the-optgroup-element-4><a href=#the-optgroup-element>optgroup</a></code> element as its parent and that <code id=the-option-element:the-optgroup-element-5><a href=#the-optgroup-element>optgroup</a></code> element has a
@@ -38804,7 +38804,7 @@
The <code id=the-textarea-element:attr-fe-inputmode-2><a href=#attr-fe-inputmode>inputmode</a></code> attribute controls the user interface's input
modality for the control.
The <code id=the-textarea-element:attr-fe-autocomplete-2><a href=#attr-fe-autocomplete>autocomplete</a></code> attribute controls how the user agent
- provides autofill behavior.
+ provides autofill behaviour.
</p>
@@ -39865,7 +39865,7 @@
- <p>The <dfn id=dom-legend-form><code>form</code></dfn> IDL attribute's behavior depends on
+ <p>The <dfn id=dom-legend-form><code>form</code></dfn> IDL attribute's behaviour depends on
whether the <code id=the-legend-element:the-legend-element-3><a href=#the-legend-element>legend</a></code> element is in a <code id=the-legend-element:the-fieldset-element-3><a href=#the-fieldset-element>fieldset</a></code> element or not. If the
<code id=the-legend-element:the-legend-element-4><a href=#the-legend-element>legend</a></code> has a <code id=the-legend-element:the-fieldset-element-4><a href=#the-fieldset-element>fieldset</a></code> element as its parent, then the <code id=the-legend-element:dom-legend-form-3><a href=#dom-legend-form>form</a></code> IDL attribute must return the same value as the <code id=the-legend-element:dom-fae-form><a href=#dom-fae-form>form</a></code> IDL attribute on that <code id=the-legend-element:the-fieldset-element-5><a href=#the-fieldset-element>fieldset</a></code> element. Otherwise,
it must return null.</p>
@@ -42566,12 +42566,12 @@
<p>If the user agent supports letting the user submit a form implicitly (for example, on some
platforms hitting the "enter" key while a text field is <a href=#focused id=implicit-submission:focused>focused</a> implicitly submits the form), then
- doing so for a form whose <a href=#default-button id=implicit-submission:default-button>default button</a> has a defined <a href=#activation-behavior id=implicit-submission:activation-behavior>activation
- behavior</a> must cause the user agent to <a href=#run-synthetic-click-activation-steps id=implicit-submission:run-synthetic-click-activation-steps>run synthetic click activation steps</a> on
+ doing so for a form whose <a href=#default-button id=implicit-submission:default-button>default button</a> has a defined <a href=#activation-behaviour id=implicit-submission:activation-behaviour>activation
+ behaviour</a> must cause the user agent to <a href=#run-synthetic-click-activation-steps id=implicit-submission:run-synthetic-click-activation-steps>run synthetic click activation steps</a> on
that <a href=#default-button id=implicit-submission:default-button-2>default button</a>.</p>
<p class=note>Consequently, if the <a href=#default-button id=implicit-submission:default-button-3>default button</a> is <a href=#concept-fe-disabled id=implicit-submission:concept-fe-disabled>disabled</a>, the form is not submitted when such an implicit
- submission mechanism is used. (A button has no <a href=#activation-behavior id=implicit-submission:activation-behavior-2>activation behavior</a> when
+ submission mechanism is used. (A button has no <a href=#activation-behaviour id=implicit-submission:activation-behaviour-2>activation behaviour</a> when
disabled.)</p>
<p class=note>There are pages on the Web that are only usable if there is a way to implicitly
@@ -42677,7 +42677,7 @@
<td> <a href=#submit-mailto-body id=form-submission-algorithm:submit-mailto-body>Mail as body</a>
</table>
- <p>If <var>scheme</var> is not one of those listed in this table, then the behavior is
+ <p>If <var>scheme</var> is not one of those listed in this table, then the behaviour is
not defined by this specification. User agents should, in the absence of another specification
defining this, act in a manner analogous to that defined in this specification for similar
schemes.</p>
@@ -42713,7 +42713,7 @@
</ol>
- <p>The behaviors are as follows:</p>
+ <p>The behaviours are as follows:</p>
<dl><dt><dfn id=submit-mutate-action>Mutate action URL</dfn>
<dd>
@@ -43709,7 +43709,7 @@
<hr>
<p>If the element's <a href=#command-facet-disabledstate id=the-menuitem-element:command-facet-disabledstate>Disabled State</a> is false
- (enabled) then the element's <a href=#activation-behavior id=the-menuitem-element:activation-behavior>activation behavior</a> depends on the element's <code id=the-menuitem-element:attr-menuitem-type-7><a href=#attr-menuitem-type>type</a></code> and <code id=the-menuitem-element:attr-menuitem-command-7><a href=#attr-menuitem-command>command</a></code>
+ (enabled) then the element's <a href=#activation-behaviour id=the-menuitem-element:activation-behaviour>activation behaviour</a> depends on the element's <code id=the-menuitem-element:attr-menuitem-type-7><a href=#attr-menuitem-type>type</a></code> and <code id=the-menuitem-element:attr-menuitem-command-7><a href=#attr-menuitem-command>command</a></code>
attributes, as follows:</p>
<dl class=switch><dt>If the element has a <a href=#master-command id=the-menuitem-element:master-command-3>master command</a> set by its <code id=the-menuitem-element:attr-menuitem-command-8><a href=#attr-menuitem-command>command</a></code> attribute<dd><p>The user agent must <a href=#run-synthetic-click-activation-steps id=the-menuitem-element:run-synthetic-click-activation-steps>run synthetic click activation steps</a> on the element's
@@ -43720,7 +43720,7 @@
attributes as if they were the empty string), and has a <code id=the-menuitem-element:attr-menuitem-checked-6><a href=#attr-menuitem-checked>checked</a></code> attribute, must remove that attribute.</p>
<p>Then, the element's <code id=the-menuitem-element:attr-menuitem-checked-7><a href=#attr-menuitem-checked>checked</a></code> attribute must be set
- to the literal value "<code>checked</code>".<dt>Otherwise<dd><p>The element's <a href=#activation-behavior id=the-menuitem-element:activation-behavior-2>activation behavior</a> is to do nothing.</dl>
+ to the literal value "<code>checked</code>".<dt>Otherwise<dd><p>The element's <a href=#activation-behaviour id=the-menuitem-element:activation-behaviour-2>activation behaviour</a> is to do nothing.</dl>
<p class=note>Firing a synthetic <code id=the-menuitem-element:event-click><a href=#event-click>click</a></code> event at the element
does not cause any of the actions described above to happen.</p>
@@ -43728,7 +43728,7 @@
<p>If the element's <a href=#command-facet-disabledstate id=the-menuitem-element:command-facet-disabledstate-2>Disabled State</a> is true
- (disabled) then the element has no <a href=#activation-behavior id=the-menuitem-element:activation-behavior-3>activation behavior</a>.</p>
+ (disabled) then the element has no <a href=#activation-behaviour id=the-menuitem-element:activation-behaviour-3>activation behaviour</a>.</p>
@@ -44080,7 +44080,7 @@
false. (The command is never checked.)</p>
<p>The <a href=#command-facet-action id=using-the-a-element-to-define-a-command:command-facet-action>Action</a> of the command, if the element has a
- defined <a href=#activation-behavior id=using-the-a-element-to-define-a-command:activation-behavior>activation behavior</a>, is to <a href=#run-synthetic-click-activation-steps id=using-the-a-element-to-define-a-command:run-synthetic-click-activation-steps>run synthetic click activation steps</a>
+ defined <a href=#activation-behaviour id=using-the-a-element-to-define-a-command:activation-behaviour>activation behaviour</a>, is to <a href=#run-synthetic-click-activation-steps id=using-the-a-element-to-define-a-command:run-synthetic-click-activation-steps>run synthetic click activation steps</a>
on the element. Otherwise, it is just to <a href=#fire-a-click-event id=using-the-a-element-to-define-a-command:fire-a-click-event>fire a <code>click</code>
event</a> at the element.</p>
@@ -44147,7 +44147,7 @@
is <a href=#concept-fe-checked id=using-the-input-element-to-define-a-command:concept-fe-checked>checked</a> attribute, and false otherwise.</p>
<p>The <a href=#command-facet-action id=using-the-input-element-to-define-a-command:command-facet-action>Action</a> of the command, if the element has a
- defined <a href=#activation-behavior id=using-the-input-element-to-define-a-command:activation-behavior>activation behavior</a>, is to <a href=#run-synthetic-click-activation-steps id=using-the-input-element-to-define-a-command:run-synthetic-click-activation-steps>run synthetic click activation steps</a>
+ defined <a href=#activation-behaviour id=using-the-input-element-to-define-a-command:activation-behaviour>activation behaviour</a>, is to <a href=#run-synthetic-click-activation-steps id=using-the-input-element-to-define-a-command:run-synthetic-click-activation-steps>run synthetic click activation steps</a>
on the element. Otherwise, it is just to <a href=#fire-a-click-event id=using-the-input-element-to-define-a-command:fire-a-click-event>fire a <code>click</code>
event</a> at the element.</p>
@@ -44235,7 +44235,7 @@
false otherwise.</p>
<p>The <a href=#command-facet-action id=using-the-menuitem-element-to-define-a-command:command-facet-action>Action</a> of the command, if the element has a
- defined <a href=#activation-behavior id=using-the-menuitem-element-to-define-a-command:activation-behavior>activation behavior</a>, is to
+ defined <a href=#activation-behaviour id=using-the-menuitem-element-to-define-a-command:activation-behaviour>activation behaviour</a>, is to
<a href=#run-synthetic-click-activation-steps id=using-the-menuitem-element-to-define-a-command:run-synthetic-click-activation-steps>run synthetic click activation steps</a> on the element. Otherwise, it is just to
<a href=#fire-a-click-event id=using-the-menuitem-element-to-define-a-command:fire-a-click-event>fire a <code>click</code> event</a> at the element.</p>
@@ -44378,8 +44378,8 @@
<p>The <a href=#command-facet-action id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:command-facet-action>Action</a> of the command is to run the following
steps:</p>
- <ol><li>Run the <a href=#focusing-steps id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:focusing-steps>focusing steps</a> for the element.<li>If the element has a defined <a href=#activation-behavior id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:activation-behavior>activation behavior</a>, <a href=#run-synthetic-click-activation-steps id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:run-synthetic-click-activation-steps>run synthetic click
- activation steps</a> on the element.<li>Otherwise, if the element does not have a defined <a href=#activation-behavior id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:activation-behavior-2>activation behavior</a>,
+ <ol><li>Run the <a href=#focusing-steps id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:focusing-steps>focusing steps</a> for the element.<li>If the element has a defined <a href=#activation-behaviour id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:activation-behaviour>activation behaviour</a>, <a href=#run-synthetic-click-activation-steps id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:run-synthetic-click-activation-steps>run synthetic click
+ activation steps</a> on the element.<li>Otherwise, if the element does not have a defined <a href=#activation-behaviour id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:activation-behaviour-2>activation behaviour</a>,
<a href=#fire-a-click-event id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:fire-a-click-event>fire a <code>click</code> event</a> at the element.</ol>
@@ -44915,7 +44915,7 @@
and <a href=#scriptTagXML>in XML</a>, the rules for the <code id=the-script-element:dom-document-write><a href=#dom-document-write>document.write()</a></code> method, the handling of <a href=#scripting>scripting</a>, etc.</p>
<p>The <code id=the-script-element:attr-script-defer-4><a href=#attr-script-defer>defer</a></code> attribute may be specified even if the <code id=the-script-element:attr-script-async-5><a href=#attr-script-async>async</a></code> attribute is specified, to cause legacy Web browsers that
- only support <code id=the-script-element:attr-script-defer-5><a href=#attr-script-defer>defer</a></code> (and not <code id=the-script-element:attr-script-async-6><a href=#attr-script-async>async</a></code>) to fall back to the <code id=the-script-element:attr-script-defer-6><a href=#attr-script-defer>defer</a></code> behavior instead of the blocking behavior that
+ only support <code id=the-script-element:attr-script-defer-5><a href=#attr-script-defer>defer</a></code> (and not <code id=the-script-element:attr-script-async-6><a href=#attr-script-async>async</a></code>) to fall back to the <code id=the-script-element:attr-script-defer-6><a href=#attr-script-defer>defer</a></code> behaviour instead of the blocking behaviour that
is the default.</p>
<p>The <dfn id=attr-script-crossorigin><code>crossorigin</code></dfn> attribute is a
@@ -47745,7 +47745,7 @@
<p>The <dfn id=dom-context-2d-arcto><code>arcTo(<var>x1</var>, <var>y1</var>, <var>x2</var>, <var>y2</var>, <var>radiusX</var>,
<var>radiusY</var>, <var>rotation</var>)</code></dfn> method must first
- <a href=#ensure-there-is-a-subpath id=building-paths:ensure-there-is-a-subpath-4>ensure there is a subpath</a> for <span>(<var>x1</var>, <var>y1</var>)</span>. Then, the behavior depends on the arguments and the last point in the
+ <a href=#ensure-there-is-a-subpath id=building-paths:ensure-there-is-a-subpath-4>ensure there is a subpath</a> for <span>(<var>x1</var>, <var>y1</var>)</span>. Then, the behaviour depends on the arguments and the last point in the
subpath, as described below.</p>
<p>Negative values for <var>radiusX</var> or <var>radiusY</var> must cause the
@@ -48511,7 +48511,7 @@
<li><p>If <var>repetition</var> is not a <a href=#case-sensitive id=fill-and-stroke-styles:case-sensitive>case-sensitive</a> match for one of
"<code>repeat</code>", "<code>repeat-x</code>", "<code>repeat-y</code>", or "<code>no-repeat</code>", throw a <code id=fill-and-stroke-styles:syntaxerror-3><a href=#syntaxerror>SyntaxError</a></code>
exception and abort these steps.<li><p>Create a new <code id=fill-and-stroke-styles:canvaspattern-10><a href=#canvaspattern>CanvasPattern</a></code> object with the image <var>image</var>
- and the repetition behavior given by <var>repetition</var>.<li><p>If <a href=#the-image-argument-is-not-origin-clean id=fill-and-stroke-styles:the-image-argument-is-not-origin-clean>the <var>image argument</var> is not origin-clean</a>, then mark the
+ and the repetition behaviour given by <var>repetition</var>.<li><p>If <a href=#the-image-argument-is-not-origin-clean id=fill-and-stroke-styles:the-image-argument-is-not-origin-clean>the <var>image argument</var> is not origin-clean</a>, then mark the
<code id=fill-and-stroke-styles:canvaspattern-11><a href=#canvaspattern>CanvasPattern</a></code> object as <dfn id=concept-canvas-pattern-not-origin-clean>not
origin-clean</dfn>.<li><p>Return the <code id=fill-and-stroke-styles:canvaspattern-12><a href=#canvaspattern>CanvasPattern</a></code> object.</ol>
@@ -48534,9 +48534,9 @@
<p>Place a copy of the image on the bitmap, anchored such that its top left corner is at the
origin of the coordinate space, with one coordinate space unit per CSS pixel of the image, then
place repeated copies of this image horizontally to the left and right, if the repetition
- behavior is "<code>repeat-x</code>", or vertically up and down, if the repetition
- behavior is "<code>repeat-y</code>", or in all four directions all over the bitmap, if
- the repetition behavior is "<code>repeat</code>".</p>
+ behaviour is "<code>repeat-x</code>", or vertically up and down, if the repetition
+ behaviour is "<code>repeat-y</code>", or in all four directions all over the bitmap, if
+ the repetition behaviour is "<code>repeat</code>".</p>
<p>If the original image data is a bitmap image, the value painted at a point in the area of the
repetitions is computed by filtering the original image data. When scaling up, if the <code id=fill-and-stroke-styles:dom-context-2d-imagesmoothingenabled><a href=#dom-context-2d-imagesmoothingenabled>imageSmoothingEnabled</a></code> attribute is set to
@@ -48544,8 +48544,8 @@
may use any filtering algorithm (for example bilinear interpolation or nearest-neighbor). When
such a filtering algorithm requires a pixel value from outside the original image data, it must
instead use the value from wrapping the pixel's coordinates to the original image's dimensions.
- (That is, the filter uses 'repeat' behavior, regardless of the value of the pattern's repetition
- behavior.)</p>
+ (That is, the filter uses 'repeat' behaviour, regardless of the value of the pattern's repetition
+ behaviour.)</p>
<li><p>Transform the resulting bitmap according to the pattern's transformation matrix.<li><p>Transform the resulting bitmap again, this time according to the <a href=#transformations id=fill-and-stroke-styles:transformations-3>current transformation matrix</a>.<li><p>Replace any part of the image outside the area in which the pattern is to be rendered with
@@ -49155,7 +49155,7 @@
rectangle is computed by filtering the original image data. The user agent may use any filtering
algorithm (for example bilinear interpolation or nearest-neighbor). When the filtering algorithm
requires a pixel value from outside the original image data, it must instead use the value from
- the nearest edge pixel. (That is, the filter uses 'clamp-to-edge' behavior.) When the filtering
+ the nearest edge pixel. (That is, the filter uses 'clamp-to-edge' behaviour.) When the filtering
algorithm requires a pixel value from outside the source rectangle but inside the original image
data, then the value from the original image data must be used.</p>
@@ -51092,9 +51092,9 @@
<ul><li>
<p>An element falling into one of the following categories between the time the user begins to
- indicate an intent to trigger the element's <a href=#activation-behavior id=pseudo-classes:activation-behavior>activation behavior</a> and either the
- time the user stops indicating an intent to trigger the element's <a href=#activation-behavior id=pseudo-classes:activation-behavior-2>activation
- behavior</a>, or the time the element's <a href=#activation-behavior id=pseudo-classes:activation-behavior-3>activation behavior</a> has finished
+ indicate an intent to trigger the element's <a href=#activation-behaviour id=pseudo-classes:activation-behaviour>activation behaviour</a> and either the
+ time the user stops indicating an intent to trigger the element's <a href=#activation-behaviour id=pseudo-classes:activation-behaviour-2>activation
+ behaviour</a>, or the time the element's <a href=#activation-behaviour id=pseudo-classes:activation-behaviour-3>activation behaviour</a> has finished
running, which ever comes first:</p>
<ul><li><code id=pseudo-classes:the-a-element-2><a href=#the-a-element>a</a></code> elements that have an <code id=pseudo-classes:attr-hyperlink-href-3><a href=#attr-hyperlink-href>href</a></code>
@@ -52336,7 +52336,7 @@
which the attribute was invoked, while that element is an <a href=#concept-item id=microdata-dom-api:concept-item-4>item</a>,
and matches nothing the rest of the time.</p>
- <p>The <dfn id=dom-itemvalue><code>itemValue</code></dfn> IDL attribute's behavior depends on
+ <p>The <dfn id=dom-itemvalue><code>itemValue</code></dfn> IDL attribute's behaviour depends on
the element, as follows:</p>
<dl><dt>If the element has no <code id=microdata-dom-api:names:-the-itemprop-attribute-3><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute<dd><p>The attribute must return null on getting and must throw an
@@ -54154,16 +54154,16 @@
<h3 id=activation>6.3 Activation</h3>
- <p>Certain elements in HTML have an <a href=#activation-behavior id=activation:activation-behavior>activation behavior</a>, which means that the user
+ <p>Certain elements in HTML have an <a href=#activation-behaviour id=activation:activation-behaviour>activation behaviour</a>, which means that the user
can activate them. This triggers a sequence of events dependent on the activation mechanism, and
normally culminating in a <code id=activation:event-click><a href=#event-click>click</a></code> event, as
described below.</p>
- <p>The user agent should allow the user to manually trigger elements that have an <a href=#activation-behavior id=activation:activation-behavior-2>activation
- behavior</a>, for instance using keyboard or voice input, or through mouse clicks. When the
- user triggers an element with a defined <a href=#activation-behavior id=activation:activation-behavior-3>activation behavior</a> in a manner other than
+ <p>The user agent should allow the user to manually trigger elements that have an <a href=#activation-behaviour id=activation:activation-behaviour-2>activation
+ behaviour</a>, for instance using keyboard or voice input, or through mouse clicks. When the
+ user triggers an element with a defined <a href=#activation-behaviour id=activation:activation-behaviour-3>activation behaviour</a> in a manner other than
clicking it, the default action of the interaction event must be to <a href=#run-synthetic-click-activation-steps id=activation:run-synthetic-click-activation-steps>run synthetic click
activation steps</a> on the element.</p>
@@ -54210,14 +54210,14 @@
script. The <code id=activation:dom-click-2><a href=#dom-click>click()</a></code> method can be used to make the <a href=#run-synthetic-click-activation-steps id=activation:run-synthetic-click-activation-steps-3>run
synthetic click activation steps</a> algorithm happen programmatically.</p>
- <p class=note>Click-focusing behavior (e.g. the focusing of a text field when user clicks in
+ <p class=note>Click-focusing behaviour (e.g. the focusing of a text field when user clicks in
one) typically happens before the click, when the mouse button is first depressed, and is
therefore not discussed here.</p>
<p>Given an element <var>target</var>, the <dfn id=nearest-activatable-element>nearest activatable element</dfn> is the
element returned by the following algorithm:</p>
- <ol><li><p>If <var>target</var> has a defined <a href=#activation-behavior id=activation:activation-behavior-4>activation behavior</a>, then return
+ <ol><li><p>If <var>target</var> has a defined <a href=#activation-behaviour id=activation:activation-behaviour-4>activation behaviour</a>, then return
<var>target</var> and abort these steps.<li><p>If <var>target</var> has a parent element, then set <var>target</var> to
that parent element and return to the first step.<li><p>Otherwise, there is no <a href=#nearest-activatable-element id=activation:nearest-activatable-element-2>nearest activatable element</a>.</ol>
@@ -54228,7 +54228,7 @@
<dfn id=canceled-activation-steps>canceled activation steps</dfn> defined for that element, if any.</p>
<p>When a user agent is to <dfn id=run-post-click-activation-steps>run post-click activation steps</dfn> on an element, it must run
- the <dfn id=activation-behavior>activation behavior</dfn> defined for that element, if any. Activation behaviors can
+ the <dfn id=activation-behaviour>activation behaviour</dfn> defined for that element, if any. Activation behaviours can
refer to the <code id=activation:event-click-5><a href=#event-click>click</a></code> event that was fired by the steps above
leading up to this point.</p>
@@ -54618,7 +54618,7 @@
</dl>
<p>An element that has its <a href=#specially-focusable id=the-tabindex-attribute:specially-focusable-7>tabindex focus flag</a> set but does not otherwise have an
- <a href=#activation-behavior id=the-tabindex-attribute:activation-behavior>activation behavior</a> defined has an <a href=#activation-behavior id=the-tabindex-attribute:activation-behavior-2>activation behavior</a> that does
+ <a href=#activation-behaviour id=the-tabindex-attribute:activation-behaviour>activation behaviour</a> defined has an <a href=#activation-behaviour id=the-tabindex-attribute:activation-behaviour-2>activation behaviour</a> that does
nothing.</p>
<p class=note>This means that an element that is only focusable because of its <code id=the-tabindex-attribute:attr-tabindex-15><a href=#attr-tabindex>tabindex</a></code> attribute will fire a <code id=the-tabindex-attribute:event-click><a href=#event-click>click</a></code> event in response to a non-mouse activation (e.g. hitting the
@@ -54830,7 +54830,7 @@
<ol><li id=unfocus-causes-change-event><div class=status><input onclick=toggleStatus(this) value=⋰ type=button><p class=bugs><strong>Spec bugs:</strong> <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=27519" title="It is a bit unclear what "has changed the value" means if a user changes the value and then changes it back before the control loses focus. I believe the correct thing to do in those cases is to not fire the event.">27519</a></div><p>If <var>entry</var> is an <code id=processing-model-6:the-input-element-2><a href=#the-input-element>input</a></code>
element, and the <code id=processing-model-6:event-input-change><a href=#event-input-change>change</a></code> event <a href=#concept-input-apply id=processing-model-6:concept-input-apply>applies</a> to the element, and the element does not have a
- defined <a href=#activation-behavior id=processing-model-6:activation-behavior>activation behavior</a>, and the user has changed the element's <a href=#concept-fe-value id=processing-model-6:concept-fe-value>value</a> or its list of <a href=#concept-input-type-file-selected id=processing-model-6:concept-input-type-file-selected>selected files</a> while the control was focused
+ defined <a href=#activation-behaviour id=processing-model-6:activation-behaviour>activation behaviour</a>, and the user has changed the element's <a href=#concept-fe-value id=processing-model-6:concept-fe-value>value</a> or its list of <a href=#concept-input-type-file-selected id=processing-model-6:concept-input-type-file-selected>selected files</a> while the control was focused
without committing that change, then <a href=#fire-a-simple-event id=processing-model-6:fire-a-simple-event>fire a simple event</a> that bubbles named <code id=processing-model-6:event-change><a href=#event-change>change</a></code> at the element.</p>
<li>
@@ -55199,7 +55199,7 @@
<p class=note>Historically, the <code id=focus-management-apis:dom-window-blur-2><a href=#dom-window-blur>focus()</a></code> and <code id=focus-management-apis:dom-window-blur-3><a href=#dom-window-blur>blur()</a></code> methods actually affected the system-level focus of the
system widget (e.g. tab or window) that contained the <a href=#browsing-context id=focus-management-apis:browsing-context-5>browsing context</a>, but hostile
- sites widely abuse this behavior to the user's detriment.</p>
+ sites widely abuse this behaviour to the user's detriment.</p>
<p>The <dfn id=dom-focus><code>focus()</code></dfn> method on elements, when invoked, must
run the following algorithm:</p>
@@ -55568,8 +55568,8 @@
host</a> (e.g. using <code id=spelling-and-grammar-checking:attr-contenteditable><a href=#attr-contenteditable>contenteditable</a></code>).</p>
<p>For each element, user agents must establish a <dfn id=concept-spellcheck-default>default
- behavior</dfn>, either through defaults or through preferences expressed by the user. There are
- three possible default behaviors for each element:</p>
+ behaviour</dfn>, either through defaults or through preferences expressed by the user. There are
+ three possible default behaviours for each element:</p>
<dl><dt><dfn id=concept-spellcheck-default-true>true-by-default</dfn>
@@ -55581,8 +55581,8 @@
<dt><dfn id=concept-spellcheck-default-inherit>inherit-by-default</dfn>
- <dd>The element's default behavior is the same as its parent element's. Elements that have no
- parent element cannot have this as their default behavior.
+ <dd>The element's default behaviour is the same as its parent element's. Elements that have no
+ parent element cannot have this as their default behaviour.
</dl>
@@ -55597,7 +55597,7 @@
<p class=note>The <i>true</i> state indicates that the element is to have its spelling and
grammar checked. The <i>default</i> state indicates that the element is to act according to a
- default behavior, possibly based on the parent element's own <code id=spelling-and-grammar-checking:attr-spellcheck><a href=#attr-spellcheck>spellcheck</a></code> state, as defined below. The <i>false</i> state
+ default behaviour, possibly based on the parent element's own <code id=spelling-and-grammar-checking:attr-spellcheck><a href=#attr-spellcheck>spellcheck</a></code> state, as defined below. The <i>false</i> state
indicates that the element is not to be checked.</p>
@@ -55626,8 +55626,8 @@
<p>The <dfn id=dom-spellcheck><code>spellcheck</code></dfn> IDL attribute, on getting, must
return true if the element's <code id=spelling-and-grammar-checking:attr-spellcheck-3><a href=#attr-spellcheck>spellcheck</a></code> content attribute is
in the <i>true</i> state, or if the element's <code id=spelling-and-grammar-checking:attr-spellcheck-4><a href=#attr-spellcheck>spellcheck</a></code>
- content attribute is in the <i>default</i> state and the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default>default behavior</a> is <a href=#concept-spellcheck-default-true id=spelling-and-grammar-checking:concept-spellcheck-default-true>true-by-default</a>, or if the element's <code id=spelling-and-grammar-checking:attr-spellcheck-5><a href=#attr-spellcheck>spellcheck</a></code> content attribute is in the <i>default</i> state and the
- element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-2>default behavior</a> is <a href=#concept-spellcheck-default-inherit id=spelling-and-grammar-checking:concept-spellcheck-default-inherit>inherit-by-default</a> and the element's parent
+ content attribute is in the <i>default</i> state and the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default>default behaviour</a> is <a href=#concept-spellcheck-default-true id=spelling-and-grammar-checking:concept-spellcheck-default-true>true-by-default</a>, or if the element's <code id=spelling-and-grammar-checking:attr-spellcheck-5><a href=#attr-spellcheck>spellcheck</a></code> content attribute is in the <i>default</i> state and the
+ element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-2>default behaviour</a> is <a href=#concept-spellcheck-default-inherit id=spelling-and-grammar-checking:concept-spellcheck-default-inherit>inherit-by-default</a> and the element's parent
element's <code id=spelling-and-grammar-checking:dom-spellcheck-2><a href=#dom-spellcheck>spellcheck</a></code> IDL attribute would return true;
otherwise, if none of those conditions applies, then the attribute must instead return false.</p>
@@ -55663,9 +55663,9 @@
state, then checking is disabled.<li>Otherwise, if there is an ancestor element with a <code id=spelling-and-grammar-checking:attr-spellcheck-9><a href=#attr-spellcheck>spellcheck</a></code> content attribute that is not in the <i>default</i>
state, then: if the nearest such ancestor's <code id=spelling-and-grammar-checking:attr-spellcheck-10><a href=#attr-spellcheck>spellcheck</a></code>
content attribute is in the <i>true</i> state, then checking is enabled; otherwise, checking is
- disabled.<li>Otherwise, if the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-3>default behavior</a>
+ disabled.<li>Otherwise, if the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-3>default behaviour</a>
is <a href=#concept-spellcheck-default-true id=spelling-and-grammar-checking:concept-spellcheck-default-true-2>true-by-default</a>, then checking is
- enabled.<li>Otherwise, if the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-4>default behavior</a>
+ enabled.<li>Otherwise, if the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-4>default behaviour</a>
is <a href=#concept-spellcheck-default-false id=spelling-and-grammar-checking:concept-spellcheck-default-false>false-by-default</a>, then checking is
disabled.<li>Otherwise, if the element's parent element has <em>its</em> checking enabled, then checking
is enabled.<li>Otherwise, checking is disabled.</ol>
@@ -55685,7 +55685,7 @@
already present when the page was loaded, or that the user did not type, or text in controls that
the user has not focused, or in parts of e-mail addresses that the user agent is not confident
were misspelt). The <dfn id=dom-forcespellcheck><code>forceSpellCheck()</code></dfn> method,
- when invoked on an element, must override this behavior, forcing the user agent to consider all
+ when invoked on an element, must override this behaviour, forcing the user agent to consider all
spelling and grammar errors in text in that element for which checking is enabled to be of
interest to the user.</p>
@@ -56866,7 +56866,7 @@
<i id=the-draggable-attribute:missing-value-default><a href=#missing-value-default>missing value default</a></i>.</p>
<p>The <i>true</i> state means the element is draggable; the <i>false</i> state means that it is
- not. The <i>auto</i> state uses the default behavior of the user agent.</p>
+ not. The <i>auto</i> state uses the default behaviour of the user agent.</p>
<p>An element with a <code id=the-draggable-attribute:the-draggable-attribute-3><a href=#the-draggable-attribute>draggable</a></code> attribute should also have a
<code id=the-draggable-attribute:attr-title><a href=#attr-title>title</a></code> attribute that names the element for the purpose of
@@ -57607,7 +57607,7 @@
true:</p>
<ul><li><p>The <a href=#concept-task id=browsing-context-names:concept-task>task</a> in which the algorithm is running is currently
- processing an <a href=#activation-behavior id=browsing-context-names:activation-behavior>activation behavior</a> whose <code id=browsing-context-names:event-click><a href=#event-click>click</a></code> event
+ processing an <a href=#activation-behaviour id=browsing-context-names:activation-behaviour>activation behaviour</a> whose <code id=browsing-context-names:event-click><a href=#event-click>click</a></code> event
was <a href=#concept-events-trusted id=browsing-context-names:concept-events-trusted>trusted</a>.<li>
<p>The <a href=#concept-task id=browsing-context-names:concept-task-2>task</a> in which the algorithm is running is currently
@@ -57639,7 +57639,7 @@
the chosen browsing context must be the current one.</p>
<p>If the given browsing context name is <code>_self</code>, then this is an
- <a href=#explicit-self-navigation-override id=browsing-context-names:explicit-self-navigation-override>explicit self-navigation override</a>, which overrides the behavior of the
+ <a href=#explicit-self-navigation-override id=browsing-context-names:explicit-self-navigation-override>explicit self-navigation override</a>, which overrides the behaviour of the
<a href=#seamless-browsing-context-flag id=browsing-context-names:seamless-browsing-context-flag>seamless browsing context flag</a> set by the <code id=browsing-context-names:attr-iframe-seamless-2><a href=#attr-iframe-seamless>seamless</a></code> attribute on <code id=browsing-context-names:the-iframe-element-2><a href=#the-iframe-element>iframe</a></code> elements.</p>
<li><p>If the given browsing context name is <code>_parent</code>, then the chosen
@@ -58448,7 +58448,7 @@
location of an HTTP redirect (<a href=#concept-http-equivalent-codes id=origin:concept-http-equivalent-codes>or equivalent</a>
in other protocols), a <code id=origin:document-19><a href=#document>Document</a></code> created using the <code id=origin:dom-domimplementation-createdocument><a href=#dom-domimplementation-createdocument>createDocument()</a></code> API, etc)<dd>
- <p>The default behavior as defined in the DOM standard applies. <a href=#refsDOM>[DOM]</a>.</p>
+ <p>The default behaviour as defined in the DOM standard applies. <a href=#refsDOM>[DOM]</a>.</p>
<p class=note>The <a href=#origin-2 id=origin:origin-2-19>origin</a> is a globally unique identifier assigned when the
<code id=origin:document-20><a href=#document>Document</a></code> is created, and the <a href=#effective-script-origin id=origin:effective-script-origin-16>effective script origin</a> is initially an
@@ -59478,7 +59478,7 @@
<ul class=brief><li>The <code id=the-location-interface:location-10><a href=#location>Location</a></code> object's <i>relevant <code id=the-location-interface:document-13><a href=#document>Document</a></code></i> has
<a href=#completely-loaded id=the-location-interface:completely-loaded>completely loaded</a>, or<li>In the <a href=#concept-task id=the-location-interface:concept-task-2>task</a> in which the algorithm is running, an
- <a href=#activation-behavior id=the-location-interface:activation-behavior>activation behavior</a> is currently being processed whose <code id=the-location-interface:event-click><a href=#event-click>click</a></code> event was <a href=#concept-events-trusted id=the-location-interface:concept-events-trusted>trusted</a>, or<li>In the <a href=#concept-task id=the-location-interface:concept-task-3>task</a> in which the algorithm is running, the event
+ <a href=#activation-behaviour id=the-location-interface:activation-behaviour>activation behaviour</a> is currently being processed whose <code id=the-location-interface:event-click><a href=#event-click>click</a></code> event was <a href=#concept-events-trusted id=the-location-interface:concept-events-trusted>trusted</a>, or<li>In the <a href=#concept-task id=the-location-interface:concept-task-3>task</a> in which the algorithm is running, the event
listener for a <a href=#concept-events-trusted id=the-location-interface:concept-events-trusted-2>trusted</a> <code id=the-location-interface:event-click-2><a href=#event-click>click</a></code> event is being handled.</ul>
<li><p>If <var>mode</var> is <i>normal navigation</i>, then act as if the <code id=the-location-interface:dom-location-assign-5><a href=#dom-location-assign>assign()</a></code> method had been called with <var>value</var> as its argument. Otherwise, act as if the <code id=the-location-interface:dom-location-replace-5><a href=#dom-location-replace>replace()</a></code> method had been called with <var>value</var> as its argument.</ol>
@@ -64170,7 +64170,7 @@
<h3 id=dynamic-markup-insertion>8.3 <dfn>Dynamic markup insertion</dfn></h3>
<p class=note>APIs for dynamically inserting markup into the document interact with the parser,
- and thus their behavior varies depending on whether they are used with <a href=#html-documents id=dynamic-markup-insertion:html-documents>HTML documents</a>
+ and thus their behaviour varies depending on whether they are used with <a href=#html-documents id=dynamic-markup-insertion:html-documents>HTML documents</a>
(and the <a href=#html-parser id=dynamic-markup-insertion:html-parser>HTML parser</a>) or XHTML in <a href=#xml-documents id=dynamic-markup-insertion:xml-documents>XML documents</a> (and the <a href=#xml-parser id=dynamic-markup-insertion:xml-parser>XML
parser</a>).</p>
@@ -64372,12 +64372,12 @@
<p>In general, adds the given string(s) to the <code id=document.write():document><a href=#document>Document</a></code>'s input stream.</p>
- <p class=warning>This method has very idiosyncratic behavior. In some cases, this method can
+ <p class=warning>This method has very idiosyncratic behaviour. In some cases, this method can
affect the state of the <a href=#html-parser id=document.write():html-parser>HTML parser</a> while the parser is running, resulting in a DOM
that does not correspond to the source of the document (e.g. if the string written is the string
"<code><plaintext></code>" or "<code><!--</code>"). In other cases,
the call can clear the current page first, as if <code id=document.write():dom-document-open><a href=#dom-document-open>document.open()</a></code> had been called. In yet more cases, the method
- is simply ignored, or throws an exception. To make matters worse, the exact behavior of this
+ is simply ignored, or throws an exception. To make matters worse, the exact behaviour of this
method can in some cases be dependent on network latency, which can lead to failures that are very hard to debug. <strong>For all these reasons, use
of this method is strongly discouraged.</strong></p>
@@ -72555,7 +72555,7 @@
is rarely used, and frequently implemented incorrectly.</p>
<p class=note>This specification does not make any attempt to support EBCDIC-based encodings and
- UTF-32 in its algorithms; support and use of these encodings can thus lead to unexpected behavior
+ UTF-32 in its algorithms; support and use of these encodings can thus lead to unexpected behaviour
in implementations of this specification.</p>
@@ -72949,10 +72949,10 @@
which may have various side-effects, and either switches the state machine to a new state to
<i>reconsume</i> the same character, or switches it to a new state to consume the next character,
or stays in the same state to consume the next character. Some states have more complicated
- behavior and can consume several characters before switching to another state. In some cases, the
+ behaviour and can consume several characters before switching to another state. In some cases, the
tokenizer state is also changed by the tree construction stage.</p>
- <p>The exact behavior of certain states depends on the <a href=#insertion-mode id=tokenization:insertion-mode>insertion mode</a> and the
+ <p>The exact behaviour of certain states depends on the <a href=#insertion-mode id=tokenization:insertion-mode>insertion mode</a> and the
<a href=#stack-of-open-elements id=tokenization:stack-of-open-elements>stack of open elements</a>. Certain states also use a <dfn id=temporary-buffer><var>temporary buffer</var></dfn> to track progress.</p>
<p>The output of the tokenization step is a series of zero or more of the following tokens:
@@ -73831,7 +73831,7 @@
<p>This definition is used when parsing character references <a href=#character-reference-in-data-state id=tokenizing-character-references:character-reference-in-data-state>in text</a> and <a href=#character-reference-in-attribute-value-state id=tokenizing-character-references:character-reference-in-attribute-value-state>in
attributes</a>.</p>
- <p>The behavior depends on the identity of the next character (the one immediately after the
+ <p>The behaviour depends on the identity of the next character (the one immediately after the
U+0026 AMPERSAND character), as follows:</p>
<dl class=switch><dt>U+0009 CHARACTER TABULATION (tab)<dt>U+000A LINE FEED (LF)<dt>U+000C FORM FEED (FF)<dt>U+0020 SPACE<dt>U+003C LESS-THAN SIGN<dt>U+0026 AMPERSAND<dt>EOF<dt>The <a href=#additional-allowed-character id=tokenizing-character-references:additional-allowed-character>additional allowed character</a>, if there is one<dd>Not a character reference. No characters are consumed, and nothing is returned. (This is not
@@ -73839,7 +73839,7 @@
<p>Consume the U+0023 NUMBER SIGN.</p>
- <p>The behavior further depends on the character after the U+0023 NUMBER SIGN:</p>
+ <p>The behaviour further depends on the character after the U+0023 NUMBER SIGN:</p>
<dl class=switch><dt>U+0078 LATIN SMALL LETTER X<dt>U+0058 LATIN CAPITAL LETTER X<dd>
@@ -77819,7 +77819,7 @@
section provides a set of suggestions for rendering HTML documents that, if followed, are likely
to lead to a user experience that closely resembles the experience intended by the documents'
authors. So as to avoid confusion regarding the normativity of this section, RFC2119 terms have
- not been used. Instead, the term "expected" is used to indicate behavior that will lead to this
+ not been used. Instead, the term "expected" is used to indicate behaviour that will lead to this
experience. For the purposes of conformance for user agents designated as <a href=#renderingUA>supporting the suggested default rendering</a>, the term "expected" in this
section has the same conformance implications as the RFC2119-defined term "must".</i></p>
@@ -77828,7 +77828,7 @@
<p>In general, user agents are expected to support CSS, and many of the suggestions in this
section are expressed in CSS terms. User agents that use other presentation mechanisms can derive
- their expected behavior by translating from the CSS rules given in this section.</p>
+ their expected behaviour by translating from the CSS rules given in this section.</p>
<p>In the absence of style-layer rules to the contrary (e.g. author style sheets), user agents are
expected to render an element so that it conveys to the user the meaning that the element
@@ -80464,7 +80464,7 @@
<code>rev="made"</code>, use <code>rel="author"</code>.)<dt><dfn id=attr-a-urn><code>urn</code></dfn> on <code id=non-conforming-features:the-a-element-8><a href=#the-a-element>a</a></code> elements<dt><dfn id=attr-link-urn><code>urn</code></dfn> on <code id=non-conforming-features:the-link-element-4><a href=#the-link-element>link</a></code> elements<dd><p>Specify the preferred persistent identifier using the <code id=non-conforming-features:attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code> attribute instead.<dt><dfn id=attr-form-accept><code>accept</code></dfn> on <code id=non-conforming-features:the-form-element-2><a href=#the-form-element>form</a></code> elements<dd><p>Use the <code id=non-conforming-features:attr-input-accept><a href=#attr-input-accept>accept</a></code> attribute directly on the <code id=non-conforming-features:the-input-element><a href=#the-input-element>input</a></code> elements instead.<dt><dfn id=attr-area-nohref><code>nohref</code>
</dfn> on <code id=non-conforming-features:the-area-element-2><a href=#the-area-element>area</a></code> elements<dd><p>Omitting the <code id=non-conforming-features:attr-hyperlink-href-2><a href=#attr-hyperlink-href>href</a></code>
attribute is sufficient; the <code id=non-conforming-features:attr-area-nohref><a href=#attr-area-nohref>nohref</a></code> attribute is
unnecessary. Omit it altogether.<dt><dfn id=attr-head-profile><code>profile</code></dfn> on <code id=non-conforming-features:the-head-element><a href=#the-head-element>head</a></code> elements<dd><p>When used for declaring which <code id=non-conforming-features:the-meta-element><a href=#the-meta-element>meta</a></code> terms are
- used in the document, unnecessary; omit it altogether, and <a href=#concept-meta-extensions id=non-conforming-features:concept-meta-extensions>register the names</a>.<dd><p>When used for triggering specific user agent behaviors: use
+ used in the document, unnecessary; omit it altogether, and <a href=#concept-meta-extensions id=non-conforming-features:concept-meta-extensions>register the names</a>.<dd><p>When used for triggering specific user agent behaviours: use
a <code id=non-conforming-features:the-link-element-5><a href=#the-link-element>link</a></code> element instead.<dt><dfn id=attr-html-version><code>version</code></dfn> on <code id=non-conforming-features:the-html-element><a href=#the-html-element>html</a></code> elements<dd><p>Unnecessary. Omit it altogether.<dt><dfn id=attr-input-ismap><code>ismap</code></dfn> on <code id=non-conforming-features:the-input-element-2><a href=#the-input-element>input</a></code> elements<dd><p>Unnecessary. Omit it altogether. All <code id=non-conforming-features:the-input-element-3><a href=#the-input-element>input</a></code> elements with a <code id=non-conforming-features:attr-input-type><a href=#attr-input-type>type</a></code> attribute in the <a href="#image-button-state-(type=image)" id="non-conforming-features:image-button-state-(type=image)">Image
Button</a> state are processed as server-side image maps.<dt><dfn id=attr-input-usemap><code>usemap</code></dfn> on <code id=non-conforming-features:the-input-element-4><a href=#the-input-element>input</a></code> elements<dd><p>Use <code id=non-conforming-features:the-img-element-2><a href=#the-img-element>img</a></code> instead of <code id=non-conforming-features:the-input-element-5><a href=#the-input-element>input</a></code> for image maps.<dt><dfn id=attr-iframe-longdesc><code>longdesc</code></dfn> on <code id=non-conforming-features:the-iframe-element-2><a href=#the-iframe-element>iframe</a></code> elements<dt><dfn id=attr-img-longdesc><code>longdesc</code></dfn> on <code id=non-conforming-features:the-img-element-3><a href=#the-img-element>img</a></code> elements<dd><p>Use a regular <code id=non-conforming-features:the-a-element-9><a href=#the-a-element>a</a></code> element to link to the
description, or (in the case of images) use an <a href=#image-map id=non-conforming-features:image-map>image
@@ -81312,7 +81312,7 @@
<p>User agents must treat <code id=other-elements,-attributes-and-apis:plaintext><a href=#plaintext>plaintext</a></code> elements in a manner equivalent to
<code id=other-elements,-attributes-and-apis:the-pre-element-2><a href=#the-pre-element>pre</a></code> elements in terms of semantics and for purposes of rendering. (The parser has
- special behavior for this element, though.)</p>
+ special behaviour for this element, though.)</p>
<hr>
@@ -81471,7 +81471,7 @@
<hr>
<p>User agents must treat <code id=other-elements,-attributes-and-apis:xmp><a href=#xmp>xmp</a></code> elements in a manner equivalent to <code id=other-elements,-attributes-and-apis:the-pre-element-4><a href=#the-pre-element>pre</a></code>
- elements in terms of semantics and for purposes of rendering. (The parser has special behavior for
+ elements in terms of semantics and for purposes of rendering. (The parser has special behaviour for
this element though.)</p>
<hr>
@@ -81540,7 +81540,7 @@
elements.</p>
<p>The object returned for <code id=other-elements,-attributes-and-apis:dom-document-all-2><a href=#dom-document-all>all</a></code> has several unusual
- behaviors:</p>
+ behaviours:</p>
<ul><li><p>The user agent must act as if the ToBoolean() operator in JavaScript converts the object
returned for <code id=other-elements,-attributes-and-apis:dom-document-all-3><a href=#dom-document-all>all</a></code> to the false value.<li><p>The user agent must act as if, for the purposes of the <code>==</code> and <code>!=</code> operators in JavaScript, the object returned for <code id=other-elements,-attributes-and-apis:dom-document-all-4><a href=#dom-document-all>all</a></code> compares as equal to the <code>undefined</code> and
@@ -84588,7 +84588,7 @@
<tr><td> <code id=events-2:event-click><a href=#event-click>click</a></code>
<td> <code id=events-2:mouseevent><a href=#mouseevent>MouseEvent</a></code>
<td> Elements
- <td> Normally a mouse event; also synthetically fired at an element before its <a href=#activation-behavior id=events-2:activation-behavior>activation behavior</a> is run, when an element is activated from a non-pointer input device (e.g. a keyboard)
+ <td> Normally a mouse event; also synthetically fired at an element before its <a href=#activation-behaviour id=events-2:activation-behaviour>activation behaviour</a> is run, when an element is activated from a non-pointer input device (e.g. a keyboard)
<tr><td> <dfn id=event-close><code>close</code></dfn>
<td> <code id=events-2:event-12><a href=#event>Event</a></code>
Modified: index
===================================================================
--- index 2015-01-07 00:52:49 UTC (rev 8875)
+++ index 2015-01-07 01:02:44 UTC (rev 8876)
@@ -375,7 +375,7 @@
<h2 id=contents class="no-num no-toc">Full table of contents</h2>
<ol class=toc><li id=toc-introduction><a href=#introduction>1 Introduction</a><ol><li><a href=#abstract>1.1 Where does this specification fit?</a><li><a href=#is-this-html5?>1.2 Is this HTML5?</a><li><a href=#background>1.3 Background</a><li><a href=#audience>1.4 Audience</a><li><a href=#scope>1.5 Scope</a><li><a href=#history-2>1.6 History</a><li><a href=#design-notes>1.7 Design notes</a><ol><li><a href=#serialisability-of-script-execution>1.7.1 Serialisability of script execution</a><li><a href=#compliance-with-other-specifications>1.7.2 Compliance with other specifications</a><li><a href=#extensibility>1.7.3 Extensibility</a></ol><li><a href=#html-vs-xhtml>1.8 HTML vs XHTML</a><li><a href=#structure-of-this-specification>1.9 Structure of this specification</a><ol><li><a href=#how-to-read-this-specification>1.9.1 How to read this specification</a><li><a href=#typographic-conventions>1.9.2 Typographic conventions</a></ol><li><a href=#fingerprint>1.10 Privacy concerns</a><
ol><li><a href=#fingerprint-postMessage>1.10.1 Cross-site communication</a></ol><li><a href=#a-quick-introduction-to-html>1.11 A quick introduction to HTML</a><ol><li><a href=#writing-secure-applications-with-html>1.11.1 Writing secure applications with HTML</a><li><a href=#common-pitfalls-to-avoid-when-using-the-scripting-apis>1.11.2 Common pitfalls to avoid when using the scripting APIs</a><li><a href=#how-to-catch-mistakes-when-writing-html:-validators-and-conformance-checkers>1.11.3 How to catch mistakes when writing HTML: validators and conformance checkers</a></ol><li><a href=#conformance-requirements-for-authors>1.12 Conformance requirements for authors</a><ol><li><a href=#presentational-markup>1.12.1 Presentational markup</a><li><a href=#syntax-errors>1.12.2 Syntax errors</a><li><a href=#restrictions-on-content-models-and-on-attribute-values>1.12.3 Restrictions on content models and on attribute values</a></ol><li><a href=#suggested-reading>1.13 Suggested reading</a>
</ol><li id=toc-infrastructure><a href=#infrastructure>2 Common infrastructure</a><ol><li><a href=#terminology>2.1 Terminology</a><ol><li><a href=#resources>2.1.1 Resources</a><li><a href=#xml>2.1.2 XML</a><li><a href=#dom-trees>2.1.3 DOM trees</a><li><a href=#scripting-2>2.1.4 Scripting</a><li><a href=#plugins>2.1.5 Plugins</a><li><a href=#encoding-terminology>2.1.6 Character encodings</a></ol><li><a href=#conformance-requirements>2.2 Conformance requirements</a><ol><li><a href=#conformance-classes>2.2.1 Conformance classes</a><li><a href=#dependencies>2.2.2 Dependencies</a><li><a href=#extensibility-2>2.2.3 Extensibility</a><li><a href=#interactions-with-xpath-and-xslt>2.2.4 Interactions with XPath and XSLT</a></ol><li><a href=#case-sensitivity-and-string-comparison>2.3 Case-sensitivity and string comparison</a><li><a href=#common-microsyntaxes>2.4 Common microsyntaxes</a><ol><li><a href=#common-parser-idioms>2.4.1 Common parser idioms</a><li><a href=#boolean-attributes>2.
4.2 Boolean attributes</a><li><a href=#keywords-and-enumerated-attributes>2.4.3 Keywords and enumerated attributes</a><li><a href=#numbers>2.4.4 Numbers</a><ol><li><a href=#signed-integers>2.4.4.1 Signed integers</a><li><a href=#non-negative-integers>2.4.4.2 Non-negative integers</a><li><a href=#floating-point-numbers>2.4.4.3 Floating-point numbers</a><li><a href=#percentages-and-dimensions>2.4.4.4 Percentages and lengths</a><li><a href=#lists-of-integers>2.4.4.5 Lists of integers</a><li><a href=#lists-of-dimensions>2.4.4.6 Lists of dimensions</a></ol><li><a href=#dates-and-times>2.4.5 Dates and times</a><ol><li><a href=#months>2.4.5.1 Months</a><li><a href=#dates>2.4.5.2 Dates</a><li><a href=#yearless-dates>2.4.5.3 Yearless dates</a><li><a href=#times>2.4.5.4 Times</a><li><a href=#local-dates-and-times>2.4.5.5 Local dates and times</a><li><a href=#time-zones>2.4.5.6 Time zones</a><li><a href=#global-dates-and-times>2.4.5.7 Global dates and times</a><li><a href=#weeks>2.4.5.
8 Weeks</a><li><a href=#durations>2.4.5.9 Durations</a><li><a href=#vaguer-moments-in-time>2.4.5.10 Vaguer moments in time</a></ol><li><a href=#colours>2.4.6 Colours</a><li><a href=#space-separated-tokens>2.4.7 Space-separated tokens</a><li><a href=#comma-separated-tokens>2.4.8 Comma-separated tokens</a><li><a href=#syntax-references>2.4.9 References</a><li><a href=#mq>2.4.10 Media queries</a></ol><li><a href=#urls>2.5 URLs</a><ol><li><a href=#terminology-2>2.5.1 Terminology</a><li><a href=#resolving-urls>2.5.2 Resolving URLs</a><li><a href=#dynamic-changes-to-base-urls>2.5.3 Dynamic changes to base URLs</a></ol><li><a href=#fetching-resources>2.6 Fetching resources</a><ol><li><a href=#terminology-3>2.6.1 Terminology</a><li><a href=#processing-model>2.6.2 Processing model</a><li><a href=#encrypted-http-and-related-security-concerns>2.6.3 Encrypted HTTP and related security concerns</a><li><a href=#content-type-sniffing>2.6.4 Determining the type of a resource</a><li><a href=
#extracting-character-encodings-from-meta-elements>2.6.5 Extracting character encodings from <code>meta</code> elements</a><li><a href=#cors-settings-attributes>2.6.6 CORS settings attributes</a><li><a href=#cors-enabled-fetch>2.6.7 CORS-enabled fetch</a></ol><li><a href=#common-dom-interfaces>2.7 Common DOM interfaces</a><ol><li><a href=#reflecting-content-attributes-in-idl-attributes>2.7.1 Reflecting content attributes in IDL attributes</a><li><a href=#collections-2>2.7.2 Collections</a><ol><li><a href=#the-htmlallcollection-interface>2.7.2.1 The <code>HTMLAllCollection</code> interface</a><li><a href=#the-htmlformcontrolscollection-interface>2.7.2.2 The <code>HTMLFormControlsCollection</code> interface</a><li><a href=#the-htmloptionscollection-interface>2.7.2.3 The <code>HTMLOptionsCollection</code> interface</a><li><a href=#the-htmlpropertiescollection-interface>2.7.2.4 The <code>HTMLPropertiesCollection</code> interface</a></ol><li><a href=#the-domstringmap-interface>2.
7.3 The <code>DOMStringMap</code> interface</a><li><a href=#domelementmap>2.7.4 DOMElementMap</a><li><a href=#transferable-objects>2.7.5 Transferable objects</a><li><a href=#safe-passing-of-structured-data>2.7.6 Safe passing of structured data</a><li><a href=#callbacks>2.7.7 Callbacks</a><li><a href=#garbage-collection>2.7.8 Garbage collection</a></ol><li><a href=#namespaces>2.8 Namespaces</a></ol><li id=toc-dom><a href=#dom>3 Semantics, structure, and APIs of HTML documents</a><ol><li><a href=#documents>3.1 Documents</a><ol><li><a href=#the-document-object>3.1.1 The <code>Document</code> object</a><li><a href=#resource-metadata-management>3.1.2 Resource metadata management</a><li><a href=#dom-tree-accessors>3.1.3 DOM tree accessors</a><li><a href=#loading-xml-documents>3.1.4 Loading XML documents</a></ol><li><a href=#elements>3.2 Elements</a><ol><li><a href=#semantics-2>3.2.1 Semantics</a><li><a href=#elements-in-the-dom>3.2.2 Elements in the DOM</a><li><a href=#element-def
initions>3.2.3 Element definitions</a><ol><li><a href=#attributes>3.2.3.1 Attributes</a></ol><li><a href=#content-models>3.2.4 Content models</a><ol><li><a href=#the-nothing-content-model>3.2.4.1 The "nothing" content model</a><li><a href=#kinds-of-content>3.2.4.2 Kinds of content</a><ol><li><a href=#metadata-content>3.2.4.2.1 Metadata content</a><li><a href=#flow-content>3.2.4.2.2 Flow content</a><li><a href=#sectioning-content>3.2.4.2.3 Sectioning content</a><li><a href=#heading-content>3.2.4.2.4 Heading content</a><li><a href=#phrasing-content>3.2.4.2.5 Phrasing content</a><li><a href=#embedded-content-2>3.2.4.2.6 Embedded content</a><li><a href=#interactive-content>3.2.4.2.7 Interactive content</a><li><a href=#palpable-content>3.2.4.2.8 Palpable content</a><li><a href=#script-supporting-elements>3.2.4.2.9 Script-supporting elements</a></ol><li><a href=#transparent-content-models>3.2.4.3 Transparent content models</a><li><a href=#paragraphs>3.2.4.4 Paragraphs</a></ol><li>
<a href=#global-attributes>3.2.5 Global attributes</a><ol><li><a href=#the-id-attribute>3.2.5.1 The <code>id</code> attribute</a><li><a href=#the-title-attribute>3.2.5.2 The <code>title</code> attribute</a><li><a href=#the-lang-and-xml:lang-attributes>3.2.5.3 The <code>lang</code> and <code>xml:lang</code> attributes</a><li><a href=#the-translate-attribute>3.2.5.4 The <code>translate</code> attribute</a><li><a href=#the-xml:base-attribute-(xml-only)>3.2.5.5 The <code>xml:base</code> attribute (XML only)</a><li><a href=#the-dir-attribute>3.2.5.6 The <code>dir</code> attribute</a><li><a href=#classes>3.2.5.7 The <code>class</code> attribute</a><li><a href=#the-style-attribute>3.2.5.8 The <code>style</code> attribute</a><li><a href=#embedding-custom-non-visible-data-with-the-data-*-attributes>3.2.5.9 Embedding custom non-visible data with the <code>data-*</code> attributes</a></ol><li><a href=#requirements-relating-to-the-bidirectional-algorithm>3.2.6 Requirements relating to t
he bidirectional algorithm</a><ol><li><a href=#authoring-conformance-criteria-for-bidirectional-algorithm-formatting-characters>3.2.6.1 Authoring conformance criteria for bidirectional-algorithm formatting characters</a><li><a href=#user-agent-conformance-criteria>3.2.6.2 User agent conformance criteria</a></ol><li><a href=#wai-aria>3.2.7 Annotations for assistive technology products (ARIA)</a></ol></ol><li id=toc-semantics><a href=#semantics>4 The elements of HTML</a><ol><li><a href=#the-root-element>4.1 The root element</a><ol><li><a href=#the-html-element>4.1.1 The <code>html</code> element</a></ol><li><a href=#document-metadata>4.2 Document metadata</a><ol><li><a href=#the-head-element>4.2.1 The <code>head</code> element</a><li><a href=#the-title-element>4.2.2 The <code>title</code> element</a><li><a href=#the-base-element>4.2.3 The <code>base</code> element</a><li><a href=#the-link-element>4.2.4 The <code>link</code> element</a><li><a href=#the-meta-element>4.2.5 The <c
ode>meta</code> element</a><ol><li><a href=#standard-metadata-names>4.2.5.1 Standard metadata names</a><li><a href=#other-metadata-names>4.2.5.2 Other metadata names</a><li><a href=#pragma-directives>4.2.5.3 Pragma directives</a><li><a href=#other-pragma-directives>4.2.5.4 Other pragma directives</a><li><a href=#charset>4.2.5.5 Specifying the document's character encoding</a></ol><li><a href=#the-style-element>4.2.6 The <code>style</code> element</a><li><a href=#interactions-of-styling-and-scripting>4.2.7 Interactions of styling and scripting</a></ol><li><a href=#sections>4.3 Sections</a><ol><li><a href=#the-body-element>4.3.1 The <code>body</code> element</a><li><a href=#the-article-element>4.3.2 The <code>article</code> element</a><li><a href=#the-section-element>4.3.3 The <code>section</code> element</a><li><a href=#the-nav-element>4.3.4 The <code>nav</code> element</a><li><a href=#the-aside-element>4.3.5 The <code>aside</code> element</a><li><a href=#the-h1,-h2,-h3,-h4,-
h5,-and-h6-elements>4.3.6 The <code>h1</code>, <code>h2</code>, <code>h3</code>, <code>h4</code>, <code>h5</code>, and
- <code>h6</code> elements</a><li><a href=#the-hgroup-element>4.3.7 The <code>hgroup</code> element</a><li><a href=#the-header-element>4.3.8 The <code>header</code> element</a><li><a href=#the-footer-element>4.3.9 The <code>footer</code> element</a><li><a href=#the-address-element>4.3.10 The <code>address</code> element</a><li><a href=#headings-and-sections>4.3.11 Headings and sections</a><ol><li><a href=#outlines>4.3.11.1 Creating an outline</a><li><a href=#sample-outlines>4.3.11.2 Sample outlines</a><li><a href=#exposing-outlines-to-users>4.3.11.3 Exposing outlines to users</a></ol><li><a href=#usage-summary-2>4.3.12 Usage summary</a><ol><li><a href=#article-or-section>4.3.12.1 Article or section?</a></ol></ol><li><a href=#grouping-content>4.4 Grouping content</a><ol><li><a href=#the-p-element>4.4.1 The <code>p</code> element</a><li><a href=#the-hr-element>4.4.2 The <code>hr</code> element</a><li><a href=#the-pre-element>4.4.3 The <code>pre</code> element</a><li><a href=#t
he-blockquote-element>4.4.4 The <code>blockquote</code> element</a><li><a href=#the-ol-element>4.4.5 The <code>ol</code> element</a><li><a href=#the-ul-element>4.4.6 The <code>ul</code> element</a><li><a href=#the-li-element>4.4.7 The <code>li</code> element</a><li><a href=#the-dl-element>4.4.8 The <code>dl</code> element</a><li><a href=#the-dt-element>4.4.9 The <code>dt</code> element</a><li><a href=#the-dd-element>4.4.10 The <code>dd</code> element</a><li><a href=#the-figure-element>4.4.11 The <code>figure</code> element</a><li><a href=#the-figcaption-element>4.4.12 The <code>figcaption</code> element</a><li><a href=#the-main-element>4.4.13 The <code>main</code> element</a><li><a href=#the-div-element>4.4.14 The <code>div</code> element</a></ol><li><a href=#text-level-semantics>4.5 Text-level semantics</a><ol><li><a href=#the-a-element>4.5.1 The <code>a</code> element</a><li><a href=#the-em-element>4.5.2 The <code>em</code> element</a><li><a href=#the-strong-element>4.5.3
The <code>strong</code> element</a><li><a href=#the-small-element>4.5.4 The <code>small</code> element</a><li><a href=#the-s-element>4.5.5 The <code>s</code> element</a><li><a href=#the-cite-element>4.5.6 The <code>cite</code> element</a><li><a href=#the-q-element>4.5.7 The <code>q</code> element</a><li><a href=#the-dfn-element>4.5.8 The <code>dfn</code> element</a><li><a href=#the-abbr-element>4.5.9 The <code>abbr</code> element</a><li><a href=#the-ruby-element>4.5.10 The <code>ruby</code> element</a><li><a href=#the-rt-element>4.5.11 The <code>rt</code> element</a><li><a href=#the-rp-element>4.5.12 The <code>rp</code> element</a><li><a href=#the-data-element>4.5.13 The <code>data</code> element</a><li><a href=#the-time-element>4.5.14 The <code>time</code> element</a><li><a href=#the-code-element>4.5.15 The <code>code</code> element</a><li><a href=#the-var-element>4.5.16 The <code>var</code> element</a><li><a href=#the-samp-element>4.5.17 The <code>samp</code> element</a><l
i><a href=#the-kbd-element>4.5.18 The <code>kbd</code> element</a><li><a href=#the-sub-and-sup-elements>4.5.19 The <code>sub</code> and <code>sup</code> elements</a><li><a href=#the-i-element>4.5.20 The <code>i</code> element</a><li><a href=#the-b-element>4.5.21 The <code>b</code> element</a><li><a href=#the-u-element>4.5.22 The <code>u</code> element</a><li><a href=#the-mark-element>4.5.23 The <code>mark</code> element</a><li><a href=#the-bdi-element>4.5.24 The <code>bdi</code> element</a><li><a href=#the-bdo-element>4.5.25 The <code>bdo</code> element</a><li><a href=#the-span-element>4.5.26 The <code>span</code> element</a><li><a href=#the-br-element>4.5.27 The <code>br</code> element</a><li><a href=#the-wbr-element>4.5.28 The <code>wbr</code> element</a><li><a href=#usage-summary>4.5.29 Usage summary</a></ol><li><a href=#links>4.6 Links</a><ol><li><a href=#introduction-2>4.6.1 Introduction</a><li><a href=#links-created-by-a-and-area-elements>4.6.2 Links created by <code>a
</code> and <code>area</code> elements</a><li><a href=#following-hyperlinks>4.6.3 Following hyperlinks</a><li><a href=#downloading-resources>4.6.4 Downloading resources</a><ol><li><a href=#hyperlink-auditing>4.6.4.1 Hyperlink auditing</a></ol><li><a href=#linkTypes>4.6.5 Link types</a><ol><li><a href=#rel-alternate>4.6.5.1 Link type "<code>alternate</code>"</a><li><a href=#link-type-author>4.6.5.2 Link type "<code>author</code>"</a><li><a href=#link-type-bookmark>4.6.5.3 Link type "<code>bookmark</code>"</a><li><a href=#link-type-external>4.6.5.4 Link type "<code>external</code>"</a><li><a href=#link-type-help>4.6.5.5 Link type "<code>help</code>"</a><li><a href=#rel-icon>4.6.5.6 Link type "<code>icon</code>"</a><li><a href=#link-type-license>4.6.5.7 Link type "<code>license</code>"</a><li><a href=#link-type-nofollow>4.6.5.8 Link type "<code>nofollow</code>"</a><li><a href=#link-type-noreferrer>4.6.5.9 Link type "<code>noreferrer</code>"</a><li><a href=#link-type-pingback>4.
6.5.10 Link type "<code>pingback</code>"</a><li><a href=#link-type-prefetch>4.6.5.11 Link type "<code>prefetch</code>"</a><li><a href=#link-type-search>4.6.5.12 Link type "<code>search</code>"</a><li><a href=#link-type-sidebar>4.6.5.13 Link type "<code>sidebar</code>"</a><li><a href=#link-type-stylesheet>4.6.5.14 Link type "<code>stylesheet</code>"</a><li><a href=#link-type-tag>4.6.5.15 Link type "<code>tag</code>"</a><li><a href=#sequential-link-types>4.6.5.16 Sequential link types</a><ol><li><a href=#link-type-next>4.6.5.16.1 Link type "<code>next</code>"</a><li><a href=#link-type-prev>4.6.5.16.2 Link type "<code>prev</code>"</a></ol><li><a href=#other-link-types>4.6.5.17 Other link types</a></ol></ol><li><a href=#edits>4.7 Edits</a><ol><li><a href=#the-ins-element>4.7.1 The <code>ins</code> element</a><li><a href=#the-del-element>4.7.2 The <code>del</code> element</a><li><a href=#attributes-common-to-ins-and-del-elements>4.7.3 Attributes common to <code>ins</code> and <co
de>del</code> elements</a><li><a href=#edits-and-paragraphs>4.7.4 Edits and paragraphs</a><li><a href=#edits-and-lists>4.7.5 Edits and lists</a><li><a href=#edits-and-tables>4.7.6 Edits and tables</a></ol><li><a href=#embedded-content>4.8 Embedded content</a><ol><li><a href=#introduction-3>4.8.1 Introduction</a><ol><li><a href=#adaptive-images>4.8.1.1 Adaptive images</a></ol><li><a href=#dependencies-2>4.8.2 Dependencies</a><li><a href=#the-picture-element>4.8.3 The <code>picture</code> element</a><li><a href=#the-source-element-when-used-with-the-picture-element>4.8.4 The <code>source</code> element when used with the <code>picture</code> element</a><li><a href=#the-img-element>4.8.5 The <code>img</code> element</a><ol><li><a href=#alt>4.8.5.1 Requirements for providing text to act as an alternative for images</a><ol><li><a href=#general-guidelines>4.8.5.1.1 General guidelines</a><li><a href=#a-link-or-button-containing-nothing-but-the-image>4.8.5.1.2 A link or button conta
ining nothing but the image</a><li><a href=#a-phrase-or-paragraph-with-an-alternative-graphical-representation:-charts,-diagrams,-graphs,-maps,-illustrations>4.8.5.1.3 A phrase or paragraph with an alternative graphical representation: charts, diagrams, graphs, maps, illustrations</a><li><a href=#a-short-phrase-or-label-with-an-alternative-graphical-representation:-icons,-logos>4.8.5.1.4 A short phrase or label with an alternative graphical representation: icons, logos</a><li><a href=#text-that-has-been-rendered-to-a-graphic-for-typographical-effect>4.8.5.1.5 Text that has been rendered to a graphic for typographical effect</a><li><a href=#a-graphical-representation-of-some-of-the-surrounding-text>4.8.5.1.6 A graphical representation of some of the surrounding text</a><li><a href=#ancillary-images>4.8.5.1.7 Ancillary images</a><li><a href="#a-purely-decorative-image-that-doesn't-add-any-information">4.8.5.1.8 A purely decorative image that doesn't add any information</a><li>
<a href=#a-group-of-images-that-form-a-single-larger-picture-with-no-links>4.8.5.1.9 A group of images that form a single larger picture with no links</a><li><a href=#a-group-of-images-that-form-a-single-larger-picture-with-links>4.8.5.1.10 A group of images that form a single larger picture with links</a><li><a href=#a-key-part-of-the-content>4.8.5.1.11 A key part of the content</a><li><a href=#an-image-not-intended-for-the-user>4.8.5.1.12 An image not intended for the user</a><li><a href=#an-image-in-an-e-mail-or-private-document-intended-for-a-specific-person-who-is-known-to-be-able-to-view-images>4.8.5.1.13 An image in an e-mail or private document intended for a specific person who is known to be able to view images</a><li><a href=#guidance-for-markup-generators>4.8.5.1.14 Guidance for markup generators</a><li><a href=#guidance-for-conformance-checkers>4.8.5.1.15 Guidance for conformance checkers</a></ol></ol><li><a href=#the-iframe-element>4.8.6 The <code>iframe</code>
element</a><li><a href=#the-embed-element>4.8.7 The <code>embed</code> element</a><li><a href=#the-object-element>4.8.8 The <code>object</code> element</a><li><a href=#the-param-element>4.8.9 The <code>param</code> element</a><li><a href=#the-video-element>4.8.10 The <code>video</code> element</a><li><a href=#the-audio-element>4.8.11 The <code>audio</code> element</a><li><a href=#the-source-element>4.8.12 The <code>source</code> element</a><li><a href=#the-track-element>4.8.13 The <code>track</code> element</a><li><a href=#media-elements>4.8.14 Media elements</a><ol><li><a href=#error-codes>4.8.14.1 Error codes</a><li><a href=#location-of-the-media-resource>4.8.14.2 Location of the media resource</a><li><a href=#mime-types>4.8.14.3 MIME types</a><li><a href=#network-states>4.8.14.4 Network states</a><li><a href=#loading-the-media-resource>4.8.14.5 Loading the media resource</a><li><a href=#offsets-into-the-media-resource>4.8.14.6 Offsets into the media resource</a><li><a hr
ef=#ready-states>4.8.14.7 Ready states</a><li><a href=#playing-the-media-resource>4.8.14.8 Playing the media resource</a><li><a href=#seeking>4.8.14.9 Seeking</a><li><a href=#media-resources-with-multiple-media-tracks>4.8.14.10 Media resources with multiple media tracks</a><ol><li><a href=#audiotracklist-and-videotracklist-objects>4.8.14.10.1 <code>AudioTrackList</code> and <code>VideoTrackList</code> objects</a><li><a href=#selecting-specific-audio-and-video-tracks-declaratively>4.8.14.10.2 Selecting specific audio and video tracks declaratively</a></ol><li><a href=#synchronising-multiple-media-elements>4.8.14.11 Synchronising multiple media elements</a><ol><li><a href=#introduction-4>4.8.14.11.1 Introduction</a><li><a href=#media-controllers>4.8.14.11.2 Media controllers</a><li><a href=#assigning-a-media-controller-declaratively>4.8.14.11.3 Assigning a media controller declaratively</a></ol><li><a href=#timed-text-tracks>4.8.14.12 Timed text tracks</a><ol><li><a href=#text
-track-model>4.8.14.12.1 Text track model</a><li><a href=#sourcing-in-band-text-tracks>4.8.14.12.2 Sourcing in-band text tracks</a><li><a href=#sourcing-out-of-band-text-tracks>4.8.14.12.3 Sourcing out-of-band text tracks</a><li><a href=#guidelines-for-exposing-cues-in-various-formats-as-text-track-cues>4.8.14.12.4 Guidelines for exposing cues in various formats as text track cues</a><li><a href=#text-track-api>4.8.14.12.5 Text track API</a><li><a href=#text-tracks-describing-chapters>4.8.14.12.6 Text tracks describing chapters</a><li><a href=#cue-events>4.8.14.12.7 Event handlers for objects of the text track APIs</a><li><a href=#best-practices-for-metadata-text-tracks>4.8.14.12.8 Best practices for metadata text tracks</a></ol><li><a href=#user-interface>4.8.14.13 User interface</a><li><a href=#time-ranges>4.8.14.14 Time ranges</a><li><a href=#the-trackevent-interface>4.8.14.15 The <code>TrackEvent</code> interface</a><li><a href=#mediaevents>4.8.14.16 Event summary</a><li
><a href=#security-and-privacy-considerations>4.8.14.17 Security and privacy considerations</a><li><a href=#best-practices-for-authors-using-media-elements>4.8.14.18 Best practices for authors using media elements</a><li><a href=#best-practices-for-implementors-of-media-elements>4.8.14.19 Best practices for implementors of media elements</a></ol><li><a href=#the-map-element>4.8.15 The <code>map</code> element</a><li><a href=#the-area-element>4.8.16 The <code>area</code> element</a><li><a href=#image-maps>4.8.17 Image maps</a><ol><li><a href=#authoring>4.8.17.1 Authoring</a><li><a href=#processing-model-2>4.8.17.2 Processing model</a></ol><li><a href=#mathml>4.8.18 MathML</a><li><a href=#svg-0>4.8.19 SVG</a><li><a href=#dimension-attributes>4.8.20 Dimension attributes</a></ol><li><a href=#tables>4.9 Tabular data</a><ol><li><a href=#the-table-element>4.9.1 The <code>table</code> element</a><ol><li><a href=#table-descriptions-techniques>4.9.1.1 Techniques for describing tables<
/a><li><a href=#table-layout-techniques>4.9.1.2 Techniques for table design</a></ol><li><a href=#the-caption-element>4.9.2 The <code>caption</code> element</a><li><a href=#the-colgroup-element>4.9.3 The <code>colgroup</code> element</a><li><a href=#the-col-element>4.9.4 The <code>col</code> element</a><li><a href=#the-tbody-element>4.9.5 The <code>tbody</code> element</a><li><a href=#the-thead-element>4.9.6 The <code>thead</code> element</a><li><a href=#the-tfoot-element>4.9.7 The <code>tfoot</code> element</a><li><a href=#the-tr-element>4.9.8 The <code>tr</code> element</a><li><a href=#the-td-element>4.9.9 The <code>td</code> element</a><li><a href=#the-th-element>4.9.10 The <code>th</code> element</a><li><a href=#attributes-common-to-td-and-th-elements>4.9.11 Attributes common to <code>td</code> and <code>th</code> elements</a><li><a href=#processing-model-3>4.9.12 Processing model</a><ol><li><a href=#forming-a-table>4.9.12.1 Forming a table</a><li><a href=#header-and-data
-cell-semantics>4.9.12.2 Forming relationships between data cells and header cells</a></ol><li><a href=#table-sorting-model>4.9.13 Table sorting model</a><li><a href=#table-examples>4.9.14 Examples</a></ol><li><a href=#forms>4.10 Forms</a><ol><li><a href=#introduction-5>4.10.1 Introduction</a><ol><li><a href="#writing-a-form's-user-interface">4.10.1.1 Writing a form's user interface</a><li><a href=#implementing-the-server-side-processing-for-a-form>4.10.1.2 Implementing the server-side processing for a form</a><li><a href=#configuring-a-form-to-communicate-with-a-server>4.10.1.3 Configuring a form to communicate with a server</a><li><a href=#client-side-form-validation>4.10.1.4 Client-side form validation</a><li><a href=#enabling-client-side-automatic-filling-of-form-controls>4.10.1.5 Enabling client-side automatic filling of form controls</a><li><a href=#improving-the-user-experience-on-mobile-devices>4.10.1.6 Improving the user experience on mobile devices</a><li><a href=#
the-difference-between-the-field-type,-the-autofill-field-name,-and-the-input-modality>4.10.1.7 The difference between the field type, the autofill field name, and the input modality</a><li><a href=#input-author-notes>4.10.1.8 Date, time, and number formats</a></ol><li><a href=#categories>4.10.2 Categories</a><li><a href=#the-form-element>4.10.3 The <code>form</code> element</a><li><a href=#the-label-element>4.10.4 The <code>label</code> element</a><li><a href=#the-input-element>4.10.5 The <code>input</code> element</a><ol><li><a href=#states-of-the-type-attribute>4.10.5.1 States of the <code>type</code> attribute</a><ol><li><a href="#hidden-state-(type=hidden)">4.10.5.1.1 Hidden state (<code>type=hidden</code>)</a><li><a href="#text-(type=text)-state-and-search-state-(type=search)">4.10.5.1.2 Text (<code>type=text</code>) state and Search state (<code>type=search</code>)</a><li><a href="#telephone-state-(type=tel)">4.10.5.1.3 Telephone state (<code>type=tel</code>)</a><li><
a href="#url-state-(type=url)">4.10.5.1.4 URL state (<code>type=url</code>)</a><li><a href="#e-mail-state-(type=email)">4.10.5.1.5 E-mail state (<code>type=email</code>)</a><li><a href="#password-state-(type=password)">4.10.5.1.6 Password state (<code>type=password</code>)</a><li><a href="#date-and-time-state-(type=datetime)">4.10.5.1.7 Date and Time state (<code>type=datetime</code>)</a><li><a href="#date-state-(type=date)">4.10.5.1.8 Date state (<code>type=date</code>)</a><li><a href="#month-state-(type=month)">4.10.5.1.9 Month state (<code>type=month</code>)</a><li><a href="#week-state-(type=week)">4.10.5.1.10 Week state (<code>type=week</code>)</a><li><a href="#time-state-(type=time)">4.10.5.1.11 Time state (<code>type=time</code>)</a><li><a href="#local-date-and-time-state-(type=datetime-local)">4.10.5.1.12 Local Date and Time state (<code>type=datetime-local</code>)</a><li><a href="#number-state-(type=number)">4.10.5.1.13 Number state (<code>type=number</code>)</a><li>
<a href="#range-state-(type=range)">4.10.5.1.14 Range state (<code>type=range</code>)</a><li><a href="#color-state-(type=color)">4.10.5.1.15 Colour state (<code>type=color</code>)</a><li><a href="#checkbox-state-(type=checkbox)">4.10.5.1.16 Checkbox state (<code>type=checkbox</code>)</a><li><a href="#radio-button-state-(type=radio)">4.10.5.1.17 Radio Button state (<code>type=radio</code>)</a><li><a href="#file-upload-state-(type=file)">4.10.5.1.18 File Upload state (<code>type=file</code>)</a><li><a href="#submit-button-state-(type=submit)">4.10.5.1.19 Submit Button state (<code>type=submit</code>)</a><li><a href="#image-button-state-(type=image)">4.10.5.1.20 Image Button state (<code>type=image</code>)</a><li><a href="#reset-button-state-(type=reset)">4.10.5.1.21 Reset Button state (<code>type=reset</code>)</a><li><a href="#button-state-(type=button)">4.10.5.1.22 Button state (<code>type=button</code>)</a></ol><li><a href=#input-impl-notes>4.10.5.2 Implemention notes regard
ing localization of form controls</a><li><a href=#common-input-element-attributes>4.10.5.3 Common <code>input</code> element attributes</a><ol><li><a href=#the-maxlength-and-minlength-attributes>4.10.5.3.1 The <code>maxlength</code> and <code>minlength</code> attributes</a><li><a href=#the-size-attribute>4.10.5.3.2 The <code>size</code> attribute</a><li><a href=#the-readonly-attribute>4.10.5.3.3 The <code>readonly</code> attribute</a><li><a href=#the-required-attribute>4.10.5.3.4 The <code>required</code> attribute</a><li><a href=#the-multiple-attribute>4.10.5.3.5 The <code>multiple</code> attribute</a><li><a href=#the-pattern-attribute>4.10.5.3.6 The <code>pattern</code> attribute</a><li><a href=#the-min-and-max-attributes>4.10.5.3.7 The <code>min</code> and <code>max</code> attributes</a><li><a href=#the-step-attribute>4.10.5.3.8 The <code>step</code> attribute</a><li><a href=#the-list-attribute>4.10.5.3.9 The <code>list</code> attribute</a><li><a href=#the-placeholder-att
ribute>4.10.5.3.10 The <code>placeholder</code> attribute</a></ol><li><a href=#common-input-element-apis>4.10.5.4 Common <code>input</code> element APIs</a><li><a href=#common-input-element-events>4.10.5.5 Common event behaviors</a></ol><li><a href=#the-button-element>4.10.6 The <code>button</code> element</a><li><a href=#the-select-element>4.10.7 The <code>select</code> element</a><li><a href=#the-datalist-element>4.10.8 The <code>datalist</code> element</a><li><a href=#the-optgroup-element>4.10.9 The <code>optgroup</code> element</a><li><a href=#the-option-element>4.10.10 The <code>option</code> element</a><li><a href=#the-textarea-element>4.10.11 The <code>textarea</code> element</a><li><a href=#the-keygen-element>4.10.12 The <code>keygen</code> element</a><li><a href=#the-output-element>4.10.13 The <code>output</code> element</a><li><a href=#the-progress-element>4.10.14 The <code>progress</code> element</a><li><a href=#the-meter-element>4.10.15 The <code>meter</code> ele
ment</a><li><a href=#the-fieldset-element>4.10.16 The <code>fieldset</code> element</a><li><a href=#the-legend-element>4.10.17 The <code>legend</code> element</a><li><a href=#form-control-infrastructure>4.10.18 Form control infrastructure</a><ol><li><a href="#a-form-control's-value">4.10.18.1 A form control's value</a><li><a href=#mutability>4.10.18.2 Mutability</a><li><a href=#association-of-controls-and-forms>4.10.18.3 Association of controls and forms</a></ol><li><a href=#attributes-common-to-form-controls>4.10.19 Attributes common to form controls</a><ol><li><a href=#naming-form-controls:-the-name-attribute>4.10.19.1 Naming form controls: the <code>name</code> attribute</a><li><a href=#submitting-element-directionality:-the-dirname-attribute>4.10.19.2 Submitting element directionality: the <code>dirname</code> attribute</a><li><a href=#limiting-user-input-length:-the-maxlength-attribute>4.10.19.3 Limiting user input length: the <code>maxlength</code> attribute</a><li><a
href=#setting-minimum-input-length-requirements:-the-minlength-attribute>4.10.19.4 Setting minimum input length requirements: the <code>minlength</code> attribute</a><li><a href=#enabling-and-disabling-form-controls:-the-disabled-attribute>4.10.19.5 Enabling and disabling form controls: the <code>disabled</code> attribute</a><li><a href=#form-submission>4.10.19.6 Form submission</a><ol><li><a href=#autofocusing-a-form-control:-the-autofocus-attribute>4.10.19.6.1 Autofocusing a form control: the <code>autofocus</code> attribute</a></ol><li><a href=#input-modalities:-the-inputmode-attribute>4.10.19.7 Input modalities: the <code>inputmode</code> attribute</a><li><a href=#autofill>4.10.19.8 Autofill</a><ol><li><a href=#autofilling-form-controls:-the-autocomplete-attribute>4.10.19.8.1 Autofilling form controls: the <code>autocomplete</code> attribute</a><li><a href=#processing-model-4>4.10.19.8.2 Processing model</a><li><a href=#user-interface-for-bulk-autofill>4.10.19.8.3 User i
nterface for bulk autofill</a><li><a href=#the-autocompleteerrorevent-interface>4.10.19.8.4 The <code>AutocompleteErrorEvent</code> interface</a></ol></ol><li><a href=#textFieldSelection>4.10.20 APIs for the text field selections</a><li><a href=#constraints>4.10.21 Constraints</a><ol><li><a href=#definitions>4.10.21.1 Definitions</a><li><a href=#constraint-validation>4.10.21.2 Constraint validation</a><li><a href=#the-constraint-validation-api>4.10.21.3 The constraint validation API</a><li><a href=#security-forms>4.10.21.4 Security</a></ol><li><a href=#form-submission-2>4.10.22 Form submission</a><ol><li><a href=#introduction-6>4.10.22.1 Introduction</a><li><a href=#implicit-submission>4.10.22.2 Implicit submission</a><li><a href=#form-submission-algorithm>4.10.22.3 Form submission algorithm</a><li><a href=#constructing-form-data-set>4.10.22.4 Constructing the form data set</a><li><a href=#selecting-a-form-submission-encoding>4.10.22.5 Selecting a form submission encoding</a
><li><a href=#url-encoded-form-data>4.10.22.6 URL-encoded form data</a><li><a href=#multipart-form-data>4.10.22.7 Multipart form data</a><li><a href=#plain-text-form-data>4.10.22.8 Plain text form data</a></ol><li><a href=#resetting-a-form>4.10.23 Resetting a form</a></ol><li><a href=#interactive-elements>4.11 Interactive elements</a><ol><li><a href=#the-details-element>4.11.1 The <code>details</code> element</a><li><a href=#the-summary-element>4.11.2 The <code>summary</code> element</a><li><a href=#the-menu-element>4.11.3 The <code>menu</code> element</a><li><a href=#the-menuitem-element>4.11.4 The <code>menuitem</code> element</a><li><a href=#context-menus>4.11.5 Context menus</a><ol><li><a href=#declaring-a-context-menu>4.11.5.1 Declaring a context menu</a><li><a href=#processing-model-5>4.11.5.2 Processing model</a><li><a href=#the-relatedevent-interfaces>4.11.5.3 The <code>RelatedEvent</code> interfaces</a></ol><li><a href=#commands>4.11.6 Commands</a><ol><li><a href=#f
acets-2>4.11.6.1 Facets</a><li><a href=#using-the-a-element-to-define-a-command>4.11.6.2 Using the <code>a</code> element to define a command</a><li><a href=#using-the-button-element-to-define-a-command>4.11.6.3 Using the <code>button</code> element to define a command</a><li><a href=#using-the-input-element-to-define-a-command>4.11.6.4 Using the <code>input</code> element to define a command</a><li><a href=#using-the-option-element-to-define-a-command>4.11.6.5 Using the <code>option</code> element to define a command</a><li><a href=#using-the-menuitem-element-to-define-a-command>4.11.6.6 Using the <code>menuitem</code> element to define a
+ <code>h6</code> elements</a><li><a href=#the-hgroup-element>4.3.7 The <code>hgroup</code> element</a><li><a href=#the-header-element>4.3.8 The <code>header</code> element</a><li><a href=#the-footer-element>4.3.9 The <code>footer</code> element</a><li><a href=#the-address-element>4.3.10 The <code>address</code> element</a><li><a href=#headings-and-sections>4.3.11 Headings and sections</a><ol><li><a href=#outlines>4.3.11.1 Creating an outline</a><li><a href=#sample-outlines>4.3.11.2 Sample outlines</a><li><a href=#exposing-outlines-to-users>4.3.11.3 Exposing outlines to users</a></ol><li><a href=#usage-summary-2>4.3.12 Usage summary</a><ol><li><a href=#article-or-section>4.3.12.1 Article or section?</a></ol></ol><li><a href=#grouping-content>4.4 Grouping content</a><ol><li><a href=#the-p-element>4.4.1 The <code>p</code> element</a><li><a href=#the-hr-element>4.4.2 The <code>hr</code> element</a><li><a href=#the-pre-element>4.4.3 The <code>pre</code> element</a><li><a href=#t
he-blockquote-element>4.4.4 The <code>blockquote</code> element</a><li><a href=#the-ol-element>4.4.5 The <code>ol</code> element</a><li><a href=#the-ul-element>4.4.6 The <code>ul</code> element</a><li><a href=#the-li-element>4.4.7 The <code>li</code> element</a><li><a href=#the-dl-element>4.4.8 The <code>dl</code> element</a><li><a href=#the-dt-element>4.4.9 The <code>dt</code> element</a><li><a href=#the-dd-element>4.4.10 The <code>dd</code> element</a><li><a href=#the-figure-element>4.4.11 The <code>figure</code> element</a><li><a href=#the-figcaption-element>4.4.12 The <code>figcaption</code> element</a><li><a href=#the-main-element>4.4.13 The <code>main</code> element</a><li><a href=#the-div-element>4.4.14 The <code>div</code> element</a></ol><li><a href=#text-level-semantics>4.5 Text-level semantics</a><ol><li><a href=#the-a-element>4.5.1 The <code>a</code> element</a><li><a href=#the-em-element>4.5.2 The <code>em</code> element</a><li><a href=#the-strong-element>4.5.3
The <code>strong</code> element</a><li><a href=#the-small-element>4.5.4 The <code>small</code> element</a><li><a href=#the-s-element>4.5.5 The <code>s</code> element</a><li><a href=#the-cite-element>4.5.6 The <code>cite</code> element</a><li><a href=#the-q-element>4.5.7 The <code>q</code> element</a><li><a href=#the-dfn-element>4.5.8 The <code>dfn</code> element</a><li><a href=#the-abbr-element>4.5.9 The <code>abbr</code> element</a><li><a href=#the-ruby-element>4.5.10 The <code>ruby</code> element</a><li><a href=#the-rt-element>4.5.11 The <code>rt</code> element</a><li><a href=#the-rp-element>4.5.12 The <code>rp</code> element</a><li><a href=#the-data-element>4.5.13 The <code>data</code> element</a><li><a href=#the-time-element>4.5.14 The <code>time</code> element</a><li><a href=#the-code-element>4.5.15 The <code>code</code> element</a><li><a href=#the-var-element>4.5.16 The <code>var</code> element</a><li><a href=#the-samp-element>4.5.17 The <code>samp</code> element</a><l
i><a href=#the-kbd-element>4.5.18 The <code>kbd</code> element</a><li><a href=#the-sub-and-sup-elements>4.5.19 The <code>sub</code> and <code>sup</code> elements</a><li><a href=#the-i-element>4.5.20 The <code>i</code> element</a><li><a href=#the-b-element>4.5.21 The <code>b</code> element</a><li><a href=#the-u-element>4.5.22 The <code>u</code> element</a><li><a href=#the-mark-element>4.5.23 The <code>mark</code> element</a><li><a href=#the-bdi-element>4.5.24 The <code>bdi</code> element</a><li><a href=#the-bdo-element>4.5.25 The <code>bdo</code> element</a><li><a href=#the-span-element>4.5.26 The <code>span</code> element</a><li><a href=#the-br-element>4.5.27 The <code>br</code> element</a><li><a href=#the-wbr-element>4.5.28 The <code>wbr</code> element</a><li><a href=#usage-summary>4.5.29 Usage summary</a></ol><li><a href=#links>4.6 Links</a><ol><li><a href=#introduction-2>4.6.1 Introduction</a><li><a href=#links-created-by-a-and-area-elements>4.6.2 Links created by <code>a
</code> and <code>area</code> elements</a><li><a href=#following-hyperlinks>4.6.3 Following hyperlinks</a><li><a href=#downloading-resources>4.6.4 Downloading resources</a><ol><li><a href=#hyperlink-auditing>4.6.4.1 Hyperlink auditing</a></ol><li><a href=#linkTypes>4.6.5 Link types</a><ol><li><a href=#rel-alternate>4.6.5.1 Link type "<code>alternate</code>"</a><li><a href=#link-type-author>4.6.5.2 Link type "<code>author</code>"</a><li><a href=#link-type-bookmark>4.6.5.3 Link type "<code>bookmark</code>"</a><li><a href=#link-type-external>4.6.5.4 Link type "<code>external</code>"</a><li><a href=#link-type-help>4.6.5.5 Link type "<code>help</code>"</a><li><a href=#rel-icon>4.6.5.6 Link type "<code>icon</code>"</a><li><a href=#link-type-license>4.6.5.7 Link type "<code>license</code>"</a><li><a href=#link-type-nofollow>4.6.5.8 Link type "<code>nofollow</code>"</a><li><a href=#link-type-noreferrer>4.6.5.9 Link type "<code>noreferrer</code>"</a><li><a href=#link-type-pingback>4.
6.5.10 Link type "<code>pingback</code>"</a><li><a href=#link-type-prefetch>4.6.5.11 Link type "<code>prefetch</code>"</a><li><a href=#link-type-search>4.6.5.12 Link type "<code>search</code>"</a><li><a href=#link-type-sidebar>4.6.5.13 Link type "<code>sidebar</code>"</a><li><a href=#link-type-stylesheet>4.6.5.14 Link type "<code>stylesheet</code>"</a><li><a href=#link-type-tag>4.6.5.15 Link type "<code>tag</code>"</a><li><a href=#sequential-link-types>4.6.5.16 Sequential link types</a><ol><li><a href=#link-type-next>4.6.5.16.1 Link type "<code>next</code>"</a><li><a href=#link-type-prev>4.6.5.16.2 Link type "<code>prev</code>"</a></ol><li><a href=#other-link-types>4.6.5.17 Other link types</a></ol></ol><li><a href=#edits>4.7 Edits</a><ol><li><a href=#the-ins-element>4.7.1 The <code>ins</code> element</a><li><a href=#the-del-element>4.7.2 The <code>del</code> element</a><li><a href=#attributes-common-to-ins-and-del-elements>4.7.3 Attributes common to <code>ins</code> and <co
de>del</code> elements</a><li><a href=#edits-and-paragraphs>4.7.4 Edits and paragraphs</a><li><a href=#edits-and-lists>4.7.5 Edits and lists</a><li><a href=#edits-and-tables>4.7.6 Edits and tables</a></ol><li><a href=#embedded-content>4.8 Embedded content</a><ol><li><a href=#introduction-3>4.8.1 Introduction</a><ol><li><a href=#adaptive-images>4.8.1.1 Adaptive images</a></ol><li><a href=#dependencies-2>4.8.2 Dependencies</a><li><a href=#the-picture-element>4.8.3 The <code>picture</code> element</a><li><a href=#the-source-element-when-used-with-the-picture-element>4.8.4 The <code>source</code> element when used with the <code>picture</code> element</a><li><a href=#the-img-element>4.8.5 The <code>img</code> element</a><ol><li><a href=#alt>4.8.5.1 Requirements for providing text to act as an alternative for images</a><ol><li><a href=#general-guidelines>4.8.5.1.1 General guidelines</a><li><a href=#a-link-or-button-containing-nothing-but-the-image>4.8.5.1.2 A link or button conta
ining nothing but the image</a><li><a href=#a-phrase-or-paragraph-with-an-alternative-graphical-representation:-charts,-diagrams,-graphs,-maps,-illustrations>4.8.5.1.3 A phrase or paragraph with an alternative graphical representation: charts, diagrams, graphs, maps, illustrations</a><li><a href=#a-short-phrase-or-label-with-an-alternative-graphical-representation:-icons,-logos>4.8.5.1.4 A short phrase or label with an alternative graphical representation: icons, logos</a><li><a href=#text-that-has-been-rendered-to-a-graphic-for-typographical-effect>4.8.5.1.5 Text that has been rendered to a graphic for typographical effect</a><li><a href=#a-graphical-representation-of-some-of-the-surrounding-text>4.8.5.1.6 A graphical representation of some of the surrounding text</a><li><a href=#ancillary-images>4.8.5.1.7 Ancillary images</a><li><a href="#a-purely-decorative-image-that-doesn't-add-any-information">4.8.5.1.8 A purely decorative image that doesn't add any information</a><li>
<a href=#a-group-of-images-that-form-a-single-larger-picture-with-no-links>4.8.5.1.9 A group of images that form a single larger picture with no links</a><li><a href=#a-group-of-images-that-form-a-single-larger-picture-with-links>4.8.5.1.10 A group of images that form a single larger picture with links</a><li><a href=#a-key-part-of-the-content>4.8.5.1.11 A key part of the content</a><li><a href=#an-image-not-intended-for-the-user>4.8.5.1.12 An image not intended for the user</a><li><a href=#an-image-in-an-e-mail-or-private-document-intended-for-a-specific-person-who-is-known-to-be-able-to-view-images>4.8.5.1.13 An image in an e-mail or private document intended for a specific person who is known to be able to view images</a><li><a href=#guidance-for-markup-generators>4.8.5.1.14 Guidance for markup generators</a><li><a href=#guidance-for-conformance-checkers>4.8.5.1.15 Guidance for conformance checkers</a></ol></ol><li><a href=#the-iframe-element>4.8.6 The <code>iframe</code>
element</a><li><a href=#the-embed-element>4.8.7 The <code>embed</code> element</a><li><a href=#the-object-element>4.8.8 The <code>object</code> element</a><li><a href=#the-param-element>4.8.9 The <code>param</code> element</a><li><a href=#the-video-element>4.8.10 The <code>video</code> element</a><li><a href=#the-audio-element>4.8.11 The <code>audio</code> element</a><li><a href=#the-source-element>4.8.12 The <code>source</code> element</a><li><a href=#the-track-element>4.8.13 The <code>track</code> element</a><li><a href=#media-elements>4.8.14 Media elements</a><ol><li><a href=#error-codes>4.8.14.1 Error codes</a><li><a href=#location-of-the-media-resource>4.8.14.2 Location of the media resource</a><li><a href=#mime-types>4.8.14.3 MIME types</a><li><a href=#network-states>4.8.14.4 Network states</a><li><a href=#loading-the-media-resource>4.8.14.5 Loading the media resource</a><li><a href=#offsets-into-the-media-resource>4.8.14.6 Offsets into the media resource</a><li><a hr
ef=#ready-states>4.8.14.7 Ready states</a><li><a href=#playing-the-media-resource>4.8.14.8 Playing the media resource</a><li><a href=#seeking>4.8.14.9 Seeking</a><li><a href=#media-resources-with-multiple-media-tracks>4.8.14.10 Media resources with multiple media tracks</a><ol><li><a href=#audiotracklist-and-videotracklist-objects>4.8.14.10.1 <code>AudioTrackList</code> and <code>VideoTrackList</code> objects</a><li><a href=#selecting-specific-audio-and-video-tracks-declaratively>4.8.14.10.2 Selecting specific audio and video tracks declaratively</a></ol><li><a href=#synchronising-multiple-media-elements>4.8.14.11 Synchronising multiple media elements</a><ol><li><a href=#introduction-4>4.8.14.11.1 Introduction</a><li><a href=#media-controllers>4.8.14.11.2 Media controllers</a><li><a href=#assigning-a-media-controller-declaratively>4.8.14.11.3 Assigning a media controller declaratively</a></ol><li><a href=#timed-text-tracks>4.8.14.12 Timed text tracks</a><ol><li><a href=#text
-track-model>4.8.14.12.1 Text track model</a><li><a href=#sourcing-in-band-text-tracks>4.8.14.12.2 Sourcing in-band text tracks</a><li><a href=#sourcing-out-of-band-text-tracks>4.8.14.12.3 Sourcing out-of-band text tracks</a><li><a href=#guidelines-for-exposing-cues-in-various-formats-as-text-track-cues>4.8.14.12.4 Guidelines for exposing cues in various formats as text track cues</a><li><a href=#text-track-api>4.8.14.12.5 Text track API</a><li><a href=#text-tracks-describing-chapters>4.8.14.12.6 Text tracks describing chapters</a><li><a href=#cue-events>4.8.14.12.7 Event handlers for objects of the text track APIs</a><li><a href=#best-practices-for-metadata-text-tracks>4.8.14.12.8 Best practices for metadata text tracks</a></ol><li><a href=#user-interface>4.8.14.13 User interface</a><li><a href=#time-ranges>4.8.14.14 Time ranges</a><li><a href=#the-trackevent-interface>4.8.14.15 The <code>TrackEvent</code> interface</a><li><a href=#mediaevents>4.8.14.16 Event summary</a><li
><a href=#security-and-privacy-considerations>4.8.14.17 Security and privacy considerations</a><li><a href=#best-practices-for-authors-using-media-elements>4.8.14.18 Best practices for authors using media elements</a><li><a href=#best-practices-for-implementors-of-media-elements>4.8.14.19 Best practices for implementors of media elements</a></ol><li><a href=#the-map-element>4.8.15 The <code>map</code> element</a><li><a href=#the-area-element>4.8.16 The <code>area</code> element</a><li><a href=#image-maps>4.8.17 Image maps</a><ol><li><a href=#authoring>4.8.17.1 Authoring</a><li><a href=#processing-model-2>4.8.17.2 Processing model</a></ol><li><a href=#mathml>4.8.18 MathML</a><li><a href=#svg-0>4.8.19 SVG</a><li><a href=#dimension-attributes>4.8.20 Dimension attributes</a></ol><li><a href=#tables>4.9 Tabular data</a><ol><li><a href=#the-table-element>4.9.1 The <code>table</code> element</a><ol><li><a href=#table-descriptions-techniques>4.9.1.1 Techniques for describing tables<
/a><li><a href=#table-layout-techniques>4.9.1.2 Techniques for table design</a></ol><li><a href=#the-caption-element>4.9.2 The <code>caption</code> element</a><li><a href=#the-colgroup-element>4.9.3 The <code>colgroup</code> element</a><li><a href=#the-col-element>4.9.4 The <code>col</code> element</a><li><a href=#the-tbody-element>4.9.5 The <code>tbody</code> element</a><li><a href=#the-thead-element>4.9.6 The <code>thead</code> element</a><li><a href=#the-tfoot-element>4.9.7 The <code>tfoot</code> element</a><li><a href=#the-tr-element>4.9.8 The <code>tr</code> element</a><li><a href=#the-td-element>4.9.9 The <code>td</code> element</a><li><a href=#the-th-element>4.9.10 The <code>th</code> element</a><li><a href=#attributes-common-to-td-and-th-elements>4.9.11 Attributes common to <code>td</code> and <code>th</code> elements</a><li><a href=#processing-model-3>4.9.12 Processing model</a><ol><li><a href=#forming-a-table>4.9.12.1 Forming a table</a><li><a href=#header-and-data
-cell-semantics>4.9.12.2 Forming relationships between data cells and header cells</a></ol><li><a href=#table-sorting-model>4.9.13 Table sorting model</a><li><a href=#table-examples>4.9.14 Examples</a></ol><li><a href=#forms>4.10 Forms</a><ol><li><a href=#introduction-5>4.10.1 Introduction</a><ol><li><a href="#writing-a-form's-user-interface">4.10.1.1 Writing a form's user interface</a><li><a href=#implementing-the-server-side-processing-for-a-form>4.10.1.2 Implementing the server-side processing for a form</a><li><a href=#configuring-a-form-to-communicate-with-a-server>4.10.1.3 Configuring a form to communicate with a server</a><li><a href=#client-side-form-validation>4.10.1.4 Client-side form validation</a><li><a href=#enabling-client-side-automatic-filling-of-form-controls>4.10.1.5 Enabling client-side automatic filling of form controls</a><li><a href=#improving-the-user-experience-on-mobile-devices>4.10.1.6 Improving the user experience on mobile devices</a><li><a href=#
the-difference-between-the-field-type,-the-autofill-field-name,-and-the-input-modality>4.10.1.7 The difference between the field type, the autofill field name, and the input modality</a><li><a href=#input-author-notes>4.10.1.8 Date, time, and number formats</a></ol><li><a href=#categories>4.10.2 Categories</a><li><a href=#the-form-element>4.10.3 The <code>form</code> element</a><li><a href=#the-label-element>4.10.4 The <code>label</code> element</a><li><a href=#the-input-element>4.10.5 The <code>input</code> element</a><ol><li><a href=#states-of-the-type-attribute>4.10.5.1 States of the <code>type</code> attribute</a><ol><li><a href="#hidden-state-(type=hidden)">4.10.5.1.1 Hidden state (<code>type=hidden</code>)</a><li><a href="#text-(type=text)-state-and-search-state-(type=search)">4.10.5.1.2 Text (<code>type=text</code>) state and Search state (<code>type=search</code>)</a><li><a href="#telephone-state-(type=tel)">4.10.5.1.3 Telephone state (<code>type=tel</code>)</a><li><
a href="#url-state-(type=url)">4.10.5.1.4 URL state (<code>type=url</code>)</a><li><a href="#e-mail-state-(type=email)">4.10.5.1.5 E-mail state (<code>type=email</code>)</a><li><a href="#password-state-(type=password)">4.10.5.1.6 Password state (<code>type=password</code>)</a><li><a href="#date-and-time-state-(type=datetime)">4.10.5.1.7 Date and Time state (<code>type=datetime</code>)</a><li><a href="#date-state-(type=date)">4.10.5.1.8 Date state (<code>type=date</code>)</a><li><a href="#month-state-(type=month)">4.10.5.1.9 Month state (<code>type=month</code>)</a><li><a href="#week-state-(type=week)">4.10.5.1.10 Week state (<code>type=week</code>)</a><li><a href="#time-state-(type=time)">4.10.5.1.11 Time state (<code>type=time</code>)</a><li><a href="#local-date-and-time-state-(type=datetime-local)">4.10.5.1.12 Local Date and Time state (<code>type=datetime-local</code>)</a><li><a href="#number-state-(type=number)">4.10.5.1.13 Number state (<code>type=number</code>)</a><li>
<a href="#range-state-(type=range)">4.10.5.1.14 Range state (<code>type=range</code>)</a><li><a href="#color-state-(type=color)">4.10.5.1.15 Colour state (<code>type=color</code>)</a><li><a href="#checkbox-state-(type=checkbox)">4.10.5.1.16 Checkbox state (<code>type=checkbox</code>)</a><li><a href="#radio-button-state-(type=radio)">4.10.5.1.17 Radio Button state (<code>type=radio</code>)</a><li><a href="#file-upload-state-(type=file)">4.10.5.1.18 File Upload state (<code>type=file</code>)</a><li><a href="#submit-button-state-(type=submit)">4.10.5.1.19 Submit Button state (<code>type=submit</code>)</a><li><a href="#image-button-state-(type=image)">4.10.5.1.20 Image Button state (<code>type=image</code>)</a><li><a href="#reset-button-state-(type=reset)">4.10.5.1.21 Reset Button state (<code>type=reset</code>)</a><li><a href="#button-state-(type=button)">4.10.5.1.22 Button state (<code>type=button</code>)</a></ol><li><a href=#input-impl-notes>4.10.5.2 Implemention notes regard
ing localization of form controls</a><li><a href=#common-input-element-attributes>4.10.5.3 Common <code>input</code> element attributes</a><ol><li><a href=#the-maxlength-and-minlength-attributes>4.10.5.3.1 The <code>maxlength</code> and <code>minlength</code> attributes</a><li><a href=#the-size-attribute>4.10.5.3.2 The <code>size</code> attribute</a><li><a href=#the-readonly-attribute>4.10.5.3.3 The <code>readonly</code> attribute</a><li><a href=#the-required-attribute>4.10.5.3.4 The <code>required</code> attribute</a><li><a href=#the-multiple-attribute>4.10.5.3.5 The <code>multiple</code> attribute</a><li><a href=#the-pattern-attribute>4.10.5.3.6 The <code>pattern</code> attribute</a><li><a href=#the-min-and-max-attributes>4.10.5.3.7 The <code>min</code> and <code>max</code> attributes</a><li><a href=#the-step-attribute>4.10.5.3.8 The <code>step</code> attribute</a><li><a href=#the-list-attribute>4.10.5.3.9 The <code>list</code> attribute</a><li><a href=#the-placeholder-att
ribute>4.10.5.3.10 The <code>placeholder</code> attribute</a></ol><li><a href=#common-input-element-apis>4.10.5.4 Common <code>input</code> element APIs</a><li><a href=#common-input-element-events>4.10.5.5 Common event behaviours</a></ol><li><a href=#the-button-element>4.10.6 The <code>button</code> element</a><li><a href=#the-select-element>4.10.7 The <code>select</code> element</a><li><a href=#the-datalist-element>4.10.8 The <code>datalist</code> element</a><li><a href=#the-optgroup-element>4.10.9 The <code>optgroup</code> element</a><li><a href=#the-option-element>4.10.10 The <code>option</code> element</a><li><a href=#the-textarea-element>4.10.11 The <code>textarea</code> element</a><li><a href=#the-keygen-element>4.10.12 The <code>keygen</code> element</a><li><a href=#the-output-element>4.10.13 The <code>output</code> element</a><li><a href=#the-progress-element>4.10.14 The <code>progress</code> element</a><li><a href=#the-meter-element>4.10.15 The <code>meter</code> el
ement</a><li><a href=#the-fieldset-element>4.10.16 The <code>fieldset</code> element</a><li><a href=#the-legend-element>4.10.17 The <code>legend</code> element</a><li><a href=#form-control-infrastructure>4.10.18 Form control infrastructure</a><ol><li><a href="#a-form-control's-value">4.10.18.1 A form control's value</a><li><a href=#mutability>4.10.18.2 Mutability</a><li><a href=#association-of-controls-and-forms>4.10.18.3 Association of controls and forms</a></ol><li><a href=#attributes-common-to-form-controls>4.10.19 Attributes common to form controls</a><ol><li><a href=#naming-form-controls:-the-name-attribute>4.10.19.1 Naming form controls: the <code>name</code> attribute</a><li><a href=#submitting-element-directionality:-the-dirname-attribute>4.10.19.2 Submitting element directionality: the <code>dirname</code> attribute</a><li><a href=#limiting-user-input-length:-the-maxlength-attribute>4.10.19.3 Limiting user input length: the <code>maxlength</code> attribute</a><li><a
href=#setting-minimum-input-length-requirements:-the-minlength-attribute>4.10.19.4 Setting minimum input length requirements: the <code>minlength</code> attribute</a><li><a href=#enabling-and-disabling-form-controls:-the-disabled-attribute>4.10.19.5 Enabling and disabling form controls: the <code>disabled</code> attribute</a><li><a href=#form-submission>4.10.19.6 Form submission</a><ol><li><a href=#autofocusing-a-form-control:-the-autofocus-attribute>4.10.19.6.1 Autofocusing a form control: the <code>autofocus</code> attribute</a></ol><li><a href=#input-modalities:-the-inputmode-attribute>4.10.19.7 Input modalities: the <code>inputmode</code> attribute</a><li><a href=#autofill>4.10.19.8 Autofill</a><ol><li><a href=#autofilling-form-controls:-the-autocomplete-attribute>4.10.19.8.1 Autofilling form controls: the <code>autocomplete</code> attribute</a><li><a href=#processing-model-4>4.10.19.8.2 Processing model</a><li><a href=#user-interface-for-bulk-autofill>4.10.19.8.3 User
interface for bulk autofill</a><li><a href=#the-autocompleteerrorevent-interface>4.10.19.8.4 The <code>AutocompleteErrorEvent</code> interface</a></ol></ol><li><a href=#textFieldSelection>4.10.20 APIs for the text field selections</a><li><a href=#constraints>4.10.21 Constraints</a><ol><li><a href=#definitions>4.10.21.1 Definitions</a><li><a href=#constraint-validation>4.10.21.2 Constraint validation</a><li><a href=#the-constraint-validation-api>4.10.21.3 The constraint validation API</a><li><a href=#security-forms>4.10.21.4 Security</a></ol><li><a href=#form-submission-2>4.10.22 Form submission</a><ol><li><a href=#introduction-6>4.10.22.1 Introduction</a><li><a href=#implicit-submission>4.10.22.2 Implicit submission</a><li><a href=#form-submission-algorithm>4.10.22.3 Form submission algorithm</a><li><a href=#constructing-form-data-set>4.10.22.4 Constructing the form data set</a><li><a href=#selecting-a-form-submission-encoding>4.10.22.5 Selecting a form submission encoding</
a><li><a href=#url-encoded-form-data>4.10.22.6 URL-encoded form data</a><li><a href=#multipart-form-data>4.10.22.7 Multipart form data</a><li><a href=#plain-text-form-data>4.10.22.8 Plain text form data</a></ol><li><a href=#resetting-a-form>4.10.23 Resetting a form</a></ol><li><a href=#interactive-elements>4.11 Interactive elements</a><ol><li><a href=#the-details-element>4.11.1 The <code>details</code> element</a><li><a href=#the-summary-element>4.11.2 The <code>summary</code> element</a><li><a href=#the-menu-element>4.11.3 The <code>menu</code> element</a><li><a href=#the-menuitem-element>4.11.4 The <code>menuitem</code> element</a><li><a href=#context-menus>4.11.5 Context menus</a><ol><li><a href=#declaring-a-context-menu>4.11.5.1 Declaring a context menu</a><li><a href=#processing-model-5>4.11.5.2 Processing model</a><li><a href=#the-relatedevent-interfaces>4.11.5.3 The <code>RelatedEvent</code> interfaces</a></ol><li><a href=#commands>4.11.6 Commands</a><ol><li><a href=#
facets-2>4.11.6.1 Facets</a><li><a href=#using-the-a-element-to-define-a-command>4.11.6.2 Using the <code>a</code> element to define a command</a><li><a href=#using-the-button-element-to-define-a-command>4.11.6.3 Using the <code>button</code> element to define a command</a><li><a href=#using-the-input-element-to-define-a-command>4.11.6.4 Using the <code>input</code> element to define a command</a><li><a href=#using-the-option-element-to-define-a-command>4.11.6.5 Using the <code>option</code> element to define a command</a><li><a href=#using-the-menuitem-element-to-define-a-command>4.11.6.6 Using the <code>menuitem</code> element to define a
command</a><li><a href=#using-the-command-attribute-on-menuitem-elements-to-define-a-command-indirectly>4.11.6.7 Using the <code>command</code> attribute on <code>menuitem</code> elements to define
a command indirectly</a><li><a href=#using-the-accesskey-attribute-on-a-label-element-to-define-a-command>4.11.6.8 Using the <code>accesskey</code> attribute
on a <code>label</code> element to define a command</a><li><a href=#using-the-accesskey-attribute-on-a-legend-element-to-define-a-command>4.11.6.9 Using the <code>accesskey</code> attribute
@@ -600,7 +600,7 @@
<p>To avoid exposing Web authors to the complexities of multithreading, the HTML and DOM APIs are
designed such that no script can ever detect the simultaneous execution of other scripts. Even
- with <a href=#worker id=serialisability-of-script-execution:worker>workers</a>, the intent is that the behavior of implementations can
+ with <a href=#worker id=serialisability-of-script-execution:worker>workers</a>, the intent is that the behaviour of implementations can
be thought of as completely serialising the execution of all scripts in all <a href=#browsing-context id=serialisability-of-script-execution:browsing-context>browsing contexts</a>.</p>
<p class=note>The <code id=serialisability-of-script-execution:dom-navigator-yieldforstorageupdates><a href=#dom-navigator-yieldforstorageupdates>navigator.yieldForStorageUpdates()</a></code> method, in
@@ -1264,7 +1264,7 @@
<p>The syntax of HTML is constrained to avoid a wide variety of problems.</p>
- <dl><dt>Unintuitive error-handling behavior<dd>
+ <dl><dt>Unintuitive error-handling behaviour<dd>
<p>Certain invalid syntax constructs, when parsed, result in DOM trees that are highly
unintuitive.</p>
@@ -1284,11 +1284,11 @@
more bizarre and convoluted error handling rules, user agents are permitted to fail whenever
encountering a <a href=#parse-error id=syntax-errors:parse-error>parse error</a>.</p>
- <dt>Errors where the error-handling behavior is not compatible with streaming user agents<dd>
+ <dt>Errors where the error-handling behaviour is not compatible with streaming user agents<dd>
- <p>Some error-handling behavior, such as the behavior for the <code><table><hr>...</code> example mentioned above, are incompatible with streaming
+ <p>Some error-handling behaviour, such as the behaviour for the <code><table><hr>...</code> example mentioned above, are incompatible with streaming
user agents (user agents that process HTML files in one pass, without storing state). To avoid
- interoperability problems with such user agents, any syntax resulting in such behavior is
+ interoperability problems with such user agents, any syntax resulting in such behaviour is
considered invalid.</p>
<dt>Errors that can result in infoset coercion<dd>
@@ -1372,7 +1372,7 @@
<div class=example>
<p>Another example of this is the DOCTYPE, which is required to trigger <a href=#no-quirks-mode id=syntax-errors:no-quirks-mode>no-quirks
- mode</a>, because the behavior of legacy user agents in <a href=#quirks-mode id=syntax-errors:quirks-mode>quirks mode</a> is often
+ mode</a>, because the behaviour of legacy user agents in <a href=#quirks-mode id=syntax-errors:quirks-mode>quirks mode</a> is often
largely undocumented.</p>
</div>
@@ -1477,7 +1477,7 @@
<dt>Cases where the default styles are likely to lead to confusion<dd>
- <p>Certain elements have default styles or behaviors that make certain combinations likely to
+ <p>Certain elements have default styles or behaviours that make certain combinations likely to
lead to confusion. Where these have equivalent alternatives without this problem, the confusing
combinations are disallowed.</p>
@@ -1491,7 +1491,7 @@
<p class=example>Another example would be the way <a href=#interactive-content-2 id=restrictions-on-content-models-and-on-attribute-values:interactive-content-2>interactive content</a> cannot be
nested. For example, a <code id=restrictions-on-content-models-and-on-attribute-values:the-button-element><a href=#the-button-element>button</a></code> element cannot contain a <code id=restrictions-on-content-models-and-on-attribute-values:the-textarea-element><a href=#the-textarea-element>textarea</a></code>
- element. This is because the default behavior of such nesting interactive elements would be
+ element. This is because the default behaviour of such nesting interactive elements would be
highly confusing to users. Instead of nesting these elements, they can be placed side by
side.</p>
@@ -2053,7 +2053,7 @@
<p>User agents that are designated as supporting the suggested default rendering must, while so
designated, implement the rules in <a href=#rendering>the rendering section</a> that that
- section defines as the behavior that user agents are <em>expected</em> to implement.</p>
+ section defines as the behaviour that user agents are <em>expected</em> to implement.</p>
<dt id=non-scripted>User agents with no scripting support<dd>
@@ -2173,7 +2173,7 @@
<p>Some conformance requirements are phrased as requirements on elements, attributes, methods or
objects. Such requirements fall into two categories: those describing content model restrictions,
- and those describing implementation behavior. Those in the former category are requirements on
+ and those describing implementation behaviour. Those in the former category are requirements on
documents and authoring tools. Those in the second category are requirements on user agents.
Similarly, some conformance requirements are phrased as requirements on authors; such requirements
are to be interpreted as conformance requirements on the documents that authors produce. (In other
@@ -2936,8 +2936,8 @@
<p class=note>Implementors are strongly urged to carefully examine any third-party libraries
they might consider using to implement the parsing of syntaxes described below. For example, date
- libraries are likely to implement error handling behavior that differs from what is required in
- this specification, since error-handling behavior is often not defined in specifications that
+ libraries are likely to implement error handling behaviour that differs from what is required in
+ this specification, since error-handling behaviour is often not defined in specifications that
describe date syntaxes similar to those used in this specification, and thus implementations tend
to vary greatly in how they handle errors.</p>
@@ -4520,7 +4520,7 @@
<h4 id=terminology-3>2.6.1 Terminology</h4>
<p id=concept-http-equivalent>User agents can implement a variety of transfer protocols, but
- this specification mostly defines behavior in terms of HTTP. <a href=#refsHTTP>[HTTP]</a></p>
+ this specification mostly defines behaviour in terms of HTTP. <a href=#refsHTTP>[HTTP]</a></p>
<p>The <dfn id=concept-http-equivalent-get>HTTP GET method</dfn> is equivalent to the default
retrieval action of the protocol. For example, RETR in FTP. Such actions are idempotent and safe,
@@ -5022,7 +5022,7 @@
<p>If a reflecting IDL attribute has an unsigned integer type (<code id=reflecting-content-attributes-in-idl-attributes:idl-unsigned-long-2><a href=#idl-unsigned-long>unsigned long</a></code>) that is <dfn id=limited-to-only-non-negative-numbers-greater-than-zero>limited to only non-negative numbers
- greater than zero</dfn>, then the behavior is similar to the previous case, but zero is not
+ greater than zero</dfn>, then the behaviour is similar to the previous case, but zero is not
allowed. On getting, the content attribute must first be parsed according to the <a href=#rules-for-parsing-non-negative-integers id=reflecting-content-attributes-in-idl-attributes:rules-for-parsing-non-negative-integers-3>rules for
parsing non-negative integers</a>, and if that is successful, and the value is in the range 1
to 2147483647 inclusive, the resulting value must be returned. If, on the other hand, it fails or
@@ -5043,7 +5043,7 @@
number</a> and then that string must be used as the new content attribute value.</p>
<p>If a reflecting IDL attribute has a floating-point number type (<code id=reflecting-content-attributes-in-idl-attributes:idl-double-2><a href=#idl-double>double</a></code> or <code id=reflecting-content-attributes-in-idl-attributes:idl-unrestricted-double-2><a href=#idl-unrestricted-double>unrestricted
- double</a></code>) that is <dfn id=limited-to-numbers-greater-than-zero>limited to numbers greater than zero</dfn>, then the behavior is
+ double</a></code>) that is <dfn id=limited-to-numbers-greater-than-zero>limited to numbers greater than zero</dfn>, then the behaviour is
similar to the previous case, but zero and negative values are not allowed. On getting, the
content attribute must be parsed according to the <a href=#rules-for-parsing-floating-point-number-values id=reflecting-content-attributes-in-idl-attributes:rules-for-parsing-floating-point-number-values-2>rules for parsing floating-point number
values</a>, and if that is successful and the value is greater than 0.0, the resulting value
@@ -5310,7 +5310,7 @@
<p>On getting, the <dfn id=dom-htmloptionscollection-length><code>length</code></dfn>
attribute must return the number of nodes <a href=#represented-by-the-collection id=the-htmloptionscollection-interface:represented-by-the-collection>represented by the collection</a>.</p>
- <p>On setting, the behavior depends on whether the new value is equal to, greater than, or less
+ <p>On setting, the behaviour depends on whether the new value is equal to, greater than, or less
than the number of nodes <a href=#represented-by-the-collection id=the-htmloptionscollection-interface:represented-by-the-collection-2>represented by the collection</a> at that time. If the number is
the same, then setting the attribute must do nothing. If the new value is greater, then <var>n</var> new <code id=the-htmloptionscollection-interface:the-option-element-4><a href=#the-option-element>option</a></code> elements with no attributes and no child nodes must be
appended to the <code id=the-htmloptionscollection-interface:the-select-element-2><a href=#the-select-element>select</a></code> element on which the <code id=the-htmloptionscollection-interface:htmloptionscollection-3><a href=#htmloptionscollection>HTMLOptionsCollection</a></code> is
@@ -5614,7 +5614,7 @@
<var>memory</var> as the "<var>memory</var>" argument.<li><p>Return <var>output</var>.</ol>
<p>The <dfn id=internal-structured-cloning-algorithm>internal structured cloning algorithm</dfn> is always called with two arguments,
- <var>input</var> and <var>memory</var>, and its behavior is as follows:</p>
+ <var>input</var> and <var>memory</var>, and its behaviour is as follows:</p>
<ol><li><p>If <var>input</var> is the source object of a pair of objects in <var>memory</var>, then
return the destination object in that pair of objects and abort these steps.<li><p>If <var>input</var> is a primitive value, then return that value and abort these
@@ -6831,7 +6831,7 @@
<h6 id=metadata-content>3.2.4.2.1 Metadata content</h6>
- <p><dfn id=metadata-content-2>Metadata content</dfn> is content that sets up the presentation or behavior of the rest of
+ <p><dfn id=metadata-content-2>Metadata content</dfn> is content that sets up the presentation or behaviour of the rest of
the content, or that sets up the relationship of the document with other documents, or that
conveys other "out of band" information.</p>
@@ -7279,7 +7279,7 @@
<p>The XML specification also allows the use of the <code id=global-attributes:attr-xml-space><a href=#attr-xml-space>xml:space</a></code>
attribute in the <a href=#xml-namespace id=global-attributes:xml-namespace>XML namespace</a> on any element in an <a href=#xml-documents id=global-attributes:xml-documents-2>XML
document</a>. This attribute has no effect on <a href=#html-elements id=global-attributes:html-elements-5>HTML elements</a>, as the default
- behavior in HTML is to preserve whitespace. <a href=#refsXML>[XML]</a></p>
+ behaviour in HTML is to preserve whitespace. <a href=#refsXML>[XML]</a></p>
<p class=note>There is no way to serialise the <code id=global-attributes:attr-xml-space-2><a href=#attr-xml-space>xml:space</a></code>
attribute on <a href=#html-elements id=global-attributes:html-elements-6>HTML elements</a> in the <code id=global-attributes:text/html><a href=#text/html>text/html</a></code> syntax.</p>
@@ -7970,7 +7970,7 @@
- <p>User agents must not derive any implementation behavior from these attributes or values.
+ <p>User agents must not derive any implementation behaviour from these attributes or values.
Specifications intended for user agents must not define these attributes to have any meaningful
values.</p>
@@ -9195,7 +9195,7 @@
<p>The <dfn id=attr-link-crossorigin><code>crossorigin</code></dfn> attribute is a <a href=#cors-settings-attribute id=the-link-element:cors-settings-attribute>CORS
settings attribute</a>. It is intended for use with external resource links.</p>
- <p>The exact behavior for links to external resources depends on the exact relationship, as
+ <p>The exact behaviour for links to external resources depends on the exact relationship, as
defined for the relevant link type. Some of the attributes control whether or not the external
resource is to be applied (as defined below).</p>
@@ -9381,7 +9381,7 @@
- <p>The <a href=#activation-behavior id=the-link-element:activation-behavior>activation behavior</a> of <code id=the-link-element:the-link-element-18><a href=#the-link-element>link</a></code> elements that create <a href=#hyperlink id=the-link-element:hyperlink-5>hyperlinks</a> is to run the following steps:</p>
+ <p>The <a href=#activation-behaviour id=the-link-element:activation-behaviour>activation behaviour</a> of <code id=the-link-element:the-link-element-18><a href=#the-link-element>link</a></code> elements that create <a href=#hyperlink id=the-link-element:hyperlink-5>hyperlinks</a> is to run the following steps:</p>
<ol><li><p>If the <code id=the-link-element:the-link-element-19><a href=#the-link-element>link</a></code> element's <a id=the-link-element:node-document-3 href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is not <a href=#fully-active id=the-link-element:fully-active>fully active</a>,
then abort these steps.<li><p><a href=#following-hyperlinks-2 id=the-link-element:following-hyperlinks-2-2>Follow the hyperlink</a> created by the
@@ -9953,13 +9953,13 @@
directives</dfn> may, under certain conditions, be registered in the <a href=https://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki PragmaExtensions page</a>. <a href=#refsWHATWGWIKI>[WHATWGWIKI]</a></p>
<p>Such extensions must use a name that is identical to an HTTP header registered in the Permanent
- Message Header Field Registry, and must have behavior identical to that described for the HTTP
+ Message Header Field Registry, and must have behaviour identical to that described for the HTTP
header. <a href=#refsIANAPERMHEADERS>[IANAPERMHEADERS]</a></p>
<p>Pragma directives corresponding to headers describing metadata, or not requiring specific user
agent processing, must not be registered; instead, use <a href=#concept-meta-extensions id=other-pragma-directives:concept-meta-extensions>metadata names</a>. Pragma directives corresponding to headers
that affect the HTTP processing model (e.g. caching) must not be registered, as they would result
- in HTTP-level behavior being different for user agents that implement HTML than for user agents
+ in HTTP-level behaviour being different for user agents that implement HTML than for user agents
that do not.</p>
<p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at any time to add a pragma
@@ -13615,7 +13615,7 @@
<pre><article lang="en-US">
<h1>My use of language and my cats</h1>
- <p>My cat's behavior hasn't changed much since her absence, except
+ <p>My cat's behaviour hasn't changed much since her absence, except
that she plays her new physique to the neighbors regularly, in an
attempt to get pets.</p>
<div lang="en-GB">
@@ -13697,7 +13697,7 @@
attributes may be used to indicate to the user the likely nature of the target resource before the
user follows the link.</p>
- <p>The <a href=#activation-behavior id=the-a-element:activation-behavior>activation behavior</a> of <code id=the-a-element:the-a-element-6><a href=#the-a-element>a</a></code> elements that create <a href=#hyperlink id=the-a-element:hyperlink-4>hyperlinks</a> is to run the following steps:</p>
+ <p>The <a href=#activation-behaviour id=the-a-element:activation-behaviour>activation behaviour</a> of <code id=the-a-element:the-a-element-6><a href=#the-a-element>a</a></code> elements that create <a href=#hyperlink id=the-a-element:hyperlink-4>hyperlinks</a> is to run the following steps:</p>
<ol><li><p>If the <code id=the-a-element:the-a-element-7><a href=#the-a-element>a</a></code> element's <a id=the-a-element:node-document href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is not <a href=#fully-active id=the-a-element:fully-active>fully active</a>, then abort these steps.<li>
@@ -15973,7 +15973,7 @@
context</a> that will be used. User agents use this name when
<a href=#following-hyperlinks-2 id=links-created-by-a-and-area-elements:following-hyperlinks-2>following hyperlinks</a>.</p>
- <p>When an <code id=links-created-by-a-and-area-elements:the-a-element-4><a href=#the-a-element>a</a></code> or <code id=links-created-by-a-and-area-elements:the-area-element-4><a href=#the-area-element>area</a></code> element's <a href=#activation-behavior id=links-created-by-a-and-area-elements:activation-behavior>activation behavior</a> is
+ <p>When an <code id=links-created-by-a-and-area-elements:the-a-element-4><a href=#the-a-element>a</a></code> or <code id=links-created-by-a-and-area-elements:the-area-element-4><a href=#the-area-element>area</a></code> element's <a href=#activation-behaviour id=links-created-by-a-and-area-elements:activation-behaviour>activation behaviour</a> is
invoked, the user agent may allow the user to indicate a preference regarding whether the
hyperlink is to be used for <a href=#navigate id=links-created-by-a-and-area-elements:navigate>navigation</a> or whether the resource it
specifies is to be downloaded.</p>
@@ -16249,7 +16249,7 @@
<code id=hyperlink-auditing:document><a href=#document>Document</a></code> containing the <a href=#hyperlink id=hyperlink-auditing:hyperlink-2>hyperlink</a> (as described below). (Tokens that fail to resolve are ignored.) This may be done in parallel
with the primary request, and is independent of the result of that request.</p>
- <p>User agents should allow the user to adjust this behavior, for example in conjunction with a
+ <p>User agents should allow the user to adjust this behaviour, for example in conjunction with a
setting that disables the sending of HTTP <code id=hyperlink-auditing:http-referer><a href=#http-referer>Referer</a></code> (sic)
headers. Based on the user's preferences, UAs may either <a href=#ignore id=hyperlink-auditing:ignore>ignore</a> the <code id=hyperlink-auditing:ping-3><a href=#ping>ping</a></code> attribute altogether, or selectively ignore URLs in the
list (e.g. ignoring any third-party URLs).</p>
@@ -20815,8 +20815,8 @@
<p>The <code id=the-embed-element:htmlembedelement><a href=#htmlembedelement>HTMLEmbedElement</a></code> object representing the element must expose the scriptable
interface of the <a href=#plugin id=the-embed-element:plugin-18>plugin</a> instantiated for the <code id=the-embed-element:the-embed-element-25><a href=#the-embed-element>embed</a></code> element, if any. At a
minimum, this interface must implement the <dfn id=dom-embed-caller>legacy caller
- operation</dfn>. (It is suggested that the default behavior of this legacy caller operation, e.g.
- the behavior of the default plugin's legacy caller operation, be to throw a
+ operation</dfn>. (It is suggested that the default behaviour of this legacy caller operation, e.g.
+ the behaviour of the default plugin's legacy caller operation, be to throw a
<code id=the-embed-element:notsupportederror><a href=#notsupportederror>NotSupportedError</a></code> exception.)</p>
@@ -20961,7 +20961,7 @@
<ol><li>
<p>If the user has indicated a preference that this <code id=the-object-element:the-object-element-6><a href=#the-object-element>object</a></code> element's <a href=#fallback-content id=the-object-element:fallback-content-2>fallback
- content</a> be shown instead of the element's usual behavior, then jump to the step below
+ content</a> be shown instead of the element's usual behaviour, then jump to the step below
labeled <i>fallback</i>.</p>
<p class=note>For example, a user could ask for the element's <a href=#fallback-content id=the-object-element:fallback-content-3>fallback content</a> to
@@ -21335,7 +21335,7 @@
<p>All <code id=the-object-element:the-object-element-42><a href=#the-object-element>object</a></code> elements have a <dfn id=dom-object-caller>legacy caller
operation</dfn>. If the <code id=the-object-element:the-object-element-43><a href=#the-object-element>object</a></code> element has an instantiated <a href=#plugin id=the-object-element:plugin-25>plugin</a> that
supports a scriptable interface that defines a legacy caller operation, then that must be the
- behavior of the object's legacy caller operation. Otherwise, the object's legacy caller operation
+ behaviour of the object's legacy caller operation. Otherwise, the object's legacy caller operation
must be to throw a <code id=the-object-element:notsupportederror><a href=#notsupportederror>NotSupportedError</a></code> exception.</p>
@@ -21850,7 +21850,7 @@
<p>If the author isn't sure if user agents will all be able to render the media resources
provided, the author can listen to the <code id=the-source-element:event-error><a href=#event-error>error</a></code> event on the last
- <code id=the-source-element:the-source-element-5><a href=#the-source-element>source</a></code> element and trigger fallback behavior:</p>
+ <code id=the-source-element:the-source-element-5><a href=#the-source-element>source</a></code> element and trigger fallback behaviour:</p>
<pre><script>
function fallback(video) {
@@ -22639,7 +22639,7 @@
<ol><li>
- <p>Optionally, run the following substeps. This is the expected behavior if the user agent
+ <p>Optionally, run the following substeps. This is the expected behaviour if the user agent
intends to not attempt to fetch the resource until the user requests it explicitly (e.g. as
a way to implement the <code id=loading-the-media-resource:attr-media-preload><a href=#attr-media-preload>preload</a></code> attribute's <code id=loading-the-media-resource:attr-media-preload-none><a href=#attr-media-preload-none>none</a></code> keyword).</p>
@@ -23446,7 +23446,7 @@
<p class=note>User agents do not need to support autoplay, and it is suggested that user
agents honor user preferences on the matter. Authors are urged to use the <code id=ready-states:attr-media-autoplay-2><a href=#attr-media-autoplay>autoplay</a></code> attribute rather than using script to force the
- video to play, so as to allow the user to override the behavior if so desired.</p>
+ video to play, so as to allow the user to override the behaviour if so desired.</p>
<p>In any case, the user agent must finally <a href=#queue-a-task id=ready-states:queue-a-task-11>queue a task</a> to <a href=#fire-a-simple-event id=ready-states:fire-a-simple-event-11>fire a simple
event</a> named <code id=ready-states:event-media-canplaythrough><a href=#event-media-canplaythrough>canplaythrough</a></code> at the element.</p>
@@ -23478,7 +23478,7 @@
<p class=note>Authors are urged to use the <code id=ready-states:attr-media-autoplay-3><a href=#attr-media-autoplay>autoplay</a></code>
attribute rather than using script to trigger automatic playback, as this allows the user to
override the automatic playback when it is not desired, e.g. when using a screen reader. Authors
- are also encouraged to consider not using the automatic playback behavior at all, and instead to
+ are also encouraged to consider not using the automatic playback behaviour at all, and instead to
let the user agent wait for the user to start playback explicitly.</p>
@@ -24061,7 +24061,7 @@
value (which would equal the time of the last frame, and might be positive Infinity).</p>
<p class=note>The range might be continuously changing, e.g. if the user agent is buffering a
- sliding window on an infinite stream. This is the behavior seen with DVRs viewing live TV, for
+ sliding window on an infinite stream. This is the behaviour seen with DVRs viewing live TV, for
instance.</p>
<p>User agents should adopt adopt a very liberal and optimistic view of what is seekable. User
@@ -26455,7 +26455,7 @@
element</a> without affecting the <code id=user-interface:mediacontroller-6><a href=#mediacontroller>MediaController</a></code>, but such features are
considered relatively advanced and unlikely to be useful to most users.</p>
- <p>The <a href=#activation-behavior id=user-interface:activation-behavior>activation behavior</a> of a <a href=#media-element id=user-interface:media-element-16>media element</a> that is <a href=#expose-a-user-interface-to-the-user id=user-interface:expose-a-user-interface-to-the-user-3>exposing a user interface to the user</a> must be
+ <p>The <a href=#activation-behaviour id=user-interface:activation-behaviour>activation behaviour</a> of a <a href=#media-element id=user-interface:media-element-16>media element</a> that is <a href=#expose-a-user-interface-to-the-user id=user-interface:expose-a-user-interface-to-the-user-3>exposing a user interface to the user</a> must be
to run the following steps:</p>
<ol><li><p>If the <a href=#media-element id=user-interface:media-element-17>media element</a> has a <a href=#current-media-controller id=user-interface:current-media-controller-9>current media controller</a>, and that
@@ -27408,7 +27408,7 @@
- <p>The <a href=#activation-behavior id=the-area-element:activation-behavior>activation behavior</a> of <code id=the-area-element:the-area-element-13><a href=#the-area-element>area</a></code> elements is to run the following
+ <p>The <a href=#activation-behaviour id=the-area-element:activation-behaviour>activation behaviour</a> of <code id=the-area-element:the-area-element-13><a href=#the-area-element>area</a></code> elements is to run the following
steps:</p>
<ol><li><p>If the <code id=the-area-element:the-area-element-14><a href=#the-area-element>area</a></code> element's <a id=the-area-element:node-document href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is not <a href=#fully-active id=the-area-element:fully-active>fully active</a>,
@@ -27831,7 +27831,7 @@
<p class=note>The corresponding IDL attributes for <code id=dimension-attributes:dom-img-height><a href=#dom-img-height>img</a></code> and
<code id=dimension-attributes:dom-input-height><a href=#dom-input-height>input</a></code> elements are defined in those respective elements'
- sections, as they are slightly more specific to those elements' other behaviors.</p>
+ sections, as they are slightly more specific to those elements' other behaviours.</p>
@@ -28113,7 +28113,7 @@
element, again in <a href=#tree-order id=the-table-element:tree-order-2>tree order</a>, followed finally by those elements whose parent is a
<code id=the-table-element:the-tfoot-element-17><a href=#the-tfoot-element>tfoot</a></code> element, still in <a href=#tree-order id=the-table-element:tree-order-3>tree order</a>.</p>
- <p>The behavior of the <dfn id=dom-table-insertrow><code>insertRow(<var>index</var>)</code></dfn> method depends on the state of the table. When it is called,
+ <p>The behaviour of the <dfn id=dom-table-insertrow><code>insertRow(<var>index</var>)</code></dfn> method depends on the state of the table. When it is called,
the method must act as required by the first item in the following list of conditions that
describes the state of the table and the <var>index</var> argument:</p>
@@ -30627,7 +30627,7 @@
<hr>
- <p>The <a href=#activation-behavior id=table-sorting-model:activation-behavior>activation behavior</a> of a <a href=#sorting-interface-th-element id=table-sorting-model:sorting-interface-th-element>sorting interface <code>th</code>
+ <p>The <a href=#activation-behaviour id=table-sorting-model:activation-behaviour>activation behaviour</a> of a <a href=#sorting-interface-th-element id=table-sorting-model:sorting-interface-th-element>sorting interface <code>th</code>
element</a> is to <a href=#set-the-sort-key id=table-sorting-model:set-the-sort-key>set the sort key</a> to the <code id=table-sorting-model:the-th-element-20><a href=#the-th-element>th</a></code> element.</p>
<p class=note>The <code id=table-sorting-model:the-table-element-20><a href=#the-table-element>table</a></code> will be sorted the next time the user agent <a href=#perform-a-microtask-checkpoint id=table-sorting-model:perform-a-microtask-checkpoint>performs a microtask checkpoint</a>.</p>
@@ -31753,9 +31753,9 @@
then the first such descendant in <a href=#tree-order id=the-label-element:tree-order>tree order</a> is the <code id=the-label-element:the-label-element-9><a href=#the-label-element>label</a></code> element's
<a href=#labeled-control id=the-label-element:labeled-control-4>labeled control</a>.</p>
- <p>The <code id=the-label-element:the-label-element-10><a href=#the-label-element>label</a></code> element's exact default presentation and behavior, in particular what
- its <a href=#activation-behavior id=the-label-element:activation-behavior>activation behavior</a> might be, if anything, should match the platform's label
- behavior. The <a href=#activation-behavior id=the-label-element:activation-behavior-2>activation behavior</a> of a <code id=the-label-element:the-label-element-11><a href=#the-label-element>label</a></code> element for events targeted
+ <p>The <code id=the-label-element:the-label-element-10><a href=#the-label-element>label</a></code> element's exact default presentation and behaviour, in particular what
+ its <a href=#activation-behaviour id=the-label-element:activation-behaviour>activation behaviour</a> might be, if anything, should match the platform's label
+ behaviour. The <a href=#activation-behaviour id=the-label-element:activation-behaviour-2>activation behaviour</a> of a <code id=the-label-element:the-label-element-11><a href=#the-label-element>label</a></code> element for events targeted
at <a href=#interactive-content-2 id=the-label-element:interactive-content-2-2>interactive content</a> descendants of a <code id=the-label-element:the-label-element-12><a href=#the-label-element>label</a></code> element, and any
descendants of those <a href=#interactive-content-2 id=the-label-element:interactive-content-2-3>interactive content</a> descendants, must be to do nothing.</p>
@@ -31770,7 +31770,7 @@
<pre><label><input type=checkbox name=lost> Lost</label></pre>
- <p>On other platforms, the behavior might be just to focus the control, or do nothing.</p>
+ <p>On other platforms, the behaviour might be just to focus the control, or do nothing.</p>
</div>
@@ -32056,7 +32056,7 @@
<code id=the-input-element:the-input-element-2><a href=#the-input-element>input</a></code> element depends on the state of its
<code id=the-input-element:attr-input-type-6><a href=#attr-input-type>type</a></code> attribute.
The subsections that define each type also clearly define in normative "bookkeeping" sections
- which of these feature apply, and which <dfn id=do-not-apply>do not apply</dfn>, to each type. The behavior of
+ which of these feature apply, and which <dfn id=do-not-apply>do not apply</dfn>, to each type. The behaviour of
these features depends on whether they apply or not, as defined in their various sections (q.v.
for <a href=#common-input-element-attributes>content attributes</a>, for <a href=#common-input-element-apis>APIs</a>, for <a href=#common-input-element-events>events</a>).</p>
@@ -33239,8 +33239,8 @@
<hr>
- <p>When an <code id=the-input-element:the-input-element-15><a href=#the-input-element>input</a></code> element is first created, the element's rendering and behavior must
- be set to the rendering and behavior defined for the <code id=the-input-element:attr-input-type-9><a href=#attr-input-type>type</a></code>
+ <p>When an <code id=the-input-element:the-input-element-15><a href=#the-input-element>input</a></code> element is first created, the element's rendering and behaviour must
+ be set to the rendering and behaviour defined for the <code id=the-input-element:attr-input-type-9><a href=#attr-input-type>type</a></code>
attribute's state, and the <a href=#value-sanitization-algorithm id=the-input-element:value-sanitization-algorithm-3>value sanitization algorithm</a>, if one is defined for the
<code id=the-input-element:attr-input-type-10><a href=#attr-input-type>type</a></code> attribute's state, must be invoked.</p>
@@ -33257,7 +33257,7 @@
IDL attribute in any mode other than the <i id=the-input-element:dom-input-value-value-11><a href=#dom-input-value-value>value</a></i> mode, and the
new state of the element's <code id=the-input-element:attr-input-type-15><a href=#attr-input-type>type</a></code> attribute puts the <code id=the-input-element:dom-input-value-8><a href=#dom-input-value>value</a></code> IDL attribute in the <i id=the-input-element:dom-input-value-value-12><a href=#dom-input-value-value>value</a></i> mode, then set the <a href=#concept-fe-value id=the-input-element:concept-fe-value-10>value</a> of the element to the value of the <code id=the-input-element:attr-input-value-6><a href=#attr-input-value>value</a></code> content attribute, if there is one, or the empty string
otherwise, and then set the control's <a href=#concept-input-value-dirty-flag id=the-input-element:concept-input-value-dirty-flag-5>dirty value
- flag</a> to false.<li><p>Update the element's rendering and behavior to the new state's.<li><p><dfn id=signal-a-type-change>Signal a type change</dfn> for the element. (The <a href="#radio-button-state-(type=radio)" id="the-input-element:radio-button-state-(type=radio)-3">Radio Button</a> state uses this, in particular.)<li><p>Invoke the <a href=#value-sanitization-algorithm id=the-input-element:value-sanitization-algorithm-4>value sanitization algorithm</a>, if one is defined for the <code id=the-input-element:attr-input-type-16><a href=#attr-input-type>type</a></code> attribute's new state.</ol>
+ flag</a> to false.<li><p>Update the element's rendering and behaviour to the new state's.<li><p><dfn id=signal-a-type-change>Signal a type change</dfn> for the element. (The <a href="#radio-button-state-(type=radio)" id="the-input-element:radio-button-state-(type=radio)-3">Radio Button</a> state uses this, in particular.)<li><p>Invoke the <a href=#value-sanitization-algorithm id=the-input-element:value-sanitization-algorithm-4>value sanitization algorithm</a>, if one is defined for the <code id=the-input-element:attr-input-type-16><a href=#attr-input-type>type</a></code> attribute's new state.</ol>
</div>
@@ -33270,7 +33270,7 @@
The <code id=the-input-element:attr-fae-form-2><a href=#attr-fae-form>form</a></code> attribute is used to explicitly associate the <code id=the-input-element:the-input-element-17><a href=#the-input-element>input</a></code> element with its <a href=#form-owner id=the-input-element:form-owner>form owner</a>.
The <code id=the-input-element:attr-fe-autofocus-2><a href=#attr-fe-autofocus>autofocus</a></code> attribute controls focus.
The <code id=the-input-element:attr-fe-inputmode-4><a href=#attr-fe-inputmode>inputmode</a></code> attribute controls the user interface's input modality for the control.
- The <code id=the-input-element:attr-fe-autocomplete-4><a href=#attr-fe-autocomplete>autocomplete</a></code> attribute controls how the user agent provides autofill behavior.
+ The <code id=the-input-element:attr-fe-autocomplete-4><a href=#attr-fe-autocomplete>autocomplete</a></code> attribute controls how the user agent provides autofill behaviour.
</p>
@@ -35591,12 +35591,12 @@
activation steps</a> consist of setting the element's <a href=#concept-fe-checked id="checkbox-state-(type=checkbox):concept-fe-checked-3">checkedness</a> to its opposite value (i.e. true if it is false,
false if it is true), and of setting the element's <code id="checkbox-state-(type=checkbox):dom-input-indeterminate-4"><a href=#dom-input-indeterminate>indeterminate</a></code> IDL attribute to false. The <a href=#canceled-activation-steps id="checkbox-state-(type=checkbox):canceled-activation-steps">canceled
activation steps</a> consist of setting the <a href=#concept-fe-checked id="checkbox-state-(type=checkbox):concept-fe-checked-4">checkedness</a> and the element's <code id="checkbox-state-(type=checkbox):dom-input-indeterminate-5"><a href=#dom-input-indeterminate>indeterminate</a></code> IDL attribute back to the values they had
- before the <a href=#pre-click-activation-steps id="checkbox-state-(type=checkbox):pre-click-activation-steps-2">pre-click activation steps</a> were run. The <a href=#activation-behavior id="checkbox-state-(type=checkbox):activation-behavior">activation behavior</a>
+ before the <a href=#pre-click-activation-steps id="checkbox-state-(type=checkbox):pre-click-activation-steps-2">pre-click activation steps</a> were run. The <a href=#activation-behaviour id="checkbox-state-(type=checkbox):activation-behaviour">activation behaviour</a>
is to <a href=#fire-a-simple-event id="checkbox-state-(type=checkbox):fire-a-simple-event">fire a simple event</a> that bubbles named <code id="checkbox-state-(type=checkbox):event-input-input"><a href=#event-input-input>input</a></code> at the element and then <a href=#fire-a-simple-event id="checkbox-state-(type=checkbox):fire-a-simple-event-2">fire a simple event</a>
that bubbles named <code id="checkbox-state-(type=checkbox):event-input-change"><a href=#event-input-change>change</a></code> at the element. </p>
- <p>If the element is not <i id="checkbox-state-(type=checkbox):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="checkbox-state-(type=checkbox):activation-behavior-2">activation
- behavior</a>.</p>
+ <p>If the element is not <i id="checkbox-state-(type=checkbox):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="checkbox-state-(type=checkbox):activation-behaviour-2">activation
+ behaviour</a>.</p>
<p><strong>Constraint validation</strong>: If the element is <i id="checkbox-state-(type=checkbox):concept-input-required"><a href=#concept-input-required>required</a></i> and its <a href=#concept-fe-checked id="checkbox-state-(type=checkbox):concept-fe-checked-5">checkedness</a> is false, then the element is <a href=#suffering-from-being-missing id="checkbox-state-(type=checkbox):suffering-from-being-missing">suffering from
being missing</a>.</p>
@@ -35719,14 +35719,14 @@
<var>R</var>'s <a href=#radio-button-group id="radio-button-state-(type=radio):radio-button-group-5">radio button group</a>, if it still has one, and if so, setting that
element's <a href=#concept-fe-checked id="radio-button-state-(type=radio):concept-fe-checked-8">checkedness</a> to true; or else, if there was no
such element, or that element is no longer in <var>R</var>'s <a href=#radio-button-group id="radio-button-state-(type=radio):radio-button-group-6">radio button group</a>, or
- if <var>R</var> no longer has a <a href=#radio-button-group id="radio-button-state-(type=radio):radio-button-group-7">radio button group</a>, setting <var>R</var>'s <a href=#concept-fe-checked id="radio-button-state-(type=radio):concept-fe-checked-9">checkedness</a> to false. The <a href=#activation-behavior id="radio-button-state-(type=radio):activation-behavior">activation behavior</a> for
+ if <var>R</var> no longer has a <a href=#radio-button-group id="radio-button-state-(type=radio):radio-button-group-7">radio button group</a>, setting <var>R</var>'s <a href=#concept-fe-checked id="radio-button-state-(type=radio):concept-fe-checked-9">checkedness</a> to false. The <a href=#activation-behaviour id="radio-button-state-(type=radio):activation-behaviour">activation behaviour</a> for
<var>R</var> is to <a href=#fire-a-simple-event id="radio-button-state-(type=radio):fire-a-simple-event">fire a simple event</a> that bubbles named <code id="radio-button-state-(type=radio):event-input-input"><a href=#event-input-input>input</a></code> at <var>R</var> and then <a href=#fire-a-simple-event id="radio-button-state-(type=radio):fire-a-simple-event-2">fire a simple event</a>
that bubbles named <code id="radio-button-state-(type=radio):event-input-change"><a href=#event-input-change>change</a></code> at <var>R</var>. </p>
- <p>If the element is not <i id="radio-button-state-(type=radio):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="radio-button-state-(type=radio):activation-behavior-2">activation
- behavior</a>.</p>
+ <p>If the element is not <i id="radio-button-state-(type=radio):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="radio-button-state-(type=radio):activation-behaviour-2">activation
+ behaviour</a>.</p>
<p><strong>Constraint validation</strong>: If an element in the <i id="radio-button-state-(type=radio):radio-button-group-8"><a href=#radio-button-group>radio button group</a></i> is <i id="radio-button-state-(type=radio):concept-input-required"><a href=#concept-input-required>required</a></i>, and all of the <code id="radio-button-state-(type=radio):the-input-element-8"><a href=#the-input-element>input</a></code> elements in the
<i id="radio-button-state-(type=radio):radio-button-group-9"><a href=#radio-button-group>radio button group</a></i> have a <a href=#concept-fe-checked id="radio-button-state-(type=radio):concept-fe-checked-10">checkedness</a> that is
@@ -35825,7 +35825,7 @@
files</a>.</p>
<p>If the element is <i id="file-upload-state-(type=file):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, then the element's
- <a href=#activation-behavior id="file-upload-state-(type=file):activation-behavior">activation behavior</a> is to run the following steps:</p>
+ <a href=#activation-behaviour id="file-upload-state-(type=file):activation-behaviour">activation behaviour</a> is to run the following steps:</p>
<ol><li><p>If the algorithm is not <a href=#allowed-to-show-a-popup id="file-upload-state-(type=file):allowed-to-show-a-popup">allowed to show a popup</a>, then abort these steps
without doing anything else.<li><p>Return, but continue running these steps <a href=#in-parallel id="file-upload-state-(type=file):in-parallel">in parallel</a>.<li><p>Optionally, wait until any prior execution of this algorithm has terminated.</p>
@@ -35847,8 +35847,8 @@
<code id="file-upload-state-(type=file):event-input-input-2"><a href=#event-input-input>input</a></code> at the <code id="file-upload-state-(type=file):the-input-element-5"><a href=#the-input-element>input</a></code> element, and finally
<a href=#fire-a-simple-event id="file-upload-state-(type=file):fire-a-simple-event-4">fire a simple event</a> that bubbles named <code id="file-upload-state-(type=file):event-input-change-2"><a href=#event-input-change>change</a></code> at the <code id="file-upload-state-(type=file):the-input-element-6"><a href=#the-input-element>input</a></code> element.</p>
- <p>If the element is not <i id="file-upload-state-(type=file):concept-fe-mutable-3"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="file-upload-state-(type=file):activation-behavior-2">activation
- behavior</a> and the user agent must not allow the user to change the element's selection.</p>
+ <p>If the element is not <i id="file-upload-state-(type=file):concept-fe-mutable-3"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="file-upload-state-(type=file):activation-behaviour-2">activation
+ behaviour</a> and the user agent must not allow the user to change the element's selection.</p>
<p><strong>Constraint validation</strong>: If the element is <i id="file-upload-state-(type=file):concept-input-required"><a href=#concept-input-required>required</a></i> and the list of <a href=#concept-input-type-file-selected id="file-upload-state-(type=file):concept-input-type-file-selected-4">selected files</a> is empty, then the element is
<a href=#suffering-from-being-missing id="file-upload-state-(type=file):suffering-from-being-missing">suffering from being missing</a>.</p>
@@ -36039,13 +36039,13 @@
<p>If the element is <i id="submit-button-state-(type=submit):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, then the element's
- <a href=#activation-behavior id="submit-button-state-(type=submit):activation-behavior">activation behavior</a> is as follows: if the element has a <a href=#form-owner id="submit-button-state-(type=submit):form-owner">form owner</a>,
+ <a href=#activation-behaviour id="submit-button-state-(type=submit):activation-behaviour">activation behaviour</a> is as follows: if the element has a <a href=#form-owner id="submit-button-state-(type=submit):form-owner">form owner</a>,
and the element's <a id="submit-button-state-(type=submit):node-document" href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is <a href=#fully-active id="submit-button-state-(type=submit):fully-active">fully active</a>,
<a href=#concept-form-submit id="submit-button-state-(type=submit):concept-form-submit">submit</a> the <a href=#form-owner id="submit-button-state-(type=submit):form-owner-2">form owner</a> from the
<code id="submit-button-state-(type=submit):the-input-element-3"><a href=#the-input-element>input</a></code> element; otherwise, do nothing.</p>
- <p>If the element is not <i id="submit-button-state-(type=submit):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="submit-button-state-(type=submit):activation-behavior-2">activation
- behavior</a>.</p>
+ <p>If the element is not <i id="submit-button-state-(type=submit):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="submit-button-state-(type=submit):activation-behaviour-2">activation
+ behaviour</a>.</p>
@@ -36200,14 +36200,14 @@
<p>If the <code id="image-button-state-(type=image):attr-input-src-7"><a href=#attr-input-src>src</a></code> attribute is set, and the image is <i id="image-button-state-(type=image):input-img-available-2"><a href=#input-img-available>available</a></i> and the user agent is configured to display that image,
then: The element <a href=#represents id="image-button-state-(type=image):represents-2">represents</a> a control for selecting a <a href=#concept-input-type-image-coordinate id="image-button-state-(type=image):concept-input-type-image-coordinate">coordinate</a> from the image specified by the
- <code id="image-button-state-(type=image):attr-input-src-8"><a href=#attr-input-src>src</a></code> attribute; if the element is <i id="image-button-state-(type=image):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, the user agent should allow the user to select this <a href=#concept-input-type-image-coordinate id="image-button-state-(type=image):concept-input-type-image-coordinate-2">coordinate</a>, and the element's <a href=#activation-behavior id="image-button-state-(type=image):activation-behavior">activation
- behavior</a> is as follows: if the element has a <a href=#form-owner id="image-button-state-(type=image):form-owner">form owner</a>, and the element's
+ <code id="image-button-state-(type=image):attr-input-src-8"><a href=#attr-input-src>src</a></code> attribute; if the element is <i id="image-button-state-(type=image):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, the user agent should allow the user to select this <a href=#concept-input-type-image-coordinate id="image-button-state-(type=image):concept-input-type-image-coordinate-2">coordinate</a>, and the element's <a href=#activation-behaviour id="image-button-state-(type=image):activation-behaviour">activation
+ behaviour</a> is as follows: if the element has a <a href=#form-owner id="image-button-state-(type=image):form-owner">form owner</a>, and the element's
<a id="image-button-state-(type=image):node-document-2" href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is <a href=#fully-active id="image-button-state-(type=image):fully-active">fully active</a>, take the user's selected <a href=#concept-input-type-image-coordinate id="image-button-state-(type=image):concept-input-type-image-coordinate-3">coordinate</a>, and <a href=#concept-form-submit id="image-button-state-(type=image):concept-form-submit">submit</a> the <code id="image-button-state-(type=image):the-input-element-10"><a href=#the-input-element>input</a></code> element's <a href=#form-owner id="image-button-state-(type=image):form-owner-2">form owner</a>
from the <code id="image-button-state-(type=image):the-input-element-11"><a href=#the-input-element>input</a></code> element. If the user activates the control without explicitly
selecting a coordinate, then the coordinate (0,0) must be assumed.</p>
<p>Otherwise, the element <a href=#represents id="image-button-state-(type=image):represents-3">represents</a> a submit button whose label is given by the
- value of the <code id="image-button-state-(type=image):attr-input-alt-2"><a href=#attr-input-alt>alt</a></code> attribute; if the element is <i id="image-button-state-(type=image):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, then the element's <a href=#activation-behavior id="image-button-state-(type=image):activation-behavior-2">activation behavior</a> is as
+ value of the <code id="image-button-state-(type=image):attr-input-alt-2"><a href=#attr-input-alt>alt</a></code> attribute; if the element is <i id="image-button-state-(type=image):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, then the element's <a href=#activation-behaviour id="image-button-state-(type=image):activation-behaviour-2">activation behaviour</a> is as
follows: if the element has a <a href=#form-owner id="image-button-state-(type=image):form-owner-3">form owner</a>, and the element's <a id="image-button-state-(type=image):node-document-3" href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is
<a href=#fully-active id="image-button-state-(type=image):fully-active-2">fully active</a>, set the <a href=#concept-input-type-image-coordinate id="image-button-state-(type=image):concept-input-type-image-coordinate-4">selected
coordinate</a> to (0,0), and <a href=#concept-form-submit id="image-button-state-(type=image):concept-form-submit-2">submit</a> the
@@ -36215,7 +36215,7 @@
<p>In either case, if the element is <i id="image-button-state-(type=image):concept-fe-mutable-3"><a href=#concept-fe-mutable>mutable</a></i> but has no
<a href=#form-owner id="image-button-state-(type=image):form-owner-5">form owner</a> or the element's <a id="image-button-state-(type=image):node-document-4" href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is not <a href=#fully-active id="image-button-state-(type=image):fully-active-3">fully active</a>,
- then its <a href=#activation-behavior id="image-button-state-(type=image):activation-behavior-3">activation behavior</a> must be to do nothing. If the element is not <i id="image-button-state-(type=image):concept-fe-mutable-4"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="image-button-state-(type=image):activation-behavior-4">activation behavior</a>.</p>
+ then its <a href=#activation-behaviour id="image-button-state-(type=image):activation-behaviour-3">activation behaviour</a> must be to do nothing. If the element is not <i id="image-button-state-(type=image):concept-fe-mutable-4"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="image-button-state-(type=image):activation-behaviour-4">activation behaviour</a>.</p>
<p>The <dfn id=concept-input-type-image-coordinate>selected coordinate</dfn> must consist of
an <var>x</var>-component and a <var>y</var>-component. The coordinates
@@ -36313,7 +36313,7 @@
</div>
- <p class=note>Many aspects of this state's behavior are similar to the behavior of the
+ <p class=note>Many aspects of this state's behaviour are similar to the behaviour of the
<code id="image-button-state-(type=image):the-img-element"><a href=#the-img-element>img</a></code> element. Readers are encouraged to read that section, where many of the same
requirements are described in more detail.</p>
@@ -36361,12 +36361,12 @@
<p>If the element is <i id="reset-button-state-(type=reset):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, then the element's
- <a href=#activation-behavior id="reset-button-state-(type=reset):activation-behavior">activation behavior</a>, if the element has a <a href=#form-owner id="reset-button-state-(type=reset):form-owner">form owner</a> and the element's
+ <a href=#activation-behaviour id="reset-button-state-(type=reset):activation-behaviour">activation behaviour</a>, if the element has a <a href=#form-owner id="reset-button-state-(type=reset):form-owner">form owner</a> and the element's
<a id="reset-button-state-(type=reset):node-document" href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is <a href=#fully-active id="reset-button-state-(type=reset):fully-active">fully active</a>, is to <a href=#concept-form-reset id="reset-button-state-(type=reset):concept-form-reset">reset</a> the <a href=#form-owner id="reset-button-state-(type=reset):form-owner-2">form owner</a>; otherwise, it is to do
nothing.</p>
- <p>If the element is not <i id="reset-button-state-(type=reset):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="reset-button-state-(type=reset):activation-behavior-2">activation
- behavior</a>.</p>
+ <p>If the element is not <i id="reset-button-state-(type=reset):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="reset-button-state-(type=reset):activation-behaviour-2">activation
+ behaviour</a>.</p>
<p><strong>Constraint validation</strong>: The element is <a href=#barred-from-constraint-validation id="reset-button-state-(type=reset):barred-from-constraint-validation">barred from constraint
validation</a>.</p>
@@ -36437,18 +36437,18 @@
- <p>The <code id="button-state-(type=button):the-input-element-2"><a href=#the-input-element>input</a></code> element <a href=#represents id="button-state-(type=button):represents">represents</a> a button with no default behavior. A
+ <p>The <code id="button-state-(type=button):the-input-element-2"><a href=#the-input-element>input</a></code> element <a href=#represents id="button-state-(type=button):represents">represents</a> a button with no default behaviour. A
label for the button must be provided in the <code id="button-state-(type=button):attr-input-value"><a href=#attr-input-value>value</a></code>
attribute, though it may be the empty string. If the element has a <code id="button-state-(type=button):attr-input-value-2"><a href=#attr-input-value>value</a></code> attribute, the button's label must be the value of that
attribute; otherwise, it must be the empty string. The element is a <a href=#concept-button id="button-state-(type=button):concept-button">button</a>.</p>
- <p>If the element is <i id="button-state-(type=button):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, the element's <a href=#activation-behavior id="button-state-(type=button):activation-behavior">activation
- behavior</a> is to do nothing.</p>
+ <p>If the element is <i id="button-state-(type=button):concept-fe-mutable"><a href=#concept-fe-mutable>mutable</a></i>, the element's <a href=#activation-behaviour id="button-state-(type=button):activation-behaviour">activation
+ behaviour</a> is to do nothing.</p>
- <p>If the element is not <i id="button-state-(type=button):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behavior id="button-state-(type=button):activation-behavior-2">activation
- behavior</a>.</p>
+ <p>If the element is not <i id="button-state-(type=button):concept-fe-mutable-2"><a href=#concept-fe-mutable>mutable</a></i>, it has no <a href=#activation-behaviour id="button-state-(type=button):activation-behaviour-2">activation
+ behaviour</a>.</p>
<p><strong>Constraint validation</strong>: The element is <a href=#barred-from-constraint-validation id="button-state-(type=button):barred-from-constraint-validation">barred from constraint
validation</a>.</p>
@@ -37119,7 +37119,7 @@
is the selected suggestion's <a href=#concept-option-value id=the-list-attribute:concept-option-value-3>value</a>, or change an
existing entry in the <code id=the-list-attribute:the-input-element-4><a href=#the-input-element>input</a></code> element's <a href=#concept-fe-values id=the-list-attribute:concept-fe-values-4>values</a> to have the value given by the selected
suggestion's <a href=#concept-option-value id=the-list-attribute:concept-option-value-4>value</a>, as if the user had himself added
- an entry with that value, or edited an existing entry to be that value. Which behavior is to be
+ an entry with that value, or edited an existing entry to be that value. Which behaviour is to be
applied depends on the user interface in a user-agent-defined manner.</p>
</dl>
@@ -37339,7 +37339,7 @@
<p>The <dfn id=dom-input-value><code>value</code></dfn> IDL attribute allows scripts to
manipulate the <a href=#concept-fe-value id=common-input-element-apis:concept-fe-value-6>value</a> of an <code id=common-input-element-apis:the-input-element-2><a href=#the-input-element>input</a></code> element. The
- attribute is in one of the following modes, which define its behavior:</p>
+ attribute is in one of the following modes, which define its behaviour:</p>
<dl><dt><dfn id=dom-input-value-value>value</dfn>
@@ -37534,7 +37534,7 @@
- <h5 id=common-input-element-events>4.10.5.5 Common event behaviors</h5>
+ <h5 id=common-input-element-events>4.10.5.5 Common event behaviours</h5>
<p>When the <code id=common-input-element-events:event-input-input><a href=#event-input-input>input</a></code> and <code id=common-input-element-events:event-input-change><a href=#event-input-change>change</a></code> events <a href=#concept-input-apply id=common-input-element-events:concept-input-apply>apply</a>
(which is the case for all <code id=common-input-element-events:the-input-element><a href=#the-input-element>input</a></code> controls other than <a href=#concept-button id=common-input-element-events:concept-button>buttons</a> and those with the <code id=common-input-element-events:attr-input-type><a href=#attr-input-type>type</a></code> attribute in the <a href="#hidden-state-(type=hidden)" id="common-input-element-events:hidden-state-(type=hidden)">Hidden</a> state), the events are fired to indicate that the
@@ -37542,12 +37542,12 @@
event fires whenever the user has modified the data of the control. The <dfn id=event-input-change><code>change</code></dfn> event fires when the value is committed, if
that makes sense for the control, or else when the control <a href=#unfocus-causes-change-event>loses focus</a>. In all cases, the <code id=common-input-element-events:event-input-input-2><a href=#event-input-input>input</a></code> event comes before the corresponding <code id=common-input-element-events:event-input-change-2><a href=#event-input-change>change</a></code> event (if any).</p>
- <p>When an <code id=common-input-element-events:the-input-element-2><a href=#the-input-element>input</a></code> element has a defined <a href=#activation-behavior id=common-input-element-events:activation-behavior>activation behavior</a>, the rules
+ <p>When an <code id=common-input-element-events:the-input-element-2><a href=#the-input-element>input</a></code> element has a defined <a href=#activation-behaviour id=common-input-element-events:activation-behaviour>activation behaviour</a>, the rules
for dispatching these events, if they <a href=#concept-input-apply id=common-input-element-events:concept-input-apply-2>apply</a>, are given
in the section above that defines the <code id=common-input-element-events:attr-input-type-2><a href=#attr-input-type>type</a></code> attribute's
state. (This is the case for all <code id=common-input-element-events:the-input-element-3><a href=#the-input-element>input</a></code> controls with the <code id=common-input-element-events:attr-input-type-3><a href=#attr-input-type>type</a></code> attribute in the <a href="#checkbox-state-(type=checkbox)" id="common-input-element-events:checkbox-state-(type=checkbox)">Checkbox</a> state, the <a href="#radio-button-state-(type=radio)" id="common-input-element-events:radio-button-state-(type=radio)">Radio Button</a> state, or the <a href="#file-upload-state-(type=file)" id="common-input-element-events:file-upload-state-(type=file)">File Upload</a> state.)</p>
- <p>For <code id=common-input-element-events:the-input-element-4><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behavior id=common-input-element-events:activation-behavior-2>activation behavior</a>, but to
+ <p>For <code id=common-input-element-events:the-input-element-4><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behaviour id=common-input-element-events:activation-behaviour-2>activation behaviour</a>, but to
which these events <a href=#concept-input-apply id=common-input-element-events:concept-input-apply-3>apply</a>, and for which the user
interface involves both interactive manipulation and an explicit commit action, then when the user
changes the element's <a href=#concept-fe-value id=common-input-element-events:concept-fe-value>value</a>, the user agent must
@@ -37563,7 +37563,7 @@
whereas the <code id=common-input-element-events:event-input-change-4><a href=#event-input-change>change</a></code> event would only fire when the user
let go of the knob, committing to a specific value.</p>
- <p>For <code id=common-input-element-events:the-input-element-7><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behavior id=common-input-element-events:activation-behavior-3>activation behavior</a>, but to
+ <p>For <code id=common-input-element-events:the-input-element-7><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behaviour id=common-input-element-events:activation-behaviour-3>activation behaviour</a>, but to
which these events <a href=#concept-input-apply id=common-input-element-events:concept-input-apply-4>apply</a>, and for which the user
interface involves an explicit commit action but no intermediate manipulation, then any time the
user commits a change to the element's <a href=#concept-fe-value id=common-input-element-events:concept-fe-value-2>value</a>, the user
@@ -37581,7 +37581,7 @@
selecting a date from the drop down calendar and then dismissing the drop down would be a commit
action.</p>
- <p>For <code id=common-input-element-events:the-input-element-10><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behavior id=common-input-element-events:activation-behavior-4>activation behavior</a>, but to
+ <p>For <code id=common-input-element-events:the-input-element-10><a href=#the-input-element>input</a></code> elements without a defined <a href=#activation-behaviour id=common-input-element-events:activation-behaviour-4>activation behaviour</a>, but to
which these events <a href=#concept-input-apply id=common-input-element-events:concept-input-apply-5>apply</a>, any time the user causes the
element's <a href=#concept-fe-value id=common-input-element-events:concept-fe-value-4>value</a> to change without an explicit commit
action, the user agent must <a href=#queue-a-task id=common-input-element-events:queue-a-task-4>queue a task</a> to <a href=#fire-a-simple-event id=common-input-element-events:fire-a-simple-event-5>fire a simple event</a> that
@@ -37653,7 +37653,7 @@
<p>The element is a <a href=#concept-button id=the-button-element:concept-button>button</a>.</p>
- <p>The <dfn id=attr-button-type><code>type</code></dfn> attribute controls the behavior of
+ <p>The <dfn id=attr-button-type><code>type</code></dfn> attribute controls the behaviour of
the button when it is activated. It is an <a href=#enumerated-attribute id=the-button-element:enumerated-attribute>enumerated attribute</a>. The following table
lists the keywords and states for the attribute — the keywords in the left column map to the
states in the cell in the second column on the same row as the keyword.</p>
@@ -37689,7 +37689,7 @@
validation</a>.</p>
<p>When a <code id=the-button-element:the-button-element-2><a href=#the-button-element>button</a></code> element is not <a href=#concept-fe-disabled id=the-button-element:concept-fe-disabled>disabled</a>,
- its <a href=#activation-behavior id=the-button-element:activation-behavior>activation behavior</a> element is to run the steps defined in the following list for
+ its <a href=#activation-behaviour id=the-button-element:activation-behaviour>activation behaviour</a> element is to run the steps defined in the following list for
the current state of the element's <code id=the-button-element:attr-button-type-4><a href=#attr-button-type>type</a></code> attribute:</p>
<dl><dt> <dfn id=attr-button-type-submit-state>Submit Button</dfn> <dd><p>If the element has a <a href=#form-owner id=the-button-element:form-owner>form owner</a> and the element's <a id=the-button-element:node-document href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a> is
@@ -37948,7 +37948,7 @@
The <code id=the-select-element:attr-fe-name-2><a href=#attr-fe-name>name</a></code> attribute represents the element's name.
The <code id=the-select-element:attr-fe-disabled-2><a href=#attr-fe-disabled>disabled</a></code> attribute is used to make the control non-interactive and to prevent its value from being submitted.
The <code id=the-select-element:attr-fe-autofocus-2><a href=#attr-fe-autofocus>autofocus</a></code> attribute controls focus.
- The <code id=the-select-element:attr-fe-autocomplete-2><a href=#attr-fe-autocomplete>autocomplete</a></code> attribute controls how the user agent provides autofill behavior.
+ The <code id=the-select-element:attr-fe-autocomplete-2><a href=#attr-fe-autocomplete>autocomplete</a></code> attribute controls how the user agent provides autofill behaviour.
</p>
<p>A <code id=the-select-element:the-select-element-26><a href=#the-select-element>select</a></code> element that is not <a href=#concept-fe-disabled id=the-select-element:concept-fe-disabled-3>disabled</a> is
@@ -38509,7 +38509,7 @@
<p>On setting, the <code id=the-option-element:dom-option-text-5><a href=#dom-option-text>text</a></code> attribute must act as if the
<code id=the-option-element:textcontent-2><a href=#textcontent>textContent</a></code> IDL attribute on the element had been set to the new value.</p>
- <p>The <dfn id=dom-option-form><code>form</code></dfn> IDL attribute's behavior depends on
+ <p>The <dfn id=dom-option-form><code>form</code></dfn> IDL attribute's behaviour depends on
whether the <code id=the-option-element:the-option-element-22><a href=#the-option-element>option</a></code> element is in a <code id=the-option-element:the-select-element-8><a href=#the-select-element>select</a></code> element or not. If the
<code id=the-option-element:the-option-element-23><a href=#the-option-element>option</a></code> has a <code id=the-option-element:the-select-element-9><a href=#the-select-element>select</a></code> element as its parent, or has an
<code id=the-option-element:the-optgroup-element-4><a href=#the-optgroup-element>optgroup</a></code> element as its parent and that <code id=the-option-element:the-optgroup-element-5><a href=#the-optgroup-element>optgroup</a></code> element has a
@@ -38804,7 +38804,7 @@
The <code id=the-textarea-element:attr-fe-inputmode-2><a href=#attr-fe-inputmode>inputmode</a></code> attribute controls the user interface's input
modality for the control.
The <code id=the-textarea-element:attr-fe-autocomplete-2><a href=#attr-fe-autocomplete>autocomplete</a></code> attribute controls how the user agent
- provides autofill behavior.
+ provides autofill behaviour.
</p>
@@ -39865,7 +39865,7 @@
- <p>The <dfn id=dom-legend-form><code>form</code></dfn> IDL attribute's behavior depends on
+ <p>The <dfn id=dom-legend-form><code>form</code></dfn> IDL attribute's behaviour depends on
whether the <code id=the-legend-element:the-legend-element-3><a href=#the-legend-element>legend</a></code> element is in a <code id=the-legend-element:the-fieldset-element-3><a href=#the-fieldset-element>fieldset</a></code> element or not. If the
<code id=the-legend-element:the-legend-element-4><a href=#the-legend-element>legend</a></code> has a <code id=the-legend-element:the-fieldset-element-4><a href=#the-fieldset-element>fieldset</a></code> element as its parent, then the <code id=the-legend-element:dom-legend-form-3><a href=#dom-legend-form>form</a></code> IDL attribute must return the same value as the <code id=the-legend-element:dom-fae-form><a href=#dom-fae-form>form</a></code> IDL attribute on that <code id=the-legend-element:the-fieldset-element-5><a href=#the-fieldset-element>fieldset</a></code> element. Otherwise,
it must return null.</p>
@@ -42566,12 +42566,12 @@
<p>If the user agent supports letting the user submit a form implicitly (for example, on some
platforms hitting the "enter" key while a text field is <a href=#focused id=implicit-submission:focused>focused</a> implicitly submits the form), then
- doing so for a form whose <a href=#default-button id=implicit-submission:default-button>default button</a> has a defined <a href=#activation-behavior id=implicit-submission:activation-behavior>activation
- behavior</a> must cause the user agent to <a href=#run-synthetic-click-activation-steps id=implicit-submission:run-synthetic-click-activation-steps>run synthetic click activation steps</a> on
+ doing so for a form whose <a href=#default-button id=implicit-submission:default-button>default button</a> has a defined <a href=#activation-behaviour id=implicit-submission:activation-behaviour>activation
+ behaviour</a> must cause the user agent to <a href=#run-synthetic-click-activation-steps id=implicit-submission:run-synthetic-click-activation-steps>run synthetic click activation steps</a> on
that <a href=#default-button id=implicit-submission:default-button-2>default button</a>.</p>
<p class=note>Consequently, if the <a href=#default-button id=implicit-submission:default-button-3>default button</a> is <a href=#concept-fe-disabled id=implicit-submission:concept-fe-disabled>disabled</a>, the form is not submitted when such an implicit
- submission mechanism is used. (A button has no <a href=#activation-behavior id=implicit-submission:activation-behavior-2>activation behavior</a> when
+ submission mechanism is used. (A button has no <a href=#activation-behaviour id=implicit-submission:activation-behaviour-2>activation behaviour</a> when
disabled.)</p>
<p class=note>There are pages on the Web that are only usable if there is a way to implicitly
@@ -42677,7 +42677,7 @@
<td> <a href=#submit-mailto-body id=form-submission-algorithm:submit-mailto-body>Mail as body</a>
</table>
- <p>If <var>scheme</var> is not one of those listed in this table, then the behavior is
+ <p>If <var>scheme</var> is not one of those listed in this table, then the behaviour is
not defined by this specification. User agents should, in the absence of another specification
defining this, act in a manner analogous to that defined in this specification for similar
schemes.</p>
@@ -42713,7 +42713,7 @@
</ol>
- <p>The behaviors are as follows:</p>
+ <p>The behaviours are as follows:</p>
<dl><dt><dfn id=submit-mutate-action>Mutate action URL</dfn>
<dd>
@@ -43709,7 +43709,7 @@
<hr>
<p>If the element's <a href=#command-facet-disabledstate id=the-menuitem-element:command-facet-disabledstate>Disabled State</a> is false
- (enabled) then the element's <a href=#activation-behavior id=the-menuitem-element:activation-behavior>activation behavior</a> depends on the element's <code id=the-menuitem-element:attr-menuitem-type-7><a href=#attr-menuitem-type>type</a></code> and <code id=the-menuitem-element:attr-menuitem-command-7><a href=#attr-menuitem-command>command</a></code>
+ (enabled) then the element's <a href=#activation-behaviour id=the-menuitem-element:activation-behaviour>activation behaviour</a> depends on the element's <code id=the-menuitem-element:attr-menuitem-type-7><a href=#attr-menuitem-type>type</a></code> and <code id=the-menuitem-element:attr-menuitem-command-7><a href=#attr-menuitem-command>command</a></code>
attributes, as follows:</p>
<dl class=switch><dt>If the element has a <a href=#master-command id=the-menuitem-element:master-command-3>master command</a> set by its <code id=the-menuitem-element:attr-menuitem-command-8><a href=#attr-menuitem-command>command</a></code> attribute<dd><p>The user agent must <a href=#run-synthetic-click-activation-steps id=the-menuitem-element:run-synthetic-click-activation-steps>run synthetic click activation steps</a> on the element's
@@ -43720,7 +43720,7 @@
attributes as if they were the empty string), and has a <code id=the-menuitem-element:attr-menuitem-checked-6><a href=#attr-menuitem-checked>checked</a></code> attribute, must remove that attribute.</p>
<p>Then, the element's <code id=the-menuitem-element:attr-menuitem-checked-7><a href=#attr-menuitem-checked>checked</a></code> attribute must be set
- to the literal value "<code>checked</code>".<dt>Otherwise<dd><p>The element's <a href=#activation-behavior id=the-menuitem-element:activation-behavior-2>activation behavior</a> is to do nothing.</dl>
+ to the literal value "<code>checked</code>".<dt>Otherwise<dd><p>The element's <a href=#activation-behaviour id=the-menuitem-element:activation-behaviour-2>activation behaviour</a> is to do nothing.</dl>
<p class=note>Firing a synthetic <code id=the-menuitem-element:event-click><a href=#event-click>click</a></code> event at the element
does not cause any of the actions described above to happen.</p>
@@ -43728,7 +43728,7 @@
<p>If the element's <a href=#command-facet-disabledstate id=the-menuitem-element:command-facet-disabledstate-2>Disabled State</a> is true
- (disabled) then the element has no <a href=#activation-behavior id=the-menuitem-element:activation-behavior-3>activation behavior</a>.</p>
+ (disabled) then the element has no <a href=#activation-behaviour id=the-menuitem-element:activation-behaviour-3>activation behaviour</a>.</p>
@@ -44080,7 +44080,7 @@
false. (The command is never checked.)</p>
<p>The <a href=#command-facet-action id=using-the-a-element-to-define-a-command:command-facet-action>Action</a> of the command, if the element has a
- defined <a href=#activation-behavior id=using-the-a-element-to-define-a-command:activation-behavior>activation behavior</a>, is to <a href=#run-synthetic-click-activation-steps id=using-the-a-element-to-define-a-command:run-synthetic-click-activation-steps>run synthetic click activation steps</a>
+ defined <a href=#activation-behaviour id=using-the-a-element-to-define-a-command:activation-behaviour>activation behaviour</a>, is to <a href=#run-synthetic-click-activation-steps id=using-the-a-element-to-define-a-command:run-synthetic-click-activation-steps>run synthetic click activation steps</a>
on the element. Otherwise, it is just to <a href=#fire-a-click-event id=using-the-a-element-to-define-a-command:fire-a-click-event>fire a <code>click</code>
event</a> at the element.</p>
@@ -44147,7 +44147,7 @@
is <a href=#concept-fe-checked id=using-the-input-element-to-define-a-command:concept-fe-checked>checked</a> attribute, and false otherwise.</p>
<p>The <a href=#command-facet-action id=using-the-input-element-to-define-a-command:command-facet-action>Action</a> of the command, if the element has a
- defined <a href=#activation-behavior id=using-the-input-element-to-define-a-command:activation-behavior>activation behavior</a>, is to <a href=#run-synthetic-click-activation-steps id=using-the-input-element-to-define-a-command:run-synthetic-click-activation-steps>run synthetic click activation steps</a>
+ defined <a href=#activation-behaviour id=using-the-input-element-to-define-a-command:activation-behaviour>activation behaviour</a>, is to <a href=#run-synthetic-click-activation-steps id=using-the-input-element-to-define-a-command:run-synthetic-click-activation-steps>run synthetic click activation steps</a>
on the element. Otherwise, it is just to <a href=#fire-a-click-event id=using-the-input-element-to-define-a-command:fire-a-click-event>fire a <code>click</code>
event</a> at the element.</p>
@@ -44235,7 +44235,7 @@
false otherwise.</p>
<p>The <a href=#command-facet-action id=using-the-menuitem-element-to-define-a-command:command-facet-action>Action</a> of the command, if the element has a
- defined <a href=#activation-behavior id=using-the-menuitem-element-to-define-a-command:activation-behavior>activation behavior</a>, is to
+ defined <a href=#activation-behaviour id=using-the-menuitem-element-to-define-a-command:activation-behaviour>activation behaviour</a>, is to
<a href=#run-synthetic-click-activation-steps id=using-the-menuitem-element-to-define-a-command:run-synthetic-click-activation-steps>run synthetic click activation steps</a> on the element. Otherwise, it is just to
<a href=#fire-a-click-event id=using-the-menuitem-element-to-define-a-command:fire-a-click-event>fire a <code>click</code> event</a> at the element.</p>
@@ -44378,8 +44378,8 @@
<p>The <a href=#command-facet-action id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:command-facet-action>Action</a> of the command is to run the following
steps:</p>
- <ol><li>Run the <a href=#focusing-steps id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:focusing-steps>focusing steps</a> for the element.<li>If the element has a defined <a href=#activation-behavior id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:activation-behavior>activation behavior</a>, <a href=#run-synthetic-click-activation-steps id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:run-synthetic-click-activation-steps>run synthetic click
- activation steps</a> on the element.<li>Otherwise, if the element does not have a defined <a href=#activation-behavior id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:activation-behavior-2>activation behavior</a>,
+ <ol><li>Run the <a href=#focusing-steps id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:focusing-steps>focusing steps</a> for the element.<li>If the element has a defined <a href=#activation-behaviour id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:activation-behaviour>activation behaviour</a>, <a href=#run-synthetic-click-activation-steps id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:run-synthetic-click-activation-steps>run synthetic click
+ activation steps</a> on the element.<li>Otherwise, if the element does not have a defined <a href=#activation-behaviour id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:activation-behaviour-2>activation behaviour</a>,
<a href=#fire-a-click-event id=using-the-accesskey-attribute-to-define-a-command-on-other-elements:fire-a-click-event>fire a <code>click</code> event</a> at the element.</ol>
@@ -44915,7 +44915,7 @@
and <a href=#scriptTagXML>in XML</a>, the rules for the <code id=the-script-element:dom-document-write><a href=#dom-document-write>document.write()</a></code> method, the handling of <a href=#scripting>scripting</a>, etc.</p>
<p>The <code id=the-script-element:attr-script-defer-4><a href=#attr-script-defer>defer</a></code> attribute may be specified even if the <code id=the-script-element:attr-script-async-5><a href=#attr-script-async>async</a></code> attribute is specified, to cause legacy Web browsers that
- only support <code id=the-script-element:attr-script-defer-5><a href=#attr-script-defer>defer</a></code> (and not <code id=the-script-element:attr-script-async-6><a href=#attr-script-async>async</a></code>) to fall back to the <code id=the-script-element:attr-script-defer-6><a href=#attr-script-defer>defer</a></code> behavior instead of the blocking behavior that
+ only support <code id=the-script-element:attr-script-defer-5><a href=#attr-script-defer>defer</a></code> (and not <code id=the-script-element:attr-script-async-6><a href=#attr-script-async>async</a></code>) to fall back to the <code id=the-script-element:attr-script-defer-6><a href=#attr-script-defer>defer</a></code> behaviour instead of the blocking behaviour that
is the default.</p>
<p>The <dfn id=attr-script-crossorigin><code>crossorigin</code></dfn> attribute is a
@@ -47745,7 +47745,7 @@
<p>The <dfn id=dom-context-2d-arcto><code>arcTo(<var>x1</var>, <var>y1</var>, <var>x2</var>, <var>y2</var>, <var>radiusX</var>,
<var>radiusY</var>, <var>rotation</var>)</code></dfn> method must first
- <a href=#ensure-there-is-a-subpath id=building-paths:ensure-there-is-a-subpath-4>ensure there is a subpath</a> for <span>(<var>x1</var>, <var>y1</var>)</span>. Then, the behavior depends on the arguments and the last point in the
+ <a href=#ensure-there-is-a-subpath id=building-paths:ensure-there-is-a-subpath-4>ensure there is a subpath</a> for <span>(<var>x1</var>, <var>y1</var>)</span>. Then, the behaviour depends on the arguments and the last point in the
subpath, as described below.</p>
<p>Negative values for <var>radiusX</var> or <var>radiusY</var> must cause the
@@ -48511,7 +48511,7 @@
<li><p>If <var>repetition</var> is not a <a href=#case-sensitive id=fill-and-stroke-styles:case-sensitive>case-sensitive</a> match for one of
"<code>repeat</code>", "<code>repeat-x</code>", "<code>repeat-y</code>", or "<code>no-repeat</code>", throw a <code id=fill-and-stroke-styles:syntaxerror-3><a href=#syntaxerror>SyntaxError</a></code>
exception and abort these steps.<li><p>Create a new <code id=fill-and-stroke-styles:canvaspattern-10><a href=#canvaspattern>CanvasPattern</a></code> object with the image <var>image</var>
- and the repetition behavior given by <var>repetition</var>.<li><p>If <a href=#the-image-argument-is-not-origin-clean id=fill-and-stroke-styles:the-image-argument-is-not-origin-clean>the <var>image argument</var> is not origin-clean</a>, then mark the
+ and the repetition behaviour given by <var>repetition</var>.<li><p>If <a href=#the-image-argument-is-not-origin-clean id=fill-and-stroke-styles:the-image-argument-is-not-origin-clean>the <var>image argument</var> is not origin-clean</a>, then mark the
<code id=fill-and-stroke-styles:canvaspattern-11><a href=#canvaspattern>CanvasPattern</a></code> object as <dfn id=concept-canvas-pattern-not-origin-clean>not
origin-clean</dfn>.<li><p>Return the <code id=fill-and-stroke-styles:canvaspattern-12><a href=#canvaspattern>CanvasPattern</a></code> object.</ol>
@@ -48534,9 +48534,9 @@
<p>Place a copy of the image on the bitmap, anchored such that its top left corner is at the
origin of the coordinate space, with one coordinate space unit per CSS pixel of the image, then
place repeated copies of this image horizontally to the left and right, if the repetition
- behavior is "<code>repeat-x</code>", or vertically up and down, if the repetition
- behavior is "<code>repeat-y</code>", or in all four directions all over the bitmap, if
- the repetition behavior is "<code>repeat</code>".</p>
+ behaviour is "<code>repeat-x</code>", or vertically up and down, if the repetition
+ behaviour is "<code>repeat-y</code>", or in all four directions all over the bitmap, if
+ the repetition behaviour is "<code>repeat</code>".</p>
<p>If the original image data is a bitmap image, the value painted at a point in the area of the
repetitions is computed by filtering the original image data. When scaling up, if the <code id=fill-and-stroke-styles:dom-context-2d-imagesmoothingenabled><a href=#dom-context-2d-imagesmoothingenabled>imageSmoothingEnabled</a></code> attribute is set to
@@ -48544,8 +48544,8 @@
may use any filtering algorithm (for example bilinear interpolation or nearest-neighbor). When
such a filtering algorithm requires a pixel value from outside the original image data, it must
instead use the value from wrapping the pixel's coordinates to the original image's dimensions.
- (That is, the filter uses 'repeat' behavior, regardless of the value of the pattern's repetition
- behavior.)</p>
+ (That is, the filter uses 'repeat' behaviour, regardless of the value of the pattern's repetition
+ behaviour.)</p>
<li><p>Transform the resulting bitmap according to the pattern's transformation matrix.<li><p>Transform the resulting bitmap again, this time according to the <a href=#transformations id=fill-and-stroke-styles:transformations-3>current transformation matrix</a>.<li><p>Replace any part of the image outside the area in which the pattern is to be rendered with
@@ -49155,7 +49155,7 @@
rectangle is computed by filtering the original image data. The user agent may use any filtering
algorithm (for example bilinear interpolation or nearest-neighbor). When the filtering algorithm
requires a pixel value from outside the original image data, it must instead use the value from
- the nearest edge pixel. (That is, the filter uses 'clamp-to-edge' behavior.) When the filtering
+ the nearest edge pixel. (That is, the filter uses 'clamp-to-edge' behaviour.) When the filtering
algorithm requires a pixel value from outside the source rectangle but inside the original image
data, then the value from the original image data must be used.</p>
@@ -51092,9 +51092,9 @@
<ul><li>
<p>An element falling into one of the following categories between the time the user begins to
- indicate an intent to trigger the element's <a href=#activation-behavior id=pseudo-classes:activation-behavior>activation behavior</a> and either the
- time the user stops indicating an intent to trigger the element's <a href=#activation-behavior id=pseudo-classes:activation-behavior-2>activation
- behavior</a>, or the time the element's <a href=#activation-behavior id=pseudo-classes:activation-behavior-3>activation behavior</a> has finished
+ indicate an intent to trigger the element's <a href=#activation-behaviour id=pseudo-classes:activation-behaviour>activation behaviour</a> and either the
+ time the user stops indicating an intent to trigger the element's <a href=#activation-behaviour id=pseudo-classes:activation-behaviour-2>activation
+ behaviour</a>, or the time the element's <a href=#activation-behaviour id=pseudo-classes:activation-behaviour-3>activation behaviour</a> has finished
running, which ever comes first:</p>
<ul><li><code id=pseudo-classes:the-a-element-2><a href=#the-a-element>a</a></code> elements that have an <code id=pseudo-classes:attr-hyperlink-href-3><a href=#attr-hyperlink-href>href</a></code>
@@ -52336,7 +52336,7 @@
which the attribute was invoked, while that element is an <a href=#concept-item id=microdata-dom-api:concept-item-4>item</a>,
and matches nothing the rest of the time.</p>
- <p>The <dfn id=dom-itemvalue><code>itemValue</code></dfn> IDL attribute's behavior depends on
+ <p>The <dfn id=dom-itemvalue><code>itemValue</code></dfn> IDL attribute's behaviour depends on
the element, as follows:</p>
<dl><dt>If the element has no <code id=microdata-dom-api:names:-the-itemprop-attribute-3><a href=#names:-the-itemprop-attribute>itemprop</a></code> attribute<dd><p>The attribute must return null on getting and must throw an
@@ -54154,16 +54154,16 @@
<h3 id=activation>6.3 Activation</h3>
- <p>Certain elements in HTML have an <a href=#activation-behavior id=activation:activation-behavior>activation behavior</a>, which means that the user
+ <p>Certain elements in HTML have an <a href=#activation-behaviour id=activation:activation-behaviour>activation behaviour</a>, which means that the user
can activate them. This triggers a sequence of events dependent on the activation mechanism, and
normally culminating in a <code id=activation:event-click><a href=#event-click>click</a></code> event, as
described below.</p>
- <p>The user agent should allow the user to manually trigger elements that have an <a href=#activation-behavior id=activation:activation-behavior-2>activation
- behavior</a>, for instance using keyboard or voice input, or through mouse clicks. When the
- user triggers an element with a defined <a href=#activation-behavior id=activation:activation-behavior-3>activation behavior</a> in a manner other than
+ <p>The user agent should allow the user to manually trigger elements that have an <a href=#activation-behaviour id=activation:activation-behaviour-2>activation
+ behaviour</a>, for instance using keyboard or voice input, or through mouse clicks. When the
+ user triggers an element with a defined <a href=#activation-behaviour id=activation:activation-behaviour-3>activation behaviour</a> in a manner other than
clicking it, the default action of the interaction event must be to <a href=#run-synthetic-click-activation-steps id=activation:run-synthetic-click-activation-steps>run synthetic click
activation steps</a> on the element.</p>
@@ -54210,14 +54210,14 @@
script. The <code id=activation:dom-click-2><a href=#dom-click>click()</a></code> method can be used to make the <a href=#run-synthetic-click-activation-steps id=activation:run-synthetic-click-activation-steps-3>run
synthetic click activation steps</a> algorithm happen programmatically.</p>
- <p class=note>Click-focusing behavior (e.g. the focusing of a text field when user clicks in
+ <p class=note>Click-focusing behaviour (e.g. the focusing of a text field when user clicks in
one) typically happens before the click, when the mouse button is first depressed, and is
therefore not discussed here.</p>
<p>Given an element <var>target</var>, the <dfn id=nearest-activatable-element>nearest activatable element</dfn> is the
element returned by the following algorithm:</p>
- <ol><li><p>If <var>target</var> has a defined <a href=#activation-behavior id=activation:activation-behavior-4>activation behavior</a>, then return
+ <ol><li><p>If <var>target</var> has a defined <a href=#activation-behaviour id=activation:activation-behaviour-4>activation behaviour</a>, then return
<var>target</var> and abort these steps.<li><p>If <var>target</var> has a parent element, then set <var>target</var> to
that parent element and return to the first step.<li><p>Otherwise, there is no <a href=#nearest-activatable-element id=activation:nearest-activatable-element-2>nearest activatable element</a>.</ol>
@@ -54228,7 +54228,7 @@
<dfn id=canceled-activation-steps>canceled activation steps</dfn> defined for that element, if any.</p>
<p>When a user agent is to <dfn id=run-post-click-activation-steps>run post-click activation steps</dfn> on an element, it must run
- the <dfn id=activation-behavior>activation behavior</dfn> defined for that element, if any. Activation behaviors can
+ the <dfn id=activation-behaviour>activation behaviour</dfn> defined for that element, if any. Activation behaviours can
refer to the <code id=activation:event-click-5><a href=#event-click>click</a></code> event that was fired by the steps above
leading up to this point.</p>
@@ -54618,7 +54618,7 @@
</dl>
<p>An element that has its <a href=#specially-focusable id=the-tabindex-attribute:specially-focusable-7>tabindex focus flag</a> set but does not otherwise have an
- <a href=#activation-behavior id=the-tabindex-attribute:activation-behavior>activation behavior</a> defined has an <a href=#activation-behavior id=the-tabindex-attribute:activation-behavior-2>activation behavior</a> that does
+ <a href=#activation-behaviour id=the-tabindex-attribute:activation-behaviour>activation behaviour</a> defined has an <a href=#activation-behaviour id=the-tabindex-attribute:activation-behaviour-2>activation behaviour</a> that does
nothing.</p>
<p class=note>This means that an element that is only focusable because of its <code id=the-tabindex-attribute:attr-tabindex-15><a href=#attr-tabindex>tabindex</a></code> attribute will fire a <code id=the-tabindex-attribute:event-click><a href=#event-click>click</a></code> event in response to a non-mouse activation (e.g. hitting the
@@ -54830,7 +54830,7 @@
<ol><li id=unfocus-causes-change-event><div class=status><input onclick=toggleStatus(this) value=⋰ type=button><p class=bugs><strong>Spec bugs:</strong> <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=27519" title="It is a bit unclear what "has changed the value" means if a user changes the value and then changes it back before the control loses focus. I believe the correct thing to do in those cases is to not fire the event.">27519</a></div><p>If <var>entry</var> is an <code id=processing-model-6:the-input-element-2><a href=#the-input-element>input</a></code>
element, and the <code id=processing-model-6:event-input-change><a href=#event-input-change>change</a></code> event <a href=#concept-input-apply id=processing-model-6:concept-input-apply>applies</a> to the element, and the element does not have a
- defined <a href=#activation-behavior id=processing-model-6:activation-behavior>activation behavior</a>, and the user has changed the element's <a href=#concept-fe-value id=processing-model-6:concept-fe-value>value</a> or its list of <a href=#concept-input-type-file-selected id=processing-model-6:concept-input-type-file-selected>selected files</a> while the control was focused
+ defined <a href=#activation-behaviour id=processing-model-6:activation-behaviour>activation behaviour</a>, and the user has changed the element's <a href=#concept-fe-value id=processing-model-6:concept-fe-value>value</a> or its list of <a href=#concept-input-type-file-selected id=processing-model-6:concept-input-type-file-selected>selected files</a> while the control was focused
without committing that change, then <a href=#fire-a-simple-event id=processing-model-6:fire-a-simple-event>fire a simple event</a> that bubbles named <code id=processing-model-6:event-change><a href=#event-change>change</a></code> at the element.</p>
<li>
@@ -55199,7 +55199,7 @@
<p class=note>Historically, the <code id=focus-management-apis:dom-window-blur-2><a href=#dom-window-blur>focus()</a></code> and <code id=focus-management-apis:dom-window-blur-3><a href=#dom-window-blur>blur()</a></code> methods actually affected the system-level focus of the
system widget (e.g. tab or window) that contained the <a href=#browsing-context id=focus-management-apis:browsing-context-5>browsing context</a>, but hostile
- sites widely abuse this behavior to the user's detriment.</p>
+ sites widely abuse this behaviour to the user's detriment.</p>
<p>The <dfn id=dom-focus><code>focus()</code></dfn> method on elements, when invoked, must
run the following algorithm:</p>
@@ -55568,8 +55568,8 @@
host</a> (e.g. using <code id=spelling-and-grammar-checking:attr-contenteditable><a href=#attr-contenteditable>contenteditable</a></code>).</p>
<p>For each element, user agents must establish a <dfn id=concept-spellcheck-default>default
- behavior</dfn>, either through defaults or through preferences expressed by the user. There are
- three possible default behaviors for each element:</p>
+ behaviour</dfn>, either through defaults or through preferences expressed by the user. There are
+ three possible default behaviours for each element:</p>
<dl><dt><dfn id=concept-spellcheck-default-true>true-by-default</dfn>
@@ -55581,8 +55581,8 @@
<dt><dfn id=concept-spellcheck-default-inherit>inherit-by-default</dfn>
- <dd>The element's default behavior is the same as its parent element's. Elements that have no
- parent element cannot have this as their default behavior.
+ <dd>The element's default behaviour is the same as its parent element's. Elements that have no
+ parent element cannot have this as their default behaviour.
</dl>
@@ -55597,7 +55597,7 @@
<p class=note>The <i>true</i> state indicates that the element is to have its spelling and
grammar checked. The <i>default</i> state indicates that the element is to act according to a
- default behavior, possibly based on the parent element's own <code id=spelling-and-grammar-checking:attr-spellcheck><a href=#attr-spellcheck>spellcheck</a></code> state, as defined below. The <i>false</i> state
+ default behaviour, possibly based on the parent element's own <code id=spelling-and-grammar-checking:attr-spellcheck><a href=#attr-spellcheck>spellcheck</a></code> state, as defined below. The <i>false</i> state
indicates that the element is not to be checked.</p>
@@ -55626,8 +55626,8 @@
<p>The <dfn id=dom-spellcheck><code>spellcheck</code></dfn> IDL attribute, on getting, must
return true if the element's <code id=spelling-and-grammar-checking:attr-spellcheck-3><a href=#attr-spellcheck>spellcheck</a></code> content attribute is
in the <i>true</i> state, or if the element's <code id=spelling-and-grammar-checking:attr-spellcheck-4><a href=#attr-spellcheck>spellcheck</a></code>
- content attribute is in the <i>default</i> state and the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default>default behavior</a> is <a href=#concept-spellcheck-default-true id=spelling-and-grammar-checking:concept-spellcheck-default-true>true-by-default</a>, or if the element's <code id=spelling-and-grammar-checking:attr-spellcheck-5><a href=#attr-spellcheck>spellcheck</a></code> content attribute is in the <i>default</i> state and the
- element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-2>default behavior</a> is <a href=#concept-spellcheck-default-inherit id=spelling-and-grammar-checking:concept-spellcheck-default-inherit>inherit-by-default</a> and the element's parent
+ content attribute is in the <i>default</i> state and the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default>default behaviour</a> is <a href=#concept-spellcheck-default-true id=spelling-and-grammar-checking:concept-spellcheck-default-true>true-by-default</a>, or if the element's <code id=spelling-and-grammar-checking:attr-spellcheck-5><a href=#attr-spellcheck>spellcheck</a></code> content attribute is in the <i>default</i> state and the
+ element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-2>default behaviour</a> is <a href=#concept-spellcheck-default-inherit id=spelling-and-grammar-checking:concept-spellcheck-default-inherit>inherit-by-default</a> and the element's parent
element's <code id=spelling-and-grammar-checking:dom-spellcheck-2><a href=#dom-spellcheck>spellcheck</a></code> IDL attribute would return true;
otherwise, if none of those conditions applies, then the attribute must instead return false.</p>
@@ -55663,9 +55663,9 @@
state, then checking is disabled.<li>Otherwise, if there is an ancestor element with a <code id=spelling-and-grammar-checking:attr-spellcheck-9><a href=#attr-spellcheck>spellcheck</a></code> content attribute that is not in the <i>default</i>
state, then: if the nearest such ancestor's <code id=spelling-and-grammar-checking:attr-spellcheck-10><a href=#attr-spellcheck>spellcheck</a></code>
content attribute is in the <i>true</i> state, then checking is enabled; otherwise, checking is
- disabled.<li>Otherwise, if the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-3>default behavior</a>
+ disabled.<li>Otherwise, if the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-3>default behaviour</a>
is <a href=#concept-spellcheck-default-true id=spelling-and-grammar-checking:concept-spellcheck-default-true-2>true-by-default</a>, then checking is
- enabled.<li>Otherwise, if the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-4>default behavior</a>
+ enabled.<li>Otherwise, if the element's <a href=#concept-spellcheck-default id=spelling-and-grammar-checking:concept-spellcheck-default-4>default behaviour</a>
is <a href=#concept-spellcheck-default-false id=spelling-and-grammar-checking:concept-spellcheck-default-false>false-by-default</a>, then checking is
disabled.<li>Otherwise, if the element's parent element has <em>its</em> checking enabled, then checking
is enabled.<li>Otherwise, checking is disabled.</ol>
@@ -55685,7 +55685,7 @@
already present when the page was loaded, or that the user did not type, or text in controls that
the user has not focused, or in parts of e-mail addresses that the user agent is not confident
were misspelt). The <dfn id=dom-forcespellcheck><code>forceSpellCheck()</code></dfn> method,
- when invoked on an element, must override this behavior, forcing the user agent to consider all
+ when invoked on an element, must override this behaviour, forcing the user agent to consider all
spelling and grammar errors in text in that element for which checking is enabled to be of
interest to the user.</p>
@@ -56866,7 +56866,7 @@
<i id=the-draggable-attribute:missing-value-default><a href=#missing-value-default>missing value default</a></i>.</p>
<p>The <i>true</i> state means the element is draggable; the <i>false</i> state means that it is
- not. The <i>auto</i> state uses the default behavior of the user agent.</p>
+ not. The <i>auto</i> state uses the default behaviour of the user agent.</p>
<p>An element with a <code id=the-draggable-attribute:the-draggable-attribute-3><a href=#the-draggable-attribute>draggable</a></code> attribute should also have a
<code id=the-draggable-attribute:attr-title><a href=#attr-title>title</a></code> attribute that names the element for the purpose of
@@ -57607,7 +57607,7 @@
true:</p>
<ul><li><p>The <a href=#concept-task id=browsing-context-names:concept-task>task</a> in which the algorithm is running is currently
- processing an <a href=#activation-behavior id=browsing-context-names:activation-behavior>activation behavior</a> whose <code id=browsing-context-names:event-click><a href=#event-click>click</a></code> event
+ processing an <a href=#activation-behaviour id=browsing-context-names:activation-behaviour>activation behaviour</a> whose <code id=browsing-context-names:event-click><a href=#event-click>click</a></code> event
was <a href=#concept-events-trusted id=browsing-context-names:concept-events-trusted>trusted</a>.<li>
<p>The <a href=#concept-task id=browsing-context-names:concept-task-2>task</a> in which the algorithm is running is currently
@@ -57639,7 +57639,7 @@
the chosen browsing context must be the current one.</p>
<p>If the given browsing context name is <code>_self</code>, then this is an
- <a href=#explicit-self-navigation-override id=browsing-context-names:explicit-self-navigation-override>explicit self-navigation override</a>, which overrides the behavior of the
+ <a href=#explicit-self-navigation-override id=browsing-context-names:explicit-self-navigation-override>explicit self-navigation override</a>, which overrides the behaviour of the
<a href=#seamless-browsing-context-flag id=browsing-context-names:seamless-browsing-context-flag>seamless browsing context flag</a> set by the <code id=browsing-context-names:attr-iframe-seamless-2><a href=#attr-iframe-seamless>seamless</a></code> attribute on <code id=browsing-context-names:the-iframe-element-2><a href=#the-iframe-element>iframe</a></code> elements.</p>
<li><p>If the given browsing context name is <code>_parent</code>, then the chosen
@@ -58448,7 +58448,7 @@
location of an HTTP redirect (<a href=#concept-http-equivalent-codes id=origin:concept-http-equivalent-codes>or equivalent</a>
in other protocols), a <code id=origin:document-19><a href=#document>Document</a></code> created using the <code id=origin:dom-domimplementation-createdocument><a href=#dom-domimplementation-createdocument>createDocument()</a></code> API, etc)<dd>
- <p>The default behavior as defined in the DOM standard applies. <a href=#refsDOM>[DOM]</a>.</p>
+ <p>The default behaviour as defined in the DOM standard applies. <a href=#refsDOM>[DOM]</a>.</p>
<p class=note>The <a href=#origin-2 id=origin:origin-2-19>origin</a> is a globally unique identifier assigned when the
<code id=origin:document-20><a href=#document>Document</a></code> is created, and the <a href=#effective-script-origin id=origin:effective-script-origin-16>effective script origin</a> is initially an
@@ -59478,7 +59478,7 @@
<ul class=brief><li>The <code id=the-location-interface:location-10><a href=#location>Location</a></code> object's <i>relevant <code id=the-location-interface:document-13><a href=#document>Document</a></code></i> has
<a href=#completely-loaded id=the-location-interface:completely-loaded>completely loaded</a>, or<li>In the <a href=#concept-task id=the-location-interface:concept-task-2>task</a> in which the algorithm is running, an
- <a href=#activation-behavior id=the-location-interface:activation-behavior>activation behavior</a> is currently being processed whose <code id=the-location-interface:event-click><a href=#event-click>click</a></code> event was <a href=#concept-events-trusted id=the-location-interface:concept-events-trusted>trusted</a>, or<li>In the <a href=#concept-task id=the-location-interface:concept-task-3>task</a> in which the algorithm is running, the event
+ <a href=#activation-behaviour id=the-location-interface:activation-behaviour>activation behaviour</a> is currently being processed whose <code id=the-location-interface:event-click><a href=#event-click>click</a></code> event was <a href=#concept-events-trusted id=the-location-interface:concept-events-trusted>trusted</a>, or<li>In the <a href=#concept-task id=the-location-interface:concept-task-3>task</a> in which the algorithm is running, the event
listener for a <a href=#concept-events-trusted id=the-location-interface:concept-events-trusted-2>trusted</a> <code id=the-location-interface:event-click-2><a href=#event-click>click</a></code> event is being handled.</ul>
<li><p>If <var>mode</var> is <i>normal navigation</i>, then act as if the <code id=the-location-interface:dom-location-assign-5><a href=#dom-location-assign>assign()</a></code> method had been called with <var>value</var> as its argument. Otherwise, act as if the <code id=the-location-interface:dom-location-replace-5><a href=#dom-location-replace>replace()</a></code> method had been called with <var>value</var> as its argument.</ol>
@@ -64170,7 +64170,7 @@
<h3 id=dynamic-markup-insertion>8.3 <dfn>Dynamic markup insertion</dfn></h3>
<p class=note>APIs for dynamically inserting markup into the document interact with the parser,
- and thus their behavior varies depending on whether they are used with <a href=#html-documents id=dynamic-markup-insertion:html-documents>HTML documents</a>
+ and thus their behaviour varies depending on whether they are used with <a href=#html-documents id=dynamic-markup-insertion:html-documents>HTML documents</a>
(and the <a href=#html-parser id=dynamic-markup-insertion:html-parser>HTML parser</a>) or XHTML in <a href=#xml-documents id=dynamic-markup-insertion:xml-documents>XML documents</a> (and the <a href=#xml-parser id=dynamic-markup-insertion:xml-parser>XML
parser</a>).</p>
@@ -64372,12 +64372,12 @@
<p>In general, adds the given string(s) to the <code id=document.write():document><a href=#document>Document</a></code>'s input stream.</p>
- <p class=warning>This method has very idiosyncratic behavior. In some cases, this method can
+ <p class=warning>This method has very idiosyncratic behaviour. In some cases, this method can
affect the state of the <a href=#html-parser id=document.write():html-parser>HTML parser</a> while the parser is running, resulting in a DOM
that does not correspond to the source of the document (e.g. if the string written is the string
"<code><plaintext></code>" or "<code><!--</code>"). In other cases,
the call can clear the current page first, as if <code id=document.write():dom-document-open><a href=#dom-document-open>document.open()</a></code> had been called. In yet more cases, the method
- is simply ignored, or throws an exception. To make matters worse, the exact behavior of this
+ is simply ignored, or throws an exception. To make matters worse, the exact behaviour of this
method can in some cases be dependent on network latency, which can lead to failures that are very hard to debug. <strong>For all these reasons, use
of this method is strongly discouraged.</strong></p>
@@ -72555,7 +72555,7 @@
is rarely used, and frequently implemented incorrectly.</p>
<p class=note>This specification does not make any attempt to support EBCDIC-based encodings and
- UTF-32 in its algorithms; support and use of these encodings can thus lead to unexpected behavior
+ UTF-32 in its algorithms; support and use of these encodings can thus lead to unexpected behaviour
in implementations of this specification.</p>
@@ -72949,10 +72949,10 @@
which may have various side-effects, and either switches the state machine to a new state to
<i>reconsume</i> the same character, or switches it to a new state to consume the next character,
or stays in the same state to consume the next character. Some states have more complicated
- behavior and can consume several characters before switching to another state. In some cases, the
+ behaviour and can consume several characters before switching to another state. In some cases, the
tokenizer state is also changed by the tree construction stage.</p>
- <p>The exact behavior of certain states depends on the <a href=#insertion-mode id=tokenization:insertion-mode>insertion mode</a> and the
+ <p>The exact behaviour of certain states depends on the <a href=#insertion-mode id=tokenization:insertion-mode>insertion mode</a> and the
<a href=#stack-of-open-elements id=tokenization:stack-of-open-elements>stack of open elements</a>. Certain states also use a <dfn id=temporary-buffer><var>temporary buffer</var></dfn> to track progress.</p>
<p>The output of the tokenization step is a series of zero or more of the following tokens:
@@ -73831,7 +73831,7 @@
<p>This definition is used when parsing character references <a href=#character-reference-in-data-state id=tokenizing-character-references:character-reference-in-data-state>in text</a> and <a href=#character-reference-in-attribute-value-state id=tokenizing-character-references:character-reference-in-attribute-value-state>in
attributes</a>.</p>
- <p>The behavior depends on the identity of the next character (the one immediately after the
+ <p>The behaviour depends on the identity of the next character (the one immediately after the
U+0026 AMPERSAND character), as follows:</p>
<dl class=switch><dt>U+0009 CHARACTER TABULATION (tab)<dt>U+000A LINE FEED (LF)<dt>U+000C FORM FEED (FF)<dt>U+0020 SPACE<dt>U+003C LESS-THAN SIGN<dt>U+0026 AMPERSAND<dt>EOF<dt>The <a href=#additional-allowed-character id=tokenizing-character-references:additional-allowed-character>additional allowed character</a>, if there is one<dd>Not a character reference. No characters are consumed, and nothing is returned. (This is not
@@ -73839,7 +73839,7 @@
<p>Consume the U+0023 NUMBER SIGN.</p>
- <p>The behavior further depends on the character after the U+0023 NUMBER SIGN:</p>
+ <p>The behaviour further depends on the character after the U+0023 NUMBER SIGN:</p>
<dl class=switch><dt>U+0078 LATIN SMALL LETTER X<dt>U+0058 LATIN CAPITAL LETTER X<dd>
@@ -77819,7 +77819,7 @@
section provides a set of suggestions for rendering HTML documents that, if followed, are likely
to lead to a user experience that closely resembles the experience intended by the documents'
authors. So as to avoid confusion regarding the normativity of this section, RFC2119 terms have
- not been used. Instead, the term "expected" is used to indicate behavior that will lead to this
+ not been used. Instead, the term "expected" is used to indicate behaviour that will lead to this
experience. For the purposes of conformance for user agents designated as <a href=#renderingUA>supporting the suggested default rendering</a>, the term "expected" in this
section has the same conformance implications as the RFC2119-defined term "must".</i></p>
@@ -77828,7 +77828,7 @@
<p>In general, user agents are expected to support CSS, and many of the suggestions in this
section are expressed in CSS terms. User agents that use other presentation mechanisms can derive
- their expected behavior by translating from the CSS rules given in this section.</p>
+ their expected behaviour by translating from the CSS rules given in this section.</p>
<p>In the absence of style-layer rules to the contrary (e.g. author style sheets), user agents are
expected to render an element so that it conveys to the user the meaning that the element
@@ -80464,7 +80464,7 @@
<code>rev="made"</code>, use <code>rel="author"</code>.)<dt><dfn id=attr-a-urn><code>urn</code></dfn> on <code id=non-conforming-features:the-a-element-8><a href=#the-a-element>a</a></code> elements<dt><dfn id=attr-link-urn><code>urn</code></dfn> on <code id=non-conforming-features:the-link-element-4><a href=#the-link-element>link</a></code> elements<dd><p>Specify the preferred persistent identifier using the <code id=non-conforming-features:attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code> attribute instead.<dt><dfn id=attr-form-accept><code>accept</code></dfn> on <code id=non-conforming-features:the-form-element-2><a href=#the-form-element>form</a></code> elements<dd><p>Use the <code id=non-conforming-features:attr-input-accept><a href=#attr-input-accept>accept</a></code> attribute directly on the <code id=non-conforming-features:the-input-element><a href=#the-input-element>input</a></code> elements instead.<dt><dfn id=attr-area-nohref><code>nohref</code>
</dfn> on <code id=non-conforming-features:the-area-element-2><a href=#the-area-element>area</a></code> elements<dd><p>Omitting the <code id=non-conforming-features:attr-hyperlink-href-2><a href=#attr-hyperlink-href>href</a></code>
attribute is sufficient; the <code id=non-conforming-features:attr-area-nohref><a href=#attr-area-nohref>nohref</a></code> attribute is
unnecessary. Omit it altogether.<dt><dfn id=attr-head-profile><code>profile</code></dfn> on <code id=non-conforming-features:the-head-element><a href=#the-head-element>head</a></code> elements<dd><p>When used for declaring which <code id=non-conforming-features:the-meta-element><a href=#the-meta-element>meta</a></code> terms are
- used in the document, unnecessary; omit it altogether, and <a href=#concept-meta-extensions id=non-conforming-features:concept-meta-extensions>register the names</a>.<dd><p>When used for triggering specific user agent behaviors: use
+ used in the document, unnecessary; omit it altogether, and <a href=#concept-meta-extensions id=non-conforming-features:concept-meta-extensions>register the names</a>.<dd><p>When used for triggering specific user agent behaviours: use
a <code id=non-conforming-features:the-link-element-5><a href=#the-link-element>link</a></code> element instead.<dt><dfn id=attr-html-version><code>version</code></dfn> on <code id=non-conforming-features:the-html-element><a href=#the-html-element>html</a></code> elements<dd><p>Unnecessary. Omit it altogether.<dt><dfn id=attr-input-ismap><code>ismap</code></dfn> on <code id=non-conforming-features:the-input-element-2><a href=#the-input-element>input</a></code> elements<dd><p>Unnecessary. Omit it altogether. All <code id=non-conforming-features:the-input-element-3><a href=#the-input-element>input</a></code> elements with a <code id=non-conforming-features:attr-input-type><a href=#attr-input-type>type</a></code> attribute in the <a href="#image-button-state-(type=image)" id="non-conforming-features:image-button-state-(type=image)">Image
Button</a> state are processed as server-side image maps.<dt><dfn id=attr-input-usemap><code>usemap</code></dfn> on <code id=non-conforming-features:the-input-element-4><a href=#the-input-element>input</a></code> elements<dd><p>Use <code id=non-conforming-features:the-img-element-2><a href=#the-img-element>img</a></code> instead of <code id=non-conforming-features:the-input-element-5><a href=#the-input-element>input</a></code> for image maps.<dt><dfn id=attr-iframe-longdesc><code>longdesc</code></dfn> on <code id=non-conforming-features:the-iframe-element-2><a href=#the-iframe-element>iframe</a></code> elements<dt><dfn id=attr-img-longdesc><code>longdesc</code></dfn> on <code id=non-conforming-features:the-img-element-3><a href=#the-img-element>img</a></code> elements<dd><p>Use a regular <code id=non-conforming-features:the-a-element-9><a href=#the-a-element>a</a></code> element to link to the
description, or (in the case of images) use an <a href=#image-map id=non-conforming-features:image-map>image
@@ -81312,7 +81312,7 @@
<p>User agents must treat <code id=other-elements,-attributes-and-apis:plaintext><a href=#plaintext>plaintext</a></code> elements in a manner equivalent to
<code id=other-elements,-attributes-and-apis:the-pre-element-2><a href=#the-pre-element>pre</a></code> elements in terms of semantics and for purposes of rendering. (The parser has
- special behavior for this element, though.)</p>
+ special behaviour for this element, though.)</p>
<hr>
@@ -81471,7 +81471,7 @@
<hr>
<p>User agents must treat <code id=other-elements,-attributes-and-apis:xmp><a href=#xmp>xmp</a></code> elements in a manner equivalent to <code id=other-elements,-attributes-and-apis:the-pre-element-4><a href=#the-pre-element>pre</a></code>
- elements in terms of semantics and for purposes of rendering. (The parser has special behavior for
+ elements in terms of semantics and for purposes of rendering. (The parser has special behaviour for
this element though.)</p>
<hr>
@@ -81540,7 +81540,7 @@
elements.</p>
<p>The object returned for <code id=other-elements,-attributes-and-apis:dom-document-all-2><a href=#dom-document-all>all</a></code> has several unusual
- behaviors:</p>
+ behaviours:</p>
<ul><li><p>The user agent must act as if the ToBoolean() operator in JavaScript converts the object
returned for <code id=other-elements,-attributes-and-apis:dom-document-all-3><a href=#dom-document-all>all</a></code> to the false value.<li><p>The user agent must act as if, for the purposes of the <code>==</code> and <code>!=</code> operators in JavaScript, the object returned for <code id=other-elements,-attributes-and-apis:dom-document-all-4><a href=#dom-document-all>all</a></code> compares as equal to the <code>undefined</code> and
@@ -84588,7 +84588,7 @@
<tr><td> <code id=events-2:event-click><a href=#event-click>click</a></code>
<td> <code id=events-2:mouseevent><a href=#mouseevent>MouseEvent</a></code>
<td> Elements
- <td> Normally a mouse event; also synthetically fired at an element before its <a href=#activation-behavior id=events-2:activation-behavior>activation behavior</a> is run, when an element is activated from a non-pointer input device (e.g. a keyboard)
+ <td> Normally a mouse event; also synthetically fired at an element before its <a href=#activation-behaviour id=events-2:activation-behaviour>activation behaviour</a> is run, when an element is activated from a non-pointer input device (e.g. a keyboard)
<tr><td> <dfn id=event-close><code>close</code></dfn>
<td> <code id=events-2:event-12><a href=#event>Event</a></code>
Modified: source
===================================================================
--- source 2015-01-07 00:52:49 UTC (rev 8875)
+++ source 2015-01-07 01:02:44 UTC (rev 8876)
@@ -656,7 +656,7 @@
<p>To avoid exposing Web authors to the complexities of multithreading, the HTML and DOM APIs are
designed such that no script can ever detect the simultaneous execution of other scripts. Even
- with <span data-x="Worker">workers</span>, the intent is that the behavior of implementations can
+ with <span data-x="Worker">workers</span>, the intent is that the behaviour of implementations can
be thought of as completely serialising the execution of all scripts in all <span data-x="browsing
context">browsing contexts</span>.</p>
@@ -1490,7 +1490,7 @@
<dl>
- <dt>Unintuitive error-handling behavior</dt>
+ <dt>Unintuitive error-handling behaviour</dt>
<dd>
@@ -1520,14 +1520,14 @@
</dd>
- <dt>Errors where the error-handling behavior is not compatible with streaming user agents</dt>
+ <dt>Errors where the error-handling behaviour is not compatible with streaming user agents</dt>
<dd>
- <p>Some error-handling behavior, such as the behavior for the <code
+ <p>Some error-handling behaviour, such as the behaviour for the <code
data-x=""><table><hr>...</code> example mentioned above, are incompatible with streaming
user agents (user agents that process HTML files in one pass, without storing state). To avoid
- interoperability problems with such user agents, any syntax resulting in such behavior is
+ interoperability problems with such user agents, any syntax resulting in such behaviour is
considered invalid.</p>
</dd>
@@ -1633,7 +1633,7 @@
<div class="example">
<p>Another example of this is the DOCTYPE, which is required to trigger <span>no-quirks
- mode</span>, because the behavior of legacy user agents in <span>quirks mode</span> is often
+ mode</span>, because the behaviour of legacy user agents in <span>quirks mode</span> is often
largely undocumented.</p>
</div>
@@ -1779,7 +1779,7 @@
<dd>
- <p>Certain elements have default styles or behaviors that make certain combinations likely to
+ <p>Certain elements have default styles or behaviours that make certain combinations likely to
lead to confusion. Where these have equivalent alternatives without this problem, the confusing
combinations are disallowed.</p>
@@ -1793,7 +1793,7 @@
<p class="example">Another example would be the way <span>interactive content</span> cannot be
nested. For example, a <code>button</code> element cannot contain a <code>textarea</code>
- element. This is because the default behavior of such nesting interactive elements would be
+ element. This is because the default behaviour of such nesting interactive elements would be
highly confusing to users. Instead of nesting these elements, they can be placed side by
side.</p>
@@ -2467,7 +2467,7 @@
<p>User agents that are designated as supporting the suggested default rendering must, while so
designated, implement the rules in <a href="#rendering">the rendering section</a> that that
- section defines as the behavior that user agents are <em>expected</em> to implement.</p>
+ section defines as the behaviour that user agents are <em>expected</em> to implement.</p>
</dd>
@@ -2616,7 +2616,7 @@
<p>Some conformance requirements are phrased as requirements on elements, attributes, methods or
objects. Such requirements fall into two categories: those describing content model restrictions,
- and those describing implementation behavior. Those in the former category are requirements on
+ and those describing implementation behaviour. Those in the former category are requirements on
documents and authoring tools. Those in the second category are requirements on user agents.
Similarly, some conformance requirements are phrased as requirements on authors; such requirements
are to be interpreted as conformance requirements on the documents that authors produce. (In other
@@ -3797,8 +3797,8 @@
<p class="note">Implementors are strongly urged to carefully examine any third-party libraries
they might consider using to implement the parsing of syntaxes described below. For example, date
- libraries are likely to implement error handling behavior that differs from what is required in
- this specification, since error-handling behavior is often not defined in specifications that
+ libraries are likely to implement error handling behaviour that differs from what is required in
+ this specification, since error-handling behaviour is often not defined in specifications that
describe date syntaxes similar to those used in this specification, and thus implementations tend
to vary greatly in how they handle errors.</p>
@@ -6699,7 +6699,7 @@
<h4>Terminology</h4>
<p id="concept-http-equivalent">User agents can implement a variety of transfer protocols, but
- this specification mostly defines behavior in terms of HTTP. <ref spec=HTTP></p>
+ this specification mostly defines behaviour in terms of HTTP. <ref spec=HTTP></p>
<p>The <dfn data-x="concept-http-equivalent-get">HTTP GET method</dfn> is equivalent to the default
retrieval action of the protocol. For example, RETR in FTP. Such actions are idempotent and safe,
@@ -7426,7 +7426,7 @@
<p>If a reflecting IDL attribute has an unsigned integer type (<code
data-x="idl-unsigned-long">unsigned long</code>) that is <dfn>limited to only non-negative numbers
- greater than zero</dfn>, then the behavior is similar to the previous case, but zero is not
+ greater than zero</dfn>, then the behaviour is similar to the previous case, but zero is not
allowed. On getting, the content attribute must first be parsed according to the <span>rules for
parsing non-negative integers</span>, and if that is successful, and the value is in the range 1
to 2147483647 inclusive, the resulting value must be returned. If, on the other hand, it fails or
@@ -7450,7 +7450,7 @@
<p>If a reflecting IDL attribute has a floating-point number type (<code
data-x="idl-double">double</code> or <code data-x="idl-unrestricted-double">unrestricted
- double</code>) that is <dfn>limited to numbers greater than zero</dfn>, then the behavior is
+ double</code>) that is <dfn>limited to numbers greater than zero</dfn>, then the behaviour is
similar to the previous case, but zero and negative values are not allowed. On getting, the
content attribute must be parsed according to the <span>rules for parsing floating-point number
values</span>, and if that is successful and the value is greater than 0.0, the resulting value
@@ -7850,7 +7850,7 @@
<p>On getting, the <dfn><code data-x="dom-HTMLOptionsCollection-length">length</code></dfn>
attribute must return the number of nodes <span>represented by the collection</span>.</p>
- <p>On setting, the behavior depends on whether the new value is equal to, greater than, or less
+ <p>On setting, the behaviour depends on whether the new value is equal to, greater than, or less
than the number of nodes <span>represented by the collection</span> at that time. If the number is
the same, then setting the attribute must do nothing. If the new value is greater, then <var>n</var> new <code>option</code> elements with no attributes and no child nodes must be
appended to the <code>select</code> element on which the <code>HTMLOptionsCollection</code> is
@@ -8247,7 +8247,7 @@
</ol>
<p>The <dfn>internal structured cloning algorithm</dfn> is always called with two arguments,
- <var>input</var> and <var>memory</var>, and its behavior is as follows:</p>
+ <var>input</var> and <var>memory</var>, and its behaviour is as follows:</p>
<ol>
@@ -9928,7 +9928,7 @@
<h6>Metadata content</h6>
- <p><dfn>Metadata content</dfn> is content that sets up the presentation or behavior of the rest of
+ <p><dfn>Metadata content</dfn> is content that sets up the presentation or behaviour of the rest of
the content, or that sets up the relationship of the document with other documents, or that
conveys other "out of band" information.</p>
@@ -10796,7 +10796,7 @@
<p>The XML specification also allows the use of the <code data-x="attr-xml-space">xml:space</code>
attribute in the <span>XML namespace</span> on any element in an <span data-x="XML documents">XML
document</span>. This attribute has no effect on <span>HTML elements</span>, as the default
- behavior in HTML is to preserve whitespace. <ref spec=XML></p>
+ behaviour in HTML is to preserve whitespace. <ref spec=XML></p>
<p class="note">There is no way to serialise the <code data-x="attr-xml-space">xml:space</code>
attribute on <span>HTML elements</span> in the <code>text/html</code> syntax.</p>
@@ -11720,7 +11720,7 @@
<div w-nodev>
- <p>User agents must not derive any implementation behavior from these attributes or values.
+ <p>User agents must not derive any implementation behaviour from these attributes or values.
Specifications intended for user agents must not define these attributes to have any meaningful
values.</p>
@@ -13448,7 +13448,7 @@
<p>The <dfn><code data-x="attr-link-crossorigin">crossorigin</code></dfn> attribute is a <span>CORS
settings attribute</span>. It is intended for use with external resource links.</p>
- <p>The exact behavior for links to external resources depends on the exact relationship, as
+ <p>The exact behaviour for links to external resources depends on the exact relationship, as
defined for the relevant link type. Some of the attributes control whether or not the external
resource is to be applied (as defined below).</p>
@@ -13671,7 +13671,7 @@
<div w-nodev>
- <p>The <span>activation behavior</span> of <code>link</code> elements that create <span
+ <p>The <span>activation behaviour</span> of <code>link</code> elements that create <span
data-x="hyperlink">hyperlinks</span> is to run the following steps:</p>
<ol><!-- c.f. <a> and <area>'s similar sections -->
@@ -14576,14 +14576,14 @@
href="https://wiki.whatwg.org/wiki/PragmaExtensions">WHATWG Wiki PragmaExtensions page</a>. <ref spec=WHATWGWIKI></p>
<p>Such extensions must use a name that is identical to an HTTP header registered in the Permanent
- Message Header Field Registry, and must have behavior identical to that described for the HTTP
+ Message Header Field Registry, and must have behaviour identical to that described for the HTTP
header. <ref spec=IANAPERMHEADERS></p>
<p>Pragma directives corresponding to headers describing metadata, or not requiring specific user
agent processing, must not be registered; instead, use <span
data-x="concept-meta-extensions">metadata names</span>. Pragma directives corresponding to headers
that affect the HTTP processing model (e.g. caching) must not be registered, as they would result
- in HTTP-level behavior being different for user agents that implement HTML than for user agents
+ in HTTP-level behaviour being different for user agents that implement HTML than for user agents
that do not.</p>
<p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at any time to add a pragma
@@ -18909,7 +18909,7 @@
<pre><article lang="en-US">
<h1>My use of language and my cats</h1>
- <p>My cat's behavior hasn't changed much since her absence, except
+ <p>My cat's behaviour hasn't changed much since her absence, except
that she plays her new physique to the neighbors regularly, in an
attempt to get pets.</p>
<div lang="en-GB">
@@ -19017,7 +19017,7 @@
attributes may be used to indicate to the user the likely nature of the target resource before the
user follows the link.</p>
- <p>The <span>activation behavior</span> of <code>a</code> elements that create <span
+ <p>The <span>activation behaviour</span> of <code>a</code> elements that create <span
data-x="hyperlink">hyperlinks</span> is to run the following steps:</p>
<ol><!-- c.f. <area>'s similar section, also <link>'s -->
@@ -21982,7 +21982,7 @@
context</span> that will be used. <span w-nodev>User agents use this name when
<span>following hyperlinks</span>.</span></p>
- <p>When an <code>a</code> or <code>area</code> element's <span>activation behavior</span> is
+ <p>When an <code>a</code> or <code>area</code> element's <span>activation behaviour</span> is
invoked, the user agent may allow the user to indicate a preference regarding whether the
hyperlink is to be used for <span data-x="navigate">navigation</span> or whether the resource it
specifies is to be downloaded.</p>
@@ -22358,7 +22358,7 @@
--> (as described below). (Tokens that fail to resolve are ignored.) This may be done in parallel
with the primary request, and is independent of the result of that request.</p>
- <p>User agents should allow the user to adjust this behavior, for example in conjunction with a
+ <p>User agents should allow the user to adjust this behaviour, for example in conjunction with a
setting that disables the sending of HTTP <code data-x="http-referer">Referer</code> (sic)
headers. Based on the user's preferences, UAs may either <span>ignore</span> the <code
data-x="attr-hyperlink-ping">ping</code> attribute altogether, or selectively ignore URLs in the
@@ -25984,8 +25984,8 @@
<p>The <code>HTMLEmbedElement</code> object representing the element must expose the scriptable
interface of the <span>plugin</span> instantiated for the <code>embed</code> element, if any. At a
minimum, this interface must implement the <dfn data-x="dom-embed-caller">legacy caller
- operation</dfn>. (It is suggested that the default behavior of this legacy caller operation, e.g.
- the behavior of the default plugin's legacy caller operation, be to throw a
+ operation</dfn>. (It is suggested that the default behaviour of this legacy caller operation, e.g.
+ the behaviour of the default plugin's legacy caller operation, be to throw a
<code>NotSupportedError</code> exception.)</p>
</div>
@@ -26169,7 +26169,7 @@
<li>
<p>If the user has indicated a preference that this <code>object</code> element's <span>fallback
- content</span> be shown instead of the element's usual behavior, then jump to the step below
+ content</span> be shown instead of the element's usual behaviour, then jump to the step below
labeled <i>fallback</i>.</p>
<p class="note">For example, a user could ask for the element's <span>fallback content</span> to
@@ -26756,7 +26756,7 @@
<p>All <code>object</code> elements have a <dfn data-x="dom-object-caller">legacy caller
operation</dfn>. If the <code>object</code> element has an instantiated <span>plugin</span> that
supports a scriptable interface that defines a legacy caller operation, then that must be the
- behavior of the object's legacy caller operation. Otherwise, the object's legacy caller operation
+ behaviour of the object's legacy caller operation. Otherwise, the object's legacy caller operation
must be to throw a <code>NotSupportedError</code> exception.</p>
</div>
@@ -27565,7 +27565,7 @@
<p>If the author isn't sure if user agents will all be able to render the media resources
provided, the author can listen to the <code data-x="event-error">error</code> event on the last
- <code>source</code> element and trigger fallback behavior:</p>
+ <code>source</code> element and trigger fallback behaviour:</p>
<pre><script>
function fallback(video) {
@@ -28796,7 +28796,7 @@
<li>
- <p>Optionally, run the following substeps. This is the expected behavior if the user agent
+ <p>Optionally, run the following substeps. This is the expected behaviour if the user agent
intends to not attempt to fetch the resource until the user requests it explicitly (e.g. as
a way to implement the <code data-x="attr-media-preload">preload</code> attribute's <code
data-x="attr-media-preload-none">none</code> keyword).</p>
@@ -30006,7 +30006,7 @@
<p class="note">User agents do not need to support autoplay, and it is suggested that user
agents honor user preferences on the matter. Authors are urged to use the <code
data-x="attr-media-autoplay">autoplay</code> attribute rather than using script to force the
- video to play, so as to allow the user to override the behavior if so desired.</p>
+ video to play, so as to allow the user to override the behaviour if so desired.</p>
<p>In any case, the user agent must finally <span>queue a task</span> to <span>fire a simple
event</span> named <code data-x="event-media-canplaythrough">canplaythrough</code> at the element.</p>
@@ -30048,7 +30048,7 @@
<p class="note">Authors are urged to use the <code data-x="attr-media-autoplay">autoplay</code>
attribute rather than using script to trigger automatic playback, as this allows the user to
override the automatic playback when it is not desired, e.g. when using a screen reader. Authors
- are also encouraged to consider not using the automatic playback behavior at all, and instead to
+ are also encouraged to consider not using the automatic playback behaviour at all, and instead to
let the user agent wait for the user to start playback explicitly.</p>
<div w-nodev>
@@ -30918,7 +30918,7 @@
value (which would equal the time of the last frame, and might be positive Infinity).</p>
<p class="note">The range might be continuously changing, e.g. if the user agent is buffering a
- sliding window on an infinite stream. This is the behavior seen with DVRs viewing live TV, for
+ sliding window on an infinite stream. This is the behaviour seen with DVRs viewing live TV, for
instance.</p>
<p>User agents should adopt adopt a very liberal and optimistic view of what is seekable. User
@@ -34165,7 +34165,7 @@
element</span> without affecting the <code>MediaController</code>, but such features are
considered relatively advanced and unlikely to be useful to most users.</p>
- <p>The <span>activation behavior</span> of a <span>media element</span> that is <span
+ <p>The <span>activation behaviour</span> of a <span>media element</span> that is <span
data-x="expose a user interface to the user">exposing a user interface to the user</span> must be
to run the following steps:</p>
@@ -35421,7 +35421,7 @@
<div w-nodev>
- <p>The <span>activation behavior</span> of <code>area</code> elements is to run the following
+ <p>The <span>activation behaviour</span> of <code>area</code> elements is to run the following
steps:</p>
<ol><!-- c.f. <a>'s similar section -->
@@ -35988,7 +35988,7 @@
<p class="note">The corresponding IDL attributes for <code data-x="dom-img-height">img</code> and
<code data-x="dom-input-height">input</code> elements are defined in those respective elements'
- sections, as they are slightly more specific to those elements' other behaviors.</p>
+ sections, as they are slightly more specific to those elements' other behaviours.</p>
</div>
@@ -36341,7 +36341,7 @@
element, again in <span>tree order</span>, followed finally by those elements whose parent is a
<code>tfoot</code> element, still in <span>tree order</span>.</p>
- <p>The behavior of the <dfn><code data-x="dom-table-insertRow">insertRow(<var>index</var>)</code></dfn> method depends on the state of the table. When it is called,
+ <p>The behaviour of the <dfn><code data-x="dom-table-insertRow">insertRow(<var>index</var>)</code></dfn> method depends on the state of the table. When it is called,
the method must act as required by the first item in the following list of conditions that
describes the state of the table and the <var>index</var> argument:</p>
@@ -39839,7 +39839,7 @@
<hr>
- <p>The <span>activation behavior</span> of a <span>sorting interface <code>th</code>
+ <p>The <span>activation behaviour</span> of a <span>sorting interface <code>th</code>
element</span> is to <span>set the sort key</span> to the <code>th</code> element.</p>
<p class="note">The <code>table</code> will be sorted the next time the user agent <span
@@ -41336,9 +41336,9 @@
then the first such descendant in <span>tree order</span> is the <code>label</code> element's
<span>labeled control</span>.</p>
- <p>The <code>label</code> element's exact default presentation and behavior, in particular what
- its <span>activation behavior</span> might be, if anything, should match the platform's label
- behavior. The <span>activation behavior</span> of a <code>label</code> element for events targeted
+ <p>The <code>label</code> element's exact default presentation and behaviour, in particular what
+ its <span>activation behaviour</span> might be, if anything, should match the platform's label
+ behaviour. The <span>activation behaviour</span> of a <code>label</code> element for events targeted
at <span>interactive content</span> descendants of a <code>label</code> element, and any
descendants of those <span>interactive content</span> descendants, must be to do nothing.</p>
@@ -41356,7 +41356,7 @@
<pre><label><input type=checkbox name=lost> Lost</label></pre>
- <p>On other platforms, the behavior might be just to focus the control, or do nothing.</p>
+ <p>On other platforms, the behaviour might be just to focus the control, or do nothing.</p>
</div>
@@ -41729,7 +41729,7 @@
<code>input</code> element depends on the state of its
<code data-x="attr-input-type">type</code> attribute.
The subsections that define each type also clearly define in normative "bookkeeping" sections
- which of these feature apply, and which <dfn>do not apply</dfn>, to each type. The behavior of
+ which of these feature apply, and which <dfn>do not apply</dfn>, to each type. The behaviour of
these features depends on whether they apply or not, as defined in their various sections (q.v.
for <a href="#common-input-element-attributes">content attributes</a>, for <a
href="#common-input-element-apis">APIs</a>, for <a
@@ -42986,8 +42986,8 @@
<hr>
- <p>When an <code>input</code> element is first created, the element's rendering and behavior must
- be set to the rendering and behavior defined for the <code data-x="attr-input-type">type</code>
+ <p>When an <code>input</code> element is first created, the element's rendering and behaviour must
+ be set to the rendering and behaviour defined for the <code data-x="attr-input-type">type</code>
attribute's state, and the <span>value sanitization algorithm</span>, if one is defined for the
<code data-x="attr-input-type">type</code> attribute's state, must be invoked.</p>
@@ -43024,7 +43024,7 @@
otherwise, and then set the control's <span data-x="concept-input-value-dirty-flag">dirty value
flag</span> to false.</p></li>
- <li><p>Update the element's rendering and behavior to the new state's.</p></li>
+ <li><p>Update the element's rendering and behaviour to the new state's.</p></li>
<li><p><dfn>Signal a type change</dfn> for the element. (The <span
data-x="attr-input-type-radio">Radio Button</span> state uses this, in particular.)</p></li>
@@ -43045,7 +43045,7 @@
The <code data-x="attr-fae-form">form</code> attribute is used to explicitly associate the <code>input</code> element with its <span>form owner</span>.
The <code data-x="attr-fe-autofocus">autofocus</code> attribute controls focus.
The <code data-x="attr-fe-inputmode">inputmode</code> attribute controls the user interface's input modality for the control.
- The <code data-x="attr-fe-autocomplete">autocomplete</code> attribute controls how the user agent provides autofill behavior.
+ The <code data-x="attr-fe-autocomplete">autocomplete</code> attribute controls how the user agent provides autofill behaviour.
</p>
<div w-nodev>
@@ -45643,14 +45643,14 @@
activation steps</span> consist of setting the <span
data-x="concept-fe-checked">checkedness</span> and the element's <code
data-x="dom-input-indeterminate">indeterminate</code> IDL attribute back to the values they had
- before the <span>pre-click activation steps</span> were run. The <span>activation behavior</span>
+ before the <span>pre-click activation steps</span> were run. The <span>activation behaviour</span>
is to <span>fire a simple event</span> that bubbles named <code
data-x="event-input-input">input</code> at the element and then <span>fire a simple event</span>
that bubbles named <code data-x="event-input-change">change</code> at the element. <!-- It's not
cancelable. Once this fires, the control is checked, end of story. --></p>
<p>If the element is not <i data-x="concept-fe-mutable">mutable</i>, it has no <span>activation
- behavior</span>.</p>
+ behaviour</span>.</p>
<p><strong>Constraint validation</strong>: If the element is <i
data-x="concept-input-required">required</i> and its <span
@@ -45812,7 +45812,7 @@
element's <span data-x="concept-fe-checked">checkedness</span> to true; or else, if there was no
such element, or that element is no longer in <var>R</var>'s <span>radio button group</span>, or
if <var>R</var> no longer has a <span>radio button group</span>, setting <var>R</var>'s <span
- data-x="concept-fe-checked">checkedness</span> to false. The <span>activation behavior</span> for
+ data-x="concept-fe-checked">checkedness</span> to false. The <span>activation behaviour</span> for
<var>R</var> is to <span>fire a simple event</span> that bubbles named <code
data-x="event-input-input">input</code> at <var>R</var> and then <span>fire a simple event</span>
that bubbles named <code data-x="event-input-change">change</code> at <var>R</var>. <!-- It's not
@@ -45825,7 +45825,7 @@
-->
<p>If the element is not <i data-x="concept-fe-mutable">mutable</i>, it has no <span>activation
- behavior</span>.</p>
+ behaviour</span>.</p>
<p><strong>Constraint validation</strong>: If an element in the <i data-x="radio button group">radio button group</i> is <i
data-x="concept-input-required">required</i>, and all of the <code>input</code> elements in the
@@ -45933,7 +45933,7 @@
files</span>.</p>
<p>If the element is <i data-x="concept-fe-mutable">mutable</i>, then the element's
- <span>activation behavior</span> is to run the following steps:</p>
+ <span>activation behaviour</span> is to run the following steps:</p>
<ol>
@@ -45970,7 +45970,7 @@
data-x="event-input-change">change</code> at the <code>input</code> element.</p>
<p>If the element is not <i data-x="concept-fe-mutable">mutable</i>, it has no <span>activation
- behavior</span> and the user agent must not allow the user to change the element's selection.</p>
+ behaviour</span> and the user agent must not allow the user to change the element's selection.</p>
<p><strong>Constraint validation</strong>: If the element is <i
data-x="concept-input-required">required</i> and the list of <span
@@ -46190,13 +46190,13 @@
<div w-nodev>
<p>If the element is <i data-x="concept-fe-mutable">mutable</i>, then the element's
- <span>activation behavior</span> is as follows: if the element has a <span>form owner</span>,
+ <span>activation behaviour</span> is as follows: if the element has a <span>form owner</span>,
and the element's <span>node document</span> is <span>fully active</span>,
<span data-x="concept-form-submit">submit</span> the <span>form owner</span> from the
<code>input</code> element; otherwise, do nothing.</p>
<p>If the element is not <i data-x="concept-fe-mutable">mutable</i>, it has no <span>activation
- behavior</span>.</p>
+ behaviour</span>.</p>
</div>
@@ -46384,7 +46384,7 @@
<code data-x="attr-input-src">src</code> attribute; if the element is <i
data-x="concept-fe-mutable">mutable</i>, the user agent should allow the user to select this <span
data-x="concept-input-type-image-coordinate">coordinate</span>, and the element's <span>activation
- behavior</span> is as follows: if the element has a <span>form owner</span>, and the element's
+ behaviour</span> is as follows: if the element has a <span>form owner</span>, and the element's
<span>node document</span> is <span>fully active</span>, take the user's selected <span
data-x="concept-input-type-image-coordinate">coordinate</span>, and <span
data-x="concept-form-submit">submit</span> the <code>input</code> element's <span>form owner</span>
@@ -46393,7 +46393,7 @@
<p>Otherwise, the element <span>represents</span> a submit button whose label is given by the
value of the <code data-x="attr-input-alt">alt</code> attribute; if the element is <i
- data-x="concept-fe-mutable">mutable</i>, then the element's <span>activation behavior</span> is as
+ data-x="concept-fe-mutable">mutable</i>, then the element's <span>activation behaviour</span> is as
follows: if the element has a <span>form owner</span>, and the element's <span>node document</span> is
<span>fully active</span>, set the <span data-x="concept-input-type-image-coordinate">selected
coordinate</span> to (0,0), and <span data-x="concept-form-submit">submit</span> the
@@ -46401,8 +46401,8 @@
<p>In either case, if the element is <i data-x="concept-fe-mutable">mutable</i> but has no
<span>form owner</span> or the element's <span>node document</span> is not <span>fully active</span>,
- then its <span>activation behavior</span> must be to do nothing. If the element is not <i
- data-x="concept-fe-mutable">mutable</i>, it has no <span>activation behavior</span>.</p>
+ then its <span>activation behaviour</span> must be to do nothing. If the element is not <i
+ data-x="concept-fe-mutable">mutable</i>, it has no <span>activation behaviour</span>.</p>
<p>The <dfn data-x="concept-input-type-image-coordinate">selected coordinate</dfn> must consist of
an <var>x</var>-component and a <var>y</var>-component. The coordinates
@@ -46514,7 +46514,7 @@
</div>
- <p class="note">Many aspects of this state's behavior are similar to the behavior of the
+ <p class="note">Many aspects of this state's behaviour are similar to the behaviour of the
<code>img</code> element. Readers are encouraged to read that section, where many of the same
requirements are described in more detail.</p>
@@ -46563,13 +46563,13 @@
<div w-nodev>
<p>If the element is <i data-x="concept-fe-mutable">mutable</i>, then the element's
- <span>activation behavior</span>, if the element has a <span>form owner</span> and the element's
+ <span>activation behaviour</span>, if the element has a <span>form owner</span> and the element's
<span>node document</span> is <span>fully active</span>, is to <span
data-x="concept-form-reset">reset</span> the <span>form owner</span>; otherwise, it is to do
nothing.</p>
<p>If the element is not <i data-x="concept-fe-mutable">mutable</i>, it has no <span>activation
- behavior</span>.</p>
+ behaviour</span>.</p>
<p><strong>Constraint validation</strong>: The element is <span>barred from constraint
validation</span>.</p>
@@ -46643,7 +46643,7 @@
</div>
- <p>The <code>input</code> element <span>represents</span> a button with no default behavior. A
+ <p>The <code>input</code> element <span>represents</span> a button with no default behaviour. A
label for the button must be provided in the <code data-x="attr-input-value">value</code>
attribute, though it may be the empty string. <span w-nodev>If the element has a <code
data-x="attr-input-value">value</code> attribute, the button's label must be the value of that
@@ -46653,10 +46653,10 @@
<div w-nodev>
<p>If the element is <i data-x="concept-fe-mutable">mutable</i>, the element's <span>activation
- behavior</span> is to do nothing.</p>
+ behaviour</span> is to do nothing.</p>
<p>If the element is not <i data-x="concept-fe-mutable">mutable</i>, it has no <span>activation
- behavior</span>.</p>
+ behaviour</span>.</p>
<p><strong>Constraint validation</strong>: The element is <span>barred from constraint
validation</span>.</p>
@@ -47497,7 +47497,7 @@
existing entry in the <code>input</code> element's <span
data-x="concept-fe-values">values</span> to have the value given by the selected
suggestion's <span data-x="concept-option-value">value</span>, as if the user had himself added
- an entry with that value, or edited an existing entry to be that value. Which behavior is to be
+ an entry with that value, or edited an existing entry to be that value. Which behaviour is to be
applied depends on the user interface in a user-agent-defined manner.</p>
</dd>
@@ -47768,7 +47768,7 @@
<p>The <dfn><code data-x="dom-input-value">value</code></dfn> IDL attribute allows scripts to
manipulate the <span data-x="concept-fe-value">value</span> of an <code>input</code> element. The
- attribute is in one of the following modes, which define its behavior:</p>
+ attribute is in one of the following modes, which define its behaviour:</p>
<dl>
@@ -48063,7 +48063,7 @@
<div w-nodev>
- <h5 id="common-input-element-events">Common event behaviors</h5>
+ <h5 id="common-input-element-events">Common event behaviours</h5>
<p>When the <code data-x="event-input-input">input</code> and <code
data-x="event-input-change">change</code> events <span data-x="concept-input-apply">apply</span>
@@ -48078,7 +48078,7 @@
data-x="event-input-input">input</code> event comes before the corresponding <code
data-x="event-input-change">change</code> event (if any).</p>
- <p>When an <code>input</code> element has a defined <span>activation behavior</span>, the rules
+ <p>When an <code>input</code> element has a defined <span>activation behaviour</span>, the rules
for dispatching these events, if they <span data-x="concept-input-apply">apply</span>, are given
in the section above that defines the <code data-x="attr-input-type">type</code> attribute's
state. (This is the case for all <code>input</code> controls with the <code
@@ -48087,7 +48087,7 @@
data-x="attr-input-type-radio">Radio Button</span> state, or the <span
data-x="attr-input-type-file">File Upload</span> state.)</p>
- <p>For <code>input</code> elements without a defined <span>activation behavior</span>, but to
+ <p>For <code>input</code> elements without a defined <span>activation behaviour</span>, but to
which these events <span data-x="concept-input-apply">apply</span>, and for which the user
interface involves both interactive manipulation and an explicit commit action, then when the user
changes the element's <span data-x="concept-fe-value">value</span>, the user agent must
@@ -48104,7 +48104,7 @@
whereas the <code data-x="event-input-change">change</code> event would only fire when the user
let go of the knob, committing to a specific value.</p>
- <p>For <code>input</code> elements without a defined <span>activation behavior</span>, but to
+ <p>For <code>input</code> elements without a defined <span>activation behaviour</span>, but to
which these events <span data-x="concept-input-apply">apply</span>, and for which the user
interface involves an explicit commit action but no intermediate manipulation, then any time the
user commits a change to the element's <span data-x="concept-fe-value">value</span>, the user
@@ -48125,7 +48125,7 @@
selecting a date from the drop down calendar and then dismissing the drop down would be a commit
action.</p>
- <p>For <code>input</code> elements without a defined <span>activation behavior</span>, but to
+ <p>For <code>input</code> elements without a defined <span>activation behaviour</span>, but to
which these events <span data-x="concept-input-apply">apply</span>, any time the user causes the
element's <span data-x="concept-fe-value">value</span> to change without an explicit commit
action, the user agent must <span>queue a task</span> to <span>fire a simple event</span> that
@@ -48230,7 +48230,7 @@
<p>The element is a <span data-x="concept-button">button</span>.</p>
- <p>The <dfn><code data-x="attr-button-type">type</code></dfn> attribute controls the behavior of
+ <p>The <dfn><code data-x="attr-button-type">type</code></dfn> attribute controls the behaviour of
the button when it is activated. It is an <span>enumerated attribute</span>. The following table
lists the keywords and states for the attribute — the keywords in the left column map to the
states in the cell in the second column on the same row as the keyword.</p>
@@ -48276,7 +48276,7 @@
validation</span>.</p>
<p>When a <code>button</code> element is not <span data-x="concept-fe-disabled">disabled</span>,
- its <span>activation behavior</span> element is to run the steps defined in the following list for
+ its <span>activation behaviour</span> element is to run the steps defined in the following list for
the current state of the element's <code data-x="attr-button-type">type</code> attribute:</p>
<dl>
@@ -48662,7 +48662,7 @@
The <code data-x="attr-fe-name">name</code> attribute represents the element's name.
The <code data-x="attr-fe-disabled">disabled</code> attribute is used to make the control non-interactive and to prevent its value from being submitted.
The <code data-x="attr-fe-autofocus">autofocus</code> attribute controls focus.
- The <code data-x="attr-fe-autocomplete">autocomplete</code> attribute controls how the user agent provides autofill behavior.
+ The <code data-x="attr-fe-autocomplete">autocomplete</code> attribute controls how the user agent provides autofill behaviour.
</p>
<p>A <code>select</code> element that is not <span data-x="concept-fe-disabled">disabled</span> is
@@ -49367,7 +49367,7 @@
<p>On setting, the <code data-x="dom-option-text">text</code> attribute must act as if the
<code>textContent</code> IDL attribute on the element had been set to the new value.</p>
- <p>The <dfn><code data-x="dom-option-form">form</code></dfn> IDL attribute's behavior depends on
+ <p>The <dfn><code data-x="dom-option-form">form</code></dfn> IDL attribute's behaviour depends on
whether the <code>option</code> element is in a <code>select</code> element or not. If the
<code>option</code> has a <code>select</code> element as its parent, or has an
<code>optgroup</code> element as its parent and that <code>optgroup</code> element has a
@@ -49742,7 +49742,7 @@
The <code data-x="attr-fe-inputmode">inputmode</code> attribute controls the user interface's input
modality for the control.
The <code data-x="attr-fe-autocomplete">autocomplete</code> attribute controls how the user agent
- provides autofill behavior.
+ provides autofill behaviour.
</p>
<!--TOPIC:DOM APIs-->
@@ -51132,7 +51132,7 @@
<div w-nodev>
- <p>The <dfn><code data-x="dom-legend-form">form</code></dfn> IDL attribute's behavior depends on
+ <p>The <dfn><code data-x="dom-legend-form">form</code></dfn> IDL attribute's behaviour depends on
whether the <code>legend</code> element is in a <code>fieldset</code> element or not. If the
<code>legend</code> has a <code>fieldset</code> element as its parent, then the <code
data-x="dom-legend-form">form</code> IDL attribute must return the same value as the <code
@@ -54817,12 +54817,12 @@
<p>If the user agent supports letting the user submit a form implicitly (for example, on some
platforms hitting the "enter" key while a text field is <span>focused</span> implicitly submits the form), then
doing so for a form whose <span>default button</span> has a defined <span>activation
- behavior</span> must cause the user agent to <span>run synthetic click activation steps</span> on
+ behaviour</span> must cause the user agent to <span>run synthetic click activation steps</span> on
that <span>default button</span>.</p>
<p class="note">Consequently, if the <span>default button</span> is <span
data-x="concept-fe-disabled">disabled</span>, the form is not submitted when such an implicit
- submission mechanism is used. (A button has no <span>activation behavior</span> when
+ submission mechanism is used. (A button has no <span>activation behaviour</span> when
disabled.)</p>
<p class="note">There are pages on the Web that are only usable if there is a way to implicitly
@@ -54996,7 +54996,7 @@
<td> <span data-x="submit-mailto-body">Mail as body</span>
</table>
- <p>If <var>scheme</var> is not one of those listed in this table, then the behavior is
+ <p>If <var>scheme</var> is not one of those listed in this table, then the behaviour is
not defined by this specification. User agents should, in the absence of another specification
defining this, act in a manner analogous to that defined in this specification for similar
schemes.</p>
@@ -55045,7 +55045,7 @@
</ol>
- <p>The behaviors are as follows:</p>
+ <p>The behaviours are as follows:</p>
<dl>
@@ -56576,7 +56576,7 @@
<hr>
<p>If the element's <span data-x="command-facet-DisabledState">Disabled State</span> is false
- (enabled) then the element's <span>activation behavior</span> depends on the element's <code
+ (enabled) then the element's <span>activation behaviour</span> depends on the element's <code
data-x="attr-menuitem-type">type</code> and <code data-x="attr-menuitem-command">command</code>
attributes, as follows:</p>
@@ -56587,7 +56587,7 @@
<dd><p>The user agent must <span>run synthetic click activation steps</span> on the element's
<span>master command</span>.</p></dd>
- <!-- we know it has a defined <span>activation behavior</span> if we get here -->
+ <!-- we know it has a defined <span>activation behaviour</span> if we get here -->
<dt>If the <code data-x="attr-menuitem-type">type</code> attribute is in the <span
@@ -56615,7 +56615,7 @@
<dt>Otherwise</dt>
- <dd><p>The element's <span>activation behavior</span> is to do nothing.</p></dd>
+ <dd><p>The element's <span>activation behaviour</span> is to do nothing.</p></dd>
</dl>
@@ -56625,7 +56625,7 @@
<!-- v2COMMAND: Expose the Triggers facet again. -->
<p>If the element's <span data-x="command-facet-DisabledState">Disabled State</span> is true
- (disabled) then the element has no <span>activation behavior</span>.</p>
+ (disabled) then the element has no <span>activation behaviour</span>.</p>
</div>
@@ -57147,7 +57147,7 @@
false. (The command is never checked.)</p>
<p>The <span data-x="command-facet-Action">Action</span> of the command, if the element has a
- defined <span>activation behavior</span>, is to <span>run synthetic click activation steps</span>
+ defined <span>activation behaviour</span>, is to <span>run synthetic click activation steps</span>
on the element. Otherwise, it is just to <span>fire a <code data-x="event-click">click</code>
event</span> at the element.</p>
@@ -57232,7 +57232,7 @@
is <span data-x="concept-fe-checked">checked</span> attribute, and false otherwise.</p>
<p>The <span data-x="command-facet-Action">Action</span> of the command, if the element has a
- defined <span>activation behavior</span>, is to <span>run synthetic click activation steps</span>
+ defined <span>activation behaviour</span>, is to <span>run synthetic click activation steps</span>
on the element. Otherwise, it is just to <span>fire a <code data-x="event-click">click</code>
event</span> at the element.</p>
@@ -57332,7 +57332,7 @@
false otherwise.</p>
<p>The <span data-x="command-facet-Action">Action</span> of the command, if the element has a
- defined <span>activation behavior</span><!-- it doesn't if the element is disabled -->, is to
+ defined <span>activation behaviour</span><!-- it doesn't if the element is disabled -->, is to
<span>run synthetic click activation steps</span> on the element. Otherwise, it is just to
<span>fire a <code data-x="event-click">click</code> event</span> at the element.</p>
@@ -57504,10 +57504,10 @@
<li>Run the <span>focusing steps</span> for the element.</li>
- <li>If the element has a defined <span>activation behavior</span>, <span>run synthetic click
+ <li>If the element has a defined <span>activation behaviour</span>, <span>run synthetic click
activation steps</span> on the element.</li>
- <li>Otherwise, if the element does not have a defined <span>activation behavior</span>,
+ <li>Otherwise, if the element does not have a defined <span>activation behaviour</span>,
<span>fire a <code data-x="event-click">click</code> event</span> at the element.</li>
</ol>
@@ -58220,7 +58220,7 @@
data-x="attr-script-async">async</code> attribute is specified, to cause legacy Web browsers that
only support <code data-x="attr-script-defer">defer</code> (and not <code
data-x="attr-script-async">async</code>) to fall back to the <code
- data-x="attr-script-defer">defer</code> behavior instead of the blocking behavior that
+ data-x="attr-script-defer">defer</code> behaviour instead of the blocking behaviour that
is the default.</p>
<p>The <dfn><code data-x="attr-script-crossorigin">crossorigin</code></dfn> attribute is a
@@ -62678,7 +62678,7 @@
<p>The <dfn><code data-x="dom-context-2d-arcTo">arcTo(<var>x1</var>, <var>y1</var>, <var>x2</var>, <var>y2</var>, <var>radiusX</var>,
<var>radiusY</var>, <var>rotation</var>)</code></dfn> method must first
- <span>ensure there is a subpath</span> for <span data-x="">(<var>x1</var>, <var>y1</var>)</span>. Then, the behavior depends on the arguments and the last point in the
+ <span>ensure there is a subpath</span> for <span data-x="">(<var>x1</var>, <var>y1</var>)</span>. Then, the behaviour depends on the arguments and the last point in the
subpath, as described below.</p>
<p>Negative values for <var>radiusX</var> or <var>radiusY</var> must cause the
@@ -63774,7 +63774,7 @@
exception and abort these steps.</p></li>
<li><p>Create a new <code>CanvasPattern</code> object with the image <var>image</var>
- and the repetition behavior given by <var>repetition</var>.</p></li>
+ and the repetition behaviour given by <var>repetition</var>.</p></li>
<!--ADD-TOPIC:Security-->
<li><p>If <span>the <var>image argument</var> is not origin-clean</span>, then mark the
@@ -63809,9 +63809,9 @@
<p>Place a copy of the image on the bitmap, anchored such that its top left corner is at the
origin of the coordinate space, with one coordinate space unit per CSS pixel of the image, then
place repeated copies of this image horizontally to the left and right, if the repetition
- behavior is "<code data-x="">repeat-x</code>", or vertically up and down, if the repetition
- behavior is "<code data-x="">repeat-y</code>", or in all four directions all over the bitmap, if
- the repetition behavior is "<code data-x="">repeat</code>".</p>
+ behaviour is "<code data-x="">repeat-x</code>", or vertically up and down, if the repetition
+ behaviour is "<code data-x="">repeat-y</code>", or in all four directions all over the bitmap, if
+ the repetition behaviour is "<code data-x="">repeat</code>".</p>
<p>If the original image data is a bitmap image, the value painted at a point in the area of the
repetitions is computed by filtering the original image data. When scaling up, if the <code
@@ -63820,8 +63820,8 @@
may use any filtering algorithm (for example bilinear interpolation or nearest-neighbor). When
such a filtering algorithm requires a pixel value from outside the original image data, it must
instead use the value from wrapping the pixel's coordinates to the original image's dimensions.
- (That is, the filter uses 'repeat' behavior, regardless of the value of the pattern's repetition
- behavior.)</p>
+ (That is, the filter uses 'repeat' behaviour, regardless of the value of the pattern's repetition
+ behaviour.)</p>
<!-- drawImage() has similar paragraphs with different rules -->
</li>
@@ -64821,7 +64821,7 @@
rectangle is computed by filtering the original image data. The user agent may use any filtering
algorithm (for example bilinear interpolation or nearest-neighbor). When the filtering algorithm
requires a pixel value from outside the original image data, it must instead use the value from
- the nearest edge pixel. (That is, the filter uses 'clamp-to-edge' behavior.) When the filtering
+ the nearest edge pixel. (That is, the filter uses 'clamp-to-edge' behaviour.) When the filtering
algorithm requires a pixel value from outside the source rectangle but inside the original image
data, then the value from the original image data must be used.</p>
<!-- see CORE-32111 and:
@@ -67243,9 +67243,9 @@
<li>
<p>An element falling into one of the following categories between the time the user begins to
- indicate an intent to trigger the element's <span>activation behavior</span> and either the
+ indicate an intent to trigger the element's <span>activation behaviour</span> and either the
time the user stops indicating an intent to trigger the element's <span>activation
- behavior</span>, or the time the element's <span>activation behavior</span> has finished
+ behaviour</span>, or the time the element's <span>activation behaviour</span> has finished
running, which ever comes first:</p>
<ul>
@@ -69040,7 +69040,7 @@
which the attribute was invoked, while that element is an <span data-x="concept-item">item</span>,
and matches nothing the rest of the time.</p>
- <p>The <dfn><code data-x="dom-itemValue">itemValue</code></dfn> IDL attribute's behavior depends on
+ <p>The <dfn><code data-x="dom-itemValue">itemValue</code></dfn> IDL attribute's behaviour depends on
the element, as follows:</p>
<dl>
@@ -72075,7 +72075,7 @@
<h3>Activation</h3>
- <p>Certain elements in HTML have an <span>activation behavior</span>, which means that the user
+ <p>Certain elements in HTML have an <span>activation behaviour</span>, which means that the user
can activate them. This triggers a sequence of events dependent on the activation mechanism, and
normally culminating in a <code data-x="event-click">click</code> event<span w-nodev>, as
described below</span>.</p>
@@ -72083,8 +72083,8 @@
<div w-nodev>
<p>The user agent should allow the user to manually trigger elements that have an <span>activation
- behavior</span>, for instance using keyboard or voice input, or through mouse clicks. When the
- user triggers an element with a defined <span>activation behavior</span> in a manner other than
+ behaviour</span>, for instance using keyboard or voice input, or through mouse clicks. When the
+ user triggers an element with a defined <span>activation behaviour</span> in a manner other than
clicking it, the default action of the interaction event must be to <span>run synthetic click
activation steps</span> on the element.</p> <!-- interaction event spec point -->
@@ -72169,7 +72169,7 @@
script. The <code data-x="dom-click">click()</code> method can be used to make the <span>run
synthetic click activation steps</span> algorithm happen programmatically.</p>
- <p class="note">Click-focusing behavior (e.g. the focusing of a text field when user clicks in
+ <p class="note">Click-focusing behaviour (e.g. the focusing of a text field when user clicks in
one) typically happens before the click, when the mouse button is first depressed, and is
therefore not discussed here.</p> <!-- interaction event spec point -->
@@ -72178,7 +72178,7 @@
<ol>
- <li><p>If <var>target</var> has a defined <span>activation behavior</span>, then return
+ <li><p>If <var>target</var> has a defined <span>activation behaviour</span>, then return
<var>target</var> and abort these steps.</p></li>
<li><p>If <var>target</var> has a parent element, then set <var>target</var> to
@@ -72195,7 +72195,7 @@
<dfn>canceled activation steps</dfn> defined for that element, if any.</p>
<p>When a user agent is to <dfn>run post-click activation steps</dfn> on an element, it must run
- the <dfn>activation behavior</dfn> defined for that element, if any. Activation behaviors can
+ the <dfn>activation behaviour</dfn> defined for that element, if any. Activation behaviours can
refer to the <code data-x="event-click">click</code> event that was fired by the steps above
leading up to this point.</p>
@@ -72746,7 +72746,7 @@
</dl>
<p>An element that has its <span>tabindex focus flag</span> set but does not otherwise have an
- <span>activation behavior</span> defined has an <span>activation behavior</span> that does
+ <span>activation behaviour</span> defined has an <span>activation behaviour</span> that does
nothing.</p>
<p class="note">This means that an element that is only focusable because of its <code
@@ -73068,7 +73068,7 @@
<li id="unfocus-causes-change-event"><p>If <var>entry</var> is an <code>input</code>
element, and the <code data-x="event-input-change">change</code> event <span
data-x="concept-input-apply">applies</span> to the element, and the element does not have a
- defined <span>activation behavior</span>, and the user has changed the element's <span
+ defined <span>activation behaviour</span>, and the user has changed the element's <span
data-x="concept-fe-value">value</span> or its list of <span
data-x="concept-input-type-file-selected">selected files</span> while the control was focused
without committing that change, then <span>fire a simple event</span> that bubbles named <code
@@ -73588,7 +73588,7 @@
<p class="note">Historically, the <code data-x="dom-window-blur">focus()</code> and <code
data-x="dom-window-blur">blur()</code> methods actually affected the system-level focus of the
system widget (e.g. tab or window) that contained the <span>browsing context</span>, but hostile
- sites widely abuse this behavior to the user's detriment.</p>
+ sites widely abuse this behaviour to the user's detriment.</p>
<p>The <dfn><code data-x="dom-focus">focus()</code></dfn> method on elements, when invoked, must
run the following algorithm:</p>
@@ -74020,8 +74020,8 @@
host</span> (e.g. using <code data-x="attr-contenteditable">contenteditable</code>).</p>
<p>For each element, user agents must establish a <dfn data-x="concept-spellcheck-default">default
- behavior</dfn>, either through defaults or through preferences expressed by the user. There are
- three possible default behaviors for each element:</p>
+ behaviour</dfn>, either through defaults or through preferences expressed by the user. There are
+ three possible default behaviours for each element:</p>
<dl>
@@ -74035,8 +74035,8 @@
<dt><dfn data-x="concept-spellcheck-default-inherit">inherit-by-default</dfn>
- <dd>The element's default behavior is the same as its parent element's. Elements that have no
- parent element cannot have this as their default behavior.
+ <dd>The element's default behaviour is the same as its parent element's. Elements that have no
+ parent element cannot have this as their default behaviour.
</dl>
@@ -74052,7 +74052,7 @@
<p class="note">The <i>true</i> state indicates that the element is to have its spelling and
grammar checked. The <i>default</i> state indicates that the element is to act according to a
- default behavior, possibly based on the parent element's own <code
+ default behaviour, possibly based on the parent element's own <code
data-x="attr-spellcheck">spellcheck</code> state, as defined below. The <i>false</i> state
indicates that the element is not to be checked.</p>
@@ -74095,10 +74095,10 @@
return true if the element's <code data-x="attr-spellcheck">spellcheck</code> content attribute is
in the <i>true</i> state, or if the element's <code data-x="attr-spellcheck">spellcheck</code>
content attribute is in the <i>default</i> state and the element's <span
- data-x="concept-spellcheck-default">default behavior</span> is <span
+ data-x="concept-spellcheck-default">default behaviour</span> is <span
data-x="concept-spellcheck-default-true">true-by-default</span>, or if the element's <code
data-x="attr-spellcheck">spellcheck</code> content attribute is in the <i>default</i> state and the
- element's <span data-x="concept-spellcheck-default">default behavior</span> is <span
+ element's <span data-x="concept-spellcheck-default">default behaviour</span> is <span
data-x="concept-spellcheck-default-inherit">inherit-by-default</span> and the element's parent
element's <code data-x="dom-spellcheck">spellcheck</code> IDL attribute would return true;
otherwise, if none of those conditions applies, then the attribute must instead return false.</p>
@@ -74174,11 +74174,11 @@
<!-- default -->
- <li>Otherwise, if the element's <span data-x="concept-spellcheck-default">default behavior</span>
+ <li>Otherwise, if the element's <span data-x="concept-spellcheck-default">default behaviour</span>
is <span data-x="concept-spellcheck-default-true">true-by-default</span>, then checking is
enabled.</li>
- <li>Otherwise, if the element's <span data-x="concept-spellcheck-default">default behavior</span>
+ <li>Otherwise, if the element's <span data-x="concept-spellcheck-default">default behaviour</span>
is <span data-x="concept-spellcheck-default-false">false-by-default</span>, then checking is
disabled.</li>
@@ -74207,7 +74207,7 @@
already present when the page was loaded, or that the user did not type, or text in controls that
the user has not focused, or in parts of e-mail addresses that the user agent is not confident
were misspelt). The <dfn><code data-x="dom-forceSpellCheck">forceSpellCheck()</code></dfn> method,
- when invoked on an element, must override this behavior, forcing the user agent to consider all
+ when invoked on an element, must override this behaviour, forcing the user agent to consider all
spelling and grammar errors in text in that element for which checking is enabled to be of
interest to the user.</p>
@@ -76421,7 +76421,7 @@
<i data-x="missing value default">missing value default</i>.</p>
<p>The <i>true</i> state means the element is draggable; the <i>false</i> state means that it is
- not. The <i>auto</i> state uses the default behavior of the user agent.</p>
+ not. The <i>auto</i> state uses the default behaviour of the user agent.</p>
<p>An element with a <code data-x="attr-draggable">draggable</code> attribute should also have a
<code data-x="attr-title">title</code> attribute that names the element for the purpose of
@@ -77484,7 +77484,7 @@
<ul>
<li><p>The <span data-x="concept-task">task</span> in which the algorithm is running is currently
- processing an <span>activation behavior</span> whose <code data-x="event-click">click</code> event
+ processing an <span>activation behaviour</span> whose <code data-x="event-click">click</code> event
was <span data-x="concept-events-trusted">trusted</span>.</li>
<li>
@@ -77532,7 +77532,7 @@
the chosen browsing context must be the current one.</p>
<p>If the given browsing context name is <code data-x="">_self</code>, then this is an
- <span>explicit self-navigation override</span>, which overrides the behavior of the
+ <span>explicit self-navigation override</span>, which overrides the behaviour of the
<span>seamless browsing context flag</span> set by the <code
data-x="attr-iframe-seamless">seamless</code> attribute on <code>iframe</code> elements.</p>
@@ -78700,7 +78700,7 @@
<dd>
- <p>The default behavior as defined in the DOM standard applies. <ref spec=DOM>.</p>
+ <p>The default behaviour as defined in the DOM standard applies. <ref spec=DOM>.</p>
<p class="note">The <span>origin</span> is a globally unique identifier assigned when the
<code>Document</code> is created, and the <span>effective script origin</span> is initially an
@@ -80184,7 +80184,7 @@
<span>completely loaded</span>, or</li>
<li>In the <span data-x="concept-task">task</span> in which the algorithm is running, an
- <span>activation behavior</span> is currently being processed whose <code
+ <span>activation behaviour</span> is currently being processed whose <code
data-x="event-click">click</code> event was <span
data-x="concept-events-trusted">trusted</span>, or</li>
@@ -86551,8 +86551,8 @@
<ol>
- <!-- Aryeh says: Copies Firefox behavior as of January 2011 (4.0b8). WebKit is somewhat laxer,
- and Opera throws no exceptions at all. gsnedders reports Opera's behavior causes site-compat
+ <!-- Aryeh says: Copies Firefox behaviour as of January 2011 (4.0b8). WebKit is somewhat laxer,
+ and Opera throws no exceptions at all. gsnedders reports Opera's behaviour causes site-compat
problems, and I figure most sites depend on Firefox if on anything, so go with that. -->
<!-- Since updated to drop whitespace, based on the arguments here:
@@ -86720,7 +86720,7 @@
<h3><dfn>Dynamic markup insertion</dfn></h3>
<p class="note">APIs for dynamically inserting markup into the document interact with the parser,
- and thus their behavior varies depending on whether they are used with <span>HTML documents</span>
+ and thus their behaviour varies depending on whether they are used with <span>HTML documents</span>
(and the <span>HTML parser</span>) or XHTML in <span>XML documents</span> (and the <span>XML
parser</span>).</p>
@@ -87044,13 +87044,13 @@
<p>In general, adds the given string(s) to the <code>Document</code>'s input stream.</p>
- <p class="warning">This method has very idiosyncratic behavior. In some cases, this method can
+ <p class="warning">This method has very idiosyncratic behaviour. In some cases, this method can
affect the state of the <span>HTML parser</span> while the parser is running, resulting in a DOM
that does not correspond to the source of the document (e.g. if the string written is the string
"<code data-x=""><plaintext></code>" or "<code data-x=""><!--</code>"). In other cases,
the call can clear the current page first, as if <code
data-x="dom-document-open">document.open()</code> had been called. In yet more cases, the method
- is simply ignored, or throws an exception. To make matters worse, the exact behavior of this
+ is simply ignored, or throws an exception. To make matters worse, the exact behaviour of this
method can in some cases be dependent on network latency<!--
Namely, in the following case:
@@ -97676,7 +97676,7 @@
is rarely used, and frequently implemented incorrectly.</p>
<p class="note">This specification does not make any attempt to support EBCDIC-based encodings and
- UTF-32 in its algorithms; support and use of these encodings can thus lead to unexpected behavior
+ UTF-32 in its algorithms; support and use of these encodings can thus lead to unexpected behaviour
in implementations of this specification.</p>
@@ -98304,10 +98304,10 @@
which may have various side-effects, and either switches the state machine to a new state to
<i>reconsume</i> the same character, or switches it to a new state to consume the next character,
or stays in the same state to consume the next character. Some states have more complicated
- behavior and can consume several characters before switching to another state. In some cases, the
+ behaviour and can consume several characters before switching to another state. In some cases, the
tokenizer state is also changed by the tree construction stage.</p>
- <p>The exact behavior of certain states depends on the <span>insertion mode</span> and the
+ <p>The exact behaviour of certain states depends on the <span>insertion mode</span> and the
<span>stack of open elements</span>. Certain states also use a <dfn><var data-x="temporary
buffer">temporary buffer</var></dfn> to track progress.</p>
@@ -100349,7 +100349,7 @@
data state">in text</span> and <span data-x="character reference in attribute value state">in
attributes</span>.</p>
- <p>The behavior depends on the identity of the next character (the one immediately after the
+ <p>The behaviour depends on the identity of the next character (the one immediately after the
U+0026 AMPERSAND character), as follows:</p>
<dl class="switch">
@@ -100374,7 +100374,7 @@
<p>Consume the U+0023 NUMBER SIGN.</p>
- <p>The behavior further depends on the character after the U+0023 NUMBER SIGN:</p>
+ <p>The behaviour further depends on the character after the U+0023 NUMBER SIGN:</p>
<dl class="switch">
@@ -106408,7 +106408,7 @@
section provides a set of suggestions for rendering HTML documents that, if followed, are likely
to lead to a user experience that closely resembles the experience intended by the documents'
authors. So as to avoid confusion regarding the normativity of this section, RFC2119 terms have
- not been used. Instead, the term "expected" is used to indicate behavior that will lead to this
+ not been used. Instead, the term "expected" is used to indicate behaviour that will lead to this
experience. For the purposes of conformance for user agents designated as <a
href="#renderingUA">supporting the suggested default rendering</a>, the term "expected" in this
section has the same conformance implications as the RFC2119-defined term "must".</i></p>
@@ -106418,7 +106418,7 @@
<p>In general, user agents are expected to support CSS, and many of the suggestions in this
section are expressed in CSS terms. User agents that use other presentation mechanisms can derive
- their expected behavior by translating from the CSS rules given in this section.</p>
+ their expected behaviour by translating from the CSS rules given in this section.</p>
<p>In the absence of style-layer rules to the contrary (e.g. author style sheets), user agents are
expected to render an element so that it conveys to the user the meaning that the element
@@ -109331,7 +109331,7 @@
<dd><p>When used for declaring which <code>meta</code> terms are
used in the document, unnecessary; omit it altogether, and <span
data-x="concept-meta-extensions">register the names</span>.</p></dd>
- <dd><p>When used for triggering specific user agent behaviors: use
+ <dd><p>When used for triggering specific user agent behaviours: use
a <code>link</code> element instead.</p></dd>
<dt><dfn><code data-x="attr-html-version">version</code></dfn> on <code>html</code> elements</dt>
@@ -110470,7 +110470,7 @@
<p>User agents must treat <code>plaintext</code> elements in a manner equivalent to
<code>pre</code> elements in terms of semantics and for purposes of rendering. (The parser has
- special behavior for this element, though.)</p>
+ special behaviour for this element, though.)</p>
<hr>
@@ -110638,7 +110638,7 @@
<hr>
<p>User agents must treat <code>xmp</code> elements in a manner equivalent to <code>pre</code>
- elements in terms of semantics and for purposes of rendering. (The parser has special behavior for
+ elements in terms of semantics and for purposes of rendering. (The parser has special behaviour for
this element though.)</p>
<hr>
@@ -110718,7 +110718,7 @@
elements.</p>
<p>The object returned for <code data-x="dom-document-all">all</code> has several unusual
- behaviors:</p>
+ behaviours:</p>
<ul>
@@ -115492,7 +115492,7 @@
<td> <code data-x="event-click">click</code>
<td> <code>MouseEvent</code>
<td> Elements
- <td> Normally a mouse event; also synthetically fired at an element before its <span>activation behavior</span> is run, when an element is activated from a non-pointer input device (e.g. a keyboard)
+ <td> Normally a mouse event; also synthetically fired at an element before its <span>activation behaviour</span> is run, when an element is activated from a non-pointer input device (e.g. a keyboard)
<tr> <!-- close -->
<td> <dfn><code data-x="event-close">close</code></dfn>
More information about the Commit-Watchers
mailing list