Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 4.0
-
Fix Version/s: 4.1
-
Component/s: Sample Apps
-
Labels:None
-
Environment:ICEfaces4 trunk revision# 45077
Server: tomcat7
Browser: IE7, FF3.6/34 & Chrome43
JSF: Mojarra 2.2.10
-
Assignee Priority:P2
-
Affects:Sample App./Tutorial
Description
The showcase demos that use a messages component to show errors (ace:messages) are not clearing these errors from the messages when the user navigates to another demo in the showcase. This is confusing for the user as the new demo renders with the old error messages from the previous demo.
For example:
showcase > FileEntry > Callback:
When navigating to the Callback demo all messages generated on previous fileEntry demos are rendered inside a single message panel, like in attached screen shot.
For example:
showcase > FileEntry > Callback:
When navigating to the Callback demo all messages generated on previous fileEntry demos are rendered inside a single message panel, like in attached screen shot.
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | callback.PNG [ 20180 ] |
Summary | showcase - ace:fileEntry error messages on Callback demo | showcase - demos that use ace:messages not clearing errors |
Assignee | Judy Guglielmin [ judy.guglielmin ] | |
Security | Private [ 10001 ] | |
Fix Version/s | 4.1 [ 11375 ] | |
Affects Version/s | 4.0 [ 11382 ] | |
Priority | Major [ 3 ] | Minor [ 4 ] |
Description |
showcase > FileEntry > Callback:
When navigating to the Callback demo all messages generated on previous fileEntry demos are rendered inside a single message panel, like in attached screen shot. |
The showcase demos that use a messages component to show errors (ace:messages) are not clearing these errors from the messages when the user navigates to another demo in the showcase. This is confusing for the user as the new demo renders with the old error messages from the previous demo.
For example: showcase > FileEntry > Callback: When navigating to the Callback demo all messages generated on previous fileEntry demos are rendered inside a single message panel, like in attached screen shot. |
Affects | Sample App./Tutorial [ 10001 ] | |
Assignee Priority | P2 [ 10011 ] | |
Component/s | ACE-Components [ 10050 ] |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Attachment | callback1.PNG [ 22001 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #46278 | Tue Nov 24 11:13:40 MST 2015 | judy.guglielmin | |
Files Changed | ||||
![]() ![]() ![]() ![]() |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #46306 | Tue Dec 01 10:41:13 MST 2015 | judy.guglielmin | |
Files Changed | ||||
![]() ![]() ![]() ![]() ![]() |
Status | Resolved [ 5 ] | Closed [ 6 ] |
rev 46259
note that the fileEntry examples all had the same id and so used <ace:message for="...." with a unique id for each example to ensure that the actual message (since the fileEntry is the only component on the form don't need ace:messages), is tied to a unique component id.
For the growlMessages and ace:messages example use the following
<icecore:config messagePersistence="false"/>
to clear the messages between requests.