PaintWorklet: Call into PaintWorklet (cross-thread, blocking) on commit complete |
||
Issue descriptionDesign doc: https://docs.google.com/document/d/1USTH2Vd4D2tALsvZvy4B2aWotKWjkCYP5m0g7b90RAU/view This bug tracks calling (cross-thread, blocking) from LayerTreeHostImpl::CommitComplete over to the PaintWorklet thread, passing the set of PaintWorklet bundles (see issue 884698). It does not track doing anything with the results (that is a separate bug). This was largely done during the prototype CL (https://chromium-review.googlesource.com/c/chromium/src/+/1251465) and just needs to be tidied up and made sure its architecturally sound.
,
Oct 1
,
Oct 1
Pointers to prototype CL: Plumbing from LTH --> LTI: https://chromium-review.googlesource.com/c/chromium/src/+/1251465/7/cc/trees/layer_tree_host.cc Calling into paint worklet during CommitComplete: https://chromium-review.googlesource.com/c/chromium/src/+/1251465/7/cc/trees/layer_tree_host_impl.cc Doing the cross-thread hop + blocking on result: https://chromium-review.googlesource.com/c/chromium/src/+/1251465/7/third_party/blink/renderer/platform/graphics/paint_worklet_paint_dispatcher.cc (Paint function) |
||
►
Sign in to add a comment |
||
Comment 1 by smcgruer@chromium.org
, Oct 1