Contact emails

andypa...@google.com, pjmclach...@google.com, eng...@google.com

Explainer

https://github.com/WICG/PEPC/blob/main/explainer.md

Specification

none

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

This Origin Trial focuses only on the use of the control for
camera/microphone permissions.

Blink component

Chromium Public Trackers > Chromium > Internals > Permissions >
PermissionElement

TAG review

None

TAG review status

Pending

Risks
Interoperability and Compatibility

There is risk that this feature fails to be adopted by other browsers,
though we believe we can address non-supportive signal from other vendors

Gecko: neutral

WebKit: Initial Oppose (
https://github.com/WebKit/standards-positions/issues/270), we are addressing
feedback <https://github.com/WICG/PEPC/pull/17>. Some concerns will require
experimental data from OT implementers to address, and this is a goal of
the Origin Trial.

Web developers:

Positive - several first and third party partners are committed to
experimenting with the API and have implementations ready for when the OT
launches.

Other signals:

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


   - Solicit more informed Web developer feedback to validate the element
   API shape & functionality, including styling restrictions, specific to use
   of the Page-embedded Permission Control for Camera / Mic.
   - Validate developer use cases
   - Ensure that the feature works correctly in conjunction with adjacent
   features.
   - Ensure that the feature provides a better overall UX for permission
   interactions by allowing users a recovery path and less interruptions.
   - Check metrics against existing permission usage as a baseline, for
   example, investigate any significant increases or decreases in overall
   block/accept rates in OT to ensure users are having a safe, easy to use
   experience


Debuggability

None

Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, Chrome OS, Android, and Android WebView)?

No - OT will not include Android & Android WebView


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

Yes -
https://wpt.fyi/results/html/semantics/permission-element?label=experimental&label=master&aligned


Flag name on chrome://flags

none

Finch feature name

PermissionElement

Tracking bug

https://issues.chromium.org/issues/40275129

Launch bug

https://launch.corp.google.com/launch/4320707/approver/14626

Estimated milestones

Shipping OT on desktop

126


Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5125006551416832

Links to previous Intent discussions

Ready for Developer Testing :

https://groups.google.com/a/chromium.org/g/blink-dev/c/D-mE5qIlkWY/m/TTEImcBnAAAJ


Intent to prototype:

https://groups.google.com/a/chromium.org/g/blink-dev/c/TGsrhP4ref0/m/bHFj3id9AgAJ


-- 
*Penny McLachlan*
(she/her)

Senior Product Manager
pjmclach...@google.com
Google Chrome

-- 
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/CAFuQ4YuA5Fskj1QyrzL%2BXpZdQGe_vCu-wQjgqqhDwazC0Rr4FA%40mail.gmail.com.

Reply via email to