You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified that I use latest version of all @mantine/* packages
What version of @mantine/* packages do you have in package.json?
7.7.0
What package has an issue?
@mantine/dropzone
What framework do you use?
Vite
In which browsers you can reproduce the issue?
Chrome
Describe the bug
I can't seem to activate the file picker by focusing on the dropzone component and pressing either space or enter. V6 works, so I believe the issue relates to some interaction with react-dropzone-esm which was introduced in V7. More specifically, rootRef seems to be null, so we never make it past this condition.
If possible, include a link to a codesandbox with a minimal reproduction
No response
Possible fix
If you remove ref from ...getRootProps({ ref }), on this line, then the keyboard activation works, but I'm not sure if that's the best solution? I think also ...getRootProps is creating a prop called ref which if you try to access it, even just looking at it via dev tools, you get the special props warning.
Self-service
I would be willing to implement a fix for this issue
The text was updated successfully, but these errors were encountered:
Dependencies check up
What version of @mantine/* packages do you have in package.json?
7.7.0
What package has an issue?
@mantine/dropzone
What framework do you use?
Vite
In which browsers you can reproduce the issue?
Chrome
Describe the bug
I can't seem to activate the file picker by focusing on the dropzone component and pressing either space or enter. V6 works, so I believe the issue relates to some interaction with
react-dropzone-esm
which was introduced in V7. More specifically,rootRef
seems to be null, so we never make it past this condition.If possible, include a link to a codesandbox with a minimal reproduction
No response
Possible fix
If you remove
ref
from...getRootProps({ ref }),
on this line, then the keyboard activation works, but I'm not sure if that's the best solution? I think also...getRootProps
is creating a prop calledref
which if you try to access it, even just looking at it via dev tools, you get the special props warning.Self-service
The text was updated successfully, but these errors were encountered: