Consider inverting the order of FinalizeFrame and Event processing in LowLatency canvas contexts |
||
Issue descriptionToT processes events and then calls FinalizeFrame [1]. FinalizeFrame() itself only does something once, clearing |dirty_rect_| after done once [2] [1] https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/html/canvas/canvas_rendering_context.cc?q=canvasrenderingcontext&sq=package:chromium&dr=CSs&l=135 [2] https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/html/canvas/html_canvas_element.cc?type=cs&q=HTMLCanvasElement::FinalizeFrame+dirty_rect_&g=0&l=386
,
Nov 7
fserb@ you reviewed once a CL about this but somehow I managed to confuse polygerrit and it never landed :-P So: rebooting it.
,
Dec 4
After careful consideration we concluded that this would not improve latency after all; also we might move from the Event listener model anyway.
,
Dec 4
For future reference https://crrev.com/c/1324912 was the CL doing this. |
||
►
Sign in to add a comment |
||
Comment 1 by mcasas@chromium.org
, Nov 7