[
https://issues.apache.org/jira/browse/WICKET-5877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492443#comment-14492443
]
Sven Meier commented on WICKET-5877:
------------------------------------
I'm not happy with #getDate() either. It seems this is an implementation detail
that leaked out.
Wicket-datetime will be decommissioned after Wicket 7, so I'm reluctant to
change anything in this component:
http://mail-archives.apache.org/mod_mbox/wicket-dev/201502.mbox/%3ccamomwmqcvuadiq+mfqcvlcydnkcv+eoekm3rmsoxgsonegq...@mail.gmail.com%3E
> DateTimeField changes not getting effective without page refresh
> ----------------------------------------------------------------
>
> Key: WICKET-5877
> URL: https://issues.apache.org/jira/browse/WICKET-5877
> Project: Wicket
> Issue Type: Bug
> Components: wicket-datetime
> Affects Versions: 1.4.20, 6.19.0
> Reporter: Ulrich Schmidt
> Assignee: Sven Meier
> Priority: Minor
> Attachments: HomePage.html, HomePage.html, HomePage.java,
> HomePage.java
>
>
> DateTimeFields displays a date, a date-selection icon and time in form hh:mm.
> If one just edits the hour or minute and press a button right away where the
> "onSubmit"-method displays the entered valut to log, the LOGGER shows the
> resulting timestamp as if it wasn't changed.
> Editing the time only becomes effective if you refresh the page by pressing
> "F5" or select the date-selection icon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
