Ask and vote for your questions in the moderator at http://goo.gl/VjjIy
Blink and WebKit use a compositor to display web contents to the user's screen. But how do we take a render tree (the browser's internal representation of a web page) and display it using a compositor? How do we decide what content should have a separate compositing layer, and how does compositing benefit us?
In this Google Developers Live session, Chrome software engineer Shawn Singh will introduce basic concepts of compositing, and then we will focus on how Blink bridges the gap between the render tree and the compositor. This is only a slice of the overall rendering architecture, but it will be fun and insightful for any web developers and browser developers with an interest in how Blink and WebKit render web pages.