Could a single Screen interface object yield multiple segments in a window?

[michaelwasserman]

Could a single Screen interface object yield multiple segments in a window?
This question arises from discussion on w3c/window-management#35

I'm seeking clarity on whether a single Screen interface object might comprise a foldable display or pair of dual-screen displays. If so, it may be prudent to expose bounds of 'screen segments' in a manner that doesn't require a window to be positioned over that fold/seam.

As a practical example: a web application (with adequate permissions) may wish to place windows (e.g. via window.open() or window.moveTo()) relative to a fold/seam contained within a single Screen. Information about the bounds of the fold/seam or segments of the Screen would be required to do that. So, it may be valuable to expose 'screen segments' more broadly than just to the Window objects which happen to intersect each fold/seam.

Please also note the relevance of the proposed Screen Fold API
Let's seek compatibility between proposals and support forthcoming screen paradigms! I hope we can discuss plans/compatibility in advance of TPAC 2020 or as a Second Screen CG topic; thanks!