Calender content is overlapped with previous content after changing the year value to 1800 in single date picker

web-ridge / react-native-paper-dates

Smooth and fast cross platform Material Design date and time picker for React Native Paper

https://www.reactnativepaperdates.com

MIT License

640 stars 164 forks source link

Calender content is overlapped with previous content after changing the year value to 1800 in single date picker #285

Closed DZ-37 closed 1 year ago

DZ-37 commented 1 year ago

Current behaviour

i am facing currently following issues in single date picker on Android platform

issue1 :

i have selected year value as 1800 in single date picker from the dropdown menu which results into calender text getting overlapped with previous text. i have also attached screenshots for reference

issue2:

select year as 2100 from single date picker
the calender content is disappered

Your Environment

software	version

| android | 10 | react-native | 0.71.7 | react-native-paper | 5.7.2 | node | v14.21.2 | npm or yarn | 6.14.17 | expo sdk | 48.0.11

github-actions[bot] commented 1 year ago

Hey! Thanks for opening the issue. Can you provide a minimal repro which demonstrates the issue? Posting a snippet of your code in the issue is useful, but it's not usually straightforward to run. A repro will help us debug the issue faster. Please try to keep the repro as small as possible. The easiest way to provide a repro is on snack.expo.dev. If it's not possible to repro it on snack.expo.dev, then you can also provide the repro in a GitHub repository.

DZ-37 commented 1 year ago

The Bug that i have reported above is occuring on Android. But running this snack on Android does not work here as i always get ''Can't find variable: Intl" error. But one can try running it on iOS which works. You can click below link to run it in snack expo dev

repro

steps to reproduce 1st bug
- select year as 1800 from the year menu as given in the screenshot below and then you can find the bug already.
steps to reproduce 2nd bug
- select year value 2200 from the year menu and then you will be able to see the bug as given below in the screenshot

github-actions[bot] commented 1 year ago

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.