Open Bug 1953077 Opened 9 days ago Updated 6 days ago

www.nintendo.com - The slides from the guide are blank

Categories

(Web Compatibility :: Site Reports, defect, P2)

Firefox 138
ARM
Android

Tracking

(Webcompat Score:7, Webcompat Priority:P2, firefox136 affected, firefox137 affected, firefox138 affected)

Webcompat Score 7
Webcompat Priority P2
Tracking Status
firefox136 --- affected
firefox137 --- affected
firefox138 --- affected

People

(Reporter: ctanase, Unassigned)

References

(Depends on 1 open bug, )

Details

(4 keywords, Whiteboard: [webcompat-source:web-bugs][webcompat:sightline])

User Story

platform:windows,mac,linux,android
impact:content-missing
configuration:general
affects:all
branch:release
diagnosis-team:webcompat
user-impact-score:600

Attachments

(2 files)

Environment:
Operating system: Android 10
Firefox version: Firefox Mobile 136.0/138

Preconditions:

  • Account needed

Steps to reproduce:

  1. Go to https://www.nintendo.com/it-it/Notizie/Guida-strategica-di-Super-Mario-Bros-Il-Film-2533905.html
  2. Log into your account.
  3. Observe the guide.

Expected Behavior:
The slides of the guide are visible.

Actual Behavior:
The slides of the guide are blank.

Notes:

  • Reproduces regardless of the status of ETP
  • Reproduces in firefox-nightly, and firefox-release
  • Does not reproduce in chrome

Created from https://github.com/webcompat/web-bugs/issues/149642

Attached image image.png
Version: unspecified → Firefox 138

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

Whiteboard: [webcompat-source:web-bugs] → [webcompat-source:web-bugs][webcompat:sightline]
Webcompat Score: --- → 1
Severity: -- → S2
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: 1 → 7
Priority: -- → P2
Depends on: 1953879

I spun off bug 1953879 as a platform bug for this.

We could deploy the following CSS sitepatch to work around this:

.slider .slider__container img {
  flex-shrink: 0;
}

(The issue here has to do with the fact that these images given a specified width:100%, and the site expects them to take on that width, but we shrink them (taking advantage of the default flex-shrink:1) in an attempt to get them all to fit into their flex container. Chrome/WebKit also attempt to shrink the images, but they don't actually have any room to shrink because they immediately run into their resolved automatic minimum width, which they resolve as also being 100%, basically. So one way to match their behavior with an intervention here is to simply disable shrinking for these images, as the above CSS snippet would do.)

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: