The Fight Against Layout Jank

The completion of web page rendering does not mean that its layout is fixed. The loading of a media resource (such as an image) may cause the layout to change due to its size, and in streaming layouts, the image size is usually determined only after rendering. This can also be caused by font loading and rearrangement layout, or XHR requests will bring more content to the page. We've been trying to prevent layout jitters - that's what I call layout janks. It's annoying and no one likes it. At the best case, it will make you lose your position when reading; at the worst case, you may click on something you don't want to click on at all.

While trying to understand the new layout instability API and discuss it with friends, Eric Portis gave some very insightful points. Basically, layout jitter is a problem and is working on solving it in many ways:

• Solve the problem from the content/creation level: we now have intrinsicsize as HTML attribute and aspect-ratio as CSS attribute. Both are designed to solve this problem, although they don't have good browser support yet and require a DIY aspect ratio box instead. Also, the same is true for the idea of ​​changing UA stylesheets to expand aspect-ratio effectiveness.
• Solve the problem from the browser behavior level: scroll anchoring is also designed to solve this problem. It is now enabled by default is a big step forward. If you need it, you can still control it via CSS (via overflow-anchor ).
• Measuring Problems and Causes: The Layout Instability API is designed for this and it can be used to enable tools to monitor it.

The above is the detailed content of The Fight Against Layout Jank. For more information, please follow other related articles on the PHP Chinese website!