Firefox reader mode not available on an article on a website
Categories
(Toolkit :: Reader Mode, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox89 | --- | affected |
People
(Reporter: foss, Unassigned)
Details
Hello,
I'm using Firefox Nightly under Debian GNU/Linux 10.
Steps to reproduce:
- First of all, I reproduce this issue on a website protected by a login, I can sent you in private the problematic webpage.
- Open the problematic webpage which is an article which looks like pretty standard.
Result:
The reader mode icon is not available and the shortcut to enable reader mode doesn't work. On other website article, reader mode works. This is not a regression, it never works on the particular website.
Expected result:
I should be able to use the reader mode on the article.
If you want me to try some debugging to determine why the problem occurs don't hesitate to ask me.
Thanks in advance.
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Reader Mode' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Comment 2•3 years ago
|
||
Hi, Alex. Are there any similar non-private articles on that site that you can download and attach to this bug?
|
Reporter | |
Comment 3•3 years ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) (Catching up on needinfos) from comment #2)
Hi, Alex. Are there any similar non-private articles on that site that you can download and attach to this bug?
Unfortunately, no.
|
||
Comment 4•3 years ago
|
||
Without a testcase it is impossible to do anything to fix this bug.
|
|
Reporter | |
Comment 5•3 years ago
|
||
(In reply to :Gijs (he/him) from comment #4)
Without a testcase it is impossible to do anything to fix this bug.
I understand, but, is there nothing I can do to help you without having access to the article? Launching a debug mode which could inform us why the reader mode doesn't work for example?
|
|
||
Comment 6•3 years ago
|
||
(In reply to Alex ARNAUD from comment #5)
(In reply to :Gijs (he/him) from comment #4)
Without a testcase it is impossible to do anything to fix this bug.
I understand, but, is there nothing I can do to help you without having access to the article? Launching a debug mode which could inform us why the reader mode doesn't work for example?
Attach the raw HTML from the webpage. If the text of the article is somehow confidential, replace all the text with garbage words of equal length, keep all spacing and punctuation the same. Keep all classes and ids and other attributes and tags in the markup the same, and ensure that that testcase still reproduces the problem.
|
|
||
Comment 7•3 years ago
|
||
Alternatively, you can look at the implementation of https://searchfox.org/mozilla-central/source/toolkit/components/reader/Readability-readerable.js yourself, and/or debug what it is doing in the browser debugger ( https://developer.mozilla.org/en-US/docs/Tools/Browser_Toolbox ), and determine why it is not reaching the threshold of readerable content in these webpages.
|
|
Reporter | |
Comment 8•3 years ago
|
||
Unfortunately, removing JS seems to make it working as expected.
If I find a way to provide you a test case or investigate I'll do it and reopen this issue.
Thanks for the pointers :Gijs.
|
|
||
Comment 9•3 years ago
•
|
||
(In reply to Alex ARNAUD from comment #8)
Unfortunately, removing JS seems to make it working as expected.
This suggests that the JS is changing the DOM - you could try getting the generated markup after the JS runs using something like copy(document.documentElement.outerHTML) in the console (will put the entirety of the DOM's generated markup into the clipboard) and putting that in an editor, saving the HTML, and then seeing if that reproduces issues.
(you might need to take the JS out from that generated result)
Description
•