-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
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
Calendar 'modal' as overlapping components (when yearsDiff >= 100y.) #415
Comments
PRs are welcome! |
Do you have a clue about what's going on here ? |
Hey! Thanks for opening the issue. Can you provide more information about the issue? Please fill the issue template when opening the issue without deleting any section. We need all the information we can, to be able to help. Make sure to at least provide - Current behaviour, Expected behaviour, A way to reproduce the issue with minimal code (link to snack.expo.dev) or a repo on GitHub, and the information about your environment (such as the platform of the device, versions of all the packages etc.). |
I have the same issue. I think the following is the cause, but I don't know how to fix it. https://github.com/web-ridge/react-native-paper-dates/blob/master/src/Date/Month.tsx#L461 Modifying the |
Hello 👋, this issue has been open for more than a month without a repro or any activity. If the issue is still present in the latest version, please provide a repro or leave a comment within 7 days to keep it open, otherwise it will be closed automatically. If you found a solution or workaround for the issue, please comment here for others to find. If this issue is critical for you, please consider sending a pull request to fix it. |
Hey, we're experiencing this issue as well on iOS:
To reproduce simply select year 1920 for example. |
Current behavior
ANDROID && IOS
Using Single-Date mode in the calendar, if the picker date is 100 year under 'current-year' we get weird components overlapping.
Expected behavior
All dates should works properly.
How to reproduce?
Preview
1901-01-01 <> 1923-01-01 (1925-01-01 is OK)
What have you tried so far?
Your Environment
The text was updated successfully, but these errors were encountered: