RESOLVED FIXED 293089
[Permissions API] Report the true permission state of Geolocation only when that API has been used since the page load
https://bugs.webkit.org/show_bug.cgi?id=293089
Summary [Permissions API] Report the true permission state of Geolocation only when t...
rupin
Reported 2025-05-15 18:18:47 PDT
[Permissions API] Report the true permission state of Geolocation only when that API has been used since the page load
Attachments
Radar WebKit Bug Importer
Comment 1 2025-05-15 18:18:55 PDT
rupin
Comment 2 2025-05-15 18:20:40 PDT
EWS
Comment 3 2025-05-21 15:29:31 PDT
Committed 295237@main (386b21db7bdc): <https://commits.webkit.org/295237@main> Reviewed commits have been landed. Closing PR #45470 and removing active labels.
rupin
Comment 4 2025-06-06 19:37:50 PDT
*** Bug 258726 has been marked as a duplicate of this bug. ***
rupin
Comment 5 2025-06-06 19:42:55 PDT
*** Bug 275950 has been marked as a duplicate of this bug. ***
rupin
Comment 6 2025-06-06 19:43:13 PDT
*** Bug 275479 has been marked as a duplicate of this bug. ***
smoser
Comment 7 2025-08-12 10:52:05 PDT
Thanks for the fix! I tried reproducing the behavior for https://bugs.webkit.org/show_bug.cgi?id=275479. Using https://permission.site/permission-status I noticed, that the permission state correctly is reported as GRANTED when I query with navigator.permissions.query({ name: 'geolocation' }) but the `change` event for the permission status, outlined at https://developer.mozilla.org/en-US/docs/Web/API/PermissionStatus/change_event, does not fire when going from PROMPT to GRANTED. Is that intended?
rupin
Comment 8 2025-08-12 13:27:28 PDT
Hello! Currently, the change event is not fully supported, and we are aware of this.
smoser
Comment 9 2025-08-14 05:03:52 PDT
Thanks for confirming! I reported a similar discrepancy between the query and event permission API on MacOS at https://bugs.webkit.org/show_bug.cgi?id=275268, potentially close it as duplicate.
rupin
Comment 10 2025-08-14 09:17:03 PDT
Sounds good, thank you for filing the bug!
Note You need to log in before you can comment on or make changes to this bug.