You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Klein Koerkamp (JIRA)" <ji...@apache.org> on 2008/10/29 14:55:44 UTC
[jira] Created: (WICKET-1902) Javascript error multiple click on
closing modalwindow
Javascript error multiple click on closing modalwindow
------------------------------------------------------
Key: WICKET-1902
URL: https://issues.apache.org/jira/browse/WICKET-1902
Project: Wicket
Issue Type: Bug
Components: wicket-extensions
Affects Versions: 1.3.4
Environment: Internet Explorer
Reporter: Frank Klein Koerkamp
Fix For: 1.3.4
When I multiple click on the closing button of the modalwindow i get js error.
On the line win.current.close();. Because window.current == null.
Maybe an extra check?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-1902) Javascript error multiple click on
closing modalwindow
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-1902.
-----------------------------------
Assignee: Igor Vaynberg (was: Matej Knopp)
Resolution: Fixed
this was fixed in 1.4.x with ajax preconditions
> Javascript error multiple click on closing modalwindow
> ------------------------------------------------------
>
> Key: WICKET-1902
> URL: https://issues.apache.org/jira/browse/WICKET-1902
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.3.4
> Environment: Internet Explorer
> Reporter: Frank Klein Koerkamp
> Assignee: Igor Vaynberg
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> When I multiple click on the closing button of the modalwindow i get js error.
> On the line win.current.close();. Because window.current == null.
> Maybe an extra check?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1902) Javascript error multiple click on
closing modalwindow
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg updated WICKET-1902:
----------------------------------
Fix Version/s: (was: 1.3.4)
> Javascript error multiple click on closing modalwindow
> ------------------------------------------------------
>
> Key: WICKET-1902
> URL: https://issues.apache.org/jira/browse/WICKET-1902
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.3.4
> Environment: Internet Explorer
> Reporter: Frank Klein Koerkamp
> Assignee: Matej Knopp
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> When I multiple click on the closing button of the modalwindow i get js error.
> On the line win.current.close();. Because window.current == null.
> Maybe an extra check?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WICKET-1902) Javascript error multiple click on
closing modalwindow
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg reassigned WICKET-1902:
-------------------------------------
Assignee: Matej Knopp
> Javascript error multiple click on closing modalwindow
> ------------------------------------------------------
>
> Key: WICKET-1902
> URL: https://issues.apache.org/jira/browse/WICKET-1902
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.3.4
> Environment: Internet Explorer
> Reporter: Frank Klein Koerkamp
> Assignee: Matej Knopp
> Fix For: 1.3.4
>
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> When I multiple click on the closing button of the modalwindow i get js error.
> On the line win.current.close();. Because window.current == null.
> Maybe an extra check?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.