You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Roman Kalyakin (JIRA)" <ji...@apache.org> on 2009/08/13 15:36:14 UTC
[jira] Created: (WICKET-2423) Not all "domready" events are called
when two wicket-event.js files are added to the page
Not all "domready" events are called when two wicket-event.js files are added to the page
-----------------------------------------------------------------------------------------
Key: WICKET-2423
URL: https://issues.apache.org/jira/browse/WICKET-2423
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.4.0
Reporter: Roman Kalyakin
Attachments: wicket-events.patch
When more than one wicket portlets run in a portal a page could get more than one wicket-event.js entry and more than one Wicket.Event.add(window, "domready", function() {...});. In this case not all of these "domready" functions are executed.
It happens because Wicket.Event object is created every time browser reaches wicket-event.js entry declaration which in turn causes Wicket.Event.fireDomReadyHandlers function to execute not all functions (this function is called only once when the global variable 'window.loaded' is set to false).
Attached patch fixes the problem by ensuring that Wicket.Event object is created only once.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-2423) Not all "domready" events are called
when two wicket-event.js files are added to the page
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-2423.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4.1
Assignee: Igor Vaynberg
> Not all "domready" events are called when two wicket-event.js files are added to the page
> -----------------------------------------------------------------------------------------
>
> Key: WICKET-2423
> URL: https://issues.apache.org/jira/browse/WICKET-2423
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.0
> Reporter: Roman Kalyakin
> Assignee: Igor Vaynberg
> Fix For: 1.4.1
>
> Attachments: wicket-events.patch
>
>
> When more than one wicket portlets run in a portal a page could get more than one wicket-event.js entry and more than one Wicket.Event.add(window, "domready", function() {...});. In this case not all of these "domready" functions are executed.
> It happens because Wicket.Event object is created every time browser reaches wicket-event.js entry declaration which in turn causes Wicket.Event.fireDomReadyHandlers function to execute not all functions (this function is called only once when the global variable 'window.loaded' is set to false).
> Attached patch fixes the problem by ensuring that Wicket.Event object is created only once.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2423) Not all "domready" events are called
when two wicket-event.js files are added to the page
Posted by "Roman Kalyakin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Kalyakin updated WICKET-2423:
-----------------------------------
Attachment: wicket-events.patch
> Not all "domready" events are called when two wicket-event.js files are added to the page
> -----------------------------------------------------------------------------------------
>
> Key: WICKET-2423
> URL: https://issues.apache.org/jira/browse/WICKET-2423
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.0
> Reporter: Roman Kalyakin
> Attachments: wicket-events.patch
>
>
> When more than one wicket portlets run in a portal a page could get more than one wicket-event.js entry and more than one Wicket.Event.add(window, "domready", function() {...});. In this case not all of these "domready" functions are executed.
> It happens because Wicket.Event object is created every time browser reaches wicket-event.js entry declaration which in turn causes Wicket.Event.fireDomReadyHandlers function to execute not all functions (this function is called only once when the global variable 'window.loaded' is set to false).
> Attached patch fixes the problem by ensuring that Wicket.Event object is created only once.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.