1895541 - css content-visibility: auto resets object-fit on contentvisibilityautostatechange

Status: RESOLVED DUPLICATE of bug 1886745

(Core :: Layout, defect, P3)

Description

[Nick Zotenko]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:125.0) Gecko/20100101 Firefox/125.0

Steps to reproduce:

if image tags have both css properties content-visibility: auto; and object-fit: contain;

object-fit would be reset to a default value (object-fit: fill) when contentvisibilityautostatechange triggered

here is an example of reproduction on codepen

Actual results:

object-fit reset to default value

Expected results:

object-fit won't reset and would save original value

Comment 1

[Alice0775 White]

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f89991d1b2cdd13120304730efba7878d4cfac5b&tochange=af2192d1c5378cb3d6d9334ddcf52500f94bc385

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1804761

:jihye, since you are the author of the regressor, bug 1804761, could you take a look?

For more information, please visit BugBot documentation.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1804761

Comment 4

[Liz Henry (:lizzard) (relman/hg->git project)]

Emilio or asurkov, I wonder if one of you can help out here, since you both reviewed the patch ? Thanks!

Comment 5

[Emilio Cobos Álvarez (:emilio)]

So I can get chrome on a similarly weird state if I add contain: size explicitly. But off-hand this seems like bug 1886745.

However, I think this shouldn't work per spec, unless we also make contain-intrinsic-size not work for object-fit purposes?

Comment 6

[Emilio Cobos Álvarez (:emilio)]

Ah, I lie, bug 1886745 is exactly this and covers contain-intrinsic-size too.

Comment 7

[alexander :surkov (:asurkov)]

Sorry for the late reply. I'm not actively involved with Gecko lately. It's good to see the bug was marked as a duplicate of a fixed bug, so apparently, the problem is resolved. I'm canceling the pending NI requests.