Allow content scripts on reader mode pages
Categories
(WebExtensions :: General, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: andy+bugzilla, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [design-decision-denied] triaged, security input needed [webextensions-security] )
Attachments
(1 file)
2.00 KB,
patch
|
kmag
:
feedback+
|
Details | Diff | Splinter Review |
Updated•8 years ago
|
Reporter | ||
Updated•8 years ago
|
Comment 2•8 years ago
|
||
Comment 5•8 years ago
|
||
Comment 7•8 years ago
|
||
Updated•8 years ago
|
Comment 8•8 years ago
|
||
Comment 11•8 years ago
|
||
Comment 12•8 years ago
|
||
Comment 13•8 years ago
|
||
Comment 14•8 years ago
|
||
Comment 15•8 years ago
|
||
Comment 16•8 years ago
|
||
Comment 18•8 years ago
|
||
Comment 21•8 years ago
|
||
Comment 22•8 years ago
|
||
Comment 23•8 years ago
|
||
Comment 24•8 years ago
|
||
Comment 25•8 years ago
|
||
Comment 27•8 years ago
|
||
Comment 30•8 years ago
|
||
Reporter | ||
Updated•8 years ago
|
Comment 32•8 years ago
|
||
Comment 33•8 years ago
|
||
Comment 34•8 years ago
|
||
Reporter | ||
Comment 35•8 years ago
|
||
Comment 36•8 years ago
|
||
Comment 37•8 years ago
|
||
Updated•8 years ago
|
Comment 39•8 years ago
|
||
Comment 40•8 years ago
|
||
Comment 42•8 years ago
|
||
Comment 43•8 years ago
|
||
Comment 44•8 years ago
|
||
Comment 45•8 years ago
|
||
Reporter | ||
Updated•8 years ago
|
Reporter | ||
Comment 46•8 years ago
|
||
Comment 47•7 years ago
|
||
Comment 49•7 years ago
|
||
Comment 50•7 years ago
|
||
Comment 51•7 years ago
|
||
Comment 52•7 years ago
|
||
Updated•7 years ago
|
Comment 53•7 years ago
|
||
Comment 54•6 years ago
|
||
As it seems some bugs are being closed cause "there has been very little interest" on them i want to confirm that i'm still interested on this bug.
Comment 55•6 years ago
|
||
X2 the prior comment - "i want to confirm that i'm still interested on this bug."
I would think that all users of the 'SingleFile' extension would want it to work in "reader view" mode - currently it will not due to this bug.
Comment 58•5 years ago
|
||
Will Reader Mode become accessible for customisation and/or inject script/CSS?
Are there any plans for it?
I ended up writing the entire thing as a customisation script but it would be better not to duplicate most of the processes that are already provided by the reader-mode.
Comment 59•5 years ago
•
|
||
(In reply to erosman from comment #58)
Will Reader Mode become accessible for customisation and/or inject script/CSS?
Are there any plans for it?
I think we'd be OK with allowing extensions to access the sandboxed iframe containing content only (but not the UI), but I'm not 100% sure how that'd work in practice, and it requires actually doing the sandboxing work (bug 1204818) first, as discussed in previous comments.
Nobody is currently working on any of that work.
Comment 60•5 years ago
|
||
Now when we have "Recommended" a.k.a. "verified" extensions, maybe we could allow them all on reader page?
The fact they are verified should clear all security concerns, right?
Comment 61•5 years ago
|
||
(In reply to juraj.masiar from comment #60)
The fact they are verified should clear all security concerns, right?
No. The verification/review builds on the restrictions already imposed on add-ons by virtue of the limited API surface. Extending that API surface is still a risk; at best it would significantly increase the amount of time that'd need to be spent on reviews / recommendations.
Comment 62•5 years ago
|
||
As an alternative (for now), is it possible to make the text data available via some API?
Currently tabs.Tab
has isArticle
. The code in reader mode selects the text applicable for the reader mode. Is is possible to get that text via an API and/or can it be added to tabs.Tab
?
eg: tabs.getReaderText()
or tabs.Tab
-> readerText
The reason is that I have written customization code for the reader mode (mostly visual and text related) and since Firefox Reader Mode is not customizable, I was forced to duplicate the process of finding the relevant text. Since Firefox already has done it, making the text available would make it possible to avoid a lot of duplicated processes.
Updated•3 years ago
|
Comment 64•3 years ago
|
||
Users, me included, want to redefine fonts of Firefox Reader. You know, to enjoy longreads rendered via Open Sans, PT Serif, etc. Since there is no native GUI way, we have to mess with userContent.css then restart the browser, verify, go back to edit line-height, restart again, etc There are numerous addons that allow to style pages, e.g. Firemonkey by Eros who has contributed arguments and pleas above. All these addons have no access to about:reader. Why? Why the issue got stuck, no traction at all? Err… Hello?
Comment 65•2 years ago
|
||
You should be able to use userChrome.css for that.
Comment 66•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Description
•