1961139 - [css-view-transitions] Maybe revisit ink overflow handling

Status: RESOLVED DUPLICATE of bug 1965263

(Core :: CSS Parsing and Computation, defect)

Description

[Emilio Cobos Álvarez [:emilio]]

Bug 1961010 makes a lot of progressions given it gets the right ink overflow positioning and rendering.

However, it seems like part of what should happen instead is for the pseudo-elements to render their image outside of their bounds (which is arguably a bit weird, it's not clear to me how it interacts with intrinsic sizing etc...)

So we might need to revisit that depending on the outcome of https://github.com/w3c/csswg-drafts/issues/12092.

Comment 1

[Boris Chiou [:boris]]

It seems this and Bug 1965263 may be duplicated. Both are related to the usage of ink-overflow box and border-box.
Also, the spec issue doesn't have any new feedback, so looks like we still have to follow this comment for now:

The ink overflow is captured in the snapshot, however it doesn't affect sizing and geometry. The transform is what would map the originating border box to its visual position, and the mapping between that and the actual snapshot coordinates which include the overflowing descendants and the ink overflow is internal.

In other words, we may have to implement the mapping from the originating border-box to the actual snapshot coordinates, for view transition in nsImageFrame.