Page Embedded Permission Control (PEPC) #270
Labels
concerns: complexity
This proposal seems needlessly complex
concerns: device independence
Proposal is hardware- or OS-specific, in a way that may risk the device independence of the Web
concerns: duplication
This proposal duplicates functionality of an existing web platform feature
concerns: internationalization
This proposal doesn't sufficiently account for different languages or locales
concerns: maintenance
It's not clear the proposal is getting maintained.
concerns: portability
This proposal may be impossible or difficult to implement on at least one important platform
concerns: usability
This proposal will create usability issues for users
from: Google
Proposed, edited, or co-edited by Google.
position: oppose
topic: accessibility
Spec relates to accessibility
topic: app-like capabilities
Spec relates to native app style capabilities (e.g. things under the "PWA" or "Fugu" brands)
topic: html
Spec relates to HTML (Hypertext Markup Language)
topic: markup
Spec relates to markup: elements, attributes, etc
topic: meaningful user consent
Feature likely requires meaningful user consent to allow
venue: WICG
Proposal is incubated in the Web Incubator Community Group
WebKittens
@marcoscaceres
Title of the spec
Page Embedded Permission Control
URL to the spec
No response
URL to the spec's repository
https://github.com/WICG/PEPC
Issue Tracker URL
No response
Explainer URL
No response
TAG Design Review URL
No response
Mozilla standards-positions issue URL
mozilla/standards-positions#908
WebKit Bugzilla URL
No response
Radar URL
No response
Description
The Page Embedded Permission Control (prev Permission Element) is a new HTML element embedded into web content that allows users to initiate a permission request flow (vs. permissions api which lets developers prompt users). This reframes the current permission model from developer-push to user-pull, where we can be confident of user intent.
The text was updated successfully, but these errors were encountered: