← back to v146 · populate-targeturl-during-file-handling
conformance · v146
v146 · populate-targeturl-during-file-handling — conformance probe
6 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
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
launchqueue-exists |
window.launchQueue is the entry point for receiving file-handling launch events. | exists | … | |
launchqueue-setconsumer-is-function |
launchQueue.setConsumer is the registration method for the launch handler. | typeof | … | |
launchparams-interface-exposed |
The LaunchParams interface is exposed on the global scope. | exists | … | |
launchparams-has-targeturl |
LaunchParams exposes the targetURL property — the URL the file handler was launched against. | script | … | |
launchparams-has-files |
LaunchParams still exposes files (FileSystemHandle[]) — the pre-existing surface that the new targetURL augments. | script | … | |
launchparams-targeturl-stringifies |
When populated, LaunchParams.targetURL is a string (URL serialisation) per the file-handling launch algorithm. | script | … |