Tag Archives: Composited Render Layer Borders
The newest (or freshest, whichever way you say it) builds of Chromium are now coming with two new experimental features that previously required command line flags. By going to “about:flags” in the Omnibox, you can see there is now an “FPS counter” and “Focus on existing tab on open” in the list of options that you can turn on.
The FPS counter will allow you to gauge how well hardware acceleration when it is on by showing you the frames per second. Looking at some of the technical documents on the Chromium site suggests that this is to be used with composited render layer borders. If one of our esteemed developers/readers can tell us how to use it in the comments, that would be appreciated. Thanks for your feedback in advance.
The focus existing tab is a useful feature when you have a ton of tabs open. I have this problem all the time. Instead of Chromium opening a page, if you already have it loaded in a tab it will instantly switch to that tab. This one’s a keeper, at least for me, so hopefully it will be added to Chrome at some point.
The newest builds of Chromium feature a Chrome Experiment via “about:flags” that I have not seen before: composited render layer borders. When I first looked at this, I assumed it must have something to do with the increased use of graphical capabilities being added into Chrome, and I was right.
According to the Chromium documentation regarding WebKit rendering basics, a RenderObject is associated with a RenderLayer. The purpose of these layers is to allow content to overlap each other as they are composited. The problem, however, is that oftentimes these layers are either semi-transparent or not visible at all.