On Thu, Feb 25, 2016 at 6:32 AM, Benjamin Francis <bfran...@mozilla.com> wrote: > Thanks for the heads-up. Will this be available to all chrome privileged > code (i.e. not behind a mozApp permission)? If so, this could be a great > starting point for what I'm describing. The main differences being the way > you instantiate a "browser window", and a new chrome-only HTML element with > a new name and a cleaner API (the current mozBrowser extension to iframes is > a bit of a mess).
Yes, it's available to any chrome documents. It is gated on the "browser" permission from mozApps, but the permission manager allows all permissions for chrome documents by default, so as a result it's always available in chrome docs. If we removed all the mozApps stuff at some point, it would just reduce to checking if the document is chrome for this case. > Also, is this restricted to desktop or could it be exposed on other > platforms too (i.e. Android/Gonk)? The current bug only exposes it on desktop. I would assume it can be made to work on Android since we had b2gdroid there, and Gonk since Firefox OS used it. However, I haven't tried these combinations explicitly as part of the bug I mentioned. - Ryan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
