1956264 - www.aliexpress.com - Header menu is broken

Status: RESOLVED DUPLICATE of bug 1946443

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

Description

[Raul Bucata]

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

Steps to reproduce:

1. Navigate to: https://www.aliexpress.com/ssr/300000512/BundleDeals2?disableNav=YES
2. Scroll up and down and observe the header menu

Expected Behavior:
The items inside the menu are rendered correctly

Actual Behavior:
The header menu items are misplaced and some are missing

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

Comment 1

[Raul Bucata]

Attachment: Chr vs FF

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 3

[Sky Schubert [:skyschub]]

Might be related to bug 1946443, which is fixed by spoofing as Chrome. I can't test this one right now, ni? myself to test this later.

Comment 4

[Daniel Holbert [:dholbert]]

(In reply to Dennis Schubert [:denschub] from comment #3)

Might be related to bug 1946443, which is fixed by spoofing as Chrome. I can't test this one right now, ni? myself to test this later.

Indeed, the screenshots there look very similar (with awkwardly-deatched "free shipping" header-bar); and UA-spoofing seems to fix the issues here.

Testing in RDM:

• The first device-profile option in our dropdown (Galaxy Note 20 Android 11) gives the expected layout. (It includes UA string Mozilla/5.0 (Linux; Android 11; SAMSUNG SM-G973U) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/14.2 Chrome/87.0.4280.141 Mobile Safari/537.36)

• ...and if I simply edit the UA-string-field to the Firefox 136 for Android UA string -- Mozilla/5.0 (Android 15; Mobile; rv:136.0) Gecko/136.0 Firefox/136.0 -- and reload the page, then I get the broken layout shown in the screenshot here.

Looks like we've had some outreach attempts over on bug 1946443 but we're considering a sitepatch already over there. I guess I'll flag this as webcompat:needs-sitepatch, but really maybe we should dupe to avoid writing the same redundant sitepatch and/or doing redundant outreach on two separate bugs for the same site, for roughly-the-same sort of issue? (leaving ni=dschubert open for that question)

Comment 5

[Randell Jesup [:jesup] (needinfo me)]

I agree it should be duped; it appears to just be another visual effect of the same issue and is fixed by the same sitepatch/spoof