> What are the spec implementations of this change? I don't believe that the spec requires a change; it has broad language that says only "If the user agent <https://infra.spec.whatwg.org/#user-agent> does not support locking the screen orientation to orientation" without specifying anything about when or if a UA must support it. The PSA is just about making the currently fragmented and unreliable behavior on tablets uniformly not supported.
> Have you brought this up to other implementers that also ship on Tablets? I haven't, but good point; I will do so. thanks -fl On Fri, Feb 28, 2025 at 9:34 AM Mike Taylor <miketa...@chromium.org> wrote: > On 2/28/25 12:31 PM, 'Frank Liberato' via blink-dev wrote: > > Contact Email > > liber...@google.com > > twelling...@google.com > > Specification > > ScreenOrientation::lock() > <https://www.w3.org/TR/screen-orientation/#lock-method> > > Chrome Status Entry > > https://chromestatus.com/feature/5144443101118464 > > Summary > > Android tablets can and sometimes do lie about handling an application’s > request to lock orientation. For example, in response to an application > request to lock the orientation to landscape while in portrait mode, the > tablet might report success after (a) doing nothing, (b) letterboxing while > remaining in portrait, or (c) correctly rotating the display. This makes > the behavior of the ScreenOrientation::lock() API on tablets hard for sites > to rely on; a successfully resolved Promise doesn’t always mean what the > spec says it means. > > Further, these behaviors are becoming more common among tablets. We > expect this trend to continue. > > To address this, we plan to make ScreenOrientation::lock() for all > non-phone form-factors reject the resulting Promise with a > `NotSupportedError` without attempting to lock orientation. > > What are the spec implementations of this change? Have you brought this up > to other implementers that also ship on Tablets? > > > Foldables will behave according to Chrome’s belief about the current > device shape, though Chrome’s detection of this continues to be somewhat > flaky > <https://source.chromium.org/chromium/chromium/src/+/main:ui/android/java/src/org/chromium/ui/base/DeviceFormFactor.java;drc=d7cd8fa1f66656974d5878f7cb0973d651b7a416;l=79>. > Other form-factors, e.g. “automotive”, don’t really make sense with this > API anyway. > > Blink Components > > Blink>ScreenOrientation > > Tracking Bug > > https://launch.corp.google.com/launch/4383592 > > https://b.corp.google.com/issues/384736274 > > Estimated Milestone M136 -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/87a37476-72e4-4aad-824d-ce3e00616a01n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/87a37476-72e4-4aad-824d-ce3e00616a01n%40chromium.org?utm_medium=email&utm_source=footer> > . > > -- *I sometimes work nonstandard hours. Please don't feel any urgency to respond outside of your working hours.* -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANsaiKiQr2oV3Cg2y0_VQXCWomAL3AiesyPs1S1wdvZGvFL2_g%40mail.gmail.com.
