Closed Bug 1892697 Opened 1 years ago Closed 2 months ago

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

Categories

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

Firefox 127
Other
Android

Tracking

(Webcompat Score:6, Webcompat Priority:P2, firefox125 affected, firefox127 affected)

VERIFIED FIXED
Webcompat Score 6
Webcompat Priority P2
Tracking Status
firefox125 --- affected
firefox127 --- affected

People

(Reporter: rbucata, Unassigned)

References

()

Details

(Keywords: webcompat:contact-in-progress, webcompat:have-login, webcompat:site-report, Whiteboard: [webcompat:sightline])

User Story

platform:android
impact:content-missing
configuration:general
affects:all
branch:release
diagnosis-team:webcompat
user-impact-score:300
outreach-assignee:jrmuizel
outreach-response-date:2025-07-07

Attachments

(1 file)

Attached video 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
Severity: -- → S3
User Story: (updated)
Priority: -- → P2
User Story: (updated)

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.)

Flags: needinfo?(dschubert)

(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. :)

User Story: (updated)
Flags: needinfo?(dschubert)
See Also: → 1892701
See Also: → 1892700
See Also: → 1892704
Whiteboard: [webcompat:sightline]
Webcompat Priority: --- → P2
Duplicate of this bug: 1946347
Webcompat Score: --- → 6
User Story: (updated)

We should be getting the tier1 mobile experience now. Can you reopen if you can still reproduce the difference?

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED

Yup, verified fixed as far as I can tell.

Signing in at https://mail.yahoo.com/ in latest Firefox Nightly on Android, I end up at https://mail.yahoo.com/m/ , the "good" URL noted in comment 1, with e.g. stars at the right side of the screen for each message, and with the searchbar staying fixed at the top of the screen as I scroll (matching the Chrome experience in comment 0's screencast).

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

Attachment

General

Creator:
Created:
Updated:
Size: