From e22252c6895c5bbebf94ea71366df9a178979aac Mon Sep 17 00:00:00 2001 From: "trop[bot]" <37223003+trop[bot]@users.noreply.github.com> Date: Mon, 9 Feb 2026 15:36:55 +0100 Subject: [PATCH] docs: fix framerate limit when osr with shared texture (#49728) Co-authored-by: trop[bot] <37223003+trop[bot]@users.noreply.github.com> Co-authored-by: reito --- docs/api/web-contents.md | 2 +- docs/tutorial/offscreen-rendering.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api/web-contents.md b/docs/api/web-contents.md index c5aab8baf1..351a39e322 100644 --- a/docs/api/web-contents.md +++ b/docs/api/web-contents.md @@ -2168,7 +2168,7 @@ Returns `boolean` - If _offscreen rendering_ is enabled returns whether it is cu * `fps` Integer If _offscreen rendering_ is enabled sets the frame rate to the specified number. -Only values between 1 and 240 are accepted. +When `webPreferences.offscreen.useSharedTexture` is `false` only values between 1 and 240 are accepted. #### `contents.getFrameRate()` diff --git a/docs/tutorial/offscreen-rendering.md b/docs/tutorial/offscreen-rendering.md index 5decbaf822..c8960939cd 100644 --- a/docs/tutorial/offscreen-rendering.md +++ b/docs/tutorial/offscreen-rendering.md @@ -14,7 +14,7 @@ _Notes_: * There are two rendering modes that can be used (see the section below) and only the dirty area is passed to the `paint` event to be more efficient. * You can stop/continue the rendering as well as set the frame rate. -* When `webPreferences.offscreen.useSharedTexture` is not `true`, the maximum frame rate is 240 because greater values bring only performance +* When `webPreferences.offscreen.useSharedTexture` is `false`, the maximum frame rate is 240 because greater values bring only performance losses with no benefits. * When nothing is happening on a webpage, no frames are generated. * An offscreen window is always created as a