Status: Untriaged Owner: [email protected] Labels: Type-Bug Pri-2 OS-All Area-Extensions Size-Medium
New issue 21905 by [email protected]: cross-context callbacks can get lost http://code.google.com/p/chromium/issues/detail?id=21905 I have some test code where I'm calling chrome.toolstrip.expand on a toolstrip from a different toolstrip like this: other.chrome.toolstrip.expand({url:"hello.html"}, function() {...}); If url is a valid extension URL, then the callback never gets fired. If it's a 404 or a non-extension URL (e.g. www.google.com), then the callback gets fired. Matt and I looked at this a little bit. It appears that UnregisterContext is getting called on "other", and that this is somehow getting rid of the pending request. Matt speculated that this was because StartRequest is using currentContext rather than callingContext, but changing this didn't appear to help. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
