Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.3
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Tomcat 7
-
Salesforce Case Reference:
Description
In our showcase, if you select an item in the ace:autoCompleteEntry - Overview example and then reload the browser, the ace:autoCompleteEntry field retains it's value. This is the expected behaviour as the value is bound to a Window Scoped backing bean.
However, if you change the showcase to default to the ace:autoCompleteEntry - Lazy Loading example, choosing a value and then performing a page reload will result in an empty ace:autoCompleteEntry field.
However, if you change the showcase to default to the ace:autoCompleteEntry - Lazy Loading example, choosing a value and then performing a page reload will result in an empty ace:autoCompleteEntry field.
Closing issue, marking as Cannot Reproduce.
I was was actually able to reproduce the issue using the 3.3 release, with both binary and source bundles. I noticed that the issue was no longer present using the 3.3 EE release. I noticed that the only commit in the ace:autoCompleteEntry component that could've fixed the issue was at revision 34530 for
ICE-9208. I applied those changes to the 3.3 source release and built the whole project. The issue reported in this JIRA was no longer present.So, this issue has already been fixed. We can provide a patched 3.3 release for the customer with this fix if they require so. Otherwise, they can just use the 3.3 EE release or newer. The changes in the 34530 revision are small and don't affect any other areas of the product.