[Box] chrome 88: Failed to execute 'px' on 'CSS': The provided double value is non-finite.
See original GitHub issue- The issue is present in the latest release.
- I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
Setting undefined
value to the margin, padding,… props of a Box
component would throw the following exception. This issue only is reproducible on chrome 88.
Failed to execute 'px' on 'CSS': The provided double value is non-finite.
Expected Behavior 🤔
Should ignore undefined
value for props.
Steps to Reproduce 🕹
https://codesandbox.io/s/box-issue-with-undefined-forked-hxp13
<Box m={undefined} />
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Failed to execute 'px' on 'CSS': The provided double value is ...
Setting undefined value to the margin, padding,... props of a Box component would throw the following exception. This issue only is reproducible ...
Read more >"The provided double value is non-finite" error when ...
Failed to execute 'elementsFromPoint' on 'Document': The provided double value is non-finite ...implies that the WebDriver instance was ...
Read more >Safari Technology Preview Release Notes - Apple Developer
Safari Technology Preview Release 147 is now available for download for macOS Monterey 12.3 or later and macOS Ventura beta. Updates to Safari...
Read more >Compose UI - Android Developers
In UI tests using a Compose rule, continuations resumed during withFrameNanos callbacks will not be dispatched until after all frame callbacks have finished ......
Read more >Diff - 94ca2b10d8..f39a1b8992 - chromium/src - Git at Google
Otherwise, nested calls might fail due to the shared FieldTrialList ... Value* values) { - // DeviceLocalAccount policies are not available for not ......
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
The issue with the Box is fixed in #24527. It will be released soon or later. Regarding the other cases, make sure you are not providing
NaN
as a CSS value. please continue the discussion on https://github.com/cssinjs/jss/issues/1445 (the best place to fix the root cause)If you find a place where the NaN is generated from Material-UI, and you have a reproduction to prove it like it was the case with the Box in this issue (#24519), please open a new issue.
I don’t know if this is related but we are experiencing something similar with users that upgraded to Chrome 88.
This issue for us seems to be related
<Dialog />
https://material-ui.com/api/dialog/