Add support for requestVideoFrameCallback API and MediaStreamTrack-based backend support
Created attachment 441367 [details] Patch
Created attachment 441372 [details] Patch
Created attachment 441376 [details] Patch
Comment on attachment 441376 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=441376&action=review > Source/WebCore/html/HTMLVideoElement.cpp:585 > + auto identifier = ++m_nextVideoFrameRequestIndex; Nit: extra space
Created attachment 441594 [details] Patch
Created attachment 441603 [details] Patch
Comment on attachment 441603 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=441603&action=review > Source/WebCore/html/HTMLVideoElement.cpp:585 > + auto identifier = ++m_nextVideoFrameRequestIndex; Should fix the space, as noticed by Eric.
Created attachment 441707 [details] Patch
Comment on attachment 441707 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=441707&action=review > Source/WebCore/html/HTMLVideoElement.cpp:583 > + if (m_nextVideoFrameRequestIndex == std::numeric_limits<unsigned>::max()) > + return 0; This probably log an error, possibly also to the JS console
(In reply to Eric Carlson from comment #9) > Comment on attachment 441707 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=441707&action=review > > > Source/WebCore/html/HTMLVideoElement.cpp:583 > > + if (m_nextVideoFrameRequestIndex == std::numeric_limits<unsigned>::max()) > > + return 0; > > This probably log an error, possibly also to the JS console Given we are using a Vector, I guess we should just remove this check.
Created attachment 441855 [details] Patch for landing
ChangeLog entry in Source/WTF/ChangeLog contains OOPS!.
Created attachment 441864 [details] Patch for landing
Committed r284528 (243270@main): <https://commits.webkit.org/243270@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 441864 [details].
<rdar://problem/84459428>