Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Message-ID: <99758792.1224209084249.JavaMail.jira@brutus>
Date: Thu, 16 Oct 2008 19:04:44 -0700 (PDT)
From: "Leonardo Uribe (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Subject: [jira] Updated: (MYFACES-2011) Javascript error on links after
 clicking a popup/download link
In-Reply-To: <1769461259.1223954984395.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MYFACES-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonardo Uribe updated MYFACES-2011:
------------------------------------

    Status: Patch Available  (was: Open)

> 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
>            Assignee: Leonardo Uribe
>             Fix For: 1.2.5-SNAPSHOT
>
>         Attachments: MYFACES-2011-JSF12.patch
>
>
> 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.