-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explain how this is related to the Foldables proposal #21
Comments
@diekus fyi The link to that spec work can be found here: https://w3c.github.io/screen-fold/ |
A concern that was raised in a TAG meeting (see w3ctag/design-reviews#413) is that the foldables work is still in flux and this API needs to blend seamlessly with that work. If these APIs don't ship in lock-step there is a risk that one will ship, the ongoing work in the other will then require changes, but the shipping API will not be able to change due to web compat issues. |
We have been coordinating with Screen Fold (Device Posture) and Window Segment proposals through the Second Screen Community Group. While hardware and paradigms are indeed evolving, there is a fairly stable problem space where we can align complimentary proposals. The CG even produced a Form Factors draft report with some guiding principles for using these APIs. This repo's explainer and readme point to the other proposals and the report. We're continually aligning to avoid compatibility issues, but any specific issues should definitely be raised, like here and here. |
Should this somewhere explain how it's related to Foldables? The Edge explainer references this present explainer.
The text was updated successfully, but these errors were encountered: