mdn-issue-by-spec

WHATWG DOM Workstream-relevant MDN issues

Issues filed on MDN Web Docs related to pages attached to technologies developed by WHATWG DOM Workstream.

• [dom] Range.extractContents() and Range.surroundContents() describe behaviour incorrectly (2024-09-12T14:20:49Z)

• [dom] Range: isPointInRange() method, offset not explained (2024-09-11T15:30:33Z)

• [dom] Range: comparePoint() method return not actually explained (2024-09-11T09:07:39Z)

• [dom] Range: compareBoundaryPoints() method examples and explanation unclear (2024-09-11T08:59:47Z)

• [html, dom, uievents] Event pages: claim (or imply) that onXYZ and addEventListener are equivalent but they are not (2024-08-09T02:19:02Z)

• [dom] Element.shadowRoot should note browser shadow roots aren’t accessible (2024-08-02T19:32:27Z)

• [dom] Chrome has XMLNS as default namespace (2023-10-16T08:39:40Z)

• [html, dom, cssom-view-1, uievents, pointerlock-2, selection-api, page-visibility-2] Keydown, keyup, keypress pages should mention they work on document, body, etc (2023-08-14T20:14:56Z)

• [dom, cssom-view-1, uievents, pointerlock-2, pointerevents3, fullscreen, DOM-Parsing] MouseDown & MouseUp event articles should compare them to PointerDown & PointerUp (2023-07-11T08:38:52Z)

• [dom] Event.preventDefault: Inaccessible example (2023-06-22T14:18:14Z)

• [service-workers-1, dom, cssom-view-1, notifications, pointerevents3] Page titles should reflect usage: crypto.getRandomValues instead of Crypto: getRandomValues() (2021-09-16T10:09:38Z)

• [html, dom, WebIDL-1, cssom-view-1, FileAPI, uievents, pointerlock-2] Remove alert() from live samples (2021-08-03T21:17:44Z)