Skip to content
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

existing-client-event and POST navigations #32

Open
alancutter opened this issue Jun 22, 2021 · 0 comments
Open

existing-client-event and POST navigations #32

alancutter opened this issue Jun 22, 2021 · 0 comments
Labels
future-api Issue discusses possible extensions to the current API.

Comments

@alancutter
Copy link
Collaborator

alancutter commented Jun 22, 2021

If the user performs a POST method navigation into the scope of a web app who has "capture_links": "existing-client-event" should the POST data be retained in the launch event?

We should probably expose a Request object rather than just the URL that got captured.

Possible launch event API:

interface LaunchParams {
  readonly attribute Request capturedNavigation;
  readonly attribute FrozenArray<FileSystemHandle> files;
}

How would the site invoke this POST navigation? I think at the moment the web only has form elements to be able to do POST navigations for the document. Location.assign() should probably be updated to accept Request objects.

@alancutter alancutter added the future-api Issue discusses possible extensions to the current API. label Oct 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future-api Issue discusses possible extensions to the current API.
Projects
None yet
Development

No branches or pull requests

1 participant