On Fri, Mar 20, 2009 at 10:23 AM, Jeremy Orlow <[email protected]> wrote:
> Are there any plans (long term or short) to render stuff like iframes with > a different origin inside a different process? Does the story get more > complicated with plugs and extensions? > > *More background:* > I'm looking at implementing window.sessionStorage. It's spec ( > http://dev.w3.org/html5/webstorage/#the-sessionstorage-attribute) says: > > The sessionStorage attribute represents the set of storage areas specific > to the current top-level browsing context. > > Each top-level browsing context has a unique set of session storage areas, > one for each origin. > > Webkit already has a nice implementation that should actually work pretty > well for chrome, provided that there's never more than one process per > top-level browsing context. > > One area that seems much more murky to me is plugins. I assume that if a > plugin interacts with a page's javascript, it'll be doing it in that page's > render process...is this correct? > yep that's correct. > > Are there any complications extensions might add? > > > Thanks! > J > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
