Re: [blink-dev] What are "Update layers", "Update layer trees" and "Composite layers" in Chrome devtools

The confusion may be this: mousemove events are always dispatched at the beginning of a rendering update, that's why it looks like the Composite Layers item is associated with the mousemove event. Click events are dispatched separately from rendering updates. I would guess there are Composite

Re: [blink-dev] Intent to Implement and Ship: WebCodecs dequeue event

LGTM1, seems like a simple and useful addition! On Fri, 5 Aug 2022 at 22:38 Chris Cunningham wrote: > Contact emailschcunning...@chromium.org > > Explainerhttps://github.com/w3c/webcodecs/blob/main/explainer.md > > Specificationhttps://w3c.github.io/webcodecs > > Summary > > This feature tracks

Re: [blink-dev] What are "Update layers", "Update layer trees" and "Composite layers" in Chrome devtools

On Fri, Aug 5, 2022 at 12:41 PM Maxim Vaarwel wrote: > Hello, Stefan Zagar. Could you explain then to me one thing? If dev-tools > shows bars named as Composite Layers every time when we use display's > hardware. Then why don't I see them when I hold my mouse pointer on one > point and do

Re: [blink-dev] What are "Update layers", "Update layer trees" and "Composite layers" in Chrome devtools

Hello, Stefan Zagar. Could you explain then to me one thing? If dev-tools shows bars named as Composite Layers every time when we use display's hardware. Then why don't I see them when I hold my mouse pointer on one point and do clicks? Also why I don't see Composite Layers bars when I do

[blink-dev] Intent to Implement and Ship: WebCodecs dequeue event

Contact emailschcunning...@chromium.org Explainerhttps://github.com/w3c/webcodecs/blob/main/explainer.md Specificationhttps://w3c.github.io/webcodecs Summary This feature tracks adding a single event named "dequeue" and event handler to the audio and video encoder and decoder interfaces (e.g.

[blink-dev] Re: Ready for Trial: Quick intensive timer throttling of loaded background pages

+Scott Haseley as an expert in this field. We would like to start experimenting with this intervention on 1% Stable very soon. We've been experimenting on 50% of Beta for almost 2 months. The results are encouraging and we aren't aware of negative Web developer feedback. Do we need your LGTM to

Re: [blink-dev] Intent to Experiment: Align Timers (including DOM timers) at 125 Hz

On Fri, Aug 5, 2022 at 11:00 AM Dave Tapuska wrote: > Stefan, this was just for "non-zero delay" timers? Are there still > potential issues there? > Ah, sorry, I missed that detail. In that case, I think none of my objections apply. > > On Fri, Aug 5, 2022 at 1:19 PM Stefan Zager wrote: > >>

Re: [blink-dev] Intent to Experiment: Align Timers (including DOM timers) at 125 Hz

Stefan, this was just for "non-zero delay" timers? Are there still potential issues there? On Fri, Aug 5, 2022 at 1:19 PM Stefan Zager wrote: > This is a common programming pattern: > > requestAnimationFrame(() => { > setTimeout(() => { > // At this point, it's very likely that layout is

Re: [blink-dev] What are "Update layers", "Update layer trees" and "Composite layers" in Chrome devtools

On Fri, Aug 5, 2022 at 10:05 AM Maxim Vaarwel wrote: > Nowadays rendering chrome engine has been changed. > > For demonstrating new confusion moment: > 1. Open a blank tab > 2. Open dev-tools, next open Perfomance tab and run a recording performance > 3. In process of the recording performance

Re: [blink-dev] Intent to Experiment: Align Timers (including DOM timers) at 125 Hz

This is a common programming pattern: requestAnimationFrame(() => { setTimeout(() => { // At this point, it's very likely that layout is clean, // because we *just* completed a rendering update. // Queries of layout information are very unlikely to // trigger a forced layout.

Re: [chromium-dev] Re: [blink-dev] Inactive OWNERS cleanup

Hi folks, A fair bit of the feedback on Kentaro's proposal has focused on improving Owners suggestions and better handling OOO Owners. We do believe there's a lot of room to improve owners suggestions to help improve review time. OOO is one aspect, but you could also imagine such a system taking

Re: [blink-dev] What are "Update layers", "Update layer trees" and "Composite layers" in Chrome devtools

Nowadays rendering chrome engine has been changed. For demonstrating new confusion moment: 1. Open a blank tab 2. Open dev-tools, next open Perfomance tab and run a recording performance 3. In process of the recording performance just doing moves by mouse on the blank page during 3sec or less

Re: [blink-dev] Intent to Ship: CSS 'ic' Length Unit

LGTM On Fri, Aug 5, 2022 at 10:27 AM Daniel Bratell wrote: > LGTM3 > > /Daniel > On 2022-08-05 07:47, Yoav Weiss wrote: > > LGTM2 > > On Fri, Aug 5, 2022 at 12:08 AM slightlyoff via Chromestatus < > admin+slightly...@cr-status.appspotmail.com> wrote: > >> LGTM1 >> -- >> You received this

[blink-dev] PSA: Chrome will start ignoring touch-action changes at pointerdown, again!

Summary: Chrome will soon ignore any changes to touch-action done at a pointerdown event handler until the end of current touch-gesture, fully matching the spec and other major browsers again. Details crbug.com/1314739 The PointerEvents spec requires the browser to ignore any changes

Re: [blink-dev] Intent to Ship: CSS 'ic' Length Unit

LGTM3 /Daniel On 2022-08-05 07:47, Yoav Weiss wrote: LGTM2 On Fri, Aug 5, 2022 at 12:08 AM slightlyoff via Chromestatus > wrote: LGTM1 -- You received this message because you are subscribed to the Google Groups