We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Material UI components in next/link break next in the latest canary builds
Steps to reproduce the behavior, please provide code snippets or a repository:
<Link>
A code sandbox of the bug is available here: https://codesandbox.io/s/ll0qmmm0ql
You should be able to use Material UI component as the first child in a Link just as before (i.e. as was possible in next@8)
You can use a standard HTML element such as <div> (or another valid child such as <>) to wrap the Material UI child and the bug is subverted.
<div>
<>
I think the bug was introduced by #7196 in canary-20.
The bug doesn't exist in canary-19 (after downgrading, using a material UI component as the first child works fine)
The error thrown in next build is
next build
Failed to execute 'observe' on 'IntersectionObserver': parameter 1 is not of type 'Element'
The text was updated successfully, but these errors were encountered:
Material-UI v3 components don't forward the ref to the DOM node. They do in v4.
Sorry, something went wrong.
ijjk
Successfully merging a pull request may close this issue.
Bug report
Describe the bug
Material UI components in next/link break next in the latest canary builds
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
<Link>
A code sandbox of the bug is available here: https://codesandbox.io/s/ll0qmmm0ql
Expected behavior
You should be able to use Material UI component as the first child in a Link just as before (i.e. as was possible in next@8)
Screenshots
System information
Additional context
You can use a standard HTML element such as
<div>
(or another valid child such as<>
) to wrap the Material UI child and the bug is subverted.I think the bug was introduced by #7196 in canary-20.
The bug doesn't exist in canary-19 (after downgrading, using a material UI component as the first child works fine)
The error thrown in
next build
isThe text was updated successfully, but these errors were encountered: