RESOLVED FIXED 223248
Apply permission policy to geolocation
https://bugs.webkit.org/show_bug.cgi?id=223248
Summary Apply permission policy to geolocation
youenn fablet
Reported 2021-03-16 03:59:49 PDT
Apply permission policy to geolocation
Attachments
Patch (13.78 KB, patch)
2021-03-16 04:02 PDT, youenn fablet
no flags
Patch (15.97 KB, patch)
2021-03-16 07:45 PDT, youenn fablet
no flags
Patch for landing (16.07 KB, patch)
2021-03-30 07:43 PDT, youenn fablet
no flags
youenn fablet
Comment 1 2021-03-16 04:02:52 PDT
youenn fablet
Comment 2 2021-03-16 07:45:16 PDT
Eric Carlson
Comment 3 2021-03-17 09:20:10 PDT
Comment on attachment 423328 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=423328&action=review > Source/WebCore/Modules/geolocation/Geolocation.cpp:358 > + if (!isFeaturePolicyAllowedByDocumentAndAllOwners(FeaturePolicy::Type::Geolocation, *document(), LogFeaturePolicyFailure::Yes)) > + return true; As we discussed, I think a linked-on-or-after check would be a good idea so we don't break existing apps that depend on the old behavior.
youenn fablet
Comment 4 2021-03-23 03:51:19 PDT
> As we discussed, I think a linked-on-or-after check would be a good idea so > we don't break existing apps that depend on the old behavior. If we add a linked-on-or-after check here, we probably need to do the same when computing the origin shown on the geolocation prompt. We can probably do that, but maybe we can try to land this change and use linked-on-or-after if we see breakage?
Radar WebKit Bug Importer
Comment 5 2021-03-23 04:00:53 PDT
EWS
Comment 6 2021-03-30 05:27:55 PDT
Tools/Scripts/svn-apply failed to apply attachment 423328 [details] to trunk. Please resolve the conflicts and upload a new patch.
youenn fablet
Comment 7 2021-03-30 07:43:22 PDT
Created attachment 424637 [details] Patch for landing
EWS
Comment 8 2021-03-31 04:16:18 PDT
Committed r275276: <https://commits.webkit.org/r275276> All reviewed patches have been landed. Closing bug and clearing flags on attachment 424637 [details].
Note You need to log in before you can comment on or make changes to this bug.