Open Bug 1934567 Opened 1 year ago Updated 3 months ago

www.port8.fi - Scrolling is not possible (works with Chromium user-agent)

Categories

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

Product:
Web Compatibility
Component:
Site Reports
Type:
defect

Tracking

(Webcompat Priority:P3, Webcompat Score:1, firefox-esr115 unaffected, firefox-esr128 unaffected, firefox133+ wontfix, firefox134+ wontfix, firefox135+ wontfix, firefox136 wontfix)

Status:
ASSIGNED
Project Flags:
Webcompat Priority P3
Webcompat Score 1
Tracking Flags:
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox133 + wontfix
firefox134 + wontfix
firefox135 + wontfix
firefox136 --- wontfix

People

(Reporter: rbucata, Assigned: twisniewski)

References

(Regression,
URL
)

Details

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

User Story

platform:windows,mac,linux,android
impact:site-broken
configuration:general
affects:all
branch:release
user-impact-score:0
diagnosis-team:webcompat

Attachments

(2 files)

Chr vs FF
1.29 MB, video/mp4
Details
Bug 1934567 - add a CSS webcompat intervention to fix scrolling on www.port8.fi/bokning; r?denschub
48 bytes, text/x-phabricator-request
Details | Review

Environment:
Operating system: Android 15
Firefox version: Firefox Mobile 133.0

Steps to reproduce:

  1. Navigate to: https://www.port8.fi/bokning/
  2. Attempt to scroll the page and observe

Expected Behavior:
Scrolling is functional

Actual Behavior:
Nothing happens

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

status-firefox133: --- → affected
status-firefox135: --- → affected

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

status-firefox134: --- → affected

I can reproduce the issue on Nightly135.0a1 Windows11 if browser window is the minimum width.
Regression window:

https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c80bd2a91fa59c6d71518b16b50ed650e5e2a0a5&tochange=962d10bd0a8c1e3fbdfd11d6adbea2f9b93fc0a2

status-firefox-esr115: --- → unaffected
status-firefox-esr128: --- → unaffected
Component: Site Reports → Layout: Tables
Keywords: regression
OS: Android → All
Product: Web Compatibility → Core
Regressed by: 1923201
Hardware: ARM → All

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

For more information, please visit BugBot documentation.

Flags: needinfo?(emilio)

This is unlikely to be a layout bug, the site works correctly with a Chrome UA.

Ah, the site has:

@media (max-width: 959px) {
  html.firefox .row div[class*=col-lg-].pos-bottom,
  html.firefox .row div[class*=col-lg-].pos-middle {
    height: inherit !important;
  }
}

That would do.

Component: Layout: Tables → Site Reports
Flags: needinfo?(emilio)
Product: Core → Web Compatibility
Summary: www.port8.fi - Scrolling is not possible → www.port8.fi - Scrolling is not possible (works with Chromium user-agent)
Severity: -- → S2
User Story: (updated)
Keywords: webcompat:needs-contact, webcompat:needs-sitepatch
Priority: -- → P1

The bug is marked as tracked for firefox133 (release), tracked for firefox134 (beta) and tracked for firefox135 (nightly). However, the bug still isn't assigned.

:twisniewski, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Flags: needinfo?(twisniewski)
Attached video Chr vs FF —
Flags: needinfo?(twisniewski)
Keywords: leave-open
Assignee: nobody → twisniewski
Status: NEW → ASSIGNED
Pushed by twisniewski@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/40f8d15f8b79 add a CSS webcompat intervention to fix scrolling on www.port8.fi/bokning; r=denschub,webcompat-reviewers

Are we planning to ship this intervention in 134?

Flags: needinfo?(twisniewski)

I'm not against uplifting it if we feel strongly enough to do so, but I was not planning to do so.

Flags: needinfo?(twisniewski)
Webcompat Priority: --- → P3
User Story: (updated)
Webcompat Priority: P3 → P2
Webcompat Score: --- → 6
Webcompat Score: 6 → 3
Webcompat Score: 3 → 2
User Story: (updated)
Webcompat Score: 2 → 6
Webcompat Score: 6 → 2
Webcompat Score: 2 → 1
User Story: (updated)
Webcompat Priority: P2 → P3

(In reply to Emilio Cobos Álvarez [:emilio] from comment #4)

This is unlikely to be a layout bug, the site works correctly with a Chrome UA.

Ah, the site has:

@media (max-width: 959px) {
  html.firefox .row div[class*=col-lg-].pos-bottom,
  html.firefox .row div[class*=col-lg-].pos-middle {
    height: inherit !important;
  }
}

Notably, Chrome reproduces the same issue (site can't be scrolled) if I copypaste the <html class="..."> attribute over from the page's DOM in Firefox into the page's DOM in Chrome (the most important part being the firefox class name, which is what makes that^ CSS rule apply).

So: this is a case where we're entirely interoperable with Chrome, and the site just happens to be serving broken CSS to browsers-that-claim-to-be-Firefox. (And the broken CSS happened to work in the past, but it stopped working when we landed bug 1923201 and took a step closer to interoperability, which is why this manifested as a regression.)

--> Adding webcompat:site-bug to reflect this.

User Story: (updated)
Keywords: webcompat:site-bug
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: