[question]: DatePicker crashes with "Cannot read properties of null (reading 'scrollTop')" about mui-x HOT 4 CLOSED

Alright, no worries 👍

Seems like the issue disappeared after doing the following:

• Upgrading to React 18.2.0
• Moving LocalizationProvider to just be defined once at the app root, instead of separately for each date picker

Soo a bit of a mystery this one still 😄 but I suspect that the fix here was the upgrade to React 18, rather than the LocalizationProvider change.

from mui-x.

Hello @juiceo
This seems like a very strange issue.
Are you able to replicate it in codesanbox or using a plain repository?

• Could you expand more about the environment you are using?
  What build/development (e.g. webpack, vite, or something else) environment are you using?
• Does it happen on development build, production build, or both?
• Maybe your modules got corrupted in some way. Have you tried deleting node_modules and re-installing or also removing the lock file and downloading all fresh packages to test if the issue is not related to your particular installation edge cases? 🤔

from mui-x.

Hi @LukasTy - thanks for the suggestions! So:

• We are using Vite (4.4.11) as our build tool
• The issue happens both in development as well as in our production builds
• Probably not a case of node_modules being corrupted, as the issue persists in our production builds where we always install them from scratch.

I don't think I have time now to make a clean reproduction of the issue (tbh not sure how to reproduce it even 😄), but I'll keep digging around our repo to try and find some clues.

Any other suggestions? Maybe particular MUI versions that could be tried?

from mui-x.

Hi @juiceo
I've tried replicating your problem locally using vite, but couldn't reproduce any issue. 😞
I'm sorry, but until you can provide a reproduction example, I'm not sure we can be of more help.

P.S. I've tried React v18 and v17 and dev and production builds. 🤔

from mui-x.