Skip to content

existing-client-event and POST navigations #32

@alancutter

Description

@alancutter

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    future-apiIssue discusses possible extensions to the current API.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions