You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Changelog.md
+33Lines changed: 33 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,39 @@ Other guidelines:
26
26
* Roughly order changes within those groupings by impact.
27
27
-->
28
28
29
+
## 27.0.0
30
+
31
+
### Changes since 26.1.0
32
+
33
+
* Node.js v20 is now the minimum supported version.
34
+
* Added a variety of event constructors, even though we do not implement their associated specifications or ever fire them: `BeforeUnloadEvent`, `BlobEvent`, `DeviceMotionEvent` (omitting `requestPermission()`), `DeviceOrientationEvent` (omitting `requestPermission()`), `PointerEvent`, `PromiseRejectionEvent`, and `TransitionEvent`.
35
+
* Added `movementX` and `movementY` to `MouseEvent`. (These are from the [Pointer Lock](https://w3c.github.io/pointerlock/) specification, the rest of which is not implemented.)
36
+
* Added `customElements.getName()`. (mash-graz)
37
+
* Updated the [virtual console](https://github.com/jsdom/jsdom/blob/ab384d4e381eb6bb99ade4146698d35167b54837/README.md#virtual-consoles):
38
+
*`"jsdomError"` events are now documented, with specific `type` properties and other properties that depend on the type.
39
+
*`sendTo()` was renamed to `forwardTo()`.
40
+
* The `jsdomErrors` option to `forwardTo()` can be used to control which errors are sent to the Node.js console. This replaces the previous `omitJSDOMErrors` boolean option.
41
+
*`"jsdomError"`s for failed `XMLHttpRequest` fetches are no longer emitted.
42
+
* The values that are printed when forwarding `"jsdomError"`s to the Node.js console are streamlined.
43
+
* Switched our CSS selector engine from [`nwsapi`](https://www.npmjs.com/nwsapi) to [`@asamuzakjp/dom-selector`](https://www.npmjs.com/package/@asamuzakjp/dom-selector), closing over 20 selector-related bugs.
44
+
* Upgraded [`tough-cookie`](https://www.npmjs.com/package/tough-cookie), which now considers URLs like `http://localhost/` to be secure contexts (per [the spec](https://w3c.github.io/webappsec-secure-contexts/#is-origin-trustworthy)), and thus will return `Secure`-flagged cookies for such URLs. (colincasey)
45
+
* Upgraded [`cssstyle`](https://github.com/jsdom/cssstyle), which brings along many improvements and fixes to the `CSSStyleDeclaration` object and its properties.
46
+
* Updated the user agent stylesheet to be derived from the HTML Standard, instead of from an old revision of Chromium.
47
+
* Changed `element.click()` to fire a `PointerEvent` instead of a `MouseEvent`.
48
+
* Changed certain events to be passive by default.
49
+
* Changed the `<input>` element's `pattern=""` attribute to use the `v` regular expression flag, instead of `u`.
50
+
* Fixed many specification conformance issues with the `Window` object, including named properties and changing various data properties to accessor properties.
51
+
* Fixed `document.createEvent()` to accept a more correct set of event names.
52
+
* Fixed the `ElementInternals` accessibility getters and setters. (They were introduced in v23.1.0, but due to inadequate test coverage never actually worked.)
53
+
* Fixed using `Object.defineProperty()` on certain objects, such as `HTMLSelectElement` instances.
54
+
* Fixed `jsdom.reconfigure({ url })` not updating `document.baseURI` or properties derived from it. (This regressed in v26.1.0.)
55
+
* Fixed CSS system colors, as well as the `initial`, `inherit`, and `unset` keywords, to resolve correctly. (asamuzaK)
* Upgraded `cssstyle`, which brings along various CSS parsing fixes.
61
+
29
62
## 27.0.0-beta.3
30
63
31
64
* Breaking change: upgraded `tough-cookie`, which now considers URLs like `http://localhost/` to be secure contexts (per [the spec](https://w3c.github.io/webappsec-secure-contexts/#is-origin-trustworthy)), and thus will return `Secure`-flagged cookies for such URLs. (colincasey)
0 commit comments