1484432 - Ebay search result filters broken in Firefox for Android

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect)

Description

[Albert Scheiner [:alberts]]

Attachment: ebay-mobile-firefox-nightly-vs-chrome.jpg

On ebay the filter options for search results are displayed broken for Firefox (Android). I have attached a screenshot comparing Firefox Nightly and Chrome.

Comment 1

[Albert Scheiner [:alberts]]

I tested it with the tracking blocker disabled, but that made no difference. 
There are several more minor issues visible in the screenshot as well:
- Header spacing left and right (grey borders / padding?)
- the position of the number of comments next to the star "(1)" is a bit off
- there is an additional circled info "i" next to the text "Trending at" in Firefox, but not in Chrome. Clicking on it shows a popup which is mostly hidden. Visible for me is "Trending price is [linebreak] 90 days."

Comment 2

[Karl Dubost💡 :karlcow]

Maybe a regression due to Bug 1483233

Comment 3

[Dennis Schubert [:denschub]]

Yes, totally a regression of bug 1483233, unfortunately. However, I just tested with the UA overrides disabled and we still end up in a redirect loop, so as of right now, we have the choice between a completely broken ebay, or some rendering issues... :(

The UA override is only temporary and will be removed once ebay fixes their browser detection, so this is probably not too bad. Marking as needsdiagnosis in the meantime, maybe we can learn something here.

Thanks for the report and the detailed info, Albert! :)

Comment 4

[Albert Scheiner [:alberts]]

Just checking today the filter column looks good to me. Can this be closed, or should it stick around for after the overwrite gets removed?

Comment 5

[Mike Taylor [:miketaylr]]

I think a question for Dennis...

Comment 6

[Dennis Schubert [:denschub]]

So... the answer is that I don't know. Right now, yes, it looks fixed. But we are still spoofing as Chrome on eBay, so we really cannot be sure that it stays fixed. (Maybe they discovered the bug in their QA cycles and fixed it deliberately, maybe it was an accident...)

I filed bug 1487401 for us to track the deprecation of said UA spoof, and I will link these issues correctly, so I think we are fine with closing this for now, as we can always re-open if needed.