-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow user scripts for the new Firefox Reader facility about:reader
#2195
Comments
I'll bet dollars to donuts that like other |
I didn't say (although I wanted to) in my initial comment that I have zero knowledge about what my update implied. Perhaps it just opened a large security whole in my browser, but since I use only user scripts written by me, I am less concerned with potential security issues from my own scripts. But, indeed a more knowledgeable person, in the inner workings of both Firefox and Grease Monkey, should look into this. |
What exactly are the steps to launch such an |
For example open the following link, and in the address bar, at the right, just before the reload button there is a small button like a book. Just press it. http://getpocket.com/blog/2015/06/pocket-is-now-built-into-firefox/ (I guess you need the latest Firefox 38.0, and this feature works only on some pages like the one above.) |
Oh, no |
Indeed the address bar still shows the original URL, but if you run inside the console (I applied the patch described in the first comment and it works.) |
e.g. |
This should be in 3.5beta1; let me know what you think: |
Perfect. Works like a charm for reader URL's. Thanks. |
With the latest edition of Firefox, they have integrated the Pocket "reader", which when activated will load a "reading" version of the original page at an URL like
about:reader?...
.However user scripts are not allowed for
about
pages, including theabout:reader
.I've made a small hack in
modules/util/isGreasemonkeyable.js
, by adding a line like the one below just afterif (/^about:blank/.test(url)) return true;
:The text was updated successfully, but these errors were encountered: