
Loading…
uBlock's `third-party` filter option does not follow strictly ABP's semantic #114
gorhill
commented
gorhill
commented
Ok I have the code in, commented out, until we can find an instance of a plug-in which works in ABP but not in uBlock.
gorhill
commented
Will wait for a case.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Exposed by #109.
It appears that officially, in ABP,
third-partymeans "third-party according to document in current frame", while in uBlock it is interpreted as "third-party according to document in current tab".Also, for ABP, a plug-in is a distinct document within its own frame. For example, requests to
fwmrm.net, from within a plug-in pulled fromfwmrm.net, embedded inexample.comis interpreted as first-party by ABP (third-party by uBlock).