Chrome OS currently supports split view, the feature that allows you to have two windows side by side. The team is adding support for multi-display split view.
A code commit that I spotted today says “Introduce multi-display support” and goes to explain the whole process in detail. Highlights:
In the present CL:
- You can enter clamshell split view on multiple displays.
- On each display where split view is active, overview shall show the
cannot snap warning on windows that cannot currently be snapped in split
view on that particular display.
- If you end overview while there is a display with split view and no
overview window that can currently be snapped there, then the cannot
snap toast shall not appear. For consistency, even in tablet mode, where
there will still be no multi-display support, the cannot snap toast will
not appear when ending overview.
- For now, there are no split view drag indicators.
- For now, if you disconnect a display where clamshell split view is
active, and then reconnect that display, any windows that were in
overview on that display stay away from that display.
- For now, in clamshell mode, long pressing the overview button (which
is present in case of tablet position with an external pointing device)
will do nothing.
For future CLs:
- Unit tests cover tablet split view with the feature flag enabled.
- Split view and virtual desks work together.
- Transitions between clamshell and tablet are handled correctly.
- Split view drag indicators appear on all displays simultaneously.
- If you disconnect a display where clamshell split view is active, and
then reconnect that display, any windows that were in overview on that
display go back to that display and get back their original bounds.
- In clamshell mode, long pressing the overview button (which is present
in case of tablet position with an external pointing device) will do
whatever we decide it should do.
- Simplify code after the feature is fully launched. For example, there
is no need to have SplitViewController::split_view_type_ per display,
but until the feature is fully launched, that variable will need to be
in SplitViewController for when the feature flag is disabled.
I don’t really have to add anything to this now. This seems to be one of the many code changes that the team is planning to make to enable this feature. If you are a Chromebook user who uses an external monitor or multiple monitors with your Chromebook, this will be something that you should keep an eye out for.