On Thu, Jul 25, 2013 at 10:25 AM, Justin Lebar <justin.le...@gmail.com> wrote: > Unless you have an <iframe> inside the <browser remote=true>, and it's > that <iframe> that you were setting as an app? If that's the case, > could you merge the <iframe> and <browser remote=true>? (You could > either use a <browser> or an <iframe mozbrowser>.)
As I understand it this is the case. From Mark's original post: >> The problem would >> probably (ie, I haven't checked) go away if we just hosted the content >> directly in the <browser> element (ie, dropped the iframe), but we'd prefer >> to avoid that currently if possible (mainly so we can host multiple of these >> iframes in a single remote process if desired) The "host multiple iframes in a single remote process" bit is somewhat aspirational and not really driven by any reasoning beyond "it might be nice to avoid unnecessary per-process overhead". That's probably not a problem that should be solved at this level (and might not need solving at all), so for the moment I think I'd suggest just getting rid of the iframe setup. Gavin _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
