> As I understand it this is the case. From Mark's original post: Ah, thanks. I missed that whole paragraph.
With some simple Gecko patches, we could pretty easily control which process an iframe gets allocated into, so going down that route sounds sane to me. Alternatively, if you made the frame directly inside the <browser> chrome, then I think that would probably also solve the problem. -Justin _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
