On Tue, Sep 15, 2009 at 6:04 PM, Ben the Indefatigable <[email protected]> wrote: > > I am just diving into Chromium this week, I've built 64-bit Chromium > on Ubuntu Jaunty and playing with debugging. I'm super excited about > extensions -- the html/css/js-based design is brilliant -- and I loved > Aaron's Google I/O presentation about extensions. > > While extensions show up in the Chromium Task Manager fine, they are > not quite working in the about:memory page (Task Manager -> Stats for > nerds). I vaguely remember that about:memory might not be exposed in > Chrome and I'm not saying this needs attention, but I thought I'd just > jot down my notes. > > When I installed the Gmail Checker extension, it was listed as "Tab" > with no title. Then when I clicked on it to open gmail, the gmail page > was listed under that same Tab in such a way that there was no > indication anymore that the single renderer process had both the > extension and the gmail page, i.e. it now looked like the other Tabs > with a single page listed under them. Upon closing the gmail page it > went back to being a blank unnamed Tab.
You're right that this appears to be broken, thanks for the report. In the future, feel free to file these directly in the bug database. I've filed http://code.google.com/p/chromium/issues/detail?id=22020 if you'd like to track it. > As another side note I saw that the extension's script was temporarily > using window.open instead of chrome.tabs.create: > > <code>// This should work, but is crashing in current dev build. Fixed > on trunk. > // chrome.tabs.create({url: gmail}); > window.open(gmail);</code> > > And I wondered if this impacted whether the gmail page would be opened > in the same process as the extension. It reminds me of what Darin > Fisher described in his presentation about how gmail nulls out the > originating object in order to tell Chrome to use a new process for > the new tab which is important especially for other domains and > unrelated URLs. Yes, in this case it winds up being opened in the same process. We could change the code to do the gmail trick you describe, but in this case this was temporary code so we didn't care. We've talked about enforcing this kind of behavior in general with extensions to disallow communication with cross origin windows opened via window.open(), but for now we've decided that this isn't worth it. You can cause the same issues if you add an iframe in your extension. If you want to explicitly avoid this process issue with windows and tabs, we'll support specific APIs via chrome.tabs.* and chrome.windows.*. Long term, we'd love to solve the cross-origin out-of-process communication issue, but for now it continues to be a point of research for Chrome on the whole. Erik --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" 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/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
