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?
Latest
What package has an issue?
@mantine/core
What framework do you use?
Next.js
In which browsers you can reproduce the issue?
Chrome
Describe the bug
In the PinInput component in RTL mode, the inputs should not be arranged from right to left as shown in the image.
If possible, include a link to a codesandbox with a minimal reproduction
No response
Possible fix
Since the input only accepts English letters and numbers, it should follow the LTR rule.
If the component is enhanced to support all characters from various languages worldwide, it should remain LTR and unchanged when type="number". In the normal (Alphanumeric) mode, it will be up to the developer to decide whether to switch to RTL or not.
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?
Latest
What package has an issue?
@mantine/core
What framework do you use?
Next.js
In which browsers you can reproduce the issue?
Chrome
Describe the bug
In the PinInput component in RTL mode, the inputs should not be arranged from right to left as shown in the image.
If possible, include a link to a codesandbox with a minimal reproduction
No response
Possible fix
Since the input only accepts English letters and numbers, it should follow the LTR rule.
If the component is enhanced to support all characters from various languages worldwide, it should remain LTR and unchanged when
type="number"
. In the normal (Alphanumeric) mode, it will be up to the developer to decide whether to switch to RTL or not.Self-service
The text was updated successfully, but these errors were encountered: