this issue seems to be clear now - i will mark this as 'confirmed'

I don't think that any examples of this behavior are necessary because I understand the issue.

The confusion here is that LibreJS will put scripts in the "Blocked" category when the parser can't parse them, which in this case is caused by the script being a 404 error.

LibreJS does this because it wouldn't be logical to do anything but  deny scripts that the parser can't make sense of.

i still dont understand this problem exactly but going only by the literal meaning of words i see here - i would have to say that it is not acceptable behavior to throw an error because of a missing script - even so it is a network error and not a parsing error - the browser itself has no problem with missing scripts - they are uneventful i.e. not worth mentioning except for debugging - it just keeps rendering what is can - librejs should do the same - the only information librejs should display should be related to freedom issues

again i am perhaps misunderstanding - id like to see if andrew will clarify this one

trying to confirm this but both of the links given are non-exiting pages - can you find an example page that demonstrates this bug?

also, regarding the problem description: "missing javascript files fail to properly parse" - could you clarify what is the the actual error? - obviously a file must exist in order to be successfully parsed but what demonstrable problem does this cause?

note that libreJS v0.7 is a nearly total re-write; so this issue very likely refers to only one of them

can you specify which version of libreJS this behavior apllies to?

if this behavior is seen using libreJS v0.6, could you try libreJS v0.7 on a firefox derivative >= v57 to see if the same issue still exists?