fixes brave/brave-browser/5406 (WIP)

[ryanbr]

This a quick fix on an outstanding issue on brave/brave-browser#5406 for skepticalscience.com

Blocking this script will prevent the browser from a lock up. This solution is a temp fix, and could be re-tested/removed in future.

Was re-reported here: https://community.brave.com/t/why-does-this-website-lockup-the-browser/102074/2

[pes10k]

@ryanbr I appreciate the goal here, but I don't think we should merge this if the relevant script is tracking related, w/o at least a better solution planned out. Is this something we could solve with a uBO style replacement?

In ohther words, I'm happy to merge this, but only if @ryanbr you can take it on as an action item to make sure we get a better solution worked out here in the short term (even if its not on you to implement the better solution). WDYT?

[ryanbr]

I'll investigate a better option, atleast we know which script is causing it now.

[diracdeltas]

alternatively we could just allow fingerprinting from skepticalscience.net on skepticalscience.com in https://github.com/brave/brave-core/blob/master/common/shield_exceptions.cc#L41. that might fix it given that the site works fine without fp turned on.

[ryanbr]

The ubo method for reference: skepticalscience.net##+js(aopr, hcdrawticks) though a number of other snippets would do it. Not sure if its worth adding a whitelist for finderprinting.

[pes10k]

@ryanbr @diracdeltas sounds like we have a way forward then? Keep the just-added exception in place until cosmetic filtering lands and hits stable, and then pull it out?

If thats right, @ryanbr can you keep that on your todo list, to pull the just-added exception once cosmetic filtering hits stable?