Page 2 of 2
Re: about:reader
Posted: Thu Jun 11, 2015 8:52 pm
by barbaz
Luigi wrote:I'm not quite sure I understand the second part.
If you Allow a domain (e.g. googleusercontent.com) but Mark a subdomain of it Untrusted (e.g. webcache.googleusercontent.com) then the subdomain will be Untrusted but the rest of the domain will be Allowed - IOW, in such a case the Untrusted listing gets priority.
I'm hypothesizing that something analogous is happening to you with about:reader URLs in that about:reader is like the Allowed domain and the site you're viewing in about:reader is like the untrusted subdomain.
(I really think that some feedback from Giorgio or another Mod would be helpful here at this point. Maybe someone else can explain it better.)
Luigi wrote:Does it mean that if wikipedia is untrusted then I can't use the reader on it?
Apparently, yes...
Re: about:reader
Posted: Thu Jun 11, 2015 8:55 pm
by barbaz
BTW, it might help us explain it if you could post the text you get in the tooltip of the about:reader tab when it's trying to view an Untrusted site. It looks from your screenshots like that might be the real URL (as opposed to the "wrong" URL in your address bar).
Re: about:reader
Posted: Fri Jun 12, 2015 7:35 am
by Luigi
barbaz wrote:
I think the about:reader URL is not just "about:reader", but "about:reader?[...]" or "about:reader.[...]".
I tried adding about:reader.[...] to the whitelist but it doesn't do anything. about.reader?[...] is not accepted.
At this point it seems like I have to whitelist a host to be able to use the reader on it but it's absurd.
Re: about:reader
Posted: Fri Jun 12, 2015 7:45 am
by Luigi
barbaz wrote:BTW, it might help us explain it if you could post the text you get in the tooltip of the about:reader tab when it's trying to view an Untrusted site. It looks from your screenshots like that might be the real URL (as opposed to the "wrong" URL in your address bar).
Here's the pic
Regards
Re: about:reader
Posted: Fri Jun 12, 2015 11:57 am
by barbaz
That is a very helpful screenshot. Wonder if it actually is replacing the page's DOM instead of actually navigating the page to the about:reader URL?
Wonder what happens if you try typing that URL in your URL bar and going there directly?
You can get the last part of the about:reader URL as follows: type Ctrl-Shift-K to open the Web Console, and enter this:
Code: Select all
window.encodeURIComponent("https://en.wikipedia.org/wiki/Ian_Craig")
If the URL contains any backslashes, you'll need to replace it with \\
(because the \ is an escape character)
If the URL contains any actual " characters, you'll need to replace it with \"
Re: about:reader
Posted: Fri Jun 12, 2015 2:25 pm
by Luigi
barbaz wrote:That is a very helpful screenshot. Wonder if it actually is replacing the page's DOM instead of actually navigating the page to the about:reader URL?
Wonder what happens if you try typing that URL in your URL bar and going there directly?
It works!
Is there a way I can insert the
about:reader?url= part in the whitelist?
barbaz wrote:
You can get the last part of the about:reader URL as follows: type Ctrl-Shift-K to open the Web Console, and enter this:
Code: Select all
window.encodeURIComponent("https://en.wikipedia.org/wiki/Ian_Craig")
If the URL contains any backslashes, you'll need to replace it with \\
(because the \ is an escape character)
If the URL contains any actual " characters, you'll need to replace it with \"
By the time I understood what you meant I had already transcribed the URL with encodings and all, but thanks
P.S: Any news from Giorgio or other developers?
Re: about:reader
Posted: Fri Jun 12, 2015 3:56 pm
by barbaz
Luigi wrote:It works!
Awesome!
So I suppose you can work around this by starting Reader from a user script menu command that navigates you to the reader URL, instead of invoking Reader the "normal" way.
(I would think it'd make a reasonable NoScript RFE to supply the option to automatically navigate to Reader mode when Reader mode is requested, for any non-whitelisted site
If you want to file one... I'm not sure whether that is better off posted on the end of this thread, or if it should be posted in its own thread in NoScript Development with a link to this thread to illustrate the problem; I'll just go with whatever you decide.)
Luigi wrote:Is there a way I can insert the about:reader?url= part in the whitelist?
You are already doing that by having about:reader in the whitelist.
Luigi wrote:P.S: Any news from Giorgio or other developers?
Giorgio is the only developer, but I'd assume that if Giorgio or the other Mods have something to say, they'd post it here...
Re: about:reader
Posted: Fri Jun 12, 2015 4:42 pm
by Luigi
barbaz wrote:
So I suppose you can work around this by starting Reader from a user script menu command that navigates you to the reader URL, instead of invoking Reader the "normal" way.
Possibly, but it would be more complicated than temporarily allowing the website
I guess I'll study that option (greasemonkey?) if there is no other way with noscript.
barbaz wrote:
(I would think it'd make a reasonable NoScript RFE to supply the option to automatically navigate to Reader mode when Reader mode is requested, for any non-whitelisted site
If you want to file one... I'm not sure whether that is better off posted on the end of this thread, or if it should be posted in its own thread in NoScript Development with a link to this thread to illustrate the problem; I'll just go with whatever you decide.)
Done.
Still, I'm surprised nobody else had noticed this so far...
P.S: I just found this:
viewtopic.php?f=10&t=20741 
Re: about:reader
Posted: Fri Jun 12, 2015 6:18 pm
by barbaz
Luigi wrote:Possibly, but it would be more complicated than temporarily allowing the website
I guess I'll study that option (greasemonkey?) if there is no other way with noscript.
Yeah, Greasemonkey or Scriptish (but the latter seems to be dead). Basically, the guts of it would look something like
Code: Select all
GM_registerMenuCommand('Reader', function(){
let encodedURL=encodeURIComponent(window.location.href)
window.location.href="about:reader?url="+encodedURL;
});
(
Warning: untested!)
Luigi wrote:Still, I'm surprised nobody else had noticed this so far...
It's not that surprising. You (& me too, for that matter
but you more so) partially use the Untrusted list in an "unconventional" manner - we add sites that we intend to visit but are unsafe to Allow due to the nature of the content they host (such as user-provided content that could theoretically come from anyone). Most NoScripters use it only for sites they don't want anything to do with ever. As such, most users probably wouldn't mind having *all* content blocked from sites listed as Untrusted, but such a feature would interfere with our browsing patterns.