Regardless of technical feasibility, I believe we're discouraging new
uses of XUL in Firefox.
/a
On 1/8/16 04:55, Tim Guan-tin Chien wrote:
What prevents you from using <xul:browser remote>? Is it because the parent
frame is (X)HTML?
I don't know what prevents browser-element from being enabled on desktop
though -- it's tests are running on desktop, and the actual feature is
hidden behind a permission so we won't expose it to the web content even if
we turn it on.
On Fri, Jan 8, 2016 at 3:31 PM, J. Ryan Stinnett <jry...@gmail.com> wrote:
(CCing dev-platform as suggested on IRC.)
On Thu, Jan 7, 2016 at 9:58 PM, J. Ryan Stinnett <jry...@gmail.com> wrote:
DevTools is working on rebuilding the responsive design UI in an HTML,
chrome-scoped page. This page will want to manage child frames to show
the page content, which could be remote frames. So, I would want to
use <iframe mozbrowser="true" remote="true"/> for cases like these.
However, I noticed mozbrowser frames are currently preffed off
(dom.mozBrowserFramesEnabled) on desktop. Is there a reason for this?
Can it be turned on, or is there some kind of work still needed before
it is usable?
I assume we would eventually want to enable this anyway, so that HTML
frames can be used in the primary browser UI.
- Ryan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
--
Adam Roach
Principal Platform Engineer
a...@mozilla.com
+1 650 903 0800 x863
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
