Prevent Clean Links Extension from processing sites having content blockers disabled in their website settings

[gkarag]

When the Extension is enabled it interferes with some web pages, for example the configuration pages of tasmota open source firmware, causing javascript errors like "XMLHttpRequest cannot load … due to access control checks". The problematic behavior stops when I disable the extension in the Safari Preferences. While this problem is perhaps worth investigating, I would propose a workaround: prevent the extension part of Clean Links from processing websites on which the content blockers are disabled.

[Sh1d0w]

Hi,

thanks for the report and the suggestion. However I am not sure this is the correct solution to the issue. As you can see, my plugin is shipped with two extensions - the parameter cleaner extension and a content blocker extension. The user can use either of one of two separately or both at the same time if they wish. If I make this change what you are proposing, then it will make the later one dependent on the other and could no longer be used separately, which some users may find convenient.

Maybe a way to disable the extension for a given website sounds like a better idea, like a quick button in the fingerprint menu that the extension already have. So you can toggle it on / off for the current website from there permanently?

[gkarag]

I would speak for myself, I don't have cases in which I would use one of the extensions enabled and the other one disabled for a particular site. For me both serve as kind of content blockers and I would enable and disable them per site both in the same time. Managing own list of websites offers maximum flexibility indeed, but in my opinion it would cost time to implement and test and for me as a user it will need me to maintain yet another list. For that reason I would propose the workaround, at least as a start. How about a general setting of the parameter cleaner extension that makes it respect the content blocker preferences for the sites in addition to the workaround?