Device

Device APIs let a page read touch screens, controllers, sensors and location, keep the screen awake, and even talk to Bluetooth, USB and serial hardware. They all pass the gates of The Web Platform APIs: a secure context (localhost counts), often a permission prompt or a user click, and feature detection, because support is uneven. Mozilla rates Web Bluetooth, WebUSB, WebHID and Web NFC as harmful and Apple opposes WebUSB and Web Serial, so the lower half of the table below is Chromium 4,389 only (Chrome 1 , Edge, Opera 89 , Samsung Internet 94 ). Outputs below come from headless Chrome 152; hardware-only examples say so.

Device API support by first stable version (webstatus.dev and MDN 102 , September 2026)
API Baseline Chrome Firefox 555 Safari 10
Pointer events Widely 55 59 13
Touch events Limited 22 52 (touch screens) iOS only
Permissions Widely 44 46 16
Geolocation Widely 5 3.5 5
deviceorientation Widely 31 6 17
Gamepad Widely 35 29 10.1
Screen Wake Lock Newly (2025) 84 126 16.4
Pointer Lock Limited 37 50 10.1, not iOS
Accelerometer, Gyroscope Limited 67 No No
Keyboard map and lock Limited 69, 68 No No
Vibration Limited 32 (Android) Removed in 129 No
Presentation Limited 47 No No
Web NFC Limited Android 89 No No
Web Bluetooth Limited 70 No No
WebUSB, WebHID Limited 61, 89 No No
Web Serial Limited 89 151 (add-on) No
Battery, Device Memory Limited 38, 63 No No
Compute Pressure Limited 125 (desktop) No No

Subsections