Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 2f95edbbfe0700759b346c4ebfe1ee29688a1bd6
https://github.com/WebKit/WebKit/commit/2f95edbbfe0700759b346c4ebfe1ee29688a1bd6
Author: Enrique Ocaña González <[email protected]>
Date: 2025-11-27 (Thu, 27 Nov 2025)
Changed paths:
A
LayoutTests/platform/glib/media/media-can-play-video-decoding-limit-expected.txt
A LayoutTests/platform/glib/media/media-can-play-video-decoding-limit.html
M Tools/Scripts/build-webkit
Log Message:
-----------
[GStreamer] Add Layout Tests for content type frame rate limits
https://bugs.webkit.org/show_bug.cgi?id=303148
Reviewed by Xabier Rodriguez-Calvar.
The content type frame rate limits should have a Layout Test, as Phil
suggested in [1].
See: https://bugs.webkit.org/show_bug.cgi?id=296572
This LayoutTest checks that the content can't be played when any of the
width, height and framerate parameters go beyond the maximum limits
specified by the -DVIDEO_DECODING_LIMIT=7680x4320@60 build flag now used
by default by build-webkit. This 8K at 60fps limit shouldn't affect the
WebKit developers using the script too much, and in any case, it can be
overridden by passing a different value to build-webkit.
[1] https://github.com/WebKit/WebKit/pull/48614#pullrequestreview-3065922145
*
LayoutTests/platform/glib/media/media-can-play-video-decoding-limit-expected.txt:
Added.
* LayoutTests/platform/glib/media/media-can-play-video-decoding-limit.html:
Added.
* Tools/Scripts/build-webkit: Added VIDEO_DECODING_LIMIT build flag, needed to
exercise the limits check.
Canonical link: https://commits.webkit.org/303599@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
