We were just discussing whether this was a bug whether the other permissions are bugged...

Initially I was thinking that it is better for users if the site can't just nag them with permission prompts repeatedly. But the tradeoff is that a user may change their mind and actually want to see the prompt again.

The other thing to consider is that if a website really did want to nag a user, they could easily refresh their page or show another prompt the next time a user navigates, so I'm not sure we would actually be protecting users very much.

Maybe it is ok to allow multiple prompts per page-load but to block on 3 dismiss/ignores in general? 

Thoughts?

I was about to say "ah, it would be so annoying!" but if this is in a post-embargo world, then there's a balancing incentive. So personally I think this would be fine as long as there's a block on 3 dismiss/ignores in general.

I would prefer to allow multiple prompts but use auto-blocking, but I think allowing a single prompt might incentivize better behaviour, e.g. maybe websites would prefer to not eagerly prompt if they won't as easily be able to re-prompt at a more appropriate time?

c#6: what do you mean by allowing a single prompt?

I'm in favour of aligning the location prompt's behaviour with the other permissions and using embargo to control the total number of prompts. I think this should accelerate our timeline for implementing embargo on ignored prompts (which currently is implemented but we haven't decided whether to launch or not yet).

Sorry for poor wording, allowing a single prompt => not re-showing dismissed prompts

c#8: Ah, I see. You're definitely right in that not being able to show a prompt again until after reloading incentivises sites to prompt at the right time. But with embargo we'd be able to have a similar mechanism that's much more forbidding for developers: not being able to show a prompt for a week rather than the next reload.

It's possible that not many developers know enough about the inability to re-request location permission until after a reload. That makes the restriction less effective as a way of stopping bad behaviour. Whatever we decide, we should definitely think about how to publicise it as widely as possible.

IIRC we don't have metrics for ignore yet to make sure they have the same properties of deny, to decide whether to launch embargo for ignores. Is that still right?

Still, getting a permission prompt 3 times in the same page load seems incredibly annoying and I'm not convinced we should ever allow this even with Embargo. The only use case I can see is if someone accidentally clicks "deny", then gestures on a location icon again, and is confused when the dialog doesn't pop up again. But I think in this case we should be teaching people to go to PageInfo to toggle their (non-default) permissions. Do we have any metrics to see which sites are currently showing prompts >1 per load and what actions people are taking (maybe this makes a site's overall acceptance rate lower?)

We do have metrics for repeated ignores before a decision - I used them to decide on an initial number of 4 repeated ignores for automatic blocking. What we don't have metrics on is combined dismisses + ignores before a decision is made.

If a user ignores the permission prompt, it can only be shown once per the page load anyway (the prompt just sits there and nothing will be shown over it or replacing it), so the only way to get multiple prompts is to explicitly dismiss them with the X or Esc.

Adding Privacy because this influences user's control over sharing their data.

Update:

***Mass UI Triage***

We were unable to reproduce this bug on latest Dev version #72.0.3610.2 as the permission bubble appears 3 times now for 'Location' button. If this bug still reproduces for you, please reopen or file a new issue.

Thanks!