To unblock the VIZ launch, all screen video capture cursor rendering is being done in the browser process as a post-processing step (in content::FrameSinkVideoCaptureDevice). However, the original design called for this to happen in VIZ, perhaps even as part of the display compositing pipeline.
Note that the main blocker was due to a "plumbing" concern: We need to resolve how to get mouse move/click information to the viz::FrameSinkVideoCapturerImpl. It was not clear how the APIs would change around that, or how the mouse events would reach VIZ from the Window Service (or the browser process).
Comment 1 by m...@chromium.org
, May 16 2018Labels: -Pri-3 M-70 Pri-2