Closed supo2co closed 1 year ago
For reference, I work on the WindowManager Jetpack library for Android. We had a similar concept initially but removed it for the reasons described.
I think we need to ask @diekus what they think about it. The Surface Duo doesn't support the tent mode but there was discussions about it.
Yes developers will have to adapt their content (just like other postures) but it's an opt-in feature, aka enhancement. I'm not opposed to remove it, we can always add it later. But we shouldn't assume that foldables would never be able to do 360 and thus could provide a tent mode (with dedicated content on each segment).
It is true that devices might be able to fold over eventually support "tent mode" but exposing it through a single window would make it very challenging to adopt since developers would need to cut and rotate their views and keep them in sync.
That's a fair assumption if you want to provide content on the two segments. Now the folded over has a good semantic in the case of a foldable device capable of 360 hinge: it means the device is in tent mode on the table and meant to be interacted differently (independently of the content being shown in the back segment) than "folded" or "continous", likely without keyboard or mouse because the keyboard is popped out and sit on the table (thinking beyond phones here).
My understanding is this API would apply to when a fold intersects a single window. It isn't really about the device. The content shown on the back is tied to the content shown on the front.
At TPAC we decided to remove the folder-over posture. We can always re-add it in the future.
Ack, has it already been removed / should I just close this PR?
No @kenchris or @anssiko will merge it. I was just letting you know.
@kenchris do you mind reviewing and merging if this is ok?
Remove the Folded Over posture because it has 2 meanings as described. The document references "tent-mode" which typically means the device is propped up like a tent. Tent mode does not require a secondary display, consider a Samsung Galaxy Fold that is propped open a little like an alarm clock.
A folded over position would be very challenging for developers to support generally. If it is implemented consistently with the other APIs this means that developers will need to manually split and transform their content.
Closes #???
The following tasks have been completed:
Implementation commitment:
:boom: Error: 500 Internal Server Error :boom:
PR Preview failed to build. (Last tried on Apr 3, 2023, 9:54 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one: :rotating_light: [Spec Generator](https://www.w3.org/2015/labs/) - Spec Generator is the web service used to build specs that rely on ReSpec. :link: [Related URL](https://labs.w3.org/spec-generator/?type=respec&url=https%3A%2F%2Fraw.githubusercontent.com%2Fsupo2co%2Fdevice-posture%2F443229e94bb6f79c8a38dc0e97dd059366b312b9%2Findex.html%3FisPreview%3Dtrue) ``` 🕵️♀️ That doesn't seem to be a ReSpec document. Please check manually: https://labs.w3.org/spec-generator/uploads/Wc3vSu/index.html?isPreview=true%3FisPreview%3Dtrue&publishDate=2023-04-03 ``` _If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please [file an issue](https://github.com/tobie/pr-preview/issues/new?title=Error%20not%20surfaced%20properly&body=See%20w3c/device-posture%23100.)._