[
https://issues.apache.org/jira/browse/MYFACES-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639287#action_12639287
]
Daniel Campagnoli commented on MYFACES-2011:
--------------------------------------------
Looks like this would have been caused by MYFACES-1855
> Javascript error on links after clicking a popup/download link
> --------------------------------------------------------------
>
> Key: MYFACES-2011
> URL: https://issues.apache.org/jira/browse/MYFACES-2011
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 1.2.4
> Environment: MyFaces 1.2.4 IE7
> Reporter: Daniel Campagnoli
>
> We have just upgraded from 1.1.6 to 1.2.4 and come across an issue that looks
> similar to MYFACES-1804 in effect but looks to have a slightly different
> cause.
> The issue occurs when you first click on a download/popup link and then go to
> click another link on the same page.
> This calls oamSubmitForm which at the end calls oamClearHiddenInput which
> removes the hidden field from the dom.
> Now when you go and click on another link on the original page it calls
> oamSubmitForm. This first calls clearFormHiddenParams_formname which tries
> to get the hidden field and set the value to empty, but because it has
> already been removed from the dom the field null and an exception occurs.
> My workaround was to override oamSetHiddenInput and oamClearHiddenInput to
> instead of removing/adding the hidden field from the dom, was to (dis)enabled
> it instead. Alternatively clearFormHiddenParams_form could check to see if
> the hidden field exists before trying to set the value on it.
> Note this error happens in IE7 and not in Firefox 3
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
