🎨 Features
- Refactor internal logic related to injecting the Window context for classes that can be constructed using the "new" operator - By @capricorn86 in task #1332
- Improves the way classes can access the Browser context internally - By @capricorn86 in task #1332
- Refactor of the logic for
EventTarget.dispatchEvent()
to better handle the event phases "none", "capture", "atTarget" and "bubbling" - By @capricorn86 in task #1332 - Adds support for
HTMLInputElement.popoverTargetElement
,HTMLInputElement.popoverTargetAction
,HTMLButtonElement.popoverTargetElement
andHTMLButtonElement.popoverTargetAction
- By @capricorn86 in task #1332 - Adds support for
HTMLElement.popover
- By @capricorn86 in task #1332 - Adds support for
PerformanceObserver
,PerformanceEntry
andPerformanceObserverEntryList
- By @capricorn86 in task #1332
👷♂️ Patch fixes
- Makes it possible for a polyfill to replace
NodeList[Symbol.iterator]()
withArray.prototype.values()
- By @capricorn86 in task #1332 - Adds logic for canceling any request to start new async tasks while the
Window
is closing (e.g. usingsetTimeout()
orfetch()
) - By @capricorn86 in task #1332 - Fixes issues with errors exiting the browser when using the setting "errorCapture" set to "processLevel" - By @capricorn86 in task #1332
- Refactor internal logic, so that thrown errors are instances of unique error classes assigned to the
Window
, which makes it possible forBrowserExceptionObserver
to know whichWindow
the error originated from
- Refactor internal logic, so that thrown errors are instances of unique error classes assigned to the
- Changes
Event.composedPath()
to not return theWindow
object if the event type is "load", which is the same behaviour as the browser - By @capricorn86 in task #1332- This means that "load" events will not bubble up to the
Window
object
- This means that "load" events will not bubble up to the