You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Helmut Swaczinna (JIRA)" <de...@myfaces.apache.org> on 2007/06/22 11:28:27 UTC

[jira] Created: (TOBAGO-432) onexit not called in parent window after child window was opened by target attribute

onexit not called in parent window after child window was opened by target attribute
------------------------------------------------------------------------------------

                 Key: TOBAGO-432
                 URL: https://issues.apache.org/jira/browse/TOBAGO-432
             Project: MyFaces Tobago
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.0.11
         Environment: All
            Reporter: Helmut Swaczinna
            Priority: Minor


In my page a have a link with an target attribute which opens a new child 
window. Then I close the child
window and then I close the parent window. But the onexit handler of the 
parent window is not called.
When I close the parent window without having opened the child window the 
onexit handler is called.
You can see this when you define an onexit and an onunload handler. Closing 
the parent window after a
child window has been openend by a target attribute calls the onunload 
handler and not the onexit handler.
I've examined the code of Tobago.submitAction. There's a flag isSubmit to 
distinguish between onunload
and onexit. This flag is not set in the code when the target parameter is 
set. This is correct. But when you
examine this flag when the window is closed after the child window was 
closed it is set to true what's not correct.
So I don't know where exactly the problem is.


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


[jira] Commented: (TOBAGO-432) onexit not called in parent window after child window was opened by target attribute

Posted by "Helmut Swaczinna (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/TOBAGO-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522114 ] 

Helmut Swaczinna commented on TOBAGO-432:
-----------------------------------------

I examined the problem a little bit more. I put an alert() in tobago.js at every place where isSubmit is changed.
And that's always correct. It is set to false in submitAction() when a target attribute is specified. But after the call to 
submitAction() it is still true!! That's very strange and I don't know how this can happen. Are there any other places
in other javascript files where isSubmit might be changed?

As a workaround I put a Tobago.isSubmit = false; after the call to submitAction() in my code and then it works like
expected.

> onexit not called in parent window after child window was opened by target attribute
> ------------------------------------------------------------------------------------
>
>                 Key: TOBAGO-432
>                 URL: https://issues.apache.org/jira/browse/TOBAGO-432
>             Project: MyFaces Tobago
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.11
>         Environment: All
>            Reporter: Helmut Swaczinna
>            Priority: Minor
>
> In my page a have a link with an target attribute which opens a new child 
> window. Then I close the child
> window and then I close the parent window. But the onexit handler of the 
> parent window is not called.
> When I close the parent window without having opened the child window the 
> onexit handler is called.
> You can see this when you define an onexit and an onunload handler. Closing 
> the parent window after a
> child window has been openend by a target attribute calls the onunload 
> handler and not the onexit handler.
> I've examined the code of Tobago.submitAction. There's a flag isSubmit to 
> distinguish between onunload
> and onexit. This flag is not set in the code when the target parameter is 
> set. This is correct. But when you
> examine this flag when the window is closed after the child window was 
> closed it is set to true what's not correct.
> So I don't know where exactly the problem is.

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