Bug 228017 - Require transient activation to use Geolocation API
Summary: Require transient activation to use Geolocation API
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: https://github.com/w3c/geolocation-ap...
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-07-16 00:31 PDT by Marcos Caceres
Modified: 2021-08-16 01:18 PDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcos Caceres 2021-07-16 00:31:57 PDT
It would be nice if, in order to use the Geolocation API, transient activation was required. 

There is a proposed Geolocation API spec change at:
https://github.com/w3c/geolocation-api/pull/94

The benefits being less annoying prompts for users.

Naturally, this would break *a lot* sites, so it would be great to coordinate on a strategy across browsers. There is support from Chrome and Mozilla to work together to figure out a strategy (see GitHub pull request link above).
Comment 1 Sam Sneddon [:gsnedders] 2021-07-16 03:33:10 PDT
What's "transient activation"?
Comment 2 Sam Sneddon [:gsnedders] 2021-07-16 03:34:25 PDT
Oh, https://html.spec.whatwg.org/multipage/interaction.html#transient-activation-duration

Do people frequently hit geolocation prompts within a few seconds of each other?
Comment 3 Marcos Caceres 2021-07-16 09:00:40 PDT
(In reply to Sam Sneddon [:gsnedders] from comment #2)
> Oh,
> https://html.spec.whatwg.org/multipage/interaction.html#transient-activation-
> duration
> 
> Do people frequently hit geolocation prompts within a few seconds of each
> other?

No, we would consume the activation as it usually displays the prompt (just haven't added that to the spec yet).
Comment 4 Radar WebKit Bug Importer 2021-07-22 16:23:17 PDT
<rdar://problem/80988930>
Comment 5 Marcos Caceres 2021-07-22 18:01:49 PDT
Just noting that there are is another idea being thrown around, like only requiring transient activation on third-party contexts... that might reduce a little bit of breakage. In any case, open to ideas and really hope folks here can provide some feedback