-
Notifications
You must be signed in to change notification settings - Fork 102
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
<p:dateTimePicker> locale problem #556
Comments
You're right. We're rendering the locale twice. The fix should be quite easy, but I will have another look at that, because I don't want the |
Thanks for the hint, I applied some minor refactorings by the way in a prior commit. |
@zhedar So it's solved in the current source code version? |
@stephanrauh Yep, I fixed it by checking and applying @dajevtic's suggestion in 452697d. |
I can confirm that the new version solves this issue. |
Setting a locale other than the default causes a JavaScript error.
After investigating the problem i noticed that class DateTimePickerRenderer renders the locale attribute twice, which causes the problem.
Removing one rendering of the locale attribute (line (BsfUtils.isStringValued(dtp.getLocale()) ? "locale: [" + dtp.getLocale() + "], " : "") +) solved the issue for me...
Running on 1.0.0
The text was updated successfully, but these errors were encountered: