Contact emailsandypa...@google.com, pjmclach...@google.com,
eng...@google.com, eri...@google.com

Explainerhttps://github.com/andypaicu/PEPC/blob/main/explainer.md

SpecificationNone

Summary

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 componentUI>Browser>Permissions>Prompts
<https://bugs.chromium.org/p/chromium/issues/list?q=component:UI%3EBrowser%3EPermissions%3EPrompts>

TAG reviewNone

TAG review statusPending

Chromium Trial NamePermissionElement

Origin Trial documentation link
https://github.com/WICG/PEPC/blob/main/explainer.md

WebFeature UseCounter namekHTMLPermissionElement

Risks


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)?Yes

Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
?Yes

Partial WPT: https://wpt.fyi/results/html/semantics/permission-element


DevTrial instructionshttps://github.com/WICG/PEPC/blob/main/HOWTO.md

Flag name on chrome://flagsNone

Finch feature namePermissionElement

Requires code in //chrome?True

Estimated 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=5248170272227328

Links to previous Intent discussionsIntent to Prototype:
https://groups.google.com/a/chromium.org/g/blink-dev/c/TGsrhP4ref0/m/bHFj3id9AgAJ?utm_medium=email&utm_source=footer
Ready 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


This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALTCLq7M2xaMvR4xFUk29gAsLLUcmWBFqgKhwQfADrf%3DmniNHg%40mail.gmail.com.

Reply via email to