Skip to content
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

Does not handle PreserveOnRefresh - wrong date range set after refresh #42

Open
jusjoken opened this issue Jan 28, 2023 · 0 comments
Open

Comments

@jusjoken
Copy link

First off.. great component. I use it throughout my app and works impressive except for this issue.

I would like to be able to use @PreserveOnRefresh in my Vaadin application as well as this component, however when @PreserveOnRefresh is used on any view that uses this component and a refresh occurs, this component displays a completely different (very OLD) date range. One example after refresh was the date range was set to "1907-06-14 - 1937-06-13".

I created a test project that is a default Vaadin starter with your sample code added. My only other change was I set a default date range and I add @PreserveOnRefresh to the view.

See my project here... https://github.com/jusjoken/myappdatetest

Note in the screen grabs that the div display is still showing the correct date range even though the component is not.

Thanks for looking into this.
InitialViewonAppLaunch_defaultDate
ViewDisplayAfterRefresh
ViewDisplayAfterRefreshComponentOpen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant