Version 9 by Ken Fyten
on Jan 06, 2016 14:15.

compared with
Current by Ken Fyten
on Sep 29, 2016 10:53.

These lines were removed. This word was removed.
These lines were added. This word was added.

View page history

There are 1 changes. View first change.

 h2. Overview
 _Since 4.1_
 The _ace:clientValidateValueRange_ component validates the input of the enclosing component by allowing only numeric values within the defined minimum, maximum, or range to be submitted.
 The _ace:clientValidateValueRange_ component can be used to validate the following:
 * A minimum value (_minimum_ attribute)
 * A maximum value (_maximum_ attribute)
 * A value range (_minimum_ and _maximum_ attributes)
 {tip}See the ICEfaces Showcase [Live Demo|] of this component, complete with source code.{tip}
 h2. Getting Started
 <html ... xmlns:ace="">
  // Validate that the entered value is not greater than 10.
  <ace:textEntry id="textEntry2" value="#{clientValidateValueRangeBean.value2}"
  label="Input Value " labelPosition="left" size="8">
  <ace:clientValidateValueRange maximum="10" />
  // Validate that the entered value is within the range of 10 to 20.
  <ace:textEntry id="textEntry3" value="#{clientValidateValueRangeBean.value3}"
  label="Input Value " labelPosition="left" size="8">
  <ace:clientValidateValueRange minimum="10" maximum="20" />
 h2. Attributes
 {tip:title=TagLib Documentation}This section covers attributes involved in the typical use-cases for this component. For reference, the complete taglib documentation for this component is available [here|].{tip}
 *minimum* required value of the input. If not defined the minimum value is not verified.
 *maximum* allowed value of the input. If not defined the maximum value is not verified.
 h2. Validation Behaviour
 * Client validation occurs initially when the component value is attempted to be submitted to the server, either via an ace:ajax partial-submit or a full form submit. If the client validation fails the submit to the server is aborted and the appropriate error message is displayed in an associated ace:message, ace:messages, or ace:growlMessages component (without requiring a server-roundtrip). Thus, a form submit with multiple components is processed atomically and will be completely aborted if any of the components within it fail client validation.
 * Before submitting an entered component value the first time (either via full form submit, or an ace:ajax partial-submit), the user can tab through components in the form without triggering annoying validation messages - they won't get bugged before having the chance to actually enter a correct value.
 * However, once a component is marked invalid by a previous validation failure, it is eagerly validated: As soon as the user has entered the necessary value, the error message is removed, without requiring a form submit.
 * Client validation supports the "immediate='true'" attribute on ace:pushButton and ace:linkButton. When "immediate='true'" the button submit will occur regardless of whether one or more components in the form are failing client validation.
 h2. Event Listeners
 No direct event listener is associated with this component.
 h2. Client Behavior Events
 No direct client behavior is associated with this component.
 h2. JavaScript API
 Not applicable.
 h2. Keyboard and ARIA Support
 Not applicable.
 h2. CSS Classes
 Not applicable.
 h2. Known Issues
  * Client Validation is not supported with the ace:maskedEntry component.
 h2. Additional Resources

© Copyright 2018 ICEsoft Technologies Canada Corp.