[blink-dev] PSA: Protected Audience k-Anonymity Enforcement

We plan to start enabling the k-anonymity enforcement feature for the Protected Audience API (Intent to Ship

Re: [blink-dev] Intent to Ship: Protected Audience Ad slot size in real-time bidding signals fetch and update more interest group fields

LGTM3 On Fri, Jan 26, 2024 at 4:10 AM Paul Jensen wrote: > > > On Wed, Jan 24, 2024 at 8:29 PM Domenic Denicola > wrote: > >> >> >> On Sat, Jan 6, 2024 at 3:05 AM Paul Jensen >> wrote: >> >>> Contact emails >>> >>> pauljen...@chromium.org >>> >>> >>> Explainer >>> >>> Ad slot size in

[blink-dev] PSA: vpython (2.7) to be removed from depot_tools

depot_tools users, Next week on January 31 (US time), we will submit https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/5187892 to remove the old vpython package (powered by python 2.7) from depot_tools. vpython3 will remain part of depot_tools, supporting python 3.8 and

[blink-dev] Intent to Prototype: 'writingsuggestions' attribute

Contact emails sa...@microsoft.com, dan...@microsoft.com, stephanie.zh...@microsoft.com Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/WritingSuggestions/explainer.md

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

Hi all, to follow up here, we're happy to share that the first-party Deprecation Trial (DT for top-level sites) for 3PCD is now available. See below resources for more details: Announcement blog: https://developers.google.com/privacy-sandbox/blog/3pcd-first-party-deprecation-trial-available

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

Thank you Wesley for the useful information! > What timeline do you have in mind? I'm not sure what reasonable timelines are, not having dealt with deprecations before. Is 3 months for a deprecation trial acceptable? Devtools should already have deprecation warnings

Re: [blink-dev] Intent to Ship: Protected Audience Ad slot size in real-time bidding signals fetch and update more interest group fields

On Wed, Jan 24, 2024 at 8:29 PM Domenic Denicola wrote: > > > On Sat, Jan 6, 2024 at 3:05 AM Paul Jensen > wrote: > >> Contact emails >> >> pauljen...@chromium.org >> >> >> Explainer >> >> Ad slot size in real-time bidding signals fetch: >> https://github.com/WICG/turtledove/pull/928 >> >>

Re: [blink-dev] Intent to Extend Reverse Origin Trial: Trial for SharedArrayBuffers in non-isolated pages on Desktop platforms

Excited about the potential changes around COEP, Microsoft has a handful of apps in that situation and we'd love to chat more if there's more supporting evidence/discussion needed. On Friday, January 19, 2024 at 9:15:52 AM UTC-8 rby...@chromium.org wrote: > LGTM to extend. Breaking the

Re: [blink-dev] Re: Intent to experiment - WebAssembly JavaScript Promise Integration (update)

Yep - that is an official positive signal, thanks! On 1/24/24 7:40 PM, Francis McCabe wrote: Does this: https://mozilla.github.io/standards-positions/#wasm-js-promise-integration count as an official positive signal? Francis On Wed, Jan 24, 2024 at 3:09 AM Yoav Weiss (@Shopify) wrote:

Re: [blink-dev] Intent to Ship: Protected Audience Ad slot size in real-time bidding signals fetch and update more interest group fields

LGTM2 On 1/24/24 4:10 PM, Rick Byers wrote: Great, thank you! Yep, looks like the PR is about to land to me, I'm satisfied. LGTM1 On Wed, Jan 24, 2024 at 10:02 AM Paul Jensen wrote: That spec PR has now been reviewed and approved by the Protected Audience team and our spec mentor. 

Re: [blink-dev] Intent to Prototype: Call stacks in crash reports from unresponsive web pages

Yes I was thinking of how the stack trace format was standardized as well. How do wasm call stacks work with this proposal? dave. On Wed, Jan 24, 2024 at 8:27 PM Domenic Denicola wrote: > I agree with Dave's take on the importance of not including extension > scripts themselves, and Rick's

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

I'm also happy to support a plan to deprecate and remove. The use counter that best represents worst-case user impact at https://chromestatus.com/metrics/feature/timeline/popularity/170 at ~0.001%. But that's only when fullscreen actually happens (on user interaction) and it's very hard to say

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

On Thu, Jan 25, 2024 at 2:00 AM Wesley Luyten wrote: > Wesley from Mux here. I saw the issue come by. > > We'd be happy those API's could get deprecated and unified into the new > one. > > Our Media Chrome (library, not browser) implementation handles this > gracefully, some code here > >

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

On Tue, Jan 23, 2024 at 2:31 AM Domenic Denicola wrote: > > > On Tue, Jan 23, 2024 at 7:55 AM Thomas Guilbert > wrote: > >> Good point about the most used APIs being the boolean properties! The >> APIs are now only aliases for the standard non-prefixed fullscreen APIs (see >> this code for the