[Unrelated] Extension Conflict: LibRedirect

[SlowSoap]

Hello! It seems that NoScript and LibRedirect recently stopped playing well together. LibRedirect exists to redirect websites to privacy-respecting alternative frontends. Recently (I'm not sure exactly when, I think probably after the last update of NoScript?) when I click a link to go to, say, tumblr, from my RSS feed or something like that, it will open the page to a blank page with the original URL listed. If I press enter on the URL, then LibRedirect kicks in and allows the redirect to go through.

Does anyone have any settings suggestions that might allow for the redirects to happen automatically again? I understand redirects are generally not a positive behavior, so if no solution is possible, I understand.

I am on Floorp (a firefox fork), using NoScript version 13.6.13

EDIT: Oh a key thing I almost forgot; it particularly doesn't play nice with the frontends that I am self hosting locally. Since they're local, they're http, not https. I'm guessing that has a huge part to do with it. I do have the IP whitelisted, but I don't think that's going to be enough?

[barbaz]

How have you determined that this is a conflict with NoScript?

I am on Floorp (a firefox fork),

Floorp is not a supported browser. Do you see this extension conflict in Firefox and/or Mullvad Browser?

[SlowSoap]

I turned off all my extensions except for LibRedirect and started to enable them one by one until I found the one that seemed to stop the redirect behavior. I made sure to test all of them in a 1:1 pair like this just to be sure.

But if it's not a supported browser then the discussion is moot. Thank you for replying, though! Should I edit my post's subject line to 'closed'?

[barbaz]

But if it's not a supported browser then the discussion is moot. Thank you for replying, though! Should I edit my post's subject line to 'closed'?

Not necessarily. "not a supported browser" means NoScript is not tested on it, we don't know how well it does or doesn't run, and NoScript is unlikely to make code accommodations specific to an unsupported browser. My response mean that in addition to Floorp not being supported by NoScript, we the volunteer Support Team are not able to assist with Floorp or Floorp-specific issues. So to determine how much we can help here, we need to know from you whether or not you see the issue in a supported browser.

If you're not able to test on a supported browser, then sure you can prepend [CLOSED] to your topic title.

If you test and the issue does *not* occur on a supported browser, then we would mark this thread [Unrelated] since that would mean the issue is Floorp-specific, which is outside of NoScript's scope.

If you test and the issue *does* occur in a supported browser, then it's happening in an environment we can test in and help troubleshoot - if we find a solution there, you can figure out later on your side how to apply it to Floorp.

Let us know, thanks.

[SlowSoap]

Oh! In that case, I'm happy to assist. And after snagging Firefox and putting the two extensions on, I can confirm that it works fine on regular Firefox. I'll mark the thread as Unrelated. Thank you for your time!