[ICE-9676] ace:autoCompleteEntry Temporary Text value Overriding Component Value - ICEsoft JIRA Issue Tracker

Brad Kroeger created issue - 07/Nov/13 10:14 AM

Brad Kroeger made changes - 07/Nov/13 10:16 AM

Field	Original Value	New Value
Description	In the client application, the ace:autoCompleteEntry tag value is being set appropriately and then the user is changing the page content to another include. Upon returning to the original include with the ace:autoCompleteEntry, the value bound to the component is reset in the bean. However, the component is dislaying the previously entered (temporary text) value. Another manifestation of this issue that when a user enters a value in the component and then backs out the text so there is nothing in the field, the value is set to an empty String on the server but the UI still displays the previous value. When there is a blur event out of that field, the valueChangeListener is executed on the server, resetting in the value of the component being reset to the temporary String that was still being displayed in the UI. With direction from Art, I replaced the ace:autoCompleteEntry component with the ace:comboBox component and was not able to reproduce the issue. This suggests the problem is with the temporary text value unique to the ace:autoCompleteEntry component.	In the client application, the ace:autoCompleteEntry tag value is being set appropriately and then the user is changing the page content to another include. Upon returning to the original include with the ace:autoCompleteEntry, the value bound to the component is reset in the bean. However, the component is dislaying the previously entered (temporary text) value. Another manifestation of this issue that when a user enters a value in the component and then backs out the text so there is nothing in the field, the value is set to an empty String on the server but the UI still displays the previous value. When there is a blur event out of that field, the valueChangeListener is executed on the server, resetting in the value of the component to the temporary String that was still being displayed in the UI. With direction from Art, I replaced the ace:autoCompleteEntry component with the ace:comboBox component and was not able to reproduce the issue. This suggests the problem is with the temporary text value unique to the ace:autoCompleteEntry component.

Brad Kroeger made changes - 07/Nov/13 10:17 AM

Assignee

Arturo Zambrano [ artzambrano ]

Brad Kroeger made changes - 07/Nov/13 12:21 PM

Comment

[ You should be able to re-create the backing out issue by adding the following to the autoCompleteEntryLazy.xhtml file in the showcase:

Create a valueChangeListener for the tag:
valueChangeListener="#{autoCompleteEntryLazyBean.cityValueChange}"

Nest ace:ajax in the tag:
<ace:ajax execute="@this" render="@form" event="blur"/> ]

Brad Kroeger made changes - 07/Nov/13 3:17 PM

Description

In the client application, the ace:autoCompleteEntry tag value is being set appropriately and then the user is changing the page content to another include. Upon returning to the original include with the ace:autoCompleteEntry, the value bound to the component is reset in the bean. However, the component is dislaying the previously entered (temporary text) value.

Another manifestation of this issue that when a user enters a value in the component and then backs out the text so there is nothing in the field, the value is set to an empty String on the server but the UI still displays the previous value. When there is a blur event out of that field, the valueChangeListener is executed on the server, resetting in the value of the component to the temporary String that was still being displayed in the UI.

With direction from Art, I replaced the ace:autoCompleteEntry component with the ace:comboBox component and was not able to reproduce the issue. This suggests the problem is with the temporary text value unique to the ace:autoCompleteEntry component.

In the client application, the ace:autoCompleteEntry tag value is being set appropriately and then the user is changing the page content to another include. Upon returning to the original include with the ace:autoCompleteEntry, the value bound to the component is reset in the bean. However, the component is dislaying the previously entered (temporary text) value.

With direction from Art, I replaced the ace:autoCompleteEntry component with the ace:comboBox component and was not able to reproduce the issue. This suggests the problem is with the temporary text value unique to the ace:autoCompleteEntry component.

Ken Fyten made changes - 07/Nov/13 3:34 PM

Fix Version/s		4.0 [ 10770 ]
Fix Version/s		EE-3.3.0.GA_P02 [ 11371 ]
Assignee Priority		P1 [ 10010 ]

Arturo Zambrano made changes - 08/Nov/13 1:35 PM

Status	Open [ 1 ]	Resolved [ 5 ]
Resolution		Fixed [ 1 ]

Brad Kroeger made changes - 15/Nov/13 5:41 PM

Resolution	Fixed [ 1 ]
Status	Resolved [ 5 ]	Reopened [ 4 ]

Brad Kroeger made changes - 18/Nov/13 1:03 PM

Salesforce Case Reference

5007000000UaCTLAA3

Arturo Zambrano made changes - 18/Nov/13 3:57 PM

Status	Reopened [ 4 ]	Resolved [ 5 ]
Resolution		Fixed [ 1 ]

Ken Fyten made changes - 05/Dec/13 1:51 PM

Link

This issue blocks ~~IPCK-484~~ [ ~~IPCK-484~~ ]

Ken Fyten made changes - 30/Oct/14 11:28 AM

Fix Version/s

4.0 [ 11382 ]

Ken Fyten made changes - 14/Nov/14 5:18 PM

Status

Resolved [ 5 ]

Closed [ 6 ]

ace:autoCompleteEntry Temporary Text value Overriding Component Value

Details

Description

Issue Links

Activity

People

Dates