Refactor visual overflow computation for view-transitions (part 2)
Use the new CC mechanism to compute the visual overflow.
We pass the layout-computed visual overflow as the max extent, and
then let CC correct it in order to map the content rect.
-
We keep the replaced-content geometry projection as is, but also pass
the "max extents" to the CC laye (ViewTransitionContentLayerImpl),
and use it to map the border box of the original element to the
content box of the pseudo-element. Note that the border-box is now
in enclosing-layer space, as it needs to map correctly to the
max extents and actual extents. The border box sent over the wire
also has includes the offset from the enclosing layer, which would
only be different from zero for inline elements. -
When the captured rects from CC are delivered, they are used to map.
the contents of the old
pseudo-elements.
Bug: 347947051
Change-Id: I5202078666d016156c5abee99772726947e8a1d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5920431
Commit-Queue: Noam Rosenthal nrosenthal@chromium.org
Reviewed-by: Mike West mkwst@chromium.org
Reviewed-by: Khushal Sagar khushalsagar@chromium.org
Cr-Commit-Position: refs/heads/main@{#1368988}