A rather geeky/technical weblog, est. 2001, by Bramus
Interesting talk from “Chromium University 2020”, digging into Chrome’s Rendering Pipeline. A tour of the internals of Chromium’s rendering architecture, tracing the steps in the pipeline from web content to display pixels. Concretizes high-level concepts with pointers to important classes and data structures in the codebase While the main concepts — such as a Main …
RenderingNG is a re-architecture of the entire rendering pipeline of Chrome, for greatly improved reliability, scalability and extensibility. Listen in to find out how it works and why it makes the web better. Thanks to these advancements we get better rendering of tables, container queries support, features like Scroll-Linked Animations, etc. Related: RenderingNG — Ready …
Continue reading “RenderingNG: The next-generation rendering architecture for Chrome”
Digging deeper into Chromium’s RenderingNG architecture, this post explains its key data structures: Frame trees, The immutable fragment tree, Property trees, Display lists and paint chunks, and Compositor frames. Let’s dig into the key data structures that are inputs and outputs to the rendering pipeline. Would love to see this as a talk at a …
Continue reading “Key data structures and their roles in RenderingNG”
In the post on TablesNG, we looked at some of the features this under-the-hood rewrite for tables in Chromium provides us. But that’s only the tip of the iceberg, as the Chromium team have also been working on a whole new rendering engine architecture, named RenderingNG. In 2021, we will largely complete the process of …
Continue reading “RenderingNG — Ready for the next generation of web content”
content-visibility: the new CSS property that boosts your rendering performance
Coming to Chromium 85 is content-visibility (part of Display Locking): content-visibility enables the user agent to skip an element’s rendering work, including layout and painting, until it is needed. Because rendering is skipped, if a large portion of your content is off-screen, leveraging the content-visibility property makes the initial user load much faster. It also …
Continue reading “content-visibility: the new CSS property that boosts your rendering performance”
BlinkMacSystemFont: A Workaround
UPDATE 2020-04-28: Good news everyone! A workaround for this bug has landed in Canary (Chromium 84) and will be merged into the M83 release! The workaround described here still applies for Chromium 81. The problem As detailed before there’s this bug that shipped with Chromium 81 which somehow prevents the font-weight CSS property from being …
Continue reading “Chrome vs. BlinkMacSystemFont: A Workaround”
BlinkMacSystemFont: when bold is not bold
The folks at Igalia has been recently working on the implementation of CSS Containment in Chromium – which already shipped in Chrome 52, back in 2016 – by providing some fixes and optimizations based on the standard. Their post forms a nice intro on the subject: The main goal of CSS Containment standard is to …
Insightful post by the folks over at LogRocket on the rendering pipeline: If your site takes forever to load, chances are your users aren’t gonna wait for it to finish, even if there’s valuable content to be found there. Some studies have shown that up to 50% of users leave a page after 3 seconds …
Continue reading “How CSS works: Parsing and painting CSS in the critical rendering path”
Talk by Jake Archibald, as brought at JSConf.Asia 2018, taking a close look into the browser’s Event Loop: This talk looks at the browser’s event loop, the thing that orchestrates the main thread of the browser, which includes JavaScript, events, and rendering. We’ll look at the difference between tasks, microtasks, requestAnimationFrame, requestIdleCallback, and where events …
Continue reading “Jake Archibald: “In The Loop” — Taking a close look into the browser’s Event Loop”