-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace appmanifest's launch algorithm with one that has launch_handler behaviors #79
Conversation
I'll wait for w3c/manifest#1056 to land before merging this one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, with one comment
14e47ab
to
7444e95
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cd6973a
to
ae60cda
Compare
The manifest exports need a bit of time to propagate through, will hold off landing until then to make sure the xrefs work correctly. |
The red squiggles remaining will be fixed after w3c/manifest#1062 lands and the xrefs have time to propagate through. |
#67 #69 #84
This builds on top of w3c/manifest#1056 which adds a
launch web application
algorithm to the manifest spec. This updates the launch handler spec to replace that algorithm with its own. This enables other webapp specs (not in WICG) to gain the launch_handler behaviour without directly referencing this WICG spec.Additionally this replaces the concept of "web app launch client" with the existing "application context" concept from the manifest spec which is effectively the same thing.