would be cool if there would be some client-side validation hook,
instead of just server-side
?
HTML5 input element's min and max attributes are there for it. Form won't
be submitted and a warning will be displayed if value is not between
min-max. This validation is provided by the browser
On Fri, May 28, 2010 at 9:49 AM, Ali Ok al...@aliok.com.tr wrote:
would be cool if there would be some client-side validation hook,
instead of just server-side
?
HTML5 input element's min and max attributes are there for it. Form won't
be submitted and a warning will be displayed if value
Hi,
Got it, thanks for the reply.
Interesting: since (I think) min/max is poor, I am wondering why they
weren't naming it minimum/maximum :-)
Wait until you see HTML5 DnD, which is disaster :)
Greetings,
Ali
On Fri, May 28, 2010 at 11:01 AM, Matthias Wessendorf mat...@apache.orgwrote:
On
Hi,
This is hx:inputNumber, which can render a spinner or a slider.
It may seem so straight forward, but here is the prototype.
===
==hx:inputNumber==
===
REFS:
[0]
Hi,
why not breaking this into two components ?
hx:inputNumberSpinner and hx:inputNumberSlider
the min/max should be driven by a range validator component
-Matthias
On Thu, May 27, 2010 at 1:11 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
This is hx:inputNumber, which can render a spinner or a
+1 I agree with Matthias.
Thanks!
Bruno
On 27 May 2010 12:44, Matthias Wessendorf mat...@apache.org wrote:
Hi,
why not breaking this into two components ?
hx:inputNumberSpinner and hx:inputNumberSlider
the min/max should be driven by a range validator component
-Matthias
On Thu, May
Hi,
why not breaking this into two components ?
hx:inputNumberSpinner and hx:inputNumberSlider
Ok. My initial prototypes were separate already on my workspace.
the min/max should be driven by a range validator component
Then I am removing min and max properties from the component(s).
Or,
On Thu, May 27, 2010 at 2:07 PM, Ali Ok al...@aliok.com.tr wrote:
Hi,
why not breaking this into two components ?
hx:inputNumberSpinner and hx:inputNumberSlider
Ok. My initial prototypes were separate already on my workspace.
the min/max should be driven by a range validator component
