conformance · v150
v150 · sub-apps — conformance probe
7 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.
0
pass
0
fail
0
blocked
7
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
window-subapps-binding |
The SubApps interface binds to Window as window.subApps inside a secure, isolated context (IWA). spec ↗ | exists | … | |
subapps-add-method |
window.subApps.add() exists — installs a batch of sub apps from install paths. spec ↗ | typeof | … | |
subapps-remove-method |
window.subApps.remove() exists — uninstalls sub apps by ManifestId. spec ↗ | typeof | … | |
subapps-list-method |
window.subApps.list() exists — returns the ManifestId-keyed inventory of installed sub apps. spec ↗ | typeof | … | |
secure-context-gate |
The interface is [SecureContext]: on a non-secure context window.subApps must be absent (on a secure context either state is spec-legal, since IsolatedContext also gates it). spec ↗ | script | … | |
list-resolves-record |
When bound, list() resolves to a record (object, not an array) keyed by ManifestId, per SubAppsListResult. spec ↗ | script | … | |
add-rejects-non-rooted-path |
When bound, add() rejects with TypeError for an install path that does not start with '/' (batch-level validation). spec ↗ | script | … |