![]() ![]() On Mac and Linux only pages that need compositing for some of their content go down the accelerated path (see below for more on what would require compositing), but soon all pages will go down the accelerated path there, too. As of this writing all pages go down the hardware accelerated path on Windows, ChromeOS, and Chrome for Android. Web page layers software#It’s important to understand that Chrome has had two different rendering paths for a while now: the hardware-accelerated path and the older software path. This article attempts to cover only stuff that’s unlikely to change, but no guarantees that it’ll all still apply in six months. The web platform and standards don’t codify this level of implementation detail, so there are no guarantees anything in this article will apply to other browsers, but knowledge of internals can nevertheless be useful for advanced debugging and performance tuning.Īlso, note that this entire article is discussing a core piece of Chrome’s rendering architecture that’s changing very fast. This article covers implementation details of Chrome, not web platform features. We’re talking about WebKit here, and more specifically we’re talking about the Chromium port of WebKit. not Canvas2D or WebGL), what does that term really mean? This article explains the basic model that underpins hardware accelerated rendering of web content in Chrome. ![]() When talking about a normal web page (i.e. Modern browsers have changed the way rendering works in recent years to take advantage of graphics cards: this is often vaguely referred to as “hardware acceleration”. Rendering is the often obscure process of turning this representation of a page into a picture on the screen. For most web developers the fundamental model of a web page is the DOM. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |