1860740 - The Reader Mode option does not work and an error message appears

Status: RESOLVED FIXED

(Fenix :: General, defect)

Description

[eclaudiu64]

Attachment: mobizen_20231024_112736.mp4

User Agent: Mozilla/5.0 (Android 11; Mobile; rv:120.0) Gecko/120.0 Firefox/120.0

Steps to reproduce:

1. Access google.
2. The cookie message will appear.
3. Press "Reader mode" option.
4. The page will show an error.

Reproducible with Firefox Beta 120 and Nightly 121, stable Firefox 119 does not reproduce this error.

Actual results:

Error occurs.

Expected results:

To display the writing in "Reader mode".

Comment 1

[jackyzy823]

Test with url "https://consent.google.com/m?continue=https://www.google.com/&gl=GB&m=0&pc=t&cm=2&hl=en-US&src=1" , it behavior a little different , it show "Cannot complete the request"

Also , it may be similar as bug 1860490 , because i test with the apks with the commit (Readerview failed) and the previous one (Readerview success).

Comment 2

[Chris Peterson [:cpeterson]]

Thanks for sharing the link to bug 1860490. I agree that they look related or duplicates. I wonder if this is a regression from some WebExtension changes in 120. I will share this bug with the WebExtensions team.

Comment 3

[Chris Peterson [:cpeterson]]

[Tracking Requested - why for this release]:

Reader View is broken in 120.

@ Jeff, this bug looks like another regression from bug 1856731.

Comment 4

[Dianna Smith [:diannaS]]

.

Comment 5

[Luca Greco [:rpl] [:luca] [:lgreco]]

I gave a quick try to reproduce this issue with and without the fix from Bug 1860130 and confirmed that with the fix from Bug 1860130 applied this issue can't be reproduced anymore (the readerview mode is instead entered as expected), and so I've added Bug 1860130 to this bug depends on field.

Comment 6

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

The bug is marked as tracked for firefox120 (beta) and tracked for firefox121 (nightly). However, the bug still isn't assigned.

:amoya, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Comment 7

[Ryan VanderMeulen [:RyanVM]]

Bug 1860130 landed a couple hours ago and will be in the next Fenix nightly build. Can you please confirm that things work for you once you've received the updated build from the Play Store?

Comment 8

[eclaudiu64]

(In reply to Ryan VanderMeulen [:RyanVM] from comment #7)

Bug 1860130 landed a couple hours ago and will be in the next Fenix nightly build. Can you please confirm that things work for you once you've received the updated build from the Play Store?

I confirm that it displays correctly without error on the Firefox Nightly version 121.0a1 (Build #2015983178).

Comment 9

[Dianna Smith [:diannaS]]

Should be fixed in Mobile 120.0b6