← back to v157 · web-bluetooth-make-bluetoothremotegattserver-an-eventtarget

conformance · v157

v157 · web-bluetooth-make-bluetoothremotegattserver-an-eventtarget — conformance probe

8 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://pr-preview.s3.amazonaws.com/hjanuschka/web-bluetooth/pull/672.html#bluetoothremotegattserver chromestatus: #5138797158334464 generated 2026-09-20T00:00:00Z by builder-subagent-v154-157
0
pass
0
fail
0
blocked
8
total
id contract kind verdict detail
interface-exposed BluetoothRemoteGATTServer is exposed on the global object (Web Bluetooth available; on desktop Linux this requires the experimental WebBluetooth runtime flag). spec ↗ script
prototype-inherits-eventtarget BluetoothRemoteGATTServer.prototype inherits from EventTarget — the IDL change 'interface BluetoothRemoteGATTServer : EventTarget'. spec ↗ script
direct-parent-is-eventtarget-prototype The direct prototype of BluetoothRemoteGATTServer.prototype is exactly EventTarget.prototype (no intermediate interface). spec ↗ script
addeventlistener-inherited addEventListener is available on the server prototype and is the inherited EventTarget method, not a redefined copy. spec ↗ script
dispatchevent-is-function dispatchEvent resolves to a function through the server's prototype chain. spec ↗ typeof
onmaxwrite-handler-present The server exposes the onmaxwritewithoutresponsesizechanged event-handler attribute — the first connection-level event this inheritance change enables. spec ↗ script
gattserverdisconnected-still-on-device gattserverdisconnected remains a BluetoothDevice event (the spec did not move it to the server): the ongattserverdisconnected handler lives on BluetoothDevice.prototype. spec ↗ script
server-event-dispatch-on-live-connection On a live GATT connection, connection-level events (e.g. maxwritewithoutresponsesizechanged after MTU renegotiation) dispatch with event.target === the server instance. spec ↗ manual