Comment #1 on issue 8751 by ivan.kozik: From one chrome browser window window.open can not access another existing chrome browser window http://code.google.com/p/chromium/issues/detail?id=8751
I've run into this problem, too. See http://dev.chromium.org/developers/design-documents/process-models The relevant paragraph is: "Permitted cross-site JavaScript calls do not yet work across processes. A small set of Javascript interactions (e.g., certain properties of the window object) are not subject to the Same Origin Policy, and can be accessed from pages from a different origin (within the same browsing instance). Because the process-per-site-instance and process-per-site models may place cross-site pages in a separate renderer process, attempts to access these objects and functions will currently fail. We view this as acceptable due to the first caveat, since this will only affect cases where the user navigates a tab to a cross-site page via the location bar or bookmarks. This suggests a user intention to treat the page as independent from other tabs. In future versions of Chromium, we will likely proxy calls for this small set of objects and functions between rendering processes. This will allow such scripts to work as expected, allowing us to resolve the first caveat." If you follow a link from the page, or otherwise stay in the same process, you should be able to get a handle on the window. I really wish this was fixed, though. Perhaps the bug should be called "Website should be able to request that its pages load in the same process, no matter how they were opened" -- 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 -~----------~----~----~----~------~----~------~--~---
