← back to v133 · remove-chrome-welcome-page-triggering-via-initial-prefs-first-run-tabs
conformance · v133
v133 · remove-chrome-welcome-page-triggering-via-initial-prefs-first-run-tabs — conformance probe
5 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
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
no-chromewelcomefirstrun-on-window |
Visiting an arbitrary page does not inject any global named after Chrome's welcome flow (this removal is internal to Chrome's first-run setup; sanity check that nothing leaked to the web). | script | … | |
navigator-still-exposes-userAgent |
navigator.userAgent remains exposed; this change does not modify the navigator surface. | script | … | |
location-href-still-works |
location.href remains readable; the removal is internal. | script | … | |
history-pushstate-still-works |
history.pushState remains exposed (the removal does not affect navigation surfaces). | typeof | … | |
no-window-firstruntabs |
No window.firstRunTabs property is exposed (the internal initial-prefs mechanism has no web counterpart). | script | … |