mdn · teoli2003 · Apr 30, 2022 · Apr 30, 2022
@@ -23,7 +23,7 @@ evaluate(xpathExpression, contextNode, namespaceResolver, resultType, result)
 - `xpathExpression` is a string representing the XPath to be evaluated.
 - `contextNode` specifies the _context node_ for the query (see
   the [XPath
-  specification](https://www.w3.org/TR/xpath)). It's common to pass `document` as the context
+  specification](https://www.w3.org/TR/xpath/)). It's common to pass `document` as the context
   node.
 - `namespaceResolver` is a function that will be passed any namespace
   prefixes and should return a string representing the namespace URI associated with
@@ -203,4 +203,4 @@ nodes may have moved, been changed, added, or removed.
 - {{domxref("Document.createExpression()")}}
 - {{domxref("XPathResult")}}
 - [XPath Code Snippets](/en-US/docs/Code_snippets/XPath)
-- [Check for browser support](https://codepen.io/johan/full/ckFgn)
+- [Check for browser support](https://codepen.io/johan/full/DJoqaX)
@@ -12,7 +12,7 @@ tags:
 ---
 {{DefaultAPISidebar("DOM")}}
 
-This page describes how to use the [DOM Core](https://www.w3.org/TR/DOM-Level-3-Core) API in JavaScript to create and modify DOM objects. It applies to all Gecko-based applications (such as Firefox) both in privileged (extensions) and unprivileged (web pages) code.
+This page describes how to use the [DOM Core](https://www.w3.org/TR/DOM-Level-3-Core/) API in JavaScript to create and modify DOM objects. It applies to all Gecko-based applications (such as Firefox) both in privileged (extensions) and unprivileged (web pages) code.
 
 ### Dynamically creating a DOM tree
 

@@ -66,7 +66,7 @@ Conserving whitespace characters in the DOM is useful in many ways, but there ar
 
 ### How does CSS process whitespace?
 
-Most whitespace characters are ignored, not all of them are. In the earlier example one of the spaces between "Hello" and "World!" still exists when the page is rendered in a browser. There are rules in the browser engine that decide which whitespace characters are useful and which aren't — these are specified at least in part in [CSS Text Module Level 3](https://www.w3.org/TR/css-text-3), and especially the parts about the [CSS `white-space` property](https://www.w3.org/TR/css-text-3/#white-space-property) and [whitespace processing details](https://www.w3.org/TR/css-text-3/#white-space-processing), but we also offer an easier explanation below.
+Most whitespace characters are ignored, not all of them are. In the earlier example one of the spaces between "Hello" and "World!" still exists when the page is rendered in a browser. There are rules in the browser engine that decide which whitespace characters are useful and which aren't — these are specified at least in part in [CSS Text Module Level 3](https://www.w3.org/TR/css-text-3/), and especially the parts about the [CSS `white-space` property](https://www.w3.org/TR/css-text-3/#white-space-property) and [whitespace processing details](https://www.w3.org/TR/css-text-3/#white-space-processing), but we also offer an easier explanation below.
 
 #### Example
 

@@ -66,7 +66,7 @@ Known workarounds for this bug:
 
 ### Safari Mobile
 
-Safari Mobile 7.0+ (and likely earlier versions too) [suffers from a bug](https://bugs.webkit.org/show_bug.cgi?id=153887) where `click` events aren't fired on elements that aren't typically interactive (e.g. {{HTMLElement("div")}}) and which also don't have event listeners directly attached to the elements themselves (i.e. [event delegation](https://davidwalsh.name/event-delegate) is being used). See [this live example](https://jsfiddle.net/cvrhulu/k9t0sdnf/show/) for a demonstration. See also [Safari's docs on making elements clickable](https://developer.apple.com/library/safari/documentation/appleapplications/reference/safariwebcontent/HandlingEvents/HandlingEvents.html#//apple_ref/doc/uid/TP40006511-SW6) and the [definition of "clickable element"](https://developer.apple.com/library/safari/documentation/appleapplications/reference/safariwebcontent/HandlingEvents/HandlingEvents.html#//apple_ref/doc/uid/TP40006511-SW7).
+Safari Mobile 7.0+ (and likely earlier versions too) [suffers from a bug](https://bugs.webkit.org/show_bug.cgi?id=153887) where `click` events aren't fired on elements that aren't typically interactive (e.g. {{HTMLElement("div")}}) and which also don't have event listeners directly attached to the elements themselves (i.e. [event delegation](https://davidwalsh.name/event-delegate) is being used). See [this live example](https://jsfiddle.net/cvrhulu/k9t0sdnf/show/) for a demonstration. See also [Safari's docs on making elements clickable](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/HandlingEvents/HandlingEvents.html#//apple_ref/doc/uid/TP40006511-SW6) and the [definition of "clickable element"](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/HandlingEvents/HandlingEvents.html#/apple_ref/doc/uid/TP40006511-SW7).
 
 Known workarounds for this bug:
 

@@ -59,7 +59,7 @@ _`Element` inherits properties from its parent interface, {{DOMxRef("Node")}}, a
 
   - : The namespace URI of the element, or `null` if it is no namespace.
 
-    > **Note:** In Firefox 3.5 and earlier, HTML elements are in no namespace. In later versions, HTML elements are in the [`http://www.w3.org/1999/xhtml`](https://www.w3.org/1999/xhtml) namespace in both HTML and XML trees.
+    > **Note:** In Firefox 3.5 and earlier, HTML elements are in no namespace. In later versions, HTML elements are in the [`http://www.w3.org/1999/xhtml`](https://www.w3.org/1999/xhtml/) namespace in both HTML and XML trees.
 
 - {{DOMxRef("Element.nextElementSibling")}} {{readOnlyInline}}
   - : Is an {{DOMxRef("Element")}}, the element immediately following the given one in the tree, or `null` if there's no sibling node.

@@ -41,7 +41,7 @@ frozen at the node creation time.
 
 In Firefox 3.5 and earlier, the namespace URI for HTML elements in HTML documents is
 `null`. In later versions, in compliance with HTML5, it is
-[`http://www.w3.org/1999/xhtml`](https://www.w3.org/1999/xhtml)
+[`http://www.w3.org/1999/xhtml`](https://www.w3.org/1999/xhtml/)
 as in XHTML.
 
 You can create an element with the specified `namespaceURI` using the DOM

@@ -103,5 +103,5 @@ When using the inline HTML markup (`<body onerror="alert('an error occurred')">`
 
 ## See also
 
-- [Capture and report JavaScript errors with window.onerror (blog.sentry.io, 2016)](https://blog.sentry.io/2016/01/04/client-javascript-reporting-window-onerror)
+- [Capture and report JavaScript errors with window.onerror (blog.sentry.io, 2016)](https://blog.sentry.io/2016/01/04/client-javascript-reporting-window-onerror/)
 - [How to catch JavaScript Errors with window.onerror (even on Chrome and Firefox) (danlimerick.wordpress.com, 2014)](https://danlimerick.wordpress.com/2014/01/18/how-to-catch-javascript-errors-with-window-onerror-even-on-chrome-and-firefox/)
@@ -35,7 +35,7 @@ requestDevice(options)
 
       - : An integer representing the usage page component of the HID usage of the requested device. The usage for a top level collection is used to identify the device type.
 
-        Standard HID usage values can be found in the [HID Usage Tables](https://usb.org/document-library/hid-usage-tables-122) document
+        Standard HID usage values can be found in the [HID Usage Tables](https://usb.org/document-library/hid-usage-tables-13) document
 
     - `usage`{{Optional_Inline}}
       - : An integer representing the usage ID component of the HID usage of the requested device.

@@ -21,7 +21,7 @@ An array of report formats. Each entry contains the following:
 
   - : An integer representing the usage page component of the HID usage associated with this collection. The usage for a top level collection is used to identify the device type.
 
-    Standard HID usage values can be found in the [HID Usage Tables](https://usb.org/document-library/hid-usage-tables-122) document
+    Standard HID usage values can be found in the [HID Usage Tables](https://usb.org/document-library/hid-usage-tables-13) document
 
 - `usage`
   - : An integer representing the usage ID component of the HID usage associated with this collection.

@@ -104,5 +104,5 @@ document.getElementById('divA').textContent = 'This text is different!';
 
 - {{domxref("HTMLElement.innerText")}}
 - {{domxref("Element.innerHTML")}}
-- [More on differences between `innerText` and `textContent`](http://perfectionkills.com/the-poor-misunderstood-innerText)
+- [More on differences between `innerText` and `textContent`](http://perfectionkills.com/the-poor-misunderstood-innerText/)
   (blog post)
@@ -54,4 +54,4 @@ To learn how to use server-sent events, see our article [Using server-sent event
 ### Other resources
 
 - A [Twitter like application](https://hacks.mozilla.org/2011/06/a-wall-powered-by-eventsource-and-server-sent-events/) powered by server-sent events and [its code on GitHub](https://github.com/mozilla/webowonder-demos/tree/master/demos/friends%20timeline).
-- [HTML5 and Server-sent events](https://dsheiko.com/weblog/html5-and-server-sent-events)
+- [HTML5 and Server-sent events](https://dsheiko.com/weblog/html5-and-server-sent-events/)
@@ -24,7 +24,7 @@ Service workers only run over HTTPS, for security reasons. Having modified netwo
 
 > **Note:** On Firefox, for testing you can run service workers over HTTP (insecurely); simply check the **Enable Service Workers over HTTP (when toolbox is open)** option in the Firefox Devtools options/gear menu.
 
-> **Note:** Unlike previous attempts in this area such as [AppCache](https://alistapart.com/article/application-cache-is-a-douchebag), service workers don't make assumptions about what you are trying to do, but then break when those assumptions are not exactly right. Instead, service workers give you much more granular control.
+> **Note:** Unlike previous attempts in this area such as [AppCache](https://alistapart.com/article/application-cache-is-a-douchebag/), service workers don't make assumptions about what you are trying to do, but then break when those assumptions are not exactly right. Instead, service workers give you much more granular control.
 
 > **Note:** Service workers make heavy use of [promises](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise), as generally they will wait for responses to come through, after which they will respond with a success or failure action. The promises architecture is ideal for this.
 

@@ -16,7 +16,7 @@ This article provides information on getting started with service workers, inclu
 
 One overriding problem that web users have suffered with for years is loss of connectivity. The best web app in the world will provide a terrible user experience if you can't download it. There have been various attempts to create technologies to solve this problem, and some of the issues have been solved. But the overriding problem is that there still isn't a good overall control mechanism for asset caching and custom network requests.
 
-The previous attempt, _AppCache_, seemed to be a good idea because it allowed you to specify assets to cache really easily. However, it made many assumptions about what you were trying to do and then broke horribly when your app didn't follow those assumptions exactly. Read Jake Archibald's (unfortunately-titled but well-written) [Application Cache is a Douchebag](https://alistapart.com/article/application-cache-is-a-douchebag) for more details.
+The previous attempt, _AppCache_, seemed to be a good idea because it allowed you to specify assets to cache really easily. However, it made many assumptions about what you were trying to do and then broke horribly when your app didn't follow those assumptions exactly. Read Jake Archibald's (unfortunately-titled but well-written) [Application Cache is a Douchebag](https://alistapart.com/article/application-cache-is-a-douchebag/) for more details.
 
 > **Note:** From Firefox 84, AppCache has been removed ({{bug("1619673")}}). It is also planned for removal in Chromium 90, and is deprecated in Safari.
 

@@ -162,5 +162,5 @@ digestMessage(text)
 ## See also
 
 - [Non-cryptographic uses of SubtleCrypto](/en-US/docs/Web/API/Web_Crypto_API/Non-cryptographic_uses_of_subtle_crypto)
-- [Chromium secure origins specification](https://www.chromium.org/Home/chromium-security/prefer-secure-origins-for-powerful-new-features)
+- [Chromium secure origins specification](https://www.chromium.org/Home/chromium-security/prefer-secure-origins-for-powerful-new-features/)
 - [FIPS 180-4](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf) specifies the SHA family of digest algorithms.
@@ -30,7 +30,7 @@ the new page might also modify such data, which might then be read by the origin
 if it was reloaded).
 
 `Window.name` has also been used in some frameworks for providing
-cross-domain messaging (e.g. Dojo's [dojox.io.windowName](https://www.sitepen.com/blog/2008/07/22/windowname-transport/))
+cross-domain messaging (e.g. Dojo's [dojox.io.windowName](https://www.sitepen.com/blog/2008/07/22/windowname-transport))
 as a more secure alternative to JSONP. Modern web applications hosting sensitive data
 should, however, not rely on `window.name` for cross-domain messaging — that
 is not its intended purpose and there are safer/better ways of sharing information

@@ -4,4 +4,4 @@ slug: Web/API/XSLTProcessor/Browser_Differences
 ---
 ## Browser Differences
 
-Netscape 7.x (all platforms) and Internet Explorer 6 (Windows) support the W3C XSLT 1.0 standard ([http://www.w3.org/TR/xslt](https://www.w3.org/TR/xslt)). IE 5.0 and 5.5 (both Windows) supported only the working draft of XSLT, and thus are not compatible with XSLT 1.0 stylesheets. Netscape 6.x only partially supported XSLT 1.0.
+Netscape 7.x (all platforms) and Internet Explorer 6 (Windows) support the W3C XSLT 1.0 standard ([http://www.w3.org/TR/xslt](https://www.w3.org/TR/xslt/)). IE 5.0 and 5.5 (both Windows) supported only the working draft of XSLT, and thus are not compatible with XSLT 1.0 stylesheets. Netscape 6.x only partially supported XSLT 1.0.
@@ -29,7 +29,7 @@ new XSLTProcessor()
 - [Throws] void {{domxref("XSLTProcessor.importStylesheet")}}({{domxref("Node")}} styleSheet)
   - : Imports the XSLT stylesheet. If the given node is a document node, you can pass in a
     full XSL Transform or a [literal result element
-    transform](https://www.w3.org/TR/xslt#result-element-stylesheet); otherwise, it must be an `<xsl:stylesheet>` or
+    transform](https://www.w3.org/TR/xslt/#result-element-stylesheet); otherwise, it must be an `<xsl:stylesheet>` or
     `<xsl:transform>` element.
 - [Throws] {{domxref("DocumentFragment")}}
   {{domxref("XSLTProcessor.transformToFragment")}}({{domxref("Node")}} source, {{domxref("Document")}} owner)
@@ -43,7 +43,7 @@ new XSLTProcessor()
   - : Transforms the node source applying the stylesheet given importing using the
     {{domxref("XSLTProcessor.importStylesheet()")}} function.
 
-    The resultant object depends on the [output method](https://www.w3.org/TR/xslt#output) of the stylesheet:
+    The resultant object depends on the [output method](https://www.w3.org/TR/xslt/#output) of the stylesheet:
 
     | Output method | Result type                                                                                                      |
     | ------------- | ---------------------------------------------------------------------------------------------------------------- |

@@ -77,7 +77,7 @@ p {
 
 ## Specifications
 
-Not part of any standard. Apple has [a description in the Safari CSS Reference](https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariCSSRef/Articles/StandardCSSProperties.html#//apple_ref/css/property/-webkit-overflow-scrolling).
+Not part of any standard. Apple has [a description in the Safari CSS Reference](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariCSSRef/Articles/StandardCSSProperties.html#//apple_ref/css/property/-webkit-overflow-scrolling).
 
 ## Browser compatibility
 

@@ -58,7 +58,7 @@ When a target is touched and held on iOS, Safari displays a callout information
 
 ## Specifications
 
-Not part of any standard. Apple has a [description in the Safari CSS Reference](https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariCSSRef/Articles/StandardCSSProperties.html#//apple_ref/doc/uid/TP30001266-_webkit_touch_callout).
+Not part of any standard. Apple has a [description in the Safari CSS Reference](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariCSSRef/Articles/StandardCSSProperties.html#//apple_ref/doc/uid/TP30001266-_webkit_touch_callout).
 
 ## Browser compatibility
 

@@ -13,7 +13,7 @@ browser-compat: css.at-rules.media.-webkit-animation
 
 The **`-webkit-animation`** Boolean [CSS](/en-US/docs/Web/CSS) [media feature](/en-US/docs/Web/CSS/Media_Queries/Using_media_queries#media_features) is a [Chrome extension](/en-US/docs/Web/CSS/WebKit_Extensions) whose value is `true` if vendor-prefixed CSS {{cssxref("animation")}}s are supported.
 
-Apple has [a description in Safari CSS Reference](https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariCSSRef/Articles/OtherStandardCSS3Features.html#//apple_ref/doc/uid/TP40007601-SW3).
+Apple has [a description in Safari CSS Reference](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariCSSRef/Articles/OtherStandardCSS3Features.html#//apple_ref/doc/uid/TP40007601-SW3).
 
 > **Note:** This media feature is only supported by WebKit. If possible, use an {{cssxref("@supports")}} feature query instead.
 

@@ -14,7 +14,7 @@ browser-compat: css.at-rules.media.-webkit-transform-2d
 
 The **`-webkit-transform-2d`** Boolean [CSS](/en-US/docs/Web/CSS) [media feature](/en-US/docs/Web/CSS/Media_Queries/Using_media_queries#media_features) is a [Chrome extension](/en-US/docs/Web/CSS/WebKit_Extensions) whose value is `true` if vendor-prefixed CSS 2D {{cssxref("transform")}}s are supported.
 
-Apple has [a description in Safari CSS Reference](https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariCSSRef/Articles/OtherStandardCSS3Features.html#//apple_ref/doc/uid/TP40007601-SW3).
+Apple has [a description in Safari CSS Reference](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariCSSRef/Articles/OtherStandardCSS3Features.html#//apple_ref/doc/uid/TP40007601-SW3).
 
 ## Syntax
 

@@ -16,7 +16,7 @@ browser-compat: css.at-rules.media.-webkit-transition
 
 The **`-webkit-transition`** Boolean [CSS](/en-US/docs/Web/CSS) [media feature](/en-US/docs/Web/CSS/Media_Queries/Using_media_queries#media_features) is a [Chrome extension](/en-US/docs/Web/CSS/WebKit_Extensions) whose value is `true` if the browsing context supports [CSS transitions](/en-US/docs/Web/CSS/CSS_Transitions). It was never supported in browsers not based on WebKit or Blink.
 
-Apple has [a description in Safari CSS Reference](https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariCSSRef/Articles/OtherStandardCSS3Features.html#//apple_ref/doc/uid/TP40007601-SW3); this is now called `transition` there.
+Apple has [a description in Safari CSS Reference](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariCSSRef/Articles/OtherStandardCSS3Features.html#//apple_ref/doc/uid/TP40007601-SW3); this is now called `transition` there.
 
 > **Note:** You should not use this media feature; it was never specified, has never been widely implemented, and has been removed from all browsers. Use an {{cssxref("@supports")}} feature query instead.
 

@@ -167,4 +167,4 @@ li:nth-last-child(3) ~ li {
 ## See also
 
 - {{Cssxref(":nth-child")}}, {{Cssxref(":nth-last-of-type")}}
-- [Quantity Queries for CSS](https://alistapart.com/article/quantity-queries-for-css)
+- [Quantity Queries for CSS](https://alistapart.com/article/quantity-queries-for-css/)