This is the start of rendering a skeleton in a ::skeleton pseudo tree that we've talked about.
There are a lot of details to figure out. Now, the ::skeleton is rendered under the LayoutView at the same time as the rest of the document.
I move a skeleton document fully using an <html> root element under the ::skeleton pseudo. The question is if the author creating a skeleton should expect that an authored skeleton document should render exactly as if it was rendered standalone. If so, we need to make the ::skeleton <html> root behave as a document root with selector matching, propagation of overflow to viewport, etc.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
"skeleton.cc",Should we have a couple of smoke tests?
Member<Skeleton> skeleton_;The fact that there's a single skeleton but a HashSet of URLs surprises me. I can see that the implementation is to basically just fetch the skeleton as soon as we have a navigation (which I assume just races the two fetches). I would've pictured this more like a prefetch eventually where we have a URL->skeleton type of map that is opportunistically populated
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |