Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.8
-
Fix Version/s: 1.8.3, 1.8.2-EE-GA_P02
-
Component/s: Bridge
-
Labels:None
-
Environment:blockUIOnSubmit=true
-
ICEsoft Forum Reference:
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration
Description
When the app. has focus on an inputText field (for example) set to partialSubmit=true and the user then clicks on a commandButton, for example, to trigger an action event there can be cases where the onblur event is fired as focus leaves the inputText (and goes to the button) causes the UIBlocker to display for the partialSubmit associated with the onblur. In turn, the UIBlocker actually blocks the button click event from registering in the browser, resulting in the need for the user to click the button again to fire the action event.
To reproduce using IE view the Calendar demo in Comp. Showcase, in the popup calendar edit the date in the text field, then click the popup button. The edited date will be partialSubmitted to the server, but most times the button click will be "blocked". You'll need to click the button again to view the popup calendar.
To reproduce using IE view the Calendar demo in Comp. Showcase, in the popup calendar edit the date in the text field, then click the popup button. The edited date will be partialSubmitted to the server, but most times the button click will be "blocked". You'll need to click the button again to view the popup calendar.
Issue Links
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Field | Original Value | New Value |
---|---|---|
ICEfaces Forum Reference | http://www.icefaces.org/JForum/posts/list/12125.page#48554 | |
Salesforce Case | [] | |
Affects Version/s | 1.8RC2 [ 10163 ] | |
Assignee | Mircea Toma [ mircea.toma ] |
Salesforce Case | [] | |
Description |
When the app. has focus on an inputText field (for example) set to partialSubmit=true and the user then clicks on a commandButton, for example, to trigger an action event there can be cases where the onblur event is fired as focus leaves the inputText (and goes to the button) causes the UIBlocker to display for the partialSubmit associated with the onblur. In turn, the UIBlocker actually blocks the button click event from registering in the browser, resulting in the need for the user to click the button again to fire the action event. Since the UIBlocker is most useful for longer running submits (higher latency on the submit responses), a potential fix for this would be to delay the display of the hourglass/UIBlocker for a set period of millis, thus giving the button time to fire while preserving the UIBlocker behavior for longer running submits. Of course, this implies that it is okay for a partialSubmit to overlap with the action event submit, which might itself cause problems. |
When the app. has focus on an inputText field (for example) set to partialSubmit=true and the user then clicks on a commandButton, for example, to trigger an action event there can be cases where the onblur event is fired as focus leaves the inputText (and goes to the button) causes the UIBlocker to display for the partialSubmit associated with the onblur. In turn, the UIBlocker actually blocks the button click event from registering in the browser, resulting in the need for the user to click the button again to fire the action event. Since the UIBlocker is most useful for longer running submits (higher latency on the submit responses), a potential fix for this would be to delay the display of the hourglass/UIBlocker for a set period of millis, thus giving the button time to fire while preserving the UIBlocker behavior for longer running submits. Of course, this implies that it is okay for a partialSubmit to overlap with the action event submit, which might itself cause problems. To reproduce using IE view the Calendar demo in Comp. Showcase, in the popup calendar edit the date in the text field, then click the popup button. The edited date will be partialSubmitted to the server, but most times the button click will be "blocked". You'll need to click the button again to view the popup calendar. |
Status | Open [ 1 ] | Resolved [ 5 ] |
Affects | [Documentation (User Guide, Ref. Guide, etc.)] | |
Resolution | Fixed [ 1 ] |
Salesforce Case | [] | |
Description |
When the app. has focus on an inputText field (for example) set to partialSubmit=true and the user then clicks on a commandButton, for example, to trigger an action event there can be cases where the onblur event is fired as focus leaves the inputText (and goes to the button) causes the UIBlocker to display for the partialSubmit associated with the onblur. In turn, the UIBlocker actually blocks the button click event from registering in the browser, resulting in the need for the user to click the button again to fire the action event. Since the UIBlocker is most useful for longer running submits (higher latency on the submit responses), a potential fix for this would be to delay the display of the hourglass/UIBlocker for a set period of millis, thus giving the button time to fire while preserving the UIBlocker behavior for longer running submits. Of course, this implies that it is okay for a partialSubmit to overlap with the action event submit, which might itself cause problems. To reproduce using IE view the Calendar demo in Comp. Showcase, in the popup calendar edit the date in the text field, then click the popup button. The edited date will be partialSubmitted to the server, but most times the button click will be "blocked". You'll need to click the button again to view the popup calendar. |
When the app. has focus on an inputText field (for example) set to partialSubmit=true and the user then clicks on a commandButton, for example, to trigger an action event there can be cases where the onblur event is fired as focus leaves the inputText (and goes to the button) causes the UIBlocker to display for the partialSubmit associated with the onblur. In turn, the UIBlocker actually blocks the button click event from registering in the browser, resulting in the need for the user to click the button again to fire the action event. To reproduce using IE view the Calendar demo in Comp. Showcase, in the popup calendar edit the date in the text field, then click the popup button. The edited date will be partialSubmitted to the server, but most times the button click will be "blocked". You'll need to click the button again to view the popup calendar. |
Security | Private [ 10001 ] |
Salesforce Case | [] | |
Fix Version/s | 1.8 [ 10161 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee | Mircea Toma [ mircea.toma ] |
Resolution | Fixed [ 1 ] | |
Status | Closed [ 6 ] | Reopened [ 4 ] |
Assignee | Ken Fyten [ ken.fyten ] |
Salesforce Case | [] | |
Fix Version/s | 1.8 [ 10161 ] | |
Affects Version/s | 1.8 [ 10161 ] | |
Affects Version/s | 1.8RC2 [ 10163 ] |
Summary | UI Blocker stops button press from firing Action event | "blockUIOnSubmit=true" stops button press from firing Action event |
Salesforce Case | [] |
Salesforce Case | [] | |
Fix Version/s | 1.8.2-EE-GA_P02 [ 10226 ] |
Salesforce Case | [5007000000C3nmz] |
Fix Version/s | 1.8.3 [ 10211 ] | |
Assignee Priority | P1 | |
Assignee | Ken Fyten [ ken.fyten ] | Mircea Toma [ mircea.toma ] |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Affects | [Documentation (User Guide, Ref. Guide, etc.)] | [Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration] |
Assignee Priority | P1 |
Salesforce Case | [5007000000C3nmz] | [5007000000C3nmz, 5007000000D3aRY] |
Status | Resolved [ 5 ] | Closed [ 6 ] |