[
https://issues.apache.org/jira/browse/SHINDIG-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086379#comment-13086379
]
[email protected] commented on SHINDIG-1578:
--------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1525/
-----------------------------------------------------------
(Updated 2011-08-17 15:18:59.396755)
Review request for shindig.
Changes
-------
Added jira
Summary
-------
If gadgets.util.registerOnLoadHandler was called after the runOnLoad
counterpart was called, the callback would sit in the array... forever alone.
This addresses bug SHINDIG-1578.
https://issues.apache.org/jira/browse/SHINDIG-1578
Diffs
-----
http://svn.apache.org/repos/asf/shindig/trunk/features/src/main/javascript/features/core.util.onload/onload.js
1157211
Diff: https://reviews.apache.org/r/1525/diff
Testing
-------
Thanks,
Dan
> Improve gadgets.util.registerOnLoadHandler to be reliable for slow or lazy
> loading gadgets
> ------------------------------------------------------------------------------------------
>
> Key: SHINDIG-1578
> URL: https://issues.apache.org/jira/browse/SHINDIG-1578
> Project: Shindig
> Issue Type: Improvement
> Components: Javascript
> Reporter: Dan Dumont
> Priority: Minor
>
> The sequence of events is:
> 1) Gadget starts loading and registers some onload.
> 2) Gadget fires an async operation that takes an unknown amount of time
> 3) Open Social api is ready and runOnLoadHandlers is called.
> 4) Gadget's async operation is done. To be safe it uses
> registerOnLoadHandler to make sure everything is all set (in case the async
> operation beat the runOnLoadHandlers call)
> At this point, the call to registerOnLoadHandler would never result in the
> callback being executed.
> This should be changed to make it so once runOnLoadHandlers is called,
> registerOnLoadHandler executes the callback immediately.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
