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
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Implemented UI blocking to avoid double submit. An iframe element is overlaid on top with its area covering the entire page. This avoids any any mouse interaction. Also the onkey*** event handlers are disabled during the form submission to avoid any keyboard based interaction.
The feature is configurable either through the 'org.icefaces.blockUIOnSubmit' context parameter or it through ice:config tag, 'blockUIOnSubmit' attribute.
ice:config configuration overrides the value defined in the context parameter.
Show
Mircea Toma
added a comment - Implemented UI blocking to avoid double submit. An iframe element is overlaid on top with its area covering the entire page. This avoids any any mouse interaction. Also the onkey*** event handlers are disabled during the form submission to avoid any keyboard based interaction.
The feature is configurable either through the 'org.icefaces.blockUIOnSubmit' context parameter or it through ice:config tag, 'blockUIOnSubmit' attribute.
ice:config configuration overrides the value defined in the context parameter.
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.