Page 1 of 3

NoScript Webext browser compatibility?

Posted: Fri Sep 15, 2017 6:19 pm
by barbaz
What browsers will NoScript Webext support?

Suppose I install NoScript Webext in a browser that's missing some needed WebExtensions APIs. Will NoScript run but some features do nothing, or will NoScript not work at all? If the former, which NoScript features wouldn't work?

Re: NoScript Webext browser compatibility?

Posted: Sat Sep 16, 2017 6:19 pm
by therube
Got to figure that if it is full webx, there is no longer an install.rdf...

Might find more clues in the comments, https://addons.mozilla.org/en-us/firefo ... /versions/.

Re: NoScript Webext browser compatibility?

Posted: Sat Sep 16, 2017 6:51 pm
by barbaz
Thanks for the reply, but that's not really what I'm looking for. I'm trying to get a sense of how viable it'll be to run NoScript Webext on browsers other than Firefox.
therube wrote:Got to figure that if it is full webx, there is no longer an install.rdf...
Right, WebExtensions use manifest.json instead.

Re: NoScript Webext browser compatibility?

Posted: Tue Sep 19, 2017 2:22 am
by Thrawn
barbaz wrote:Will NoScript run but some features do nothing,
This seems likely.
which NoScript features wouldn't work?
Um...I'm going to assume "whichever ones the browser doesn't support"? Which browser did you have in mind?

Re: NoScript Webext browser compatibility?

Posted: Tue Sep 19, 2017 3:12 am
by barbaz
Thrawn wrote:
barbaz wrote:Will NoScript run but some features do nothing,
This seems likely.
That would be great if so! Image
Thrawn wrote:Which browser did you have in mind?
Currently I'm thinking Chromium or Vivaldi - https://forums.informaction.com/viewtop ... 18&t=22592

I believe both browsers have identical WebExtensions API support.

Re: NoScript Webext browser compatibility?

Posted: Fri Oct 06, 2017 3:50 pm
by barbaz
Bump.

I realise NoScript Webext is not ready for prime time yet. But surely it's known by now which APIs the various features need. And surely it's known which of those APIs are Firefox-specific.

Is that not enough information to know which NoScript features can't work outside of Firefox?

Re: NoScript Webext browser compatibility?

Posted: Fri Oct 06, 2017 4:44 pm
by 4td8s
barbaz, you'll probably have to wait until Firefox 57 officially comes out in November to find out as Thrawn told me here.

Re: NoScript Webext browser compatibility?

Posted: Fri Oct 06, 2017 4:52 pm
by GµårÐïåñ
A lot of the API are actually still not released and won't be ready until 57 is out, which means even if you know what you need, you don't have it yet to use.

The 57 rollout (by which I mostly mean the WE framework) has been a hasty one and they have left too much for the 11th hour which is very irresponsible and sure to lead to a lot of chaos, but such is the world we live in and just have to make due.

Re: NoScript Webext browser compatibility?

Posted: Fri Oct 06, 2017 4:56 pm
by barbaz
4td8s wrote:barbaz, you'll probably have to wait until Firefox 57 officially comes out in November to find out as Thrawn told me here.
That's about the actual release of NoScript Webext. The fact that it's already known to require at least Firefox 57 release, means it's already known which WebExtensions APIs it needs, doesn't it?

Re: NoScript Webext browser compatibility?

Posted: Fri Oct 06, 2017 6:06 pm
by GµårÐïåñ
barbaz wrote:... means it's already known which WebExtensions APIs it needs, doesn't it?
Correct, but knowing what you gonna need and actually having it available are two entirely different things my friend.

Re: NoScript Webext browser compatibility?

Posted: Fri Oct 06, 2017 6:40 pm
by barbaz
So is it not actually known yet which of the needed APIs will only be available in Firefox?

Re: NoScript Webext browser compatibility?

Posted: Fri Oct 06, 2017 7:20 pm
by GµårÐïåñ
barbaz wrote:So is it not actually known yet which of the needed APIs will only be available in Firefox?
No, see it this way, you know what API you plan to make, you know what those API require, and you can even preview them but they may not be completed yet, fully available yet, or even fully functional yet. So a combination of all that makes for a very slow and methodical approach because say you code based on today's draft and in two weeks, it is completely redone, you will lose all that extra work, so in some complex situations, you prefer to wait until it is "finalized" and release ready before you start dropping it into your code, lest you risk having to rewrite everything and create discontinuity with your users. Make sense now?

Re: NoScript Webext browser compatibility?

Posted: Fri Oct 06, 2017 7:34 pm
by barbaz
Ok, so you're saying the needed APIs are not only not implemented yet, but still in flux, so it's still too early for my questions to have answers.

Thanks GµårÐïåñ and 4td8s.

Re: NoScript Webext browser compatibility?

Posted: Fri Oct 06, 2017 7:43 pm
by GµårÐïåñ
barbaz wrote:Ok, so you're saying the needed APIs are not only not implemented yet, but still in flux, so it's still too early for my questions to have answers.
Correct. Unfortunately somewhat so.

Re: NoScript Webext browser compatibility?

Posted: Tue Nov 07, 2017 1:20 pm
by barbaz
Firefox 57 is now in release and only a week away from coming out. Is it still too early for my questions to have answers?