Open Bug 1768555 Opened 2 years ago Updated 2 months ago

Huge content at puticollege.com, with `table-layout:fixed` inside of flexbox

Categories

(Core :: Layout: Flexbox, defect, P3)

defect

Tracking

()

Webcompat Priority P3
Tracking Status
firefox-esr91 --- unaffected
firefox100 --- wontfix
firefox101 --- wontfix
firefox102 --- wontfix
firefox103 --- wontfix
firefox104 --- wontfix

People

(Reporter: dholbert, Unassigned)

References

(Regression)

Details

(Keywords: regression, testcase)

Attachments

(2 files)

(This was originally reported in https://webcompat.com/issues/92024 . Initially karlcow thought this was an instance of the interop issue described at https://bugs.chromium.org/p/chromium/issues/detail?id=1141209 which would mean it was really https://bugzilla.mozilla.org/show_bug.cgi?id=1745310 -- but in fact it turns out there's no dependency on float here, which means it's a distinct issue, which is why I'm filing it here.)

STR with the original site:
(note, the site has been fixed, so you have to use devtools to recreate the bad scenario where Firefox fails & Chrome does not)

  1. Visit https://www.puticollege.com/
  2. Scroll down to "Featured Classes" and inspect-in-devtools the image for the first class ("Peace Wisdom & Longevity")
  3. Go up 6 levels to the ancestor with class="list overflow-hidden ng-tns-c87-0" and add display:flex to that element's inline style.

ACTUAL RESULT:
Everything below "Featured Classes" turns into just a huge tan rectangle (around 5 million px tall according to document.documentElement.scrollHeight)

EXPECTED RESULTS:
No rendering change.

Firefox gives EXPECTED RESULTS; Chrome gives ACTUAL RESULTS.

STR with attached testcase: just load the page.

ACTUAL RESULTS: a large turquoise area (from a tiny piece of the image, blown up to be huge)
EXPECTED RESULTS: two "THIS IS A LARGE IMAGE" images shown side-by-side (with more running off the right side of the page).

Webcompat Priority: --- → ?

:TYLin, since you are the author of the regressor, bug 1469649, could you take a look?
For more information, please visit auto_nag documentation.

Flags: needinfo?(aethanyc)

Thanks for the regression range, Alice0775!

That's interesting... It's not entirely surprising there's a connection to bug 1469649, but I would expect that to have helped rather than made things worse here.

I'll clear ni=TYLin since he's on leave and I don't think this is super urgent at the moment.

Flags: needinfo?(aethanyc)

In the interests of replacing one set of flex webcompat issues with another, let's mark this as a webcompat P2. We will try to ship an intervention for the known breakage in the meantime.

Webcompat Priority: ? → P2

Thomas, is an intervention still planned for 102?

Flags: needinfo?(twisniewski)
Flags: needinfo?(aethanyc)

Dennis, you're better qualified to say whether we're going to have any interventions here for 102.

Flags: needinfo?(twisniewski) → needinfo?(dschubert)

Given the site is fixed per comment 1, I believe there is no need to ship an intervention for this site, and no rush to investigate the broken layout for the reduced testcase in comment 2.

Flags: needinfo?(aethanyc)

It looks like there no longer is a WebCompat issue here, as the site has been fixed (as mentioned in Comment 10 as well!). If something new pops up, we can ship an intervention, but I don't see any real-world breakage for this right now.

Flags: needinfo?(dschubert)

:TYlin could the priority be set on this based on comment 10?

Flags: needinfo?(aethanyc)

Yeah, we can call this P3 (I think that's our "regular but no huge rush" bucket?) per comment 10.

Flags: needinfo?(aethanyc)
Priority: -- → P3

:twisniewski do you think we can drop the Webcompat Priority level since it seems there is nothing left to do in this bug for now?

Yes, done.

Webcompat Priority: P2 → P3
Flags: needinfo?(twisniewski)
Keywords: testcase
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: