Thanks, LGTM to extend from 132-134 inclusive. On 2/3/25 5:31 AM, Andy Paicu wrote:
Thank you for the quick reply, I've added inline links to artefacts exemplifying our progress. Let me know if I can further clarify or provide more information.* Draft spec (early draft is ok, but must be spec-like and associated with the appropriate standardization venue, or WICG) Early spec draft: https://wicg.github.io/PEPC/permission-element.html, in WICG * TAG review (see exceptions <https://www.chromium.org/blink/launching-features/wide-review/#exceptions>) We have not yet sent a TAG review, we will prioritize doing so in the near future * signals <https://www.chromium.org/blink/launching-features/wide-review> requests https://github.com/WebKit/standards-positions/issues/270 https://github.com/mozilla/standards-positions/issues/908 developers: https://github.com/WICG/PEPC/issues/2#issuecomment-2393911331 https://github.com/WICG/PEPC/issues/2#issuecomment-2393820279 https://github.com/WICG/PEPC/issues/2#issuecomment-2393911331 https://github.com/WICG/PEPC/issues/2#issuecomment-2619657041 * Outreach for feedback from the spec community We've had a TPAC breakout at 2024 to discuss this https://www.w3.org/2024/09/TPAC/breakouts.html#b-2912dccd-bd4d-4671-b63f-c045c7a1703a. * WPT tests https://wpt.fyi/results/html/semantics/permission-element?label=experimental&label=master&aligned <https://wpt.fyi/results/html/semantics/permission-element?label=experimental&label=master&aligned> Kind Regards, Andy PaicuOn Fri, Jan 31, 2025 at 10:00 PM Mike Taylor <miketa...@chromium.org> wrote:Could you please comment on any progress made in the following areas <https://www.chromium.org/blink/launching-features/#origin-trials>, since the first OT? * Draft spec (early draft is ok, but must be spec-like and associated with the appropriate standardization venue, or WICG) * TAG review (seeexceptions <https://www.chromium.org/blink/launching-features/wide-review/#exceptions>) * signals <https://www.chromium.org/blink/launching-features/wide-review>requests * Outreach for feedback from the spec community * WPT tests On 1/31/25 7:41 AM, Chromestatus wrote:Contact emails andypa...@google.com, pjmclach...@google.com, eng...@google.com, eri...@google.com Explainer https://github.com/andypaicu/PEPC/blob/main/explainer.md Specification https://wicg.github.io/PEPC/permission-element.html 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 component UI>Browser>Permissions>Prompts <https://issues.chromium.org/issues?q=customfield1222907:%22UI%3EBrowser%3EPermissions%3EPrompts%22> TAG review None TAG review status Pending Origin Trial Name Page-embedded Permission Control (Camera/Mic) Chromium Trial Name PermissionElement Origin Trial documentation link https://github.com/WICG/PEPC/blob/main/explainer.md WebFeature UseCounter name kHTMLPermissionElement 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. Reason this experiment is being extended PEPC is being introduced on Android as well in M134 and we wish to allow developers time to experiment with the feature on a mobile platform where the overall UX can be quite different and users interact with certain permissions differently. Additionally there are still open questions around the markup of the element and whether it should be a void element vs allowing contents, and we would like to further explore options in this space before committing to one particular solution. Ongoing technical constraints None Debuggability None Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? No The Permission Element is not supported on Android WebView as it permission manager support to actually function and the WebView permission manager defers most permission decisions to the embedder. 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 instructions https://github.com/WICG/PEPC/blob/main/HOWTO.md Flag name on about://flags None Finch feature name PermissionElement Requires code in //chrome? True Estimated milestones Origin trial desktop first 126 Origin trial desktop last 131 Origin trial extension 1 end milestone 134 Origin trial extension 2 end milestone 137 DevTrial on desktop 121 Origin trial Android first 134 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5125006551416832?gate=5156063554568192 Links 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=footer <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 Intent to Extend Experiment 1: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALTCLq7M2xaMvR4xFUk29gAsLLUcmWBFqgKhwQfADrf%3DmniNHg%40mail.gmail.com This intent message was generated by Chrome Platform Status <https://chromestatus.com>.-- You received this message because you are subscribed to theGoogle 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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/679cc50c.2b0a0220.243291.0754.GAE%40google.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/679cc50c.2b0a0220.243291.0754.GAE%40google.com?utm_medium=email&utm_source=footer>.
-- 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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/81bfc85b-91a5-4f79-b990-f5a3eb966e48%40chromium.org.
