commit | e9828a82b5c182dc9a7fb0ae7226c35ba1726e7d | [log] [tgz] |
---|---|---|
author | Garrett Tanzer <gtanzer@chromium.org> | Tue Feb 22 20:11:51 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 22 20:11:51 2022 |
tree | 895280d08da160965dfa6a7a2c0880feffb308ea | |
parent | fd81abc689b150a3f456e1784d66600bb30e9bbe [diff] |
Fix noopener case for user activation consumption The flow for user activation consumption in window.open was as follows: Renderer: ask the browser to create a new window Browser: consume transient user activation (in the browser, and via RPC to remote frames only) Browser: return success for opener, return ignore for noopener Renderer: consume transient user activation upon success So in the noopener case, the renderer with the local frame where the window.open originated didn't have its transient user activation consumed. The new behavior is to consume user activation in the calling renderer whenever it is consumed in the browser. We accomplish this by returning a distinct value kBlocked to represent failure before the browser consumes user activation. Bug: 1264543, 1291210 Change-Id: Iffb6e3fd772bef625d3d28e600e6fb73d70ab29f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3468171 Reviewed-by: Dominic Farolino <dom@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Reviewed-by: Charles Reis <creis@chromium.org> Reviewed-by: Jonathan Ross <jonross@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Garrett Tanzer <gtanzer@chromium.org> Cr-Commit-Position: refs/heads/main@{#973876}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.