How do you measure when a component is “ready”? ⏱️ LCP is too global; Element Timing is too specific. 🛠️ I’ve been working with Bloomberg on a new #webperf API: Container Timing. Think of it as “LCP for a web component”, providing aggregated paint timing for a subtree.

#Chromium embedders: imagine full extensions support, on your lightweight //content-only product. No more complex rebasings or //chrome hacks! Just clean APIs without chrome::Profile. Shin, from @igalia.com, has been working on this.

New blog post! ✍ "Maintaining Chromium downstream: how can upstream help?" 🔗 blogs.igalia.com/dape/2025/12... cc @igalia.com

BlinkOn 20 kicks off today at Google HQ, and Igalia is there! We’ll be on stage twice today, with @seaotta.dev co-presenting the opening keynote with Penelope MacLachlan, and @jdapena.bsky.social delivering a lightning talk about timing. And we’ll have even more tomorrow!

New blog post! blogs.igalia.com/dape/2025/03... trace-chrome is a command line tool I wrote to make it easy to capture a Chromium trace from a remote device. cc @igalia.com @chromium.social #webperf

Maintaining a downstream of #Chromium is complex. But, the bigger it is, the harder it is to maintain it. How to measure a downstream size? Why it gets big? This is the topic of my new post: blogs.igalia.com/dape/2025/02... cc @igalia.com @chromium.social

Container Timing has the potential to improve the capabilities offered by the web platform to content developers to understand the performance behaviour of a web or specific components. A new tool in the WebPerf toolbox!

Hey, there is a new blog post for people who are interested in pointer compression, isolate groups, and sandbox in V8. dbezhetskov.dev/multi-sandbo...

A colaboración entre Igalia e Galnus dá os seus primeiros froitos na cidade da Coruña, onde se acaba de chegar a un acordo co concello para prantar 3000 árbores na zona de Bens co obxectivo de crear un bosque urbano www.igalia.com/2024/12/20/C...

BlinkOn starts tomorrow! I will be hosting a breakout session about Linux #Chromium running in low memory devices, and delivering a lightning talk about the work I have been involved to improve the #V8 support for native stack walking profiling. See you at BlinkOn! cc @igalia.bsky.social

New blog post: "Maintaining Chromium downstream: upgrade strategies" blogs.igalia.com/dape/2024/09... Continuing the series, this post dives into a crucial aspect: keeping track of the upstream #Chromium repositories changes. cc @igalia.bsky.social

New blog post! Maintaining downstream #Chromium blogs.igalia.com/dape/2024/03... This time I write about why projects use Chromium, and why a downstream may be needed. This is the first post of a series about the challenges of maintaining a downstream of Chromium. cc @igalia.bsky.social

New blog post! V8 profiling instrumentation overhead blogs.igalia.com/dape/2023/11... When profiling Javascript CPU usage, JIT-compiled code needs instrumentation. Unfortunately, in V8 it is disabled by default because of its overhead. I ran benchmarks to measure that. cc @igalia.bsky.social

webOS OSE 2.24.0 is out! Main highlights from web stack side: It is now based on Chromium m108. And we now use LLVM Clang and libc++, instead of libstdc++ and GCC. That way we align better with upstream, far more tested with this toolchain. www.webosose.org/blog/2023/11...

New blog post! Though Chromium official toolchains for Linux are based on LLVM Clang and libc++, GNU toolchain is supported as a community effort. In the post I write about current status (working!). Thanks to all contributors! cc @igalia.bsky.social blogs.igalia.com/dape/2023/11...