Code: Select all
||*-a.akamaihd.net/a24/gsd.html?$third-party
||*-a.akamaihd.net/a24/scripts/gsd.js?$third-party
Code: Select all
||*-a.akamaihd.net/a24/gsd.html?$third-party
||*-a.akamaihd.net/a24/scripts/gsd.js?$third-party
Yes, the problem was in uBO, not EasyList. Fixed with 72fdce64f0cd9ee763032e9bb340658086ffd987.WarFame wrote:https://github.com/gorhill/uBlock/issues/1669#issuecomment-224822448
Code: Select all
||*www.example.com/foofoofoo
www.example.com/foofoofoo
https://github.com/gorhill/uBlock/issue ... -164430835barbaz wrote:How is the wildcard in the first different from the implied wildcard on the left of the second?
Code: Select all
[0-9A-Za-z]
Code: Select all
[^0-9A-Za-z]
Code: Select all
||*www.example.com/foofoofoo
*www.example.com/foofoofoo
Then `www` won't be used as a token to store the filter, another token will be picked It's just how uBO stores its filters internally.barbaz wrote:What if the leading wildcard is explicit?Code: Select all
||*www.example.com/foofoofoo
*www.example.com/foofoofoo
I mean are the filters equivalent in terms of what they block? lewisje seems to think not.gorhill wrote:Then `www` won't be used as a token to store the filter, another token will be picked It's just how uBO stores its filters internally.
It's about my custom lists, and it's not specifically about the domain-anchor case. First off, uBlock Origin's use of word boundaries means my lists can surely get significantly shorter and more effective. There were times I added like 3 or 4 filters where if I had known about this behavior only one (better) filter would have been needed.gorhill wrote:Why the "seems like I've got a lot of filter reworking to do..."?