Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Beta1
-
Component/s: Documentation, Bridge, Framework
-
Labels:None
-
Environment:ICEfaces 2
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
We implemented a UI blocker feature in ICEfaces 1.8 to allow application developers the ability to block mouse and key events generated by the user while a submit was in progress to help prevent double submits from occurring, and to provide the user with visual feedback that the application was "busy" and to wait to before interacting with it.
We need to introduce this feature to ICEfaces 2.
.
We need to introduce this feature to ICEfaces 2.
.
Issue Links
- blocks
-
ICE-5817 Fine Grained BlockUIOnSubmit
- Closed
Activity
Deryk Sinotte
created issue -
Deryk Sinotte
made changes -
Field | Original Value | New Value |
---|---|---|
Salesforce Case | [] | |
Assignee Priority | P2 | |
Assignee | Mircea Toma [ mircea.toma ] |
Ken Fyten
made changes -
Summary | Port UI blocker feature that protects against double-submit. | Add support for "blockUIOnSubmit" feature to ICEfaces 2 for double-submit protection |
Issue Type | Improvement [ 4 ] | New Feature [ 2 ] |
Salesforce Case | [] | |
Affects | [Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial] | |
Description | We implemented a UI blocker feature in ICEfaces 1.8 to allow application developers the ability to block mouse and key events generated by the user to help prevent double submits. We need to port this feature to ICEfaces 2 |
We implemented a UI blocker feature in ICEfaces 1.8 to allow application developers the ability to block mouse and key events generated by the user while a submit was in progress to help prevent double submits from occurring, and to provide the user with visual feedback that the application was "busy" and to wait to before interacting with it. We need to introduce this feature to ICEfaces 2. . |
Ken Fyten
made changes -
Salesforce Case | [] | |
Fix Version/s | 2.0-Beta2 [ 10242 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #22417 | Fri Sep 24 08:57:20 MDT 2010 | mircea.toma | |
Files Changed | ||||
MODIFY
/icefaces2/trunk/icefaces/core/src/main/javascript/application.js
MODIFY /icefaces2/trunk/icefaces/core/src/main/java/org/icefaces/impl/facelets/tag/icefaces/core/ConfigHandler.java MODIFY /icefaces2/trunk/icefaces/core/build.javascript.xml MODIFY /icefaces2/trunk/icefaces/core/src/main/java/org/icefaces/util/EnvUtils.java MODIFY /icefaces2/trunk/icefaces/core/src/main/java/org/icefaces/impl/event/BridgeSetup.java MODIFY /projects/bridge-support/src/main/javascript/oo.js ADD /icefaces2/trunk/icefaces/core/src/main/javascript/blockui.js |
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Fix Version/s | 2.0.0 [ 10230 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee Priority | P2 |
Consideration should be given to the suggestion that this feature also be configurable either on a per-component or per-region basis, as indicated by
ICE-5817. Ideally this could be done without req. specific attributes on each component, perhaps with a container tag or component that would indicate the block UI on Submit status for the contained components. Not sure if the existing ice:config tag could also be used for this, or both.