Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P02, 4.0
-
Fix Version/s: EE-3.3.0.GA_P03, 4.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 4, ace:textEntry, ace:textAreaEntry
-
Assignee Priority:P1
-
Support Case References:Support Case 13217 :- https://icesoft.my.salesforce.com/5007000000wMBld
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
Add a new "charCount" client event to the ace:textEntryArea the ace:textEntry components. This client event will be fired whenever the number of characters entered in the component changes, either by the user typing a new character, deleting one or more characters, or cutting/pasting characters into the component.
The "charCount" client event will provide the following attributes for each event fired:
- currLength: The current length of the value string.
- charsRemaining: The number of characters remaining that can be entered. This is determined via subtracting the currLength value from the maxlength attribute value on the component. If no maxlength attribute value exists, this value is -1 (?).
This new client event supports the use-case where an application would like to present the user with a message indicating how many characters are remaining in a textEntry component that has a maxlength specified.
Note that by using a client event for this information, it is feasible for the application to trap the event on the client and prevent it from submitting to the server, if a purely client-side JavaScript update of the message is desired. In addition, the client event could instead (or in addition) submit to the server if a server-based implementation is desirable. Thus, the client-event approach provides the most flexibility.
The "charCount" client event will provide the following attributes for each event fired:
- currLength: The current length of the value string.
- charsRemaining: The number of characters remaining that can be entered. This is determined via subtracting the currLength value from the maxlength attribute value on the component. If no maxlength attribute value exists, this value is -1 (?).
This new client event supports the use-case where an application would like to present the user with a message indicating how many characters are remaining in a textEntry component that has a maxlength specified.
Note that by using a client event for this information, it is feasible for the application to trap the event on the client and prevent it from submitting to the server, if a purely client-side JavaScript update of the message is desired. In addition, the client event could instead (or in addition) submit to the server if a server-based implementation is desirable. Thus, the client-event approach provides the most flexibility.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Judy Guglielmin
created issue -
Ken Fyten
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Ken Fyten [ ken.fyten ] | |
Fix Version/s | EE-4.0.0.GA [ 11171 ] | |
Fix Version/s | EE-3.3.0.GA_P03 [ 11572 ] | |
Assignee Priority | P2 [ 10011 ] |
Ken Fyten
made changes -
Summary | add attributes for remaining characters allowed for the input field | ace:textEntry, ace:textAreaEntry - Add state attributes for remaining characters allowed for the input field |
Ken Fyten
made changes -
Summary | ace:textEntry, ace:textAreaEntry - Add state attributes for remaining characters allowed for the input field | ace:textEntry, ace:textAreaEntry - Add new "charCount" client event |
Assignee | Ken Fyten [ ken.fyten ] | Judy Guglielmin [ judy.guglielmin ] |
Environment | jsf | ICEfaces 4, ace:textEntry, ace:textAreaEntry |
Description |
upgrade the ace:textEntryArea the ace:textEntry components with an attribute which allows the ability to show how many characters have been entered, or how many are left if there is a maxlength entered.
The scenario is that a value has been entered into the 'maxlength' attribute. When the user types, there would be a counter showing how many characters they have typed in so far up to maxlength. So if the maxlength entered is 100, and they have typed in 'xxxxx' then somewhere near the input field it would say either '5 of 100 characters' or '95 characters left'. Note that currently maxlength is only an attribute on the textAreaEntry component. |
Add a new "charCount" client event to the ace:textEntryArea the ace:textEntry components. This client event will be fired whenever the number of characters entered in the component changes, either by the user typing a new character, deleting one or more characters, or cutting/pasting characters into the component.
The "charCount" client event will provide the following attributes for each event fired: - currLength: The current length of the value string. - charsRemaining: The number of characters remaining that can be entered. This is determined via subtracting the currLength value from the maxlength attribute value on the component. If no maxlength attribute value exists, this value is -1 (?). This new client event supports the use-case where an application would like to present the user with a message indicating how many characters are remaining in a textEntry component that has a maxlength specified. Note that by using a client event for this information, it is feasible for the application to trap the event on the client and prevent it from submitting to the server, if a purely client-side JavaScript update of the message is desired. In addition, the client event could instead (or in addition) submit to the server if a server-based implementation is desirable. Thus, the client-event approach provides the most flexibility. |
Affects | Documentation (User Guide, Ref. Guide, etc.),Sample App./Tutorial [ 10003, 10001 ] |
Ken Fyten
made changes -
Assignee | Judy Guglielmin [ judy.guglielmin ] | Mircea Toma [ mircea.toma ] |
Ken Fyten
made changes -
Fix Version/s | 4.1 [ 11375 ] | |
Fix Version/s | EE-4.0.0.GA [ 11171 ] |
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Liana Munroe
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Liana Munroe
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Ken Fyten
made changes -
Assignee Priority | P2 [ 10011 ] | P1 [ 10010 ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Liana Munroe
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Liana Munroe
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Liana Munroe
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Carmen Cristurean
made changes -
Attachment | Capture.PNG [ 19586 ] |
Ken Fyten
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Liana Munroe
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Mircea Toma
made changes -
Comment | [ I don't see any failures. What are the steps to reproduce the issue? ] |
Mircea Toma
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |