Closed Bug 2022289 Opened 6 months ago Closed 21 days ago

alphabetlighting.com - The page layout is broken and does not fit the screen

Categories

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

Product:
Web Compatibility
Component:
Site Reports
Platform:
Desktop
Windows 10
Type:
defect

Tracking

(Webcompat Priority:P3, Webcompat Score:4, firefox-esr115 wontfix, firefox-esr140 wontfix, firefox-esr153 wontfix, firefox148 wontfix, firefox149 wontfix, firefox150 wontfix, firefox151 wontfix, firefox154 wontfix, firefox155 wontfix, firefox156 verified)

Status:
VERIFIED FIXED
Milestone:
156 Branch
Project Flags:
Webcompat Priority P3
Webcompat Score 4
Tracking Flags:
Tracking Status
firefox-esr115 --- wontfix
firefox-esr140 --- wontfix
firefox-esr153 --- wontfix
firefox148 --- wontfix
firefox149 --- wontfix
firefox150 --- wontfix
firefox151 --- wontfix
firefox154 --- wontfix
firefox155 --- wontfix
firefox156 --- verified

People

(Reporter: rbucata, Assigned: emilio)

References

(Regression,
URL
)

Details

(Keywords: regression, webcompat:needs-diagnosis, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs], [wptsync upstream])

User Story

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

Attachments

(3 files)

Chr vs ff
1.43 MB, video/mp4
Details
Reduced test-case.
552 bytes, text/html
Details
Bug 2022289 - Don't wrongly treat a percentage flex gap as definite. r=TYLin,dholbert
48 bytes, text/x-phabricator-request
Details | Review

Environment:
Operating system: Windows 10
Firefox version: Firefox 148.0

Steps to reproduce:

  1. Navigate to: https://alphabetlighting.com/product/nu4qd-hyperbolic/
  2. Observe

Expected Behavior:
The page layout correctly wraps to fit the screen

Actual Behavior:
The page layout does not wraps to fit the screen

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/211464

status-firefox148: --- → affected
status-firefox150: --- → affected
Attached video Chr vs ff —

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

status-firefox149: --- → affected

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

:emilio, since you are the author of the regressor, bug 1732759, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

status-firefox-esr140: --- → affected
Flags: needinfo?(emilio)
User Story: (updated)
Webcompat Priority: --- → P3
Webcompat Score: --- → 1
Severity: -- → S2
User Story: (updated)
Webcompat Score: 1 → 4
Keywords: webcompat:needs-diagnosis
Priority: -- → P1

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

status-firefox151: --- → affected
Attached file Reduced test-case. —

I have no idea off-hand why gap or height: fit-content cause the bug to manifest.

Replacing fit-content with -moz-fit-content makes the bogus rendering go all the way back to the gap implementation...

Assignee: nobody → emilio
Attachment #9630399 - Attachment description: WIP: Bug 2022289 - Don't wrongly treat a percentage flex gap as definite. r=TYLin,dholbert → Bug 2022289 - Don't wrongly treat a percentage flex gap as definite. r=TYLin,dholbert
Status: NEW → ASSIGNED
Flags: needinfo?(emilio)
Pushed by ealvarez@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/b548ced3cb9c https://hg.mozilla.org/integration/autoland/rev/8bfe3a304f6a Don't wrongly treat a percentage flex gap as definite. r=layout-reviewers,dshin

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/62192 for changes under testing/web-platform/tests

Whiteboard: [webcompat-source:web-bugs] → [webcompat-source:web-bugs], [wptsync upstream]

https://hg.mozilla.org/mozilla-central/rev/8bfe3a304f6a

Status: ASSIGNED → RESOLVED
Closed: 21 days ago
status-firefox156: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 156 Branch

Upstream PR merged by moz-wptsync-bot

Is this worth an ESR153 uplift request or should it ride the train?

status-firefox154: --- → wontfix
status-firefox155: --- → wontfix
status-firefox-esr140: affected → wontfix
status-firefox-esr153: --- → affected
Flags: needinfo?(emilio)

Super long-standing regression in practice, let's let it ride the trains probably.

Flags: needinfo?(emilio)

Verified as FIXED using the RC Build

Tested with:

Browser / Version: Firefox 156.0-candidate build 1
Operating System: Windows 10 PRO x64

Status: RESOLVED → VERIFIED
status-firefox156: fixed → verified
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: