Chasingafterghosts Reporter
	Description • 6 years ago

User Agent: Mozilla/5.0 (Android 8.0.0; Mobile; rv:63.0) Gecko/63.0 Firefox/63.0

Steps to reproduce:

Visit m.huffpost.com or huffingtonpost.com using Firefox for Android.


Actual results:

The mobile site was not displayed correctly.  At least half the page was "offscreen" to the right and had to be scrolled to.  This is the case not only on the main page,  but also for individual articles, forcing the reader to scroll right to read the rest of the text on each line, back to the left to start reading the next line, back to the right to finish reading the next line, and so on.

On the main page, it may not be readily apparent if one doesn't specifically scroll to the right, because the leftmost portion of the page happens to display pictures and links to articles in a sidebar that looks like it could be the complete site, but scrolling to the right will reveal that in fact one is only getting the left half of the page.


Expected results:

A typical mobile home page and typical mobile article pages that don't require scrolling to the right should display.

In the past, Huffington Post's mobile site has been compatible with Firefox for Android (Prior to a change sometime in the last few days or weeks).

Attempts to browse the page in another Gecko-based mobile browser generated the same issue as the one that Firefox now has with the site.

Attempts to browse the page with a Blink-based mobile browser generated a working mobile version of the site without the issue described, a mobile site that closely resembled or was identical to the mobile version of the site Firefox used to render before the issue arose.

	Stefan Deiac
	Comment 1 • 6 years ago

Hi, thanks for your report. I Can confirm your issue on all branches(Nightly, Beta, Release) using Samsung Galaxy S8(Android 8.0) and Motorola Nexus 6 (Android 7.1.1). Also, the zoom in/out doesn't work on this site. 
Note: Note reproducible on Chrome.

	Kevin Brosnan [Ex-Mozilla]
	Comment 2 • 6 years ago

I think this is a dupe of a layout bug.