> Could you explain how this feature and PEPC relate, and why having them
work together is a bad thing?

PEPC is a completely different permissions UI for Chrome that disables the
experience that includes previews. The explainer for PEPC
<https://github.com/andypaicu/PEPC/blob/main/explainer.md> demonstrates
conceptual UI for PEPC, and I believe running Chrome using these
instructions <https://github.com/WICG/PEPC/blob/main/HOWTO.md> will allow
you to try it yourself.

Currently media previews are not supported in PEPC, but the outcome of the
experiment and PEPC origin trial will help inform us about whether it makes
sense to integrate these features in the future.

> Do you plan to deprecate one of the features once the Deprecation Trial
is finished?  (Or are you just requesting an Origin Trial to temporarily
disable something, and expect it to be re-enabled in the future?)

I can't speak for PEPC. For Media Previews, future changes will be based on
feedback from our Finch experiments and discussions with sites that use the
opt out origin trial.  We may, for example, decide to attempt an API that
allows sites to customize the camera and mic permissions UI in ways that
extend beyond PEPC.  Or we may not do that and instead enable previews for
all non-PEPC-using sites.

m.


On Mon, May 13, 2024 at 10:21 AM Mike Taylor <miketa...@chromium.org> wrote:

> FWIW, a deprecation trial can surpass 6 milestones - but they require
> sufficient justification as well as 3 LGTMs.
>
> That said, I'm not sure I understand the request here. I read the linked
> "Chrome Camera and Mic Previews" document, but I think the Rollout plan
> section is assuming more info than I have. Could you explain how this
> feature and PEPC relate, and why having them work together is a bad thing?
> Do you plan to deprecate one of the features once the Deprecation Trial is
> finished? (Or are you just requesting an Origin Trial to temporarily
> disable something, and expect it to be re-enabled in the future?)
>
> Something that approaches an Explainer would probably be helpful here -
> thanks!
>
> On 5/10/24 5:05 PM, mark a. foltz wrote:
>
> I'm fine with shortening the trial, as long as extensions are possible in
> case we need longer to ship a long-term solution.
>
> On Fri, May 10, 2024 at 12:39 PM Vladimir Levin <vmp...@chromium.org>
> wrote:
>
>>
>>
>> On Fri, May 10, 2024 at 2:40 PM mark a. foltz <mfo...@chromium.org>
>> wrote:
>>
>>> Contact emails mfo...@chromium.org, bryantchand...@chromium.org
>>>
>>> Explainer None
>>>
>>> Specification
>>> https://docs.google.com/document/d/1ZnX2JROjr9l4y2_OPMpfVlLOo-A5cQzD4mWarj9kXQ0/edit
>>>
>>> Design docs
>>>
>>> https://docs.google.com/document/d/1ZnX2JROjr9l4y2_OPMpfVlLOo-A5cQzD4mWarj9kXQ0/edit
>>>
>>> Summary
>>>
>>> Allow coordination between sites using Page Embedded Permissions
>>> Controls and concurrent experiments with the camera and microphone
>>> permissions UI in Chrome.
>>>
>>>
>>> Blink component Blink>MediaStream
>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EMediaStream>
>>>
>>> TAG review None
>>>
>>> TAG review status Not applicable
>>>
>>> Chromium Trial Name MediaPreviewsOptOutPersistent
>>>
>>> Origin Trial documentation link
>>> https://docs.google.com/document/d/1ZnX2JROjr9l4y2_OPMpfVlLOo-A5cQzD4mWarj9kXQ0/edit?usp=sharing
>>>
>>> WebFeature UseCounter name kOBSOLETE_PageDestruction
>>>
>>> Risks
>>>
>>>
>>> Interoperability and Compatibility
>>>
>>> None as this feature concerns the functionality of Chrome's permissions
>>> UI, and does not change the behavior of the APIs that are gated by it:
>>> navigator.mediaDevices.enumerateDevices and
>>> navigator.mediaDevices.getUserMedia Other browsers implement their own
>>> permissions UIs independently of Chrome.
>>>
>>>
>>> *Gecko*: N/A
>>>
>>> *WebKit*: N/A
>>>
>>> *Web developers*: No signals
>>>
>>> *Other signals*:
>>>
>>> Ergonomics
>>>
>>> N/A
>>>
>>>
>>> Activation
>>>
>>> N/A
>>>
>>>
>>> Security
>>>
>>> N/A
>>>
>>>
>>> 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
>>>
>>> Ongoing technical constraints
>>>
>>> There are no plans to add media previews to Chrome on platforms other
>>> than Windows/Mac/Linux.
>>>
>>>
>>> Debuggability
>>>
>>> N/A
>>>
>>>
>>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>>> Linux, ChromeOS, Android, and Android WebView)? No
>>>
>>> There are currently no plans to launch previews outside of
>>> Windows/Mac/Linux.
>>>
>>>
>>> Is this feature fully tested by web-platform-tests
>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>>> ? No
>>>
>>> N/A
>>>
>>>
>>> DevTrial instructions https://tinyurl.com/yc6mvth8
>>>
>>> Flag name on chrome://flags --enable-features=camera-mic-preview
>>>
>>> Finch feature name CameraMicPreview
>>>
>>> Requires code in //chrome? False
>>>
>>> Tracking bug https://issues.chromium.org/330762482
>>>
>>> Launch bug https://launch.corp.google.com/launch/4304480
>>>
>>> Estimated milestones
>>> Origin trial desktop first 126
>>> Origin trial desktop last 137
>>> DevTrial on desktop 122
>>>
>>
>> According to
>> https://www.chromium.org/blink/launching-features/#deprecation-trial,
>> deprecation trials should only run for up to 6 milestones before an
>> extension is required, so this may need to be adjusted
>>
>>
>>>
>>> Link to entry on the Chrome Platform Status
>>> https://chromestatus.com/feature/5100528783851520?gate=5123374989967360
>>>
>>> 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/CALgg%2BHFcLM%3DgkSy9F%2BeAZ4KiW4zyXXfZQ-eKzuNoo109czCHFA%40mail.gmail.com
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgg%2BHFcLM%3DgkSy9F%2BeAZ4KiW4zyXXfZQ-eKzuNoo109czCHFA%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 blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgg%2BHF9J0-ToRM%3DpA%2B4YUz2bksCuWMaKNo%3D3Z%2BphQd%3Dz%2BDmtQ%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgg%2BHF9J0-ToRM%3DpA%2B4YUz2bksCuWMaKNo%3D3Z%2BphQd%3Dz%2BDmtQ%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 blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgg%2BHFYAcfWjV2%3DM9mZpN%3Dz9Zz4rmq2aamn-TBCOUgL7a04jg%40mail.gmail.com.

Reply via email to