Spec client.reserved #1003
Labels
Milestone
Comments
annevk
pushed a commit
to whatwg/html
that referenced
this issue
Nov 9, 2016
Service worker's Client's reserved attribute and clients.matchAll(/* options.includeReserved */) method require getting the state of a Client object whether its environment is in reserved state or not. This commit adds the execution ready flag to the environment concept that distinguishes the state between before and after the user agent is ready to parse a fetched (or given default) document or execute a worker script. The execution ready flag is set when the global object and realm execution context are created and the main resource (for parsing/executing) is ready. Related service worker issue: w3c/ServiceWorker#1003. Fixes #1992.
alice
pushed a commit
to alice/html
that referenced
this issue
Jan 8, 2019
Service worker's Client's reserved attribute and clients.matchAll(/* options.includeReserved */) method require getting the state of a Client object whether its environment is in reserved state or not. This commit adds the execution ready flag to the environment concept that distinguishes the state between before and after the user agent is ready to parse a fetched (or given default) document or execute a worker script. The execution ready flag is set when the global object and realm execution context are created and the main resource (for parsing/executing) is ready. Related service worker issue: w3c/ServiceWorker#1003. Fixes whatwg#1992.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
History of adding
client.reserved:#870 has addressed issues around exposing the states of a reserved client to SW during a navigation and a worker creation. As part of this work,
client.reservedhas been spec'd (d88e979) to provide the reserved state of the retrievedClientobject.An issue pointed in whatwg/html#2004 (comment) has been addressed by d2c327c
The text was updated successfully, but these errors were encountered: