Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.3
-
Fix Version/s: 4.0.BETA, EE-3.3.0.GA_P02, 4.0
-
Component/s: ACE-Components, Bridge, ICE-Components
-
Labels:None
-
Environment:ICEfaces 3.x
-
Assignee Priority:P2
-
Affects:Compatibility/Configuration
Description
This turned out to be a rather strange bug:
The problem is that Safari is applying autocomplete to our
ice.view and ice.window values resulting in old values being
used even though the page is refreshed. autocomplete is
now disabled for these hidden fields (autocomplete="off"),
but there could be other places in our code where hidden fields
behave strangely due to this (such as in components).
(I didn't test other browsers extensively -- Safari may be unusual
in its application of autocomplete to hidden fields.)
Task is to either audit all the source code to ensure that "autocomplete='off'" is specified for any hidden fields being used, or build in an automatic "autocomplete='off'" mechanism into the bridge, if feasible.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Back-ported fixes.
Show
Mircea Toma
added a comment - Back-ported fixes.
Added autocomplete=off attribute to hidden input elements generated by core, compat or ace code.