Re: [blink-dev] Request for Deprecation Trial: Media Previews opt-out

On Wed, May 15, 2024 at 9:02 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > Can you expand on how (if) this is different from the past intent > > with a similar title

[blink-dev] Re: Intent to Prototype: No-Vary-Search Hint for Prerender Speculation Rules

I noticed the spec, https://github.com/WICG/nav-speculation/blob/main/triggers.md#no-vary-search-hint , doesn't have a privacy and security section -- could you add one? It looks like there's lots of other good information about the pri

Re: [blink-dev] Request for Deprecation Trial: Media Previews opt-out

> 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 de

Re: [blink-dev] Intent to Implement and Experiment: Skip Ad in Picture-in-Picture window

Hi team, This feature was initially proposed and implemented 4 years ago but remained disabled due to a lack of practical use cases. Given our team's (chromeOS UI team) plan to use this SkipAd action in our upcoming project, we are now resending this intent email for LGTMs. Please let me know

Re: [blink-dev] Intent to Ship: Deprecate Mutation Events

On Thu, May 16, 2024 at 11:00 AM Vladimir Levin wrote: > I looked into the UKM data about three months ago, before I started the >> experiment to disable all mutation events on Canary/Dev/Beta. I looked at >> the top ~30 UKM hits and dug into the site's code to see what the usage >> was. Many (~4

Re: [blink-dev] Intent to Ship: Support Video Chapter in MediaMetadata

Sorry for the slow reply here. Glad to see this works for Audio too. This might have been a bit more obvious of there were an explainer in the usual format. I expect the TAG will ask for one of those too. Please pay particular attention to considered alternatives and example code, both for the

[blink-dev] Intent to Ship: Attribution Reporting Feature: Prevent Coalescing of Headers

Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution Reporting API with Aggregatable Reports

[blink-dev] Intent to Ship: Attribution Reporting Feature: Referrer Policy for Attributionsrc Requests

Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution Reporting API with Aggregatable Reports

Re: [blink-dev] Re: Intent to Ship: Compute Pressure

Hi Arnaud, I have a followup question about this. I assumed that the feature wouldn't be enabled on Android, but judging by Chromium source and wpt.fyi test results, at least the API surface is exposed: https://wpt.fyi/results/compute-pressure/idlharness.https.any.html?label=master&label=experimen

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

On 16/05/2024 21:05, Robert Flack wrote: I believe the reason for waiting is that the intention is to switch to a different publishing model after level 3 is published? @Patrick H. Lauke  to confirm. Apologies for the convoluted model here ... I have to admit

[blink-dev] Re: Intent to Ship: Protected Audience: reporting timeouts & multiple-bids

Actually CC Erik this time. On Fri, May 17, 2024 at 8:40 AM Paul Jensen wrote: > > > On Wed, May 15, 2024 at 8:36 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Monday, May 6, 2024 at 10:03:16 PM UTC+2 Paul Jensen wrote: >> >> Contact emails >> >> pauljen...@chromium.o

[blink-dev] Re: Intent to Ship: Protected Audience: reporting timeouts & multiple-bids

On Wed, May 15, 2024 at 8:36 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Monday, May 6, 2024 at 10:03:16 PM UTC+2 Paul Jensen wrote: > > Contact emails > > pauljen...@chromium.org > > > Explainer > > Protected Audience reporting timeouts: https://github.com/WICG/ > turtledov

Re: [blink-dev] Intent to Ship: Automatic Fullscreen Content Setting

Hi Mike, I think the use cases here are clear and skipping the user activation requirement is the only way to meet them. I believe that the biggest risk here is content written assuming this setting not working without it, and it being hard to understand why. In other words, debuggability and feat

Re: Issue 341105739: Canvas content disappears when switching to another tab and back

Replying to this email means your email address will be shared with the team that works on this product. https://issues.chromium.org/issues/341105739 Changed se...@chromium.org added comment #7: I think this issue's severity and priority should be increased. WDYT? _

Re: Issue 341105739: Canvas content disappears when switching to another tab and back

Replying to this email means your email address will be shared with the team that works on this product. https://issues.chromium.org/issues/341105739 Changed se...@chromium.org added comment #6: Here is minimum the reproduction case just using canvas: var c = document.getElementById("myCa

Re: Issue 341105739: Canvas content disappears when switching to another tab and back

Replying to this email means your email address will be shared with the team that works on this product. https://issues.chromium.org/issues/341105739 Changed se...@chromium.org added comment #5: I confirmed to reproduce in my company's production and Google spreadsheet for M125 stable and M126