The Quest browser implemented this feature a couple of years ago and it's used by many WebXR experiences to control the frame rate. Often sites lower the frame rate because it's more important to have a smooth rate than a rate that is faster but with stuttering.
On Mon, Mar 13, 2023 at 11:13 AM Alex Cooper <alcoo...@chromium.org> wrote: > Contact emailsalcoo...@chromium.org, bial...@chromium.org > > ExplainerNone > > Specification > https://immersive-web.github.io/webxr/#apply-the-nominal-frame-rate > > Summary > > Allows querying for the current target frame rate of the XR Session, > querying for the frame rates that the session supports, and requesting a > change to the target frame rate. > > > Blink componentBlink>WebXR > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebXR> > > Motivation > > > > Initial public proposal > > TAG reviewhttps://github.com/w3ctag/design-reviews/issues/545 > https://github.com/w3c/transitions/issues/420 > > TAG review statusIssues addressed > > Risks > > > Interoperability and Compatibility > > > > *Gecko*: Positive (https://chromestatus.com/feature/5680169905815552) > Re-using signals from overall WebXR API chromestatus entry ( > https://chromestatus.com/feature/5680169905815552), since this is a part > of the CR for that API that we haven't implemented yet. > > *WebKit*: No signal (https://chromestatus.com/feature/5680169905815552) > Re-using signals from overall WebXR API chromestatus entry ( > https://chromestatus.com/feature/5680169905815552), since this is a part > of the CR for that API that we haven't implemented yet. > > *Web developers*: Strongly positive ( > https://chromestatus.com/feature/5680169905815552) Re-using signals from > overall WebXR API chromestatus entry ( > https://chromestatus.com/feature/5680169905815552), since this is a part > of the CR for that API that we haven't implemented yet. > > *Other signals*: > > WebView application risks > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > > > Debuggability > > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?No > > Flag name > > Requires code in //chrome?False > > Tracking bughttps://crbug.com/1377432 > > Estimated milestones > > No milestones specified > > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5157293366181888 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > 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 on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGOLbz36QHGLYyz2H_6CnsuiwN_y002YRg%2BCeWzs_dvPxhLEWg%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGOLbz36QHGLYyz2H_6CnsuiwN_y002YRg%2BCeWzs_dvPxhLEWg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGN7qDCMBf8DGhnNo7qtB8K95SyfERt4idVQDhzgus_RwD%2BTog%40mail.gmail.com.
