The change event on a Screen fires when one or more of these properties change on that screen (MDN): width, height, availWidth, availHeight, colorDepth, or orientation.
Register a listener with addEventListener. Check readiness and browser support before you rely on this event.
Syntax
Listen for change. Start with this line.
JavaScript
screen.addEventListener("change", handler)
Call
What it does
screen.addEventListener("change", handler)
Primary signature.
Built into the browser. Listen with screen.addEventListener("change", …) — no import required.
Library declarations
JavaScript
screen.addEventListener("change", handler)
Parameters
Parameter
Description
Target
Required. A Screen (often from getScreenDetails)
Secure context
Required. HTTPS / localhost
Return Value
Return Value
Description
*
Fires as a Screen event (listener receives the event).
JavaScript Examples
Example 1 — Feature Detect
Check Window Management entry points before showing multi-screen UI.
It is an experimental Window Management API event fired on a specific Screen when one or more of width, height, availWidth, availHeight, colorDepth, or orientation change on that screen (MDN).
MDN marks Screen: change as Experimental and Limited availability (not Baseline). It is not Deprecated or Non-standard. It requires a secure context (HTTPS) in supporting browsers.
Use addEventListener("change", handler) or the onchange property on a Screen object—typically one from (await window.getScreenDetails()).screens.
A generic Event. Re-read the Screen properties you care about inside the handler; the event object has no special payload for the new values.
No. Screen orientationchange is a different (legacy) event. ScreenOrientation also has its own change event. Screen change is broader and part of Window Management.
The API needs permission and may be blocked by Permissions-Policy window-management. The Promise can reject with NotAllowedError. Always feature-detect and catch errors.