commit | bdb19c7473219dc1a516e1bbd3c69f64dbb93f6b | [log] [tgz] |
---|---|---|
author | Andy Paicu <andypaicu@chromium.org> | Fri Apr 22 09:24:31 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 22 09:24:31 2022 |
tree | 15541e789213f5721a725c4ac271fa5f8a7760a6 | |
parent | 1156fcf82cd90b20281d465e3c07748f78ca31cf [diff] |
Limit the number of `PermissionObserver` handles open by the Permissions API This CL ensures that only at most one handle is open per (permission type, execution handle) pair. It introduces a new class PermissionStatusListener that will hold the actual handle and the PermissionStatus objects will hold a reference to this class. This means that the PermissionType enum needs to be accessible in blink and as such it's been moved from `content/public/browser/permission_type.h` to `third_party/blink/public/common/permissions/permission_utils.h` Additionally fix bugs uncovered along the way: * If a PTZ (pan-tilt-zoom capable camera) request is made but it results in a simple camera one, the Permissions API still tracks the PTZ permission which would be incorrect. * The New Tab Page doesn't properly get permission updates on the PermissionStatus handle because of its weird URL. (`chrome://newtab`) Fixed: 1122423 AX-Relnotes: n/a Change-Id: Ieb5e9c7203f7bf3101a41af718a7d211b8bb40f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3359620 Reviewed-by: Ravjit Uppal <ravjit@chromium.org> Reviewed-by: Kamila Hasanbega <hkamila@chromium.org> Reviewed-by: John Abd-El-Malek <jam@chromium.org> Reviewed-by: Andy Paicu <andypaicu@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/main@{#995106}
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.