[w3ctag/design-reviews] Foldables CSS (#472)

Hello TAG!

I'm requesting a TAG review of CSS primitives for dual screen layouts.

In order to enable web developers to build layouts that are optimized for foldable experiences declaratively using CSS, we must consider fundamental assumptions of CSS (i.e. a single contiguous rectangular space for laying out content) and introduce new primitives that -together with existing layout media queries- allow developers to create layouts that react to states where the root viewport spans multiple displays.

  - Explainer¹ (minimally containing user needs and example code): https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/Foldables/explainer.md

  - Security and Privacy self-review²: https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/187

  - GitHub repo (if you prefer feedback filed there): Feedback can be provided in this Tag Review issue
  - Primary contacts (and their relationship to the specification): 
      - Daniel Libby, @dlibby-, Microsoft
      - Zouhir Chahoud, @zouhir, Microsoft
  - Organization/project driving the design: Microsoft
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://www.chromestatus.com/feature/5310356412956672


Further details:

  - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)
  - The group where the work on this design is being done (or is intended to be done in the future): 
CSSWG
  - Existing major pieces of multi-stakeholder review or discussion of this design:
[csswg-drafts issue 4736](https://github.com/w3c/csswg-drafts/issues/4736) 
  - Major unresolved issues with or opposition to this design:
None at the moment
  - This work is being funded by: 
Microsoft

Note that the current explainer contains two different APIs - this TAG review is for the CSS portion. The explainer has both API surfaces mainly to reduce confusion and duplication of the introductory content (the APIs expose the very similar concepts, but in different forms). If preferable, we can split these out. We're in the very early stages, so major changes would not be unexpected, based on feedback from the CSSWG and other developers.

We'd prefer the TAG provide feedback as (please delete all but the desired option):
  💬 leave review feedback as a **comment in this issue** and @-notify [github usernames]



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/472