-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: Failed to execute 'observe' on 'ResizeObserver': parameter 1 is not of type 'Element'. #549
Comments
@bughishor Thanks for reporting this. Could you also post:
|
I can confirm two things:
Getting stack trace, will add in separate comment. |
Stack trace:
|
Sidebar, thank you for looking at this on a Saturday, much appreciated! ❤️ |
Thanks but I still miss example code causing this error. |
Apologies, I missed that request. I've created a repo, where you can see it happen live, here. Relevant snippets:
|
thank you very much |
Hi, I have the same error after upgrading my codesandbox, see https://codesandbox.io/s/react-playground-znh66 . Hope it can help! |
Thanks @Romcol |
it seems to only work if you wrap the component with |
thanks @moussaab-moulim |
@bughishor @zkwentz @Romcol @moussaab-moulim @guiaramos @pecoram @rares-lupascu @thinkdomake @Alex-TLA @jefyelin @glarivie Could you confirm that it's fixed now (in 1.19.14)? |
it works for me |
@piotr-s-brainhub I had this issue as well and upgraded to 1.19.14 but the issue is still there :/ |
@KishokanthJeganathan could you post:
|
I had the same issue using Fluent UI framework. Update:
That happens when I tried to render something like
|
Here's what I'm getting:
Error started appearing in any version after 1.18.8. The stack trace above is from 1.19.16. |
thanks but could you also post the entire file causing this error? |
Can confirm. |
Works for me in 1.19.22 |
@piotr-s-brainhub sure! I'm importing into next as follows:
and then the actual carousel component looks like:
Still getting the same error on 1.19.22. |
@rodriguezmarting I prepared a fix which should fix the problem with divs which you have described. I'll let you know when it will be available to download via npm |
@pdugan20 does v1.19.24 work for you? |
@RobertHebel yeah! looks like it's working again. thanks for your help! what ended up being the root cause? |
@pdugan20 This code has caused the problem const getChildren = () => React.cloneElement(children, { ref: childrenRef }); It has cloned element when childrenRef had null value after changing this code to const getChildren = () =>
childrenRef.current
? React.cloneElement(children, { ref: childrenRef })
: children; it works |
Getting this TypeError when trying to use a React component as a slide
My carousel code:
<Carousel> <SponsorBox title="Sponsor1" image={sponsor1} /> </Carousel>
My React component:
const SponsorBox = ({ title, image }) => { return ( <div className="box-wrapper"> <Box> <Heading tag="h4">{title}</Heading> <Image src={image} /> </Box> </div> ) }
Environment
System:
OS: Windows 10 10.0.17763
CPU: (4) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 4.15 GB / 15.86 GB
Binaries:
Node: 12.17.0 - C:\Program Files\nodejs\node.EXE
npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.17763.831.0
Internet Explorer: 11.0.17763.771
npmPackages:
@brainhubeu/react-carousel: ^1.18.10 => 1.18.10
@fortawesome/fontawesome-svg-core: ^1.2.28 => 1.2.28
@fortawesome/free-brands-svg-icons: ^5.13.0 => 5.13.0
@fortawesome/free-solid-svg-icons: ^5.13.0 => 5.13.0
@fortawesome/react-fontawesome: ^0.1.11 => 0.1.11
bloomer: ^0.6.5 => 0.6.5
bulma: ^0.9.0 => 0.9.0
gatsby: ^2.22.15 => 2.22.15
gatsby-image: ^2.4.5 => 2.4.5
gatsby-plugin-manifest: ^2.4.9 => 2.4.9
gatsby-plugin-offline: ^3.2.7 => 3.2.7
gatsby-plugin-react-helmet: ^3.3.2 => 3.3.2
gatsby-plugin-sass: ^2.3.4 => 2.3.4
gatsby-plugin-sass-resources: ^2.0.0 => 2.0.0
gatsby-plugin-sharp: ^2.6.9 => 2.6.9
gatsby-source-filesystem: ^2.3.8 => 2.3.8
gatsby-transformer-sharp: ^2.5.3 => 2.5.3
node-sass: ^4.14.1 => 4.14.1
prettier: 2.0.5 => 2.0.5
prop-types: ^15.7.2 => 15.7.2
react: ^16.12.0 => 16.13.1
react-bulma-components: ^3.3.0 => 3.3.0
react-dom: ^16.12.0 => 16.13.1
react-helmet: ^6.0.0 => 6.0.0
All browsers/devices
The text was updated successfully, but these errors were encountered: