Hi everyone, This is Shelly from the Connected Device Team, in order to support the use case of 1US 2end screen rendering with FxOS, we initiate a project of enabling multiple top-level window on b2g, please find more details in bug 1116089 or below,
https://bugzilla.mozilla.org/show_bug.cgi?id=1116089 = Goal = With a FxOS mobile device, users are able to project/launch an app or a tab of web content to another display device that does not have gecko running on it (e.g., monitor, tv screen...). The connection between a FxOS device to this non-FxOS display device could via a HDMI cord or other protocols. = Current = FxOS creates one xul window when booting up system, and this is the one and only "toplevel" window in FxOS. = Plans and direction = Kernel is able to provide a secondary frame buffer, for example, the default frame buffer is used for the built in display screen with type "fbmem0", and "fbmem1" refers to a virtual frame buffer(can be used for HDMI output). - Restrict one toplevel window per "frame buffer type" - Able to create another toplevel window via windowWatcher.openWindow(...)(?) (or something else) - Target window is no longer the first element of sTopWindow http://dxr.mozilla.org/mozilla-central/source/widget/gonk/nsWindow.cpp#194 - A new mechanism to find the focused window when SetFocus() is called http://dxr.mozilla.org/mozilla-central/source/widget/gonk/nsWindow.cpp#390 - Able to dequeue a specific type of frame buffer from GonkDisplay() per request http://dxr.mozilla.org/mozilla-central/source/widget/gonk/nsWindow.cpp#530 The whole plan is still pretty vague, hoping I'm going to the right direction, if not, please feel free to give us any advise! Thanks, Shelly _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
