1892697 - The "Search" field position is not fixed when scrolling is performed at mail.yahoo.com

Status: NEW

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

Description

[Raul Bucata]

Attachment: 20240422_151639.mp4

Environment:
Operating system: Android 12/ Android 13
Firefox version: Firefox Nightly 127.0a1 (2016016367-🦎127.0a1-20240421091131🦎)

Preconditions:
Clean profile

Steps to reproduce:

1. Navigate to: https://mail.yahoo.com/mb/?.src=ym&reason=myc
2. Perform account login
3. Scroll the page.
4. Observe the "Search" field.

Expected Behavior:
The "Search" field position is fixed

Actual Behavior:
The "Search" field position is not fixed

Notes:

• Reproducible regardless of the status of ETP
• Reproducible on the latest build of Firefox Nightly and Release
• Works as expected using Chrome
• Attachment provided
• Issue found during WebCompat team [Top100] websites testing

Comment 1

[Daniel Holbert [:dholbert]]

The screenshot is actually showing two different URLs, if you look closely.

"Bad" URL, in Firefox, starts with:
https://mail.yahoo.com/mb/ (note the "b" at the end)

"Good" URL, in Chrome, starts with:
https://mail.yahoo.com/m/

You can get the "bad" experience in Chrome if you load the "bad" URL.
You can get the "good" experience in Firefox if you load the "good" URL **and use a Chrome or Chrome-like UA string (e.g. Samsung Browser). If you've got a Firefox UA string, then the "good" URL just redirects to the "bad" URL, unfortunately.

At first glance, I'm not seeing any trouble on the "good" site (/m/) when loading it in Firefox-spoofing-as-Chrome, so I'm not sure why we're being selectively sent to a downgraded version of the page. Maybe we could land a sitepatch to UA-spoof here? We'd need to do some thorough testing to be sure nothing's broken, though.

--> Calling this webcompat:needs-sitepatch and removing needs-diagnosis. denschub, please let me know if there's a keyword I should be swapping in for needs-diagnosis to reflect that this has been diagnosed as ua-sniffing. (Maybe needs-sitepatch covers that; just want to be sure this doesn't end up back in an undiagnosed triage queue.)

Comment 2

[Dennis Schubert [:denschub]]

(In reply to Daniel Holbert [:dholbert] from comment #1)

denschub, please let me know if there's a keyword I should be swapping in for needs-diagnosis to reflect that this has been diagnosed as ua-sniffing. (Maybe needs-sitepatch covers that; just want to be sure this doesn't end up back in an undiagnosed triage queue.)

Just for posterity, and to remove the ni? - you did the right thing. :)