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

Prerender: Upstream test for presentationRequest.start() #31257

Merged
merged 1 commit into from Oct 15, 2021

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Oct 15, 2021

This CL upstreams a test for presentationRequest.start() in prerendered
pages to the WPT repository. The API is listed as "implicitly restricted
APIs" in the draft spec:
https://jeremyroman.github.io/alternate-loading-modes/prerendering.html#implicitly-restricted

This CL removes the following comment:

This cannot be upstreamed as a WPT test because the spec (probably)
will require that no error is thrown until activation.

This is because presentationRequest.start() is expected to return a
rejected promise when the window doesn't have transient activation, and
the current test correctly handles it.

If the document's active window does not have transient activation,
return a Promise rejected with an InvalidAccessError exception and
abort these steps.
https://w3c.github.io/presentation-api/#dom-presentationrequest-start

Related issues in the spec side:

Bug: 1253158
Change-Id: I6973c4c6683135b9bc27e78115d797e8d5840fed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3223703
Reviewed-by: Lingqi Chi <lingqi@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#931847}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

This CL upstreams a test for presentationRequest.start() in prerendered
pages to the WPT repository. The API is listed as "implicitly restricted
APIs" in the draft spec:
https://jeremyroman.github.io/alternate-loading-modes/prerendering.html#implicitly-restricted

This CL removes the following comment:

  This cannot be upstreamed as a WPT test because the spec (probably)
  will require that no error is thrown until activation.

This is because presentationRequest.start() is expected to return a
rejected promise when the window doesn't have transient activation, and
the current test correctly handles it.

  If the document's active window does not have transient activation,
  return a Promise rejected with an InvalidAccessError exception and
  abort these steps.
  https://w3c.github.io/presentation-api/#dom-presentationrequest-start

Related issues in the spec side:
- WICG/nav-speculation#42
- WICG/nav-speculation#36

Bug: 1253158
Change-Id: I6973c4c6683135b9bc27e78115d797e8d5840fed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3223703
Reviewed-by: Lingqi Chi <lingqi@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#931847}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants