New NoScript breaks Xkit for Tumblr

[Raye]

the new Noscript on Firefox makes it impossible for Xkit, a very popular addon to extend Tumblr's functionality, to connect to check for updates. I bring up the list of scripts being blocked and there is nothing there that i can ublock that makes it work, I have had to disable NoScript until this is fixed, unfortunately.

[SmokeRulz]

The patch notes of 10.1.2 say "Fixed background requests from other WebExtensions being blocked." However one of my WebExts, New XKit (https://github.com/new-xkit/XKit), is still getting blocked. It can't update its modules nor can I manually update them without disabling NoScript. Along with my RSS feeds getting blocked (which is now fixed!), this is the only issue I've been having with NS so far. Any ideas why XKit is still getting blocked?

[nar001]

Hello, so I'm using Tumblr with the extension Xkit, that adds a button to its interface, and updates inside the webpage (not sure how it works exactly) but since Noscript was released for 57, it blocks Xkit's ability to update at all, and I'm not sure how to unblock it? Thank you!

[barbaz]

Threads merged.

[barbaz]

The patch notes of 10.1.2 say "Fixed background requests from other WebExtensions being blocked." However one of my WebExts, New XKit (https://github.com/new-xkit/XKit), is still getting blocked. It can't update its modules nor can I manually update them without disabling NoScript. Along with my RSS feeds getting blocked (which is now fixed!), this is the only issue I've been having with NS so far. Any ideas why XKit is still getting blocked?

Is this the same issue as https://forums.informaction.com/viewtop ... =7&t=23725 ?

[SmokeRulz]

Yeah, it's the same issue. The patch notes for 10.1.2 suggested it would be fixed, but it is not.

[barbaz]

Threads merged.

[SmokeRulz]

Xkit patching is still broken in latest NoScript update. (10.1.3c1)

[SmokeRulz]

Still broken in 10.1.4.

[Khaleg]

Hello,

This behavior of blocking access from other add-ons not only happens with Xkit, it is a generalized problem. I am experiencing the same problem with a translator add-on. These translator uses his own dictionary to translate a simple word, but when a phrase is selected it uses the google translate services, or Microsoft services, and another one that I do not remember now. So, when NoScript is enabled, translating only a word works, but translating a entire phrase not. If I disable NoScript both things work, and this behavior is the same even when I have white-listed the google translator services (opening directly google translator and allowing all forever).

Kind regards

[Mathnerd314]

I noticed that my addon (https://addons.mozilla.org/en-US/firefo ... bext-fork/) is broken by NoScript too. My addon uses a content script XHR to load the next page. When NoScript is enabled, it blocks this request with this debug log entry:

Code: Select all

[NoScript] Blocking fetch Object {requestId:"...", url:"...", originUrl:undefined, documentUrl:undefined,method:"GET", type:"xmlhttprequest", timeStamp:1512165065550, frameId:0, parentFrameId:-1, proxyInfo:null, ip:null, tabId:-1}

It seems like this can be worked around for now by allowing requests of type 'fetch' in the default scope (following the little guide in https://forums.informaction.com/viewtop ... =7&t=23974), but NoScript shouldn't be interfering with these types of requests.

[SmokeRulz]

Thinking about it, NoScript might be interfering with Xkit in more ways than just blocking the auto-updates. Certain features the XKit extension uses may not be working at all, perhaps ones that are also fetching things in the background.

[SmokeRulz]

So this is just never getting fixed, then?

[TheLostSkeleton]

I've had NoScript for Firefox turned off since this issue started occurring, and I'm posting to confirm that I just turned NoScript back on only to have "New Xkit" instantly complain that it couldn't contact the update servers.

So, yes, this is still an issue nearly three months later.

I would very much like to see it fixed otherwise I may as well just uninstall NoScript entirely.