Discussion:
Datetime-local input fields "send" empty values
christophe
2018-11-30 09:43:06 UTC
Permalink
Hello

I am still a user of Wicket 6.3. At this time upgrading is not possible

I created a DateTimeField as an extension of a TextField with
type="datetime-local"
It all works fine but any change or blur event at the WEB page level
tiggers a message to the server with an empy string (in other words date &
time are missing)

Can someone help me fixw this?

Regards
Christophe

--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org
Martin Grigorov
2018-11-30 12:31:11 UTC
Permalink
Hi,

We will need some more information to be able to help you.
Post by christophe
Hello
I am still a user of Wicket 6.3. At this time upgrading is not possible
Upgrade to a newer 6.x should be relative easy and it is highly recommended
because there are security related fixes!
Post by christophe
I created a DateTimeField as an extension of a TextField with
type="datetime-local"
It all works fine but any change or blur event at the WEB page level
What do you mean by "it all works fine" ?
In which case it works ?
What do you mean by change/blur event on *page level* ? Do you change
another text field in the page ? Because I am not sure when JS document can
trigger 'change' or 'blur' event, and why this would lead to a request to
the server.
Do you use Ajax behaviors somewhere ? For this date field ? Or for an
element that is parent of this date field ?
Post by christophe
tiggers a message to the server with an empy string (in other words date &
time are missing)
Can someone help me fixw this?
Regards
Christophe
--
http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
---------------------------------------------------------------------
Loading...