← back to v142 · interoperable-pointerrawupdate-events-exposed-only-in-secure-contexts

conformance · v142

v142 · interoperable-pointerrawupdate-events-exposed-only-in-secure-contexts — conformance probe

6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.

browser: spec: https://w3c.github.io/pointerevents/#the-pointerrawupdate-event chromestatus: #5151468306956288 generated 2026-06-01T08:13:10Z by conformance-author-v1-subagent
0
pass
0
fail
0
blocked
6
total
id contract kind verdict detail
secure-context The page must be a secure context; pointerrawupdate is now only exposed there. script
onpointerrawupdate-on-window-secure-only In a secure context, window exposes the onpointerrawupdate IDL attribute. script
onpointerrawupdate-on-document Document also exposes onpointerrawupdate in secure contexts (per the Pointer Events GlobalEventHandlers mixin shape). script
pointerevent-still-exposed The PointerEvent constructor is still exposed; pointerrawupdate dispatches PointerEvent instances. exists
addeventlistener-accepts-pointerrawupdate window.addEventListener accepts the 'pointerrawupdate' event name without throwing in a secure context. script
pointermove-still-fires The plain pointermove event remains exposed regardless of secure-context restriction. script