[ 
https://issues.apache.org/jira/browse/TAPESTRY-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12555025
 ] 

Kevin Menard commented on TAPESTRY-2004:
----------------------------------------

I'll have to double-check the note about blowing away non-persisted fields.  
This may just be an issue with my code related to assumed lifecycle.  It may be 
that the values are in fact blank, but due to the update of the whole form, 
they blow out the typed in values whereas this was not a problem when only 
certain fields were updated.

> Issue updating form components in IE6
> -------------------------------------
>
>                 Key: TAPESTRY-2004
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2004
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 4.1.4
>         Environment: Windows XP SP2, IE 6
>            Reporter: Kevin Menard
>
> I have an EventListener bound to the onclick event of a checkbox.  The body 
> for the listener method updates other form components in the same form 
> holding the checkbox.  Everything works fine on every browser that I've 
> tested other than IE6.
> In IE6, the listener is executed, but the form components fail to update.  
> The problem appears to be the same as reported on the user list on July 20, 
> 2007 by Anna Vo.  Her problem was against Tapestry 4.1.2 . . . I seem to have 
> the same issue with 4.1.4-SNAPSHOT.  The thread is here:
> http://tapestry.markmail.org/search/?q=ie6+updatecomponent#query:ie6%20updatecomponent+page:1+mid:tjbrj4wxy2sjllwy+state:results
> Enabling debugging and setting it to INFO, all I see is the following:
> ERROR: 2:43:04 PM: Error received in IO response.  : 
> XMLHttpTransport.watchInFlight Error: [object Error]
> DEBUG:  XMLHttpTransport error callback failed: [object Object]
> Interestingly, if I change my  cycle.getResponseBuilder().updateComponent() 
> calls from the individual form fields to the form itself, everything updates 
> fine.  This has the unfortunate side effect of blowing out any non-persisted 
> form fields.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to