-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Export "create a new top-level browsing context"? #8449
Comments
Well, maybe. In #6315, scheduled to land on Monday, we're largely replacing the top-level browsing context concept with "top-level traversable". What you've provided is a good list of specs that we'll need to help you all update. I'll add in the export to that PR, and in particular I'll ensure "create a new top-level traversable"'s arguments are both optional. |
I've added create a fresh top-level traversable, which is exported and takes no arguments. There's a remaining problem where none of those specs pass a sourceDocument to the new navigate. Which makes sense, because there is no source... Hmm. We could go a few routes here:
(1) is annoying but most flexible. (2) is dangerous; it'll be too easy for people to forget to pass a sourceDocument when they really need to do so. (3) is most appealing, but it doesn't seem to work well for https://wicg.github.io/web-app-launch/#preparing-a-new-web-app-launch-client which has an intermediate step . How important is that intermediate step? Could it happen after navigation has started? |
Oh awesome, thanks for rationalising this with what's going on in WHATWG land, I would have had no idea.
Yep, it can happen after navigation. It mainly applies fairly cosmetic things like window decorations. |
OK, sweet! So after that is merged and indexed by the various spec cross-referencing databases (say, Tuesday-ish), you should be able to replace all of those with |
Can |
It will take a URL and an optional POST resource: https://whatpr.org/html/6315/document-sequences.html#create-a-fresh-top-level-traversable |
Would it be reasonable to export https://html.spec.whatwg.org/multipage/browsers.html#creating-a-new-top-level-browsing-context for use by W3C specs? This is referenced by a handful of web app related algorithms:
https://www.w3.org/TR/appmanifest/#launching-a-shortcut
https://w3c.github.io/web-share-target/#launching-the-web-share-target
https://wicg.github.io/manifest-incubations/index.html#dfn-launch-a-web-app
https://wicg.github.io/manifest-incubations/index.html#handling-a-protocol-launch
https://wicg.github.io/manifest-incubations/index.html#launching-the-new_note_url
https://wicg.github.io/web-app-launch/#preparing-a-new-web-app-launch-client
(Context: w3c/manifest#1056 (comment))
The text was updated successfully, but these errors were encountered: