[Webkit-unassigned] [Bug 240380] Capturing a canvas that is not in the DOM can lead to erratic frame rates or no frame emission at all

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=240380

--- Comment #5 from youenn fablet <youennf at gmail.com> ---
I did some investigations:
- CanvasCaptureMediaStreamTrack::Source::canvasChanged is correctly called each time the not-in-dom canvas is changed but it returns early due to m_canvas->renderingContext()->needsPreparationForDisplay() returning true.
- Normally, the page will call updateRendering which will make the actual preparation happening, which in turn will tell CanvasCaptureMediaStreamTrack::Source to generate a frame. This is what happens when canvas is in the DOM. When canvas is not in the DOM, Page::updateRendering is not called as often and this impacts the canvas track frame rate.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220517/f77fea22/attachment.htm>