| commit | 0c86babdc18ecd269fdb5ae8fb559331b3dd8906 | [log] [tgz] |
|---|---|---|
| author | Matt Reynolds <mattreynolds@chromium.org> | Thu Aug 24 22:21:56 2023 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 24 22:21:56 2023 |
| tree | d5a3767b5b6ca15473a1c3446f4c5dd9e1a2486a | |
| parent | 880295f58664890954af33b45f82ea1e88a54a71 [diff] |
Revert "Stop geolocation watch updates upon permission revocation" This reverts commit d02d575ab500ac29d0bad966fd53a97fe0b0f61a. Reason for revert: returns "permission was revoked" error even after permission is granted (crbug.com/1475743) Original change's description: > Stop geolocation watch updates upon permission revocation > > Previously, once a site obtained a geolocation watch (either through an already existing grant or through a new permission prompt flow), it kept receiving location updates in the registered watch callback within the same session (i.e. for as long as the user didn't close the tab or performed a navigation). This remained the case, even after the grant was revoked. This CL fixes this behaviour. > > Bug: 1462313 > > Change-Id: I3eef70bb8f5aad3f5bfc2554f429312acd238bf5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4668727 > Reviewed-by: Avi Drissman <avi@chromium.org> > Commit-Queue: Florian Jacky <fjacky@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1177378} Bug: 1462313 Change-Id: Ib9c7816fd85397bd58f0ebe355ff10b79daeaa2e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4811298 Commit-Queue: Matt Reynolds <mattreynolds@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1188049}
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.