Potential breaking change with 0.9.10
See original GitHub issueWe have some test failures around AnimateHeight.hideContent(height)
call in componentDidMount
.
TypeError: Cannot read property 'style' of null
at AnimateHeight.hideContent (node_modules/react-animate-height/lib/AnimateHeight.js:248:28)
at AnimateHeight.componentDidMount (node_modules/react-animate-height/lib/AnimateHeight.js:99:12)
at node_modules/react-test-renderer/lib/ReactCompositeComponent.js:264:25
at measureLifeCyclePerf (node_modules/react-test-renderer/lib/ReactCompositeComponent.js:75:12)
at node_modules/react-test-renderer/lib/ReactCompositeComponent.js:263:11
at CallbackQueue.notifyAll (node_modules/react-test-renderer/lib/CallbackQueue.js:76:22)
at ReactTestReconcileTransaction.close (node_modules/react-test-renderer/lib/ReactTestReconcileTransaction.js:36:26)
at ReactTestReconcileTransaction.closeAll (node_modules/react-test-renderer/lib/Transaction.js:209:25)
at ReactTestReconcileTransaction.perform (node_modules/react-test-renderer/lib/Transaction.js:156:16)
at batchedMountComponentIntoNode (node_modules/react-test-renderer/lib/ReactTestMount.js:69:27)
at ReactDefaultBatchingStrategyTransaction.perform (node_modules/react-test-renderer/lib/Transaction.js:143:20)
at Object.batchedUpdates (node_modules/react-test-renderer/lib/ReactDefaultBatchingStrategy.js:62:26)
at Object.batchedUpdates (node_modules/react-test-renderer/lib/ReactUpdates.js:97:27)
at Object.render [as create] (node_modules/react-test-renderer/lib/ReactTestMount.js:128:18)
Here’s a snippet of our current usage of AnimateHeight
<AnimateHeight
aria-labelledby={headingAriaId}
duration={300}
height={isActive ? 'auto' : 0}
id={regionAriaId}
role="region"
/>
It looks like hideContent()
and showContent
rely on style
to be present on the contentElement
, which may not always be there especially on mount in a headless test setting. Should there be some form wait until the DOM element has a style property before acting on it?
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Notice of Breaking Changes · Issue #2293 · nvim-treesitter ...
This issue is used to announce breaking changes (and possibly other critical info). ... Every breaking change is added as a new comment....
Read more >What exactly is considered a breaking change to a library crate?
A breaking change is commonly considered something that may break downstream crates (code the depends on the library in question). However, in ...
Read more >Changelog — drf-spectacular documentation - Read the Docs
Breaking changes / important additions: This is a y-stream release with a lot of bugfixes, some new features and potentially small schema changes...
Read more >An empirical investigation into problems caused by breaking ...
to productivity encountered during API evolution with breaking changes and to investigate to what extent these possible problems affect ...
Read more >Upgrading PyPlanet — PyPlanet 0.9.10 documentation
This way you will prevent sudden breaking changes that may occur in big new releases, ... It can be possible that we introduced...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Awesome, everything is green again. The only thing to potentially followup on is documenting the need to polyfill
requestAnimationFrame
. Thank you for your help.To answer your question, we’re using
react-animate-height
in out company’s style guide. Your component has been a great help!The frustrating thing is that this only affects any project feeding this component into the
react-test-renderer
. Admittedly I can’t think of much better at the moment, though I’m starting to think we don’t need to modifyshowContent()
orhideConent()
. Since this only seems to affect the renderer during the mounting process we might be able to get away with the check being only incomponentDidMount()
. Let me give that a shot locally and report back.