Page Embedded Permission Control (Permission Element)
  • Past
  • Confirmed
  • Breakout Sessions

Meeting

Event details

Date:
– Central European Summer Time
Status:
Confirmed
Location:
Giralda III - Level -2
Participants:
Elad Alon, Christian Biesinger, Andreas Bovens, Rik Cabanier, Ada Rose Cannon, Ari Chivukula, Mihai Cîrlănaru, Ian Clelland, Gabe Cohen, Nick Doty, Christian Dullweber, Chris Fredrickson, Yi Gu, Lucas Haraped, Marian Harbach, Johann Hofmann, Michael Jackson, Toshiaki Koike, Jun Kokatsu, Anssi Kostiainen, Yifan Luo, Penelope McLachlan, Tove Petersson, Przemek Praszczalek, Matthew Reynolds, Kagami Rosylight, Vincent Scheib, Thomas Steiner, Austin Sullivan, Sameer Tare, Nicola Tommasi, Xiaohan Wang, Rupert Wiser, Howard Wolosky, Paul Zuehlcke
Big meeting:
TPAC 2023 (Calendar)

Most user interactions on permission prompts are negative. For notifications (the most requested permission type), Google Chrome metrics data shows that the percentage of prompts that are ignored, dismissed or blocked by the user add up to approx 92% on desktop platforms and 85% on mobile devices.

A permission model designed to be initiated by the user would solve these issues. If the user initiates the permission request it ensures that:

  • The user understands the purpose of the permission, or at least has enough context to feel comfortable engaging in an activity that uses this permission.

  • The user’s current flow or task is related to granting this permission and as such it’s unlikely that the permission request could be interruptive.

  • The user agent can ensure the subsequent UI is placed near the current focus of attention of the user. This is because the user has just interacted with some piece of UI to request the permission which means their focus is likely in the area. Because of the above, it is unlikely that such a placement is interruptive or annoying.

This breakout would discuss a proposal for Permission Embedded Permission Control [explainer] [deck] and intends to continue the dialog from the w3c Workshop on Permissions held December 2022.

Session notes

Agenda

Chairs:
Penelope McLachlan

Description:
Most user interactions on permission prompts are negative. For notifications (the most requested permission type), Google Chrome metrics data shows that the percentage of prompts that are ignored, dismissed or blocked by the user add up to approx 92% on desktop platforms and 85% on mobile devices.

A permission model designed to be initiated by the user would solve these issues. If the user initiates the permission request it ensures that:

  • The user understands the purpose of the permission, or at least has enough context to feel comfortable engaging in an activity that uses this permission.

  • The user’s current flow or task is related to granting this permission and as such it’s unlikely that the permission request could be interruptive.

  • The user agent can ensure the subsequent UI is placed near the current focus of attention of the user. This is because the user has just interacted with some piece of UI to request the permission which means their focus is likely in the area. Because of the above, it is unlikely that such a placement is interruptive or annoying.

This breakout would discuss a proposal for Permission Embedded Permission Control [explainer] [deck] and intends to continue the dialog from the w3c Workshop on Permissions held December 2022.

Session notes

Goal(s):
Feedback on a proposal to create a Page Embedded Permission Control (Permission Element)

Materials:

Track(s):

  • privacy

Minutes

 Read minutes

Export options

Personal Links

Please log in to export this event with all the information you have access to.

Public Links

The following links do not contain any sensitive information and can be shared publicly.

Feedback

Report feedback and issues on GitHub.