回流和重新粉刷有什么区别？

This posting seems to cover the reflow vs repaint performance issues

http://www.stubbornella.org/content/2009/03/27/reflows-repaints-css-performance-making-your-javascript-slow/

As for definitions, from that post:

A repaint occurs when changes are made to an elements skin that changes visibly, but do not affect its layout.

Examples of this include outline, visibility, background, or color. According to Opera, repaint is expensive because the browser must verify the visibility of all other nodes in the DOM tree.

A reflow is even more critical to performance because it involves changes that affect the layout of a portion of the page (or the whole page).

Examples that cause reflows include: adding or removing content, explicitly or implicitly changing width, height, font-family, font-size and more.

Learn which css-properties effect repaint and review at http://csstriggers.com

In my opinion, repaint just affects the DOM itself, but reflow affects the whole page.

Repaint occurs when some changes which only its skin styles, such as color and visibility.

Reflow occur when the page of DOM changes its layout.

Recently I found a site can search which attribute will trigger repaint or reflow. http://csstriggers.com/

Here is another great post: http://blog.letitialew.com/post/30425074101/repaints-and-reflows-manipulating-the-dom

A repaint, or redraw, goes through all the elements and determines their visibility, color, outline and other visual style properties, then it updates the relevant parts of the screen.

A reflow computes the layout of the page. A reflow on an element recomputes the dimensions and position of the element, and it also triggers further reflows on that element’s children, ancestors and elements that appear after it in the DOM. Then it calls a final repaint. Reflowing is very expensive.

It also introduced when reflow occurs and how to minimize reflow.

Reflow happens when there is a change to the DOM layout. Reflow is very expensive computationally as dimensions and positions of page elements must be calculated again, then the screen will be repainted.

Example of something that will cause reflow

for (let i = 1; i <= 100; i++ {
const newEle = document.createElement('p');
newEle.textContent = 'newly created paragraph element';


document.body.appendChild(newEle);
}

The above code is very inefficient, causing 100 reflow processes for every new paragraph element appended.

You can mitigate this computationally stressful process by using .createDocumentFragment()

const docFrag = document.createDocumentFragment();


for (let i = 1; i <= 100; i++ {
const newEle = document.createElement('p');
newEle.textContent = 'newly created paragraph element';


docFrag.appendChild(newEle);
}


document.body.appendChild(docFrag);

The above code will now instead only use the reflow process 1x for the creation of 100 new paragraph elements.

Repaint is merely the changing of pixels on the monitor, while still taxing it is the lesser of two evils, since a reflow includes a repaint in its procedure.

Great explanation that I found here.

• Reflow: compute the layout of each visible element (position and size).
• Repaint: renders the pixels to screen.