Fix horizontal scrolling in docs (#9613)
Dan Abramov committed
May 5, 2017 at 18:03 UTC
6facb85f853365125b10e9f0843d013184f88d2e
1 file changed
+2
-2
docs/docs/optimizing-performance.md
+2
-2
@@ -164,7 +164,7 @@ Remember that you only need to do this for production builds. You shouldn't appl
164
165
In the **development** mode, you can visualize how components mount, update, and unmount, using the performance tools in supported browsers. For example:
166
167
-<center><img src="/react/img/blog/react-perf-chrome-timeline.png" width="651" height="228" alt="React components in Chrome timeline" /></center>
167
+<center><img src="/react/img/blog/react-perf-chrome-timeline.png" style="max-width:100%" alt="React components in Chrome timeline" /></center>
168
169
To do this in Chrome:
170
@@ -203,7 +203,7 @@ If you know that in some situations your component doesn't need to update, you c
203
204
Here's a subtree of components. For each one, `SCU` indicates what `shouldComponentUpdate` returned, and `vDOMEq` indicates whether the rendered React elements were equivalent. Finally, the circle's color indicates whether the component had to be reconciled or not.
205
206
-<figure><img src="/react/img/docs/should-component-update.png" /></figure>
206
+<figure><img src="/react/img/docs/should-component-update.png" style="max-width:100%" /></figure>
207
208
Since `shouldComponentUpdate` returned `false` for the subtree rooted at C2, React did not attempt to render C2, and thus didn't even have to invoke `shouldComponentUpdate` on C4 and C5.
209