Globally disabled NoScript is blocking scripts with name containing "fingerprint"

[BenCrulis]

I was testing noscript navigation for a while but then I globally disabled restrictions in the the extension options.

After that I added the file fingerprint2.js to the website I am working on. To my surprise, it wouldn't load although all other scripts functioned perfectly. I didn't think about noscript at first and tried changing the file location, its encoding, the line breaks, removing the number in the file name, checking the HTML... It was weird since I had another script on the same page (named script.js) which was running perfectly. A warning was displayed into the Firefox console but provided no explanation to why fingerprint2.js was not loaded. Using the link loaded the file correctly and allowed me to look at its content, which was correct. I tried to create a completely new file with the same name but it was also blocked, so I started to suspect something.

When it became clear that Noscript blocked the file based on its name, even though it shouldn't as it is set to not block anything by default, I came here to file an issue.

Steps to reproduce:

• allow scripts globally in the Noscript options
• create a file named fingerprint.js or fingerprint2.js
• make it be loaded by an html file hosted somewhere
• navigate to the page
• assert that the script was blocked with a vague warning from Firefox in the web console

If this behavior is considered normal, could it be possible to provide a bit more information on the reason of the blocking so that it is clear that noscript is responsible for it?