Skip to content

Commit e253c66

Browse files
authored
Update README.md
1 parent 1cc2d19 commit e253c66

File tree

1 file changed

+3
-8
lines changed

1 file changed

+3
-8
lines changed

README.md

+3-8
Original file line numberDiff line numberDiff line change
@@ -90,14 +90,9 @@ Or you could develop with a local HTTP server [like `serve`](https://www.npmjs.c
9090

9191
### Does "Highlight Updates" trace renders?
9292

93-
Yes, but it's also tracing if a component *may* render.
94-
In order to fully understand what counts as an "update", you need to understand how [shouldComponentUpdate](https://facebook.github.io/react/docs/advanced-performance.html#shouldcomponentupdate-in-action) works.
95-
![](https://facebook.github.io/react/img/docs/should-component-update.png)
96-
97-
Here "Highlight Updates" will draw a border around every node but C4 and C5.
98-
Why does it trace components that don't actually update? (via shouldComponentUpdate() -> false)
99-
This is a limitation of the system used to track updates, and will hopefully change in the future. It doesn't, however, trace the children of components that opt out, as there's no possibility of them updating.
100-
The higher the rate of updates happening per second the more the color changes from blue to red.
93+
With React 15 and earlier, "Highlight Updates" had false positives and highlighted more components than were actually re-rendering.
94+
95+
Since React 16, it correctly highlights only components that were re-rendered.
10196

10297
## Contributing
10398

0 commit comments

Comments
 (0)