[PermissionOptions] Simplify request path, provide resolvers, pass back request information This CL is part of a larger change to support permissions with options. A summary of changes in this CL can be found below, the full design doc can be found here: go/multi-state-permissions-dd - Simplify interfaces to rely on PermissionRequestData wrapper and refactor PermissionContextBase and its subclasses accordingly. - Update PermissionRequestData to rely on permission resolvers. - Refactor PermissionRequest to rely on unique PermissionRequestData object and pass it to permission decided callbacks. Let PermissionRequestData be owned by the PermissionRequest. The permission decided callbacks need to be enhanced with this parameter because permissions with options will need to pass back information about the particular request to the permission infrastructure. Full design doc: http://go/multi-state-permissions-dd Change-Id: I81df3cbcedb9c7ef2340a0d79734adf77f336aae Bug: 394547183, 393053278 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6490747 Reviewed-by: Colin Blundell <blundell@chromium.org> Commit-Queue: Florian Jacky <fjacky@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/main@{#1455751}
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.