Re: [w3ctag/design-reviews] Screen Fold API (#575)

Thanks @LeaVerou for you feeback.

I believe that we will see devices with non-symmetrical folds, or more than one-fold. Though it's unlikely we'll see more than 2-3 folds due to the complexity of the hinge mechanism to be put into such a device. The mechanism takes space and at some point, one must value the space in the device vs battery life vs benefits of multiple folds. 

- angle vs fold-angle, I don't have a strong opinion on it. It's just inside the namespace `screen.fold` so `angle` name seems obvious that it applies to the fold itself. 
- I don't think we want to encourage author to compute the posture based on the angle or angles. This would yield to inconsistent behaviors between sites because author would decide differently when the device is used a laptop/unfolded/etc. Also, the posture determination is a lot more complex than just the fold angle, for example if the keyboard is magnetically attached or not, if the device is standing on a table (tablet vs used as a monitor). It's important that we let the OS determine and enforce the posture because it will do a better job than web authors. Lastly user would expect the device to react certain ways when they use the device, and they will be puzzled if a given website do not behave as the rest of the ecosystem.

-- 
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/575#issuecomment-767025459