Firefox OS/1UA Multi-Screen: Difference between revisions

→‎Requirements: Add advantages
(Edit headlines)
(→‎Requirements: Add advantages)
Line 6: Line 6:
* Connect with external displays
* Connect with external displays
** For wireless connection, we have implemented Wifi Display with Miracast protocol. That is, any device capable of being a Miracast Sink, can be connected with a FxOS device.
** For wireless connection, we have implemented Wifi Display with Miracast protocol. That is, any device capable of being a Miracast Sink, can be connected with a FxOS device.
** For wired connection, we have implemented the HDMI output. This requires support of hotplug detection in Hardware Composer.
** For wired connection, we have implemented the HDMI output. This requires the support of hotplug detection in Hardware Composer.
* Open multiple top-level windows on FxOS
* Open multiple top-level windows on FxOS
** Gecko supports opening multiple top-level windows on browser naturally, however, FxOS supports single top-level window only.
** Gecko supports opening multiple top-level windows on browser naturally, while the FxOS supports single top-level window only, thus we are going to bring this ability back for FxOS.
* Manage multi-screen in System App
* Manage multi-screen in System App
=== Advantages ===
* Having multiple top-level windows means that we will have multiple DOM trees and layer trees exist in the system. The secondary window should have no difference regarding to functionality then the original one, which means that we should be able to launch WebApps, web pages, and multimedia on this secondary window.
* With the case of "1 UA multi-screen" rendering, contents of remote screen are rendered by primary device, but in the resolution of its display.
* Open arbitrary number of top-level windows and associate each of them to a display device is doable theoretically, but it depends on the support of hardware capability.


== Terminology ==
== Terminology ==
Confirmed users
220

edits