I've encountered a bug with the delay prop which would result in the placeholder showing indefinitely, with {ready: true} in props but {ready: false} in state.
I believe the events which lead to this are, when delay is set to n milliseconds, all of the following happen before n milliseconds is up:
ready prop is set to false, a timeout to set ready state is set and the ID stored in this.timeout
Some detail in props.children is changed, cause componentWillReceiveProps to be called again; this causes another timeout to set ready state to be created, and the ID stored in this.timeout is overwritten
ready prop is set to true, which sets state to {ready: true} and which also deletes the timeout set in step 2 (but, crucially, not the timeout set in step 1)
The timeout set in step 1 fires, setting state incorrectly back to {ready: false}
The pull request is one approach among many to fix this. You could also clear any existing timeout in this.timeout before setting a new one, or change the render method to
I've encountered a bug with the
delay
prop which would result in the placeholder showing indefinitely, with{ready: true}
in props but{ready: false}
in state.I believe the events which lead to this are, when delay is set to n milliseconds, all of the following happen before n milliseconds is up:
ready
prop is set to false, a timeout to setready
state is set and the ID stored inthis.timeout
props.children
is changed, causecomponentWillReceiveProps
to be called again; this causes another timeout to setready
state to be created, and the ID stored inthis.timeout
is overwrittenready
prop is set to true, which sets state to{ready: true}
and which also deletes the timeout set in step 2 (but, crucially, not the timeout set in step 1){ready: false}
The pull request is one approach among many to fix this. You could also clear any existing timeout in
this.timeout
before setting a new one, or change the render method toThanks!