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
In my code with css-in-js approach, if I want to use some risky props like gap with flex elements, I use workaround like this one
With css I use flex-gap-polyfill package as postcss plugin.
I very like your ui-library, but this is very strange to drop users who uses iPhone 11 with the iOS 13.x.
It is possible to add similar workaround like from the example above, or to add a way to pass a function-wrapper (for example in MantineProvider, which be used in similar way under the hood?
Any other ideas?)
In which browser did the problem occur
All
If possible, please include a link to a codesandbox with the reproduced problem
No response
Do you know how to fix the issue
No response
Are you willing to participate in fixing this issue and create a pull request with the fix
No response
Possible fix
No response
The text was updated successfully, but these errors were encountered:
Flexbox gap support is good enough for me, I do not think that I can provide any polyfills on my side, you should look for stylis plugins if you need to support old browsers.
What package has an issue
@mantine/core
Describe the bug
In my code with
css-in-js
approach, if I want to use some risky props likegap
with flex elements, I use workaround like this oneWith css I use
flex-gap-polyfill
package as postcss plugin.I very like your ui-library, but this is very strange to drop users who uses iPhone 11 with the iOS 13.x.
It is possible to add similar workaround like from the example above, or to add a way to pass a function-wrapper (for example in MantineProvider, which be used in similar way under the hood?
Any other ideas?)
In which browser did the problem occur
All
If possible, please include a link to a codesandbox with the reproduced problem
No response
Do you know how to fix the issue
No response
Are you willing to participate in fixing this issue and create a pull request with the fix
No response
Possible fix
No response
The text was updated successfully, but these errors were encountered: