- From: Corey Worrell via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Feb 2021 23:23:23 +0000
- To: public-css-archive@w3.org
@emilio I don't know too much about the actual rendering processes, but [this description](https://developers.google.com/web/fundamentals/performance/critical-rendering-path/render-tree-construction) makes it seem like it would be easier to calculate as there wouldn't need to be any tree traversal to compute, there would just be the one root node to be concerned with. But I understand there has to be more to it. > Up to this point we've calculated which nodes should be visible and their computed styles, but we have not calculated their exact position and size within the viewport of the device---that's the "layout" stage, also known as "reflow." > > To figure out the exact size and position of each object on the page, the browser begins at the root of the render tree and traverses it. > > The body of the above page contains two nested div's: the first (parent) div sets the display size of the node to 50% of the viewport width, and the second div---contained by the parent---sets its width to be 50% of its parent; that is, 25% of the viewport width. Very confusing as their use of "viewport width" isn't the same as the `vw` unit, which you would reasonably assume. -- GitHub Notification of comment by coreyworrell Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6026#issuecomment-786946834 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 26 February 2021 23:23:25 UTC