From 74de9934bebfe2d8b3e034d4fa197ecfbf52a616 Mon Sep 17 00:00:00 2001 From: Dan Abramov Date: Wed, 13 Dec 2017 23:53:32 +0000 Subject: [PATCH] Avoid "tick" jargon in componentDidMount docs (#415) --- content/docs/reference-react-component.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/reference-react-component.md b/content/docs/reference-react-component.md index be8fbc29..86e0d468 100644 --- a/content/docs/reference-react-component.md +++ b/content/docs/reference-react-component.md @@ -188,7 +188,7 @@ componentDidMount() This method is a good place to set up any subscriptions. If you do that, don't forget to unsubscribe in `componentWillUnmount()`. -Calling `setState()` in this method will trigger an extra rendering, but it is guaranteed to flush during the same tick. This guarantees that even though the `render()` will be called twice in this case, the user won't see the intermediate state. Use this pattern with caution because it often causes performance issues. It can, however, be necessary for cases like modals and tooltips when you need to measure a DOM node before rendering something that depends on its size or position. +Calling `setState()` in this method will trigger an extra rendering, but it will happen before the browser updates the screen. This guarantees that even though the `render()` will be called twice in this case, the user won't see the intermediate state. Use this pattern with caution because it often causes performance issues. It can, however, be necessary for cases like modals and tooltips when you need to measure a DOM node before rendering something that depends on its size or position. * * *