-
Notifications
You must be signed in to change notification settings - Fork 217
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
[Foldables] Support non-physical hinges #199
Comments
@diekus and I met in person and I'd like to reiterate again what I said in our f2f and what my colleague @dlibby- said in his comment w3c/csswg-drafts#4736 (comment): this proposal was not meant to exclude foldable devices and we truly believe the ability for websites to snap to the hinge on a foldable device with logical display regions is as important as their ability to do so on a dual-screen device with 2 separate physical display regions. it's just a matter for simple wording fix, I will do that. |
Indeed, i have an interesting chat with Zouhir. And Daniel Libby also stated the wording would be fixed. Just bringing this up since it hasn't been changed and thought it was useful to point this to the interested readers. |
Something to consider as well is how a developer would be able to target both type of devices (folding and dual screens) yet provide a different UX. Let me explain :
I'm not sure but maybe knowing the type of fold would be useful fold vs hinge for e.g. so we can let the developer decide what to do. On a hinge based device this is dead area, on a device that fold this is not, it can be used to draw things. |
In response to w3ctag/design-reviews#472
@torgo pointed out that though foldable phones, though they don't have a physical visible hinge (there is screen across the hinge), web apps still might want to consider the hinge area for animation etc
The text was updated successfully, but these errors were encountered: