1877093 - Firefox Android Not Rendering The Guardian Pages on Android Pixel 7a

Status: NEW

(Firefox for Android :: Browser Engine, defect)

Description

[Andrew Lindesay]

Steps to reproduce:

I am using an Android Pixel 7a phone running Android 14 and Firefox 122. I am viewing The Guardian web site at "https://www.theguardian.com". I then hold and tap "Open link in new tab". I may then go on to open some other links in new tabs off the main page.

Actual results:

The main page at / displayed correctly. As I scrolled down the page however it stopped rendering after some cut-off point and the remainder of the page was just white and did not display the rendered web page.

The links that were opened in new tabs were not rendered and were just displayed as white pages.

If I then quit Firefox and restart it then it will render the tabs correctly.

This seems to be easily repeatable.

Expected results:

The main page at / should have been scrollable to the end and should have rendered the entire page correctly.

Each of the opened tabs should have rendered when visited.

Comment 1

[jackyzy823]

The simplest mitigation: If you do "Reject All“ in "Manage or reject cookies" , the site becomes normal.

Comment 2

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

The severity field is not set for this bug.
:tthibaud, could you have a look please?

For more information, please visit BugBot documentation.

Comment 3

[Vasilica Tamas (Android QA) [:vtamas]]

I was able to reproduce this issue using Pixel 7 (Android 13) and Samsung Galaxy A32 (Android 13) on the latest Nightly - 124.0a1 from 13.02.2024 and Fenix RC 123.0.

Comment 4

[Emily Bourke]

I believe this is a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1788530, where there is more info about the source of the problem and a link to https://bugzilla.mozilla.org/show_bug.cgi?id=1853078, which seems to be the underlying bug.

Comment 5

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

The Bugbug bot thinks this bug should belong to the 'Fenix::Browser Engine' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.