W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2020

Re: [csswg-drafts] Proposing new CSS primitives to enable great web experiences on foldable & dual-screen devices (#4736)

From: Daniel Libby via GitHub <sysbot+gh@w3.org>
Date: Fri, 07 Feb 2020 20:17:00 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-583593041-1581106619-sysbot+gh@w3.org>
@fantasai- That is a great suggestion - your proposed features would indeed make extensibility much easier for authors to reason about, and removes the hurdle of future form factors needing to come up with various individual values to describe available configurations. We'll look into testing the concept and validating with authors that have been keen on trying out these features. 

@frivoal- Thanks for the feedback and use case! We had not fully considered the best way to treat containers with children that want to avoid the fold. Many of the [design patterns](https://docs.microsoft.com/en-us/dual-screen/introduction#how-to-work-with-the-seam) suggested for the Microsoft form factors have focused on, as you mention, a high level splitting of content, or absolutely positioning things around the hinge/fold. We'll take another look and see if the current environment variables can be harnessed or if we need some additional mechanisms to enable these scenarios.

@diekus- The proposal has is not aimed at making the spanning and environment variables exclusive to dual screen devices. I'll go back and re-review the wording to clarify this point. 

We're trying to expose the underlying system's description of the semantics of the window. For devices like Galaxy Fold or Motorola Razr, if the window manager reports a fold (I believe the currently discussed abstraction for Android is [DisplayFeature](https://android-review.googlesource.com/c/platform/frameworks/support/+/1189799)), then `spanning` would resolve accordingly. Additionally the information the system exposes regarding the geometry of the fold would populate the environment variables. 

If the window manager doesn't expose this information (i.e. expects apps to just use the available space and not treat it as logically split into content regions), then `spanning` would resolve to none.

GitHub Notification of comment by dlibby-
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4736#issuecomment-583593041 using your GitHub account
Received on Friday, 7 February 2020 20:17:06 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:00 UTC