mdn · Josh-Cena · Feb 11, 2025 · Feb 9, 2025 · Feb 11, 2025 · Feb 11, 2025
@@ -12,7 +12,5 @@ Hyperlinks connect webpages or data items to one another. In HTML, {{HTMLElement
 
 - [Hyperlink](https://en.wikipedia.org/wiki/Hyperlink) on Wikipedia
 - [Creating links](/en-US/docs/Learn_web_development/Core/Structuring_content/Creating_links)
-- [Links in HTML Documents - W3C](https://www.w3.org/TR/1999/REC-html401-19991224/struct/links.html)
-- [HTML a - hyperlink - W3C](https://w3c.github.io/html-reference/a.html)
 - [`<a>` on MDN](/en-US/docs/Web/HTML/Element/a)
 - [`<link>` on MDN](/en-US/docs/Web/HTML/Element/link)
@@ -12,7 +12,7 @@ IMSC is the result of an international effort to bring together popular profiles
 
 IMSC was designed to be a practical application of SMPTE-TT ([SMPTE ST 2052-1](https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7291854)), which is designated as a safe-harbor format by the [FCC](https://www.law.cornell.edu/cfr/text/47/79.103). As a result, most SMPTE-TT documents should render correctly using IMSC renderers (see [the limitations](https://www.w3.org/TR/ttml-imsc1.0.1/#smpte-tt-smpte-st-2052-1)), and the conversion guidelines from CTA 608/708 to SMPTE-TT ([SMPTE RP 2052-10](https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7289645) and [SMPTE RP 2052-11](https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7290363)) are also applicable to IMSC.
 
-IMSC is also a syntactic superset of both [SDP-US](https://www.w3.org/TR/ttml10-sdp-us/) and [EBU-TT-D](https://tech.ebu.ch/publications/tech3380), such that documents that conform to either of these two formats are valid IMSC documents and can be rendered by IMSC renderers — see [Compatibility with other TTML-based specifications](https://www.w3.org/TR/2018/REC-ttml-imsc1.0.1-20180424/#interop-examples) for more details.
+IMSC is also a syntactic superset of both [SDP-US](https://www.w3.org/TR/ttml10-sdp-us/) and [EBU-TT-D](https://tech.ebu.ch/publications/tech3380), such that documents that conform to either of these two formats are valid IMSC documents and can be rendered by IMSC renderers — see [Compatibility with other TTML-based specifications](https://w3c.github.io/imsc/imsc1/spec/ttml-ww-profiles.html#interop-examples) for more details.
 
 IMSC traces its origins to the CFF-TT format, and [CFF-TT documents](https://www.w3.org/TR/ttml-imsc1.1/#cff-tt) can be converted to IMSC relatively easily.
 

@@ -626,7 +626,7 @@ Along with the Harding tool, is generally recognized to be one of the two "gold
 
 - [CSS Color Module Level 3](https://www.w3.org/TR/css-color-3/)
 - [Personalization Semantics Explainer 1.0](https://www.w3.org/TR/personalization-semantics-1.0/). Working Draft
-- [Personalization Tools 1.0](https://www.w3.org/TR/2019/WD-personalization-semantics-tools-1.0-20190711/) Working Draft
+- [WAI-Adapt: Tools Module](https://www.w3.org/TR/adapt-tools/) Working Draft
 - [Three Flashes or Below Threshold Understanding SC 2.3.1](https://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-does-not-violate.html) Understanding WCAG 2.0 (Older, but contains some explanations of references made in the WCAG 2.1 criteria)
 - [Three Flashes or Below Threshold Understanding Success Criterion 2.3.1](https://www.w3.org/WAI/WCAG21/Understanding/three-flashes-or-below-threshold.html) Understanding WCAG 2.1
 - [Understanding Success Criteria 1.4.3: Contrast (Minimum)](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html)

@@ -8,7 +8,7 @@ browser-compat: api.CSSKeyframeRule.style
 
 {{ APIRef("CSSOM") }}
 
-The read-only **`CSSKeyframeRule.style`** property is the {{ domxref("CSSStyleDeclaration") }} interface for the [declaration block](https://www.w3.org/TR/1998/REC-CSS2-19980512/syndata.html#block) of the {{ domxref("CSSKeyframeRule") }}.
+The read-only **`CSSKeyframeRule.style`** property is the {{ domxref("CSSStyleDeclaration") }} interface for the declaration block of the {{ domxref("CSSKeyframeRule") }}.
 
 ## Value
 

@@ -8,7 +8,7 @@ browser-compat: api.CSSStyleRule.style
 
 {{ APIRef("CSSOM") }}
 
-The read-only **`style`** property is the {{ domxref("CSSStyleDeclaration") }} interface for the [declaration block](https://www.w3.org/TR/1998/REC-CSS2-19980512/syndata.html#block) of the {{ DOMXref("CSSStyleRule") }}.
+The read-only **`style`** property is the {{ domxref("CSSStyleDeclaration") }} interface for the declaration block of the {{ DOMXref("CSSStyleRule") }}.
 
 ## Value
 

@@ -30,16 +30,7 @@ getData(format)
 
 A string representing the drag data for the specified `format`. If the drag operation has no data or the operation has no data for the specified `format`, this method returns an empty string.
 
-### Caveats
-
-- Data availability
-
-  - : The [HTML Drag and Drop Specification](https://www.w3.org/TR/2011/WD-html5-20110113/dnd.html#drag-data-store-mode) dictates a `drag data store mode`.
-    This may result in unexpected behavior, being
-    **`DataTransfer.getData()`** not returning an expected
-    value, because not all browsers enforce this restriction.
-
-    During the `dragstart` and `drop` events, it is safe to access the data. For all other events, the data should be considered unavailable. Despite this, the items and their formats can still be enumerated.
+Note that `DataTransfer.getData()` may not return an expected value, because it only allows reading and writing data for specified events. During the `dragstart` and `drop` events, it is safe to access the data. For all other events, the data should be considered unavailable. Despite this, the items and their formats can still be enumerated.
 
 ## Examples
 

@@ -23,9 +23,13 @@ createAttributeNS(namespaceURI, qualifiedName)
 ### Parameters
 
 - `namespaceURI`
-  - : A string that specifies the [namespace URI](https://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/glossary.html#dt-namespaceURI) to associate with the attribute.
-    The {{DOMxRef("Attr.namespaceURI", "namespaceURI")}} property of the created attribute is initialized with the value of `namespaceURI`.
-    See [Valid Namespace URIs](#important_namespace_uris).
+  - : A string that specifies the {{DOMxRef("Attr.namespaceURI", "namespaceURI")}} to associate with the attribute. Some important namespace URIs are:
+    - [HTML](/en-US/docs/Web/HTML)
+      - : `http://www.w3.org/1999/xhtml`
+    - [SVG](/en-US/docs/Web/SVG)
+      - : `http://www.w3.org/2000/svg`
+    - [MathML](/en-US/docs/Web/MathML)
+      - : `http://www.w3.org/1998/Math/MathML`
 - `qualifiedName`
   - : A string that specifies the name of attribute to be created.
     The {{DOMxRef("Attr.name", "name")}} property of the created attribute is initialized with the value of `qualifiedName`.
@@ -37,19 +41,10 @@ The new {{domxref("Attr")}} node.
 ### Exceptions
 
 - `NamespaceError` {{domxref("DOMException")}}
-  - : Thrown if the [`namespaceURI`](#namespaceuri) value is not a valid [namespace URI](https://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/glossary.html#dt-namespaceURI).
+  - : Thrown if the [`namespaceURI`](#namespaceuri) value is not a valid namespace URI.
 - `InvalidCharacterError` {{domxref("DOMException")}}
   - : Thrown if the [`qualifiedName`](#qualifiedname) value is not a valid [XML name](https://www.w3.org/TR/REC-xml/#dt-name); for example, it starts with a number, hyphen, or period, or contains characters other than alphanumeric characters, underscores, hyphens, or periods.
 
-## Important Namespace URIs
-
-- [HTML](/en-US/docs/Web/HTML)
-  - : `http://www.w3.org/1999/xhtml`
-- [SVG](/en-US/docs/Web/SVG)
-  - : `http://www.w3.org/2000/svg`
-- [MathML](/en-US/docs/Web/MathML)
-  - : `http://www.w3.org/1998/Math/MathML`
-
 ## Examples
 
 ```js

@@ -23,9 +23,13 @@ createElementNS(namespaceURI, qualifiedName, options)
 ### Parameters
 
 - `namespaceURI`
-  - : A string that specifies the [namespace URI](https://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/glossary.html#dt-namespaceURI) to associate with the element.
-    The {{DOMxRef("element.namespaceURI", "namespaceURI")}} property of the created element is initialized with the value of _namespaceURI_.
-    See [Valid Namespace URIs](#important_namespace_uris).
+  - : A string that specifies the {{DOMxRef("element.namespaceURI", "namespaceURI")}} to associate with the element. Some important namespace URIs are:
+    - [HTML](/en-US/docs/Web/HTML)
+      - : `http://www.w3.org/1999/xhtml`
+    - [SVG](/en-US/docs/Web/SVG)
+      - : `http://www.w3.org/2000/svg`
+    - [MathML](/en-US/docs/Web/MathML)
+      - : `http://www.w3.org/1998/Math/MathML`
 - `qualifiedName`
   - : A string that specifies the type of element to be created.
     The {{DOMxRef("node.nodeName", "nodeName")}} property of the created element is initialized with the value of _qualifiedName_.
@@ -45,19 +49,10 @@ The new {{DOMxRef("Element")}}.
 ### Exceptions
 
 - `NamespaceError` {{domxref("DOMException")}}
-  - : Thrown if the [`namespaceURI`](#namespaceuri) value is not a valid [namespace URI](https://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/glossary.html#dt-namespaceURI).
+  - : Thrown if the [`namespaceURI`](#namespaceuri) value is not a valid namespace URI.
 - `InvalidCharacterError` {{domxref("DOMException")}}
   - : Thrown if the [`qualifiedName`](#qualifiedname) value is not a valid [XML name](https://www.w3.org/TR/REC-xml/#dt-name); for example, it starts with a number, hyphen, or period, or contains characters other than alphanumeric characters, underscores, hyphens, or periods.
 
-## Important Namespace URIs
-
-- [HTML](/en-US/docs/Web/HTML)
-  - : `http://www.w3.org/1999/xhtml`
-- [SVG](/en-US/docs/Web/SVG)
-  - : `http://www.w3.org/2000/svg`
-- [MathML](/en-US/docs/Web/MathML)
-  - : `http://www.w3.org/1998/Math/MathML`
-
 ## Examples
 
 This creates a new `<div>` element in the {{Glossary("XHTML")}} namespace and
@@ -113,4 +108,3 @@ elements from two different namespaces within a single document:
 - {{DOMxRef("document.createElement()")}}
 - {{DOMxRef("document.createTextNode()")}}
 - {{DOMxRef("Element.namespaceURI")}}
-- [Namespaces in XML](https://www.w3.org/TR/1999/REC-xml-names-19990114/)
@@ -24,7 +24,7 @@ evaluate(xpathExpression, contextNode, namespaceResolver, resultType, result)
 - `xpathExpression`
   - : A string representing the _xpath_ to be evaluated.
 - `contextNode`
-  - : The _context node_ for the query (see the [XPath specification](https://www.w3.org/TR/1999/REC-xpath-19991116/)).
+  - : The _context node_ for the query.
     It's common to pass `document` as the context node.
 - `namespaceResolver`
   - : A function that will be passed any namespace prefixes

@@ -18,7 +18,7 @@ scrollbars (if present).
 
 When `clientHeight` is used on the root element (the
 `<html>` element), (or on `<body>` if the document is
-in quirks mode), the viewport's height (excluding any scrollbar) is returned. [This is a special case of `clientHeight`](https://www.w3.org/TR/2016/WD-cssom-view-1-20160317/#dom-element-clientheight).
+in quirks mode), the viewport's height (excluding any scrollbar) is returned.
 
 > [!NOTE]
 > This property will round the value to an integer. If you need

@@ -15,7 +15,7 @@ present).
 
 When `clientWidth` is used on the root element (the
 `<html>` element), (or on `<body>` if the document is
-in quirks mode), the viewport's width (excluding any scrollbar) is returned. [This is a special case of `clientWidth`](https://www.w3.org/TR/2016/WD-cssom-view-1-20160317/#dom-element-clientwidth).
+in quirks mode), the viewport's width (excluding any scrollbar) is returned.
 
 > [!NOTE]
 > This property will round the value to an integer. If you need

@@ -128,7 +128,7 @@ name = "<script>alert('I am John in an annoying alert!')</script>";
 el.innerHTML = name; // harmless in this case
 ```
 
-Although this may look like a [cross-site scripting](https://en.wikipedia.org/wiki/Cross-site_scripting) attack, the result is harmless. HTML specifies that a {{HTMLElement("script")}} tag inserted with `innerHTML` [should not execute](https://www.w3.org/TR/2008/WD-html5-20080610/dom.html#innerhtml0).
+Although this may look like a [cross-site scripting](https://en.wikipedia.org/wiki/Cross-site_scripting) attack, the result is harmless. A {{HTMLElement("script")}} tag inserted with `innerHTML` will not execute.
 
 However, there are ways to execute JavaScript without using {{HTMLElement("script")}} elements, so there is still a security risk whenever you use `innerHTML` to set strings over which you have no control.
 For example:

@@ -14,9 +14,7 @@ This property is used when there are multiple possible targets for the ending re
 
 ## Value
 
-An {{domxref("SVGAnimatedString")}} indicating the ending resource target that opens the document when the link is activated.
-
-Sample values can be found [here](https://www.w3.org/TR/2011/REC-SVG11-20110816/linking.html#AElementTargetAttribute)
+An {{domxref("SVGAnimatedString")}} indicating the ending resource target that opens the document when the link is activated. See {{SVGAttr("target")}} for valid values.
 
 ## Examples
 

@@ -15,41 +15,25 @@ creates a new {{domxref("XMLHttpRequest")}}.
 
 ```js-nolint
 new XMLHttpRequest()
+// Non-standard
+new XMLHttpRequest(options)
 ```
 
 ### Parameters
 
-None.
+There are no standard parameters. However, Firefox allows a non-standard parameter:
+
+- `options` {{non-standard_inline}}
+  - : An object that can contain the following flag:
+    - `mozAnon`
+      - : A boolean. When setting this flag to `true` will cause the browser not to expose the {{Glossary("origin")}} and user credentials when fetching resources. Most important, this means that {{Glossary("Cookie", "cookies")}} will not be sent unless explicitly added using `setRequestHeader`.
 
 ### Return value
 
 A new {{domxref("XMLHttpRequest")}} object. The object must be prepared by at least
 calling {{domxref("XMLHttpRequest.open", "open()")}} to initialize it before calling
 {{domxref("XMLHttpRequest.send", "send()")}} to send the request to the server.
 
-## Non-standard Firefox syntax
-
-Firefox 16 added a non-standard parameter to the constructor that can enable anonymous
-mode (see [Firefox bug 692677](https://bugzil.la/692677)). Setting the `mozAnon` flag to `true`
-effectively resembles the [`AnonXMLHttpRequest()`](https://www.w3.org/TR/2012/WD-XMLHttpRequest-20120117/#dom-anonxmlhttprequest)
-constructor described in older versions of the XMLHttpRequest specification.
-
-```js
-const request = new XMLHttpRequest(paramsDictionary);
-```
-
-### Parameters (non-standard)
-
-- `objParameters`
-
-  - : One flag you can set:
-
-    - `mozAnon`
-      - : Boolean: Setting this flag to `true` will cause the browser not to
-        expose the {{Glossary("origin")}} and [user credentials](https://www.w3.org/TR/2012/WD-XMLHttpRequest-20120117/#user-credentials) when fetching resources. Most important, this means that
-        {{Glossary("Cookie", "cookies")}} will not be sent unless explicitly added using
-        setRequestHeader.
-
 ## Specifications
 
 {{Specifications}}

@@ -265,7 +265,7 @@ The recommended way to enable cross-site scripting is to use the `Access-Control
 
 ### XMLHttpRequests being stopped
 
-If you conclude with an XMLHttpRequest receiving `status=0` and `statusText=null`, this means the request was not allowed to be performed. It was [`UNSENT`](https://xhr.spec.whatwg.org/#dom-xmlhttprequest-unsent). A likely cause for this is when the [`XMLHttpRequest` origin](https://www.w3.org/TR/2010/CR-XMLHttpRequest-20100803/#xmlhttprequest-origin) (at the creation of the XMLHttpRequest) has changed when the XMLHttpRequest is subsequently `open()`. This case can happen, for example, when one has an XMLHttpRequest that gets fired on an onunload event for a window, the expected XMLHttpRequest is created when the window to be closed is still there, and finally sending the request (in other words, `open()`) when this window has lost its focus and another window gains focus. The most effective way to avoid this problem is to set a listener on the new window's {{domxref("Element/DOMActivate_event", "DOMActivate")}} event which is set once the terminated window has its {{domxref("Window/unload_event", "unload")}} event triggered.
+If you conclude with an XMLHttpRequest receiving `status=0` and `statusText=null`, this means the request was not allowed to be performed. It was [`UNSENT`](https://xhr.spec.whatwg.org/#dom-xmlhttprequest-unsent). A likely cause for this is when the `XMLHttpRequest` origin (at the creation of the XMLHttpRequest) has changed when the XMLHttpRequest is subsequently `open()`. This case can happen, for example, when one has an XMLHttpRequest that gets fired on an onunload event for a window, the expected XMLHttpRequest is created when the window to be closed is still there, and finally sending the request (in other words, `open()`) when this window has lost its focus and another window gains focus. The most effective way to avoid this problem is to set a listener on the new window's {{domxref("Element/DOMActivate_event", "DOMActivate")}} event which is set once the terminated window has its {{domxref("Window/unload_event", "unload")}} event triggered.
 
 ## Specifications
 

@@ -23,7 +23,7 @@ transformToDocument(source)
 
 ### Return value
 
-A {{domxref("Document")}}. The actual interface depends on the [output method](https://www.w3.org/TR/1999/REC-xslt-19991116#output) of the stylesheet:
+A {{domxref("Document")}}. The actual interface depends on the output method of the stylesheet, as specified by [`<xsl:output>`](/en-US/docs/Web/XML/XSLT/Reference/Element/output) element's `method`.
 
 | Output method | Result interface                                                                                       |
 | ------------- | ------------------------------------------------------------------------------------------------------ |

@@ -14,7 +14,7 @@ In Mozilla applications, **`-moz-user-input`** determines if an element will acc
 
 As of Firefox 60, this property can no longer grant an element the ability to accept user input if it normally does not. It may only be used to disable user input.
 
-> **Note:** `-moz-user-input` was one of the proposals leading to the proposed CSS 3 {{cssxref("user-input")}} property, which has not yet reached Candidate Recommendation (call for implementations). A similar property, `user-focus`, was proposed in [early drafts of a predecessor of the User Interface for CSS3 specification](https://www.w3.org/TR/2000/WD-css3-userint-20000216), but was rejected by the working group.
+The `user-input` property is currently not on a standards track.
 
 ## Syntax
 

@@ -56,7 +56,7 @@ To specify multiple background images, supply multiple values, separated by a co
 Browsers do not provide any special information on background images to assistive technology. This is important primarily for screen readers, as a screen reader will not announce its presence and therefore convey nothing to its users. If the image contains information critical to understanding the page's overall purpose, it is better to describe it semantically in the document.
 
 - [MDN Understanding WCAG, Guideline 1.1 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.1_—_providing_text_alternatives_for_non-text_content)
-- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/text-equiv-all.html)
+- [Understanding Success Criterion 1.1.1 | W3C Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html)
 
 Additionally, it is important to ensure that the contrast ratio between the background image and the foreground text is high enough that people with low vision can read the page content.