Won't block 3rd party properly

[NickC]

@SweetP Nope. Still won't work properly. I'm pretty sure it's a bug.
As soon as I add the 2 exceptions all resources get loaded, even if JavaScript is disabled.

[SweetP]

ok, thanks.
Apple has added a bunch of other types we can now block. (not sure exactly when this happened)
With some luck these new types will fix the issues you are seeing

Ill add them into v4 and hopefully get this released this coming week

[NickC]

@SweetP Awesome! Looking forward to testing out the updated version as soon as it comes out.

As I said in my AppStore review, I love the app and it’s granularity. You brought something that was really missing from the AppStore options and made Safari, at least for me, as good as Firefox/Chrome with uBlock Origin enabled.

Have a productive week ahead, Russell.

[SweetP]

Thanks
It’s not the prettiest, and perhaps needs a little more polish to make it more user friendly. But that will have to wait for another update

[SweetP]

Hi @NickC, ive just released v4.0 on my website. the App Store version should hopefully be available after review by Apple later today or tomorrow.

[NickC]

@SweetP I've tried it on another laptop with the fresh v4 from the website. I love the new types and control it allows.

Sadly, the bug still seems to happen. As soon as I add the 2 exceptions (for which I've disabled all types except the document), the page loads everything from 3rd party domains, which is weird.

Maybe the bug is that it ignores the exceptions lists settings for 3rd party types altogether?

[SweetP]

Hmm,
Ok maybe the way I am
Generating the rules is causing the issue. I’ll have another look tonight

[SweetP]

@NickC, ive just released v4.0.1 with a rewritten rule engine which should fix the the issue you are seeing

[NickC]

@SweetP OMG, it works!! You got yourself a fan.

Cannot wait for the AppStore version to update and have this rolled out to all my devices.

[SweetP]

perfect!
thanks for being persistent

The App Store version should be available later today or tomorrow

[NickC]

@SweetP And thank you for the quick fix.

As a side note, does the exceptions list enforce subdomains or just the main domain?
(i.e. research.investors.com vs investors.com)

From what I could tell, if I add just the subdomain (research.investors.com) to the exceptions list, other subdomains (myibd.investors.com, auth.investors.com, etc.) from that main domain get whitelisted as well. Is this a Safari API limitation?

[SweetP]

If you add an exception to a top level domain, it will also apply to all subdomains. To override that you need to also add an exception to any subdomains you want different settings for

[SweetP]

Subdomain exceptions should only apply to that particular subdomain… and also any sub sub domains (if that makes sense)

[NickC]

@SweetP yeah, but now if I add just the subdomain research.investors.com for example, the other subdomains from investors.com get somehow to load JS and what I selected for the research.investors.com subdomain. The root domain doesn’t have a exception added. That is, I just have 1 rule, for the subdomain research.

[NickC]

@SweetP yes, I would think so. But currently it loads other subdomains that are at the same level as it is. Like auth.investors.com gets to load stuff with only the 1 rule added for research.investors.com.

[SweetP]

Odd,
I’ll have a look tonight. But I think my rules are good…

[NickC]

@SweetP This is what I mean; I think it's more clear via a screenshot than what I wrote.
Subdomains shop., services., myidb., and www. all get to load JS.

Could it be a Safari limitation?

[SweetP]

Interesting,
As a workaround, you could set an exception on the top level domain and block everything

[NickC]

@SweetP I tried that and also tried blocking other subdomains explicitly but still they load. It’s weird.
This is probably a corner case, as the bulk of the app is about blocking 3rd party resources.
But with new tracking/fingerprinting scripts being hosted on subdomains they usually pass by unfiltered.

It would be great to specifically add an exception to those pesky subdomains and let all other subdomains load. But currently the exception doesn’t apply if one is permitting JS, all will load regardless.

[SweetP]

This seems like it may be a WebKit issue then