[blink-dev] Re: [LayerTreeView][RequestNewLayerTreeFrameSink] Nested infinite loops in render main thread

need your help, please take a look, will appreciate it. On Thursday, June 6, 2024 at 10:12:16 AM UTC+8 Lowell Liu wrote: > Hi I just create an issue https://issues.chromium.org/issues/345275130, > any guy can take a look? > > -- You received this message because you are subscribed to the Goog

[blink-dev] Upcoming roll-out plans for the Rust-based secure font stack in Blink

Hi, The Blink Style & Fonts, Google Fonts and Skia teams have been collaborating on Fontations, a secure set of font processing libraries written in Rust. We integrate Fontations into Chrome and use it in a new Skia font backend meant as a secure replacement for our usage of FreeType. The Fontatio

[blink-dev] Intent to Ship: Protected Audience - Fix implementation and spec for renderSize

Contact emails xiaoche...@google.com, shivani...@google.com, jkar...@google.com Explainer https://github.com/WICG/turtledove/pull/1145 Specification https://github.com/WICG/turtledove/pull/1141 Design docs https://docs.google.com/document/d/1JSUZzEnVGn6Rz6ncLbyhThModoxTGnBn-jS5xJf4Aq0/edit?u

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

Thank you for the detailed explanation! I have some more questions below. On Thu, Jun 6, 2024 at 7:55 PM Liviu Tinta wrote: > > Do you have a sense of how often the failure cases happen? Also what is > the cost of this failure? > The discussion is limited to in-progress prefetches that have not

Re: [blink-dev] Intent to Ship: Snap Events

Indeed, developer sentiment is full of excitement! Who wouldn't want to throw out their hyper intersection observers with a perfectly timed callback? or even better, getting insights into the concept of "changing" which is currently opaque to authors. > Philip: For the scrollsnapchange event it's

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

> Another alternative is to race the requests right? What are the downsides of that? This alternative has been mentioned in Intent to Prototype: No-Vary-Search Hint for Prefetch Speculation Rules . The downside is that sending

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

On Fri, Jun 7, 2024 at 12:18 PM Liviu Tinta wrote: > > Another alternative is to race the requests right? What are the > downsides of that? > This alternative has been mentioned in Intent to Prototype: > No-Vary-Search Hint for Prefetch Speculation Rules >

Re: [blink-dev] Intent to Ship: CSS ruby-align property

LGTM3 On Thu, Jun 6, 2024 at 9:28 PM Mike Taylor wrote: > LGTM2 > On 6/7/24 1:39 AM, Chris Harrelson wrote: > > Sorry, make that "LGTM1" > > On Thu, Jun 6, 2024 at 9:39 AM chrishtr via Chromestatus < > admin+chris...@cr-status.appspotmail.com> wrote: > >> LGTM >> -- >> You received this message

[blink-dev] Intent to Ship: Attribution Reporting Feature: Aggregate Debug Reporting

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] Intent to Ship: Third-party Cookie Grace Period Opt-Out

Added to the explainer. Thanks for calling that out. On Tue, Jun 4, 2024 at 6:39 PM Caleb Raitto wrote: > Thanks! I was mixing up the grace period and the deprecation trial. > > For the second part -- thanks for the context -- could you add some of > that context to the explainer? > > Thanks, >