| commit | b6afe3012e3de282e54a823a26bd3b64b76bca29 | [log] [tgz] |
|---|---|---|
| author | Stefan Zager <szager@chromium.org> | Mon Sep 08 23:30:45 2025 |
| committer | Stefan Zager <szager@chromium.org> | Mon Sep 08 23:30:45 2025 |
| tree | c062ba51a6af74dcdc0e3c660abdc7632812a2bc | |
| parent | 94546c2abf24f845a763222dbfa7f397dca56c6b [diff] |
Revert "[Extensions] Clarify error for attempts to access a discarded page." This reverts commit c4a9dec3e2a9bbc4d6cc2a5c7c84ecbecb9c96e7. Reason for revert: https://issuetracker.google.com/443772815 Bug: 40875684 Original change's description: > [Extensions] Clarify error for attempts to access a discarded page. > > Previously, trying to inject a script into a discarded tab would result > in a "Cannot access contents of the page. Extension manifest must > request permission to access the respective host." error, but this is > untrue for accessing discarded pages (page cannot be accessed due to the > page being discarded, not because the extension does not have necessary > host permissions). > > Bug: 40875684 > Change-Id: I2c9e18ad1c809235172aa8ab043630e34f973af1 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6918371 > Reviewed-by: Tim <tjudkins@chromium.org> > Commit-Queue: Eva Su <evasu@chromium.org> > Reviewed-by: Emilia Paz <emiliapaz@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1512630} Bug: 40875684 No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: Ibe79e4efe111e66a23ec5c3c67df0ad93a6121fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6927234 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Stefan Zager <szager@chromium.org> Owners-Override: Stefan Zager <szager@google.com> Cr-Commit-Position: refs/heads/main@{#1512752}
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.