On Jun 25, 4:39 pm, Khai Doan <[email protected]> wrote: > How many gadgets / developers experienced this problem?
No idea. There have been a LOT of new problems reported in the last few weeks, and most haven't had solutions posted. It's entirely possible that some others are related to this, but it's equally possible that none are. > Beside the > one mentioned (using your favorite js library to register an onload > handler on the iframe), what are other workaround? None that I know of; it's up to you to figure out what this change in timing might have done in your case and what you might do to fix it. The window.onload event was my workaround. > Is there an official fix for this? Is there a bug filed for this? Officially, it's not a problem. The handler's still getting called, and in a way that satisfies its description in the documentation (http://code.google.com/apis/gadgets/docs/reference/ #gadgets.util.registerOnLoadHandler), so what problem could there be? :^/ Unofficially, yes, it broke a few gadgets - but probably not that many, from Google's standpoint. If you're one of the few, too bad. > How did you find out about this? Through debugging or is there a > discussion thread, etc? Purely through debugging. There's no official notification of this kind of deep implementation change. As for a discussion thread... this is it. String --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en -~----------~----~----~----~------~----~------~--~---
