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

Mark WPTs for user activation consumption as tentative. #36938

Merged
merged 1 commit into from
Nov 11, 2022

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Nov 11, 2022

Currently these WPTs assume window.open() consumes user activation.
While this is true for most browsers, we still don't have any spec
standardizing this behavior.

#36727

Change-Id: Ia1cb6a343e4c8ab86b0b672a583398c9d6c27ad3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4023882
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1070478}

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.

Currently these WPTs assume window.open() consumes user activation.
While this is true for most browsers, we still don't have any spec
standardizing this behavior.

#36727

Change-Id: Ia1cb6a343e4c8ab86b0b672a583398c9d6c27ad3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4023882
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1070478}
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.

3 participants