Intent to Extend Experiment: Page-Embedded Permission Control
Andy Paicu
Contact emails
andy...@google.com, pjmcl...@google.com, eng...@google.com, eri...@google.comExplainer
https://github.com/andypaicu/PEPC/blob/main/explainer.mdSpecification
NoneSummary
Provide a new HTML element that interacts with the permission flow. The permission prompt is currently triggered directly from JS without the user agent having any strong signal of the user's intent. Having an in-content element that the user uses to trigger the permission flow allows for improved permission prompt UX for users as well as a recovery path from the "denied" permission state for sites. Explainer: https://github.com/WICG/PEPC/blob/main/explainer.md Instructions: https://github.com/WICG/PEPC/blob/main/HOWTO.md
Blink component
UI>Browser>Permissions>PromptsTAG review
NoneTAG review status
PendingChromium Trial Name
PermissionElementOrigin Trial documentation link
https://github.com/WICG/PEPC/blob/main/explainer.mdWebFeature UseCounter name
kHTMLPermissionElementRisks
Interoperability and Compatibility
There is a risk that this feature fails to be adopted by other browsers. This can be mitigated by polyfilling some of the functionality to ensure the feature is not completely broken in non-implementing browsers.
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:
Ergonomics
This feature will likely be used in tandem with the Permissions API (https://www.w3.org/TR/permissions/) which is already supported. The Permissions API runs async. No foreseen ergonomics risks.
Activation
A polyfill can help developers use this feature without risking broken functionality on non-supporting browsers.
Security
https://github.com/WICG/PEPC/blob/main/explainer.md#Security
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Goals for experimentation
Reason this experiment is being extended
The OT originally spans from 126-131, we would like to extend it starting from 132-134 (inclusive), as there is new functionality being added to the existing trial to support the addition of support for geolocation permission (<permission type=”geolocation”>), as well as to give additional partners chances to experiment with the existing <permission> element OT support for camera & mic permission types. The new functionality will not be ready for OT until the stable release of 132.
Ongoing technical constraints
None
Debuggability
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
YesIs this feature fully tested by web-platform-tests?
YesPartial WPT: https://wpt.fyi/results/html/semantics/permission-element
DevTrial instructions
https://github.com/WICG/PEPC/blob/main/HOWTO.mdFlag name on chrome://flags
NoneFinch feature name
PermissionElementRequires code in //chrome?
TrueEstimated milestones
| Origin trial desktop first | 126 |
| Origin trial desktop last | 131 |
| Origin trial extension 1 end milestone | 134 |
| DevTrial on desktop | 121 |
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5125006551416832?gate=5248170272227328Links to previous Intent discussions
Intent to Prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/TGsrhP4ref0/m/bHFj3id9AgAJ?utm_medium=email&utm_source=footerReady for Trial: https://groups.google.com/a/chromium.org/g/blink-dev/c/D-mE5qIlkWY
Intent to Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFuQ4YuA5Fskj1QyrzL%2BXpZdQGe_vCu-wQjgqqhDwazC0Rr4FA%40mail.gmail.com
