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.13.5
What package has an issue?
@mantine/core
What framework do you use?
Vite
In which browsers you can reproduce the issue?
All
Describe the bug
There seems to be an issue with the top property, it is not converted to rem in CSS, other position property bottom, left, right) are converted to rem successfully but top is in px
You can see in the codesandbox by inspecting the Box element from Devtools
If possible, include a link to a codesandbox with a minimal reproduction
It doesn't look like a bug. The code is written in such a way that for 0 value it uses rem for rest if no measurement type specified then it takes px as default type.
If this needs to be fixed then possible fix would be to modify condition check in px.ts file.
I don't think the default behavior is px unit in Mantine library ! As mentionned in the docs here all units are converted into rem
And as you can see in the Codesanbox provided before and the screen uploaded for 0 values or a any random value the top property is not converted to rem compared to other properties like bottom
Dependencies check up
What version of @mantine/* packages do you have in package.json?
7.13.5
What package has an issue?
@mantine/core
What framework do you use?
Vite
In which browsers you can reproduce the issue?
All
Describe the bug
There seems to be an issue with the
top
property, it is not converted torem
in CSS, other position property bottom, left, right) are converted to rem successfully but top is in pxYou can see in the codesandbox by inspecting the Box element from Devtools
If possible, include a link to a codesandbox with a minimal reproduction
https://codesandbox.io/p/sandbox/mantine-react-template-forked-v38dwq?file=%2Fsrc%2FApp.tsx%3A14%2C1
Possible fix
No response
Self-service
The text was updated successfully, but these errors were encountered: