Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 4.1
-
Assignee Priority:P2
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
The ace:clientValidate* components currently hard-code the client events that trigger their invocation. While this is fine for most use-cases, it would be nice to be able to control which events triggered their execution in some cases.
For example, the will fire when blurring away from an input component currently, but it might be desirable to have them fire only when a component is being submitted to the server, as an example.
This can be implemented by adding support for an "event" attribute on the ace:clientValidate* components which would specify the event to trigger the validation on, i.e. "blur", "keypress", "submit".
For example, the will fire when blurring away from an input component currently, but it might be desirable to have them fire only when a component is being submitted to the server, as an example.
This can be implemented by adding support for an "event" attribute on the ace:clientValidate* components which would specify the event to trigger the validation on, i.e. "blur", "keypress", "submit".
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
- maskedEntry
This component is incompatible with all the client validators. Any of the potential client validation constraints are already incapsulated by the component's client code.
- checkboxButtons
This component is incopatible because it has multiple elements that need to have their state tracked by events listeners. This is not currently doable with the jQuery Validation API.
We'll need to document the limitations for these components.
Show
Mircea Toma
added a comment - - edited
maskedEntry
This component is incompatible with all the client validators. Any of the potential client validation constraints are already incapsulated by the component's client code.
checkboxButtons
This component is incopatible because it has multiple elements that need to have their state tracked by events listeners. This is not currently doable with the jQuery Validation API.
We'll need to document the limitations for these components.
Verified ace:comboBox issues fixed ICEfaces 4 trunk r49310. Tomcat 8, MS edge, IE 11, 10, 9, FF 47, Chrome 53.
Show
Liana Munroe
added a comment - Verified ace:comboBox issues fixed ICEfaces 4 trunk r49310. Tomcat 8, MS edge, IE 11, 10, 9, FF 47, Chrome 53.
Re-opened.
Can the TLD description for the validateOn event be expanded a bit to further explain the type of events supported (DOM events?), and also the fact that when used these events override the default events used to trigger the validator, etc. ?
I added notes to the Wiki page for ace:maskedEntry indicating that client validators are not supported with it.
Explained better how 'validateOn' attribute can be used.
Show
Mircea Toma
added a comment - Explained better how 'validateOn' attribute can be used.
Introduced validateOn attribute for client validation components. The attribute takes an event name (such as click, blur or mouseout). Implemented also functionality that triggers validation on specified event.