- From: Alexis Menard <notifications@github.com>
- Date: Mon, 23 Nov 2020 14:52:35 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/575@github.com>
HIQaH! QaH! TAG! I'm requesting a TAG review of the Screen Fold API. New types of mobile devices (phone and laptop segments) are coming to market with the ability to fold the screen in some capacity, either by using foldable displays or multiple internal displays (MIDs). Examples include the Samsung Galaxy Fold, Motorola Razr, Lenovo ThinkPad X1 Fold. While the technology enabling these devices is rather new, there is a resurfacing of a trend started by ultrabooks and 2 in 1’s which have had different operating “modes” or postures depending on the hinge angle. To note a few, “book”, “tent” and “tablet” modes were available on some devices. All these postures are triggered depending on the hinge/fold angle. The above specification would expose the fold angle as well as the postures. From enhancing the usability of a website by avoiding the area of a fold, to enabling innovative use cases for the web, knowing the fold angle can help developers tailor their content to different devices. It can also enable to detect different postures the device might be in. - Explainer¹ (minimally containing user needs and example code): [here](https://github.com/SamsungInternet/Explainers/blob/master/Foldables/FoldState.md) - Security and Privacy self-review²: [here](https://w3c.github.io/screen-fold/#security-and-privacy-considerations) - GitHub repo (if you prefer feedback filed there): [here](https://github.com/w3c/screen-fold) - Primary contacts (and their relationship to the specification): - [Diego González-Zúñiga](https://github.com/diekus/) Microsoft - [Kenneth Rhode Christiansen](https://github.com/kenchris) Intel - [Alexis Menard](https://github.com/darktears) Intel - [Laura Morinigo](https://github.com/lauramorinigo) Samsung - [Anssi Kostiainen](https://github.com/anssiko) Intel, Chair of DAS WG - Organization/project driving the design: Intel and Samsung - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): [here](https://bugs.chromium.org/p/chromium/issues/detail?id=1066842) Further details: - [X] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/) - The group where standardization of this work is intended to be done ("unknown" if not known): Devices and Sensors Working Group -> https://www.w3.org/das/ - Existing major pieces of multi-stakeholder review or discussion of this design: Unknown - Major unresolved issues with or opposition to this design: None at the moment - This work is being funded by: Intel and Samsung You should also know that... Please also refer to https://webscreens.github.io/form-factors/ explainer for terminology and explanation of the problem space. We'd prefer the TAG provide feedback as (please delete all but the desired option): 🐛 open issues in our GitHub repo for **each point of feedback** -- 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
Received on Monday, 23 November 2020 22:52:48 UTC