weird behaviour with forbidding?

[Guest]

why is it that while using the "temporarily allow top-level sites by default" feature, any site you forbid automatically goes to the untrusted list, makes no sense.. is it a bug or feature?

[barbaz]

If you're talking about top-level sites: feature, because otherwise the page would reload and re-Temporarily-allow the top-level site, and you thus *couldn't* Forbid it.

If you're talking about non-top-level sites: I have no idea...

[Guest]

If you're talking about top-level sites: feature, because otherwise the page would reload and re-Temporarily-allow the top-level site, and you thus *couldn't* Forbid it.

If you're talking about non-top-level sites: I have no idea...

i was talking about both, but your first point makes sense, didn't think of that lol. it would be nice though if forbidding non top-level sites didn't make them untrusted.

[barbaz]

Yeah, that behavior for non-top-level sites doesn't really make sense to me either... I don't see why it shouldn't be possible to Forbid a site then later choose to visit it and you *want* it Temp-Allowed then...

Wonder if about:config > noscript.forbidImpliesUntrust is getting automatically flipped to provide the feature for top-level sites?

[hife]

I have noticed the same behaviour. I can understand this for the top-level domain itself, but for other domains, it can be a bit cumbersome, when you're experimenting with allowing different domains to get a site working.