Hi Jeffrey, Thanks for double-checking. We plan to launch the <geolocation> element directly to shipping in M143 without a separate OT. Since, the current PEPC trial has already validated the core principles, security, and user flow. The <geolocation> element isn't a significant enough change from what we've already tested to warrant a brand new trial.
Best, Minh On Fri, Sep 26, 2025 at 7:17 PM Jeffrey Yasskin <[email protected]> wrote: > Double-checking: is this origin trial for the <permission> element or the > <geolocation> element? Are you planning a separate origin trial for > <geolocation> before that ships, or are you expecting that element to go > straight to shipping? > > On Fri, Sep 26, 2025 at 7:04 AM Mike Taylor <[email protected]> > wrote: > >> Thanks - LGTM to extend to M143. >> >> But we'll need 3 owners for the higher %. LGTM1 for that. >> On 9/26/25 9:31 a.m., Minh Le wrote: >> >> Hi Mike, >> thank you so much for your quick reply and instructions, I hit the button >> :) >> And I will let the partners know as soon as we get the new token. >> Best, >> Minh >> >> >> On Fri, Sep 26, 2025 at 3:24 PM Mike Taylor <[email protected]> >> wrote: >> >>> Hi there, >>> >>> I see a lot of good reasons to extend here. But could you please go to >>> your chromestatus entry and in the Origin Trial section click "Request >>> another trial extension" button, and fill it out with the details in this >>> message? >>> >>> A note on timing: the OT expires in M140, which means that users who >>> upgrade to M141 (scheduled to go out next week) will no longer have access >>> to the feature. November 11th is the day after the hard-coded expiration >>> date of Nov 10th for all users (i.e., folks who haven't upgraded past 140). >>> That means your partners will need to deploy the newly minted extension >>> token before 141 goes out to avoid any disruption. So if you click on that >>> button I can approve and maybe they can hit that deadline. >>> >>> thanks, >>> Mike >>> On 9/26/25 6:11 a.m., 'Minh Le' via blink-dev wrote: >>> >>> Hello blink-dev, >>> >>> Our team requests two changes for the existing Permission Element >>> (PEPC) Origin Trial. <https://chromestatus.com/feature/5125006551416832> >>> >>> 1. >>> >>> A timeline extension for three milestones, to M143. >>> 2. >>> >>> An increase in the page load limit from 0.5% to ~5% of Chrome page >>> loads. >>> >>> The current Origin Trial for PEPC is set to expire with M140 (Nov >>> 11th), while we are targeting the launch of the standardized <geolocation> >>> API <https://github.com/WICG/PEPC/blob/main/geolocation_explainer.md>in >>> M143 and preparing a new OT for a <usermedia> API >>> <https://github.com/WICG/PEPC/blob/main/usermedia_element.md>. The >>> extension is needed to prevent a disruption for our partners, and the page >>> load increase is critical for new experimentation and for ensuring a >>> smooth, validated path to a full launch. >>> Rationale for Extension & Page Load Increase >>> >>> The PEPC API is already providing significant, measurable user benefits >>> >>> 1. >>> >>> Unlocking Value and De-risking the Launch: >>> - >>> >>> Preventing Partner Disruption: For example, in a high-traffic web >>> service, users who specifically clicked 'Use precise location' >>> previously >>> encountered barriers to changing their settings if they had blocked >>> location permissions. PEPC resolved this, leading to approximately >>> +17pp >>> and +36pp increases in successfully adjusting settings on Desktop and >>> Mobile, respectively.” Extending the trial ensures that partners like >>> Zoom, >>> Cisco, Zaplmoves, and OLX BR, Meet, Search and others do not lose >>> this functionality until we roll this change out. (see some use cases >>> here >>> <https://developer.chrome.com/blog/rethinking-web-permissions>) >>> - >>> >>> Validating at Scale: An increased page load limit allows our >>> high-traffic partners to scale their successful implementations >>> beyond the >>> current OT cap. This delivers the feature's proven benefits to a wider >>> audience sooner and, critically, allows us to validate that the >>> positive >>> results from a small experiment carry over at a larger scale, >>> mitigating >>> risks before the full M143 launch. >>> 2. >>> >>> Enabling New, High-Impact Experimentation: We need to increase the >>> page load limit to validate PEPC's integration with the upcoming >>> Approximate >>> Location >>> <https://github.com/explainers-by-googlers/approximate-geolocation> >>> feature. >>> - >>> >>> PEPC provides a natural, user-initiated entry point for managing >>> location granularity (e.g., changing from approximate to precise and >>> vice >>> versa). >>> - >>> >>> To get this right, we need to test several UI variations >>> (different button treatments and prompts) for this new user flow. >>> - >>> >>> A higher page load limit is necessary to gather statistically >>> significant data across these experimental arms, ensuring we can >>> differentiate user behavior and build the best possible experience >>> before >>> launch. >>> 3. >>> >>> New Experimentation Plan: Based on valuable feedback from other >>> browser vendors, we are splitting the generic <permission> element into >>> capability-specific elements. This OT extension provides a bridge to that >>> future: >>> - >>> >>> Geolocation: The learnings from the current OT (including the >>> Approximate Location experiments) will directly inform the launch of >>> the >>> new <geolocation> element, targeted for M143. >>> - >>> >>> User Media (Camera/Mic): We will create a new, separate OT for >>> <usermedia> to continue collaborative development on its API shape >>> after >>> the current OT expires. >>> >>> This plan ensures continuity for our partners while allowing us to ship >>> the most stable, consensus-driven solution. We appreciate your >>> consideration and welcome any questions. >>> >>> Best regards, >>> >>> Minh on behalf of the Chrome PEPC Team >>> >>> >>> -- >>> 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 [email protected]. >>> To view this discussion visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJcu7Avg7A344o1T03xuxzJ0nCyQr29p0maDG0o0f6X1kKtWMQ%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJcu7Avg7A344o1T03xuxzJ0nCyQr29p0maDG0o0f6X1kKtWMQ%40mail.gmail.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 [email protected]. >> To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3f9d44d3-e93c-4467-96f1-21384cd5a6c6%40chromium.org >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3f9d44d3-e93c-4467-96f1-21384cd5a6c6%40chromium.org?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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJcu7At-YdOxe%3Do_xtuqjKF1iU8wSMN3p3tny%3DaF9O2Cr4vYow%40mail.gmail.com.
