Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.1 Final
-
Fix Version/s: None
-
Component/s: Containers
-
Labels:None
-
Environment:n/a
Description
When a user reopens the container, the webview will be refreshed, which may, in JSF, result in an expired session response, and bring up the session expired popup. When this occurs in the browser, this usually doesn't represent a usability issue, as the user can simply hit the browser reload button. But in the container this may represent a usability issue as we've buried the reload button. It would be better if we offered a 'reload' button in the popup, or perhaps a better solution would be to auto-reload when in the container.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
When the icepush connection is not active, submitting from an expired JSF icemobile page results in a stack trace being shown to the user. When the icepush connection is active, the session expired popup is shown, although there is no reload button. This is different than in ICEfaces where a popup is always shown. If the compat library is active, the popup does have a reload button.
Show
Philip Breau
added a comment - When the icepush connection is not active, submitting from an expired JSF icemobile page results in a stack trace being shown to the user. When the icepush connection is active, the session expired popup is shown, although there is no reload button. This is different than in ICEfaces where a popup is always shown. If the compat library is active, the popup does have a reload button.
This is likely an ICEfaces popup, but it should be customizable. One solution would be to use the connectionStatus component in our demos. We may also want to support connectionStatus for JSP.