![]() The components end up in various CPU processes, threads, and sub-components within those threads. #Favorite text compositor codeIn RenderingNG, these tasks are split logically across several stages and code components. A web page loaded in a browser tab has a top-level frame, child frames for each iframe included in the top-level document, and their recursive iframe descendants.Ī visual effect is a graphical operation applied to a bitmap, such as scroll, transform, clip, filter, opacity, or blend. External resources, such as images, video, fonts, and SVGĪ frame is an HTML document, plus its URL.And, a stream of raw input events from touch screens, mice, keyboards, and other hardware devices. The contents to render are a tree of frames for each browser tab, plus the browser UI. Route input efficiently to the right places so that developer scripts and other subsystems can respond.Animate visual effects on the contents from one state to another.Render contents into pixels on the screen.Starting at the highest level and drilling down from there, the tasks of rendering are: This post will explain how its component pieces are set up, and how the rendering pipeline flows through them. In a previous post, I gave an overview of the RenderingNG architecture goals and key properties. Check out the rest of the series to learn more about RenderingNG, key data structures, VideoNG, and LayoutNG. This post is a part of a series on the Chromium rendering engine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |