mui.com documentation imploded "Cannot read properties of undefined (reading 'type')"
See original GitHub issueProbably reported to the wrong place, for that I apologize.
Duplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Current behavior 😯
https://mui.com/components/text-fields/#main-content implodes.
Expected behavior 🤔
It was working half an hour ago.
Steps to reproduce 🕹
Steps:
- Go to https://mui.com/components/text-fields/#main-content
- Wait until hydration begins.
- Observe error
Context 🔦
No response
Your environment 🌎
`Browser`
`Google Chrome Version 96.0.4664.45 (Official Build) (64-bit)``OS`
`Fedora 34 (Thirty Four) with kernel 5.14.18-200.fc34.x86_64 #1 SMP Fri Nov 12 16:48:10 UTC 2021`Issue Analytics
- State:
- Created 2 years ago
- Comments:21 (6 by maintainers)
Top Results From Across the Web
MUI 5 Cannot read properties of undefined (reading 'up ...
According to the docs: Using the theme context. Starting from v5, MUI no longer uses JSS as its default styling solution.
Read more >Troubleshooting - Material UI - MUI
This document covers known issues and common problems encountered when migrating from ... TypeError: Cannot read properties of undefined (reading 'pxToRem').
Read more >Autocomplete API - Material UI - MUI
Name Type Default
options * array
renderInput * func
autoComplete bool false
Read more >Licensing - MUI X
Error extracting license expiry timestamp. TypeError: Cannot read properties of null (reading '1') at verifyLicense. To solve the issue, you can update MUI...
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
datagrid version 5.17.8 still has the error steps to reproduce
as a result publishClick** event fired twice for both datagrids but second event can’t find column.
Any thoughts why event rowClick event fired twice for both datagrids?
Repro on Fedora 35 Workstation with Gnome 41 (default DE) up-to-date
Same as above, happens much more often on the data table pages then other pages of the documentation.
On Mon., Jan. 24, 2022, 12:32 a.m. Marija Najdova, @.***> wrote: