Bug 228017 – Require transient activation to use Geolocation API

• Status: RESOLVED
• Resolution: LATER
• Component: New Bugs

[Marcos Caceres]

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).

[Sam Sneddon [:gsnedders]]

What's "transient activation"?

[Sam Sneddon [:gsnedders]]

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?

[Marcos Caceres]

(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).

[Radar WebKit Bug Importer]

<rdar://problem/80988930>

[Marcos Caceres]

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

[Marcos Caceres]

Resolving as "later", till such time as there's standards agreement to do something here on the standards side.