1863662 - Reader View "Cannot Complete Request" if used on a recently opened tab

Status: NEW

(Fenix :: WebExtensions, defect, P2)

Description

[ponchojohn1234]

User Agent: Mozilla/5.0 (Android 13; Mobile; rv:121.0) Gecko/121.0 Firefox/121.0

Steps to reproduce:

1. Use "Open link in a new tab" option on an article link
2. Use reader view once the tab finishes loading

Actual results:

Error Message
Cannot Complete Request
Additional information about this problem or error is currently unavailable

Expected results:

Article opens in Reader View

Comment 1

[ponchojohn1234]

Attachment: screen-20231107-204623.webm

Comment 2

[jackyzy823]

Error message from toolbox console

1. Security Error: Content at https://en.m.wikipedia.org/wiki/Main_Page may not load or link to moz-extension://bad4ef56-e3b5-4c79-9e4b-3703f46496c3/readerview.html?url=https://en.m.wikipedia.org/wiki/SZA&id=1dae0f5d-1a6d-4dc8-8300-e4ffa12c6257&colorScheme=light.

2. TypeError: can't access property "eventDispatcher", this.window.moduleManager is undefined GeckoViewActorParent.sys.mjs:28:5

3. Promise resolved while context is inactive readerview-content.js:49

4. Content-Security-Policy: The page’s settings blocked the loading of a resource at inline (“default-src”). resource://android/assets/low_and_medium_risk_error_pages.html?&title=Cannot+Complete+Request&button:77:33

​

Comment 3

[jackyzy823]

It is weird that , the " Content at https://en.m.wikipedia.org/wiki/Main_Page" is not the new opened-in-new-tab page , but the original page .

Comment 4

[jackyzy823]

Some bisection on nightly apks.

2023-10-16-16-08-10 good
2023-10-17-04-02-35 bad

looks like it is still related to Bug 1856731

Comment 5

[William Durand [:willdurand]]

(In reply to jackyzy823 from comment #2)

Error message from toolbox console

2. TypeError: can't access property "eventDispatcher", this.window.moduleManager is undefined GeckoViewActorParent.sys.mjs:28:5

This looks like Bug 1858130.

Comment 6

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

Set release status flags based on info from the regressing bug 1856731

Comment 7

[Donal Meehan [:dmeehan]]

:boek do you plan on fixing this in time for Fx122, wondering if we can expect something before release?

Comment 8

[Jeff Boek [:boek]]

I am targeting a fix for 122, but this seems to be unrelated to the readermode changes that were made. Will post an update once I complete my investigation.

Comment 9

[Chris Peterson [:cpeterson]]

The Android team has not been keeping our P1 bug list up to date, so we're resetting all our P1 bugs to P2 to avoid signalling that we're actively working on bugs that we're not. The BMO documentation https://wiki.mozilla.org/BMO/UserGuide/BugFields#priority says P1 means "fix in the current release cycle" and P2 means "fix in the next release cycle or the following (nightly + 1 or nightly + 2)".

If you are actively working on this bug and expect to ship it in Fx 122 or 123, then please restore the priority back to P1.

Comment 12

[jackyzy823]

After adding log to scirptsecuritymanager , I can observe that view-source: and moz-extension are all reject for URI_DANGEROUS_TO_LOAD

Comment 14

[Joe M [:jmahon]]

:boek, this is still assigned to you, but seems to have stalled out a bit (I see some chatter by searching internal slack, but I'm not sure what the actual latest info is). Can we get a quick update on the state this was left in the last time you were looking at it? It's marked as a P2/S3, so it'll keep getting checked as part of the release process.

And if you're not actively working on it, probably best to un-assign yourself here amd remove the priority flag for transparency.

Comment 15

[Jeff Boek [:boek]]

Spoke with SUMO and this isn't currently a high priority issue which bumped this back to a P2. This will get fixed with the migration of reader mode from the extension to the one built into Gecko. I will link the issue here

Comment 19

[eclaudiu64]

This error can also be reproduced in the latest version 124 and Beta 125 and Nightly 126. I have also seen this error when I loaded a normal site, without using Reader View.

Comment 20

[eclaudiu64]

Attachment: Screenshot_20240406-222237_Firefox Nightly.jpg

I reproduced this error when accessing a website, is it related to this one?!

Comment 21

[miralobontiu]

Claudiu, please provide us some STR for confirmation.
Thanks!

Comment 22

[Tom25519]

(In reply to miralobontiu from comment #21)

Claudiu, please provide us some STR for confirmation.
Thanks!

1. Open https://bugzilla.mozilla.org
2. Search "Spectre"
3. Open an existing bug by long-press link->Open link in new tab
4. Touch "Reader view" button
5. Bug happens

It's very instering that this bug only happens when open link in new tab.

Comment 23

[eclaudiu64]

(In reply to miralobontiu from comment #21)

Claudiu, please provide us some STR for confirmation.
Thanks!

I opened Firefox Nightly, went to the address bar on the main screen and typed the address: https://www.vezioline.net and this message appeared, which is also displayed in the reader view.

Comment 24

[eclaudiu64]

(In reply to eclaudiu64 from comment #23)

(In reply to miralobontiu from comment #21)

Claudiu, please provide us some STR for confirmation.
Thanks!

I opened Firefox Nightly, went to the address bar on the main screen and typed the address: https://www.vezioline.net and this message appeared, which is also displayed in the reader view.

https://www.vezionline.net , this is the correct address, sorry for the mistake.

Comment 25

[eclaudiu64]

Attachment: mobizen_20240411_011046.mp4

I've also noticed this behavior for the reader view, when I'm on my Bugzilla profile, I hit a category in the view: "Activity by product" and it goes into that category, but the Reader view doesn't show, but when I go into the tab tray and select the same tab, it appears and Reader view. Could it be related to the error that the Reader View page cannot be viewed?

Comment 26

[eclaudiu64]

Attachment: mobizen_20240411_142206.mp4

(In reply to eclaudiu64 from comment #25)

Created attachment 9396113 [details]
mobizen_20240411_011046.mp4

I've also noticed this behavior for the reader view, when I'm on my Bugzilla profile, I hit a category in the view: "Activity by product" and it goes into that category, but the Reader view doesn't show, but when I go into the tab tray and select the same tab, it appears and Reader view. Could it be related to the error that the Reader View page cannot be viewed?

It can also be seen on other sites, that when accessing the Reader view is not available, only after I open the tab tray and click on the current tab, then the Reader view appears.

Comment 27

[Ryan VanderMeulen [:RyanVM]]

Is this working better with current Fenix nightly builds?

Comment 28

[ggmkern]

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

Is this working better with current Fenix nightly builds?

Nope. Same deal. I have to close and reopen the app in order to use reader mode on a new tab.

Comment 29

[Haik Aftandilian [:haik]]

@Zac, with dependency bug 1889066 now fixed, can progress be made on this?

Comment 30

[Zac McKenney [:zmckenney]]

Jeff tested and was able to see a bug but it's uncertain if it was the same as the previous bug that was causing this. These bugs should be fixed when we move to native for Reader mode but I'm not sure yet where we are for prioritizing that project. I will reach out to the Geckoview engineers to see where that is and determine the right course of action from there.

Comment 31

[george22gr.ay8.5.53]

I tested this bug today on Firefox 128 (Fennec F-Droid).
In this version I failed to reproduce the bug on multiple websites.
I would like to add that the bug existed on previous Fennec builds, however I cannot be sure, if the bug still exists on nightly and others.

Comment 32

[:Gab24]

Seems to be resolved on my Android Samsung phone. Thank you.