Andrey Meshkov

Results 1060 comments of Andrey Meshkov

Sounds as if it should be handled via rules conversion isn't it? * `[data-testid="primaryColumn"]:others()` -> `:not([data-testid="primaryColumn"])`

I might be missing something, but `:not(selector)` seems to be exactly the same thing as `selector:others()`. As I recall, `:not` is not fully supported in uBO, maybe that's the reason...

Есть приличный шанс что `:has` мы теперь нативно применяем, его же в браузеры добавили. Попробуйте `document.querySelectorAll` протестировать в браузерной консоли, отличается ли результат?

I assumed it does from the issue text: > Ublock Has :others() Operator..Which Keep Only A Selected Element Of A Page And Remove Everything Else..This Is Very Useful For Link...

Ah, then it's even easier, `{ remove: true }` is not needed.

Ah, now it makes perfect sense to me, thank you!

Then I guess it can be rewritten this way, right? `[data-testid="primaryColumn"]:others() -> :not(:has([data-testid="primaryColumn"]))` edit: ah, nope, it cannot, won't cover the elements inside `[data-testid="primaryColumn"]`

`$removeparam` rules are converted with some serious limitations at this moment. We hope to improve this in the future, though.

> Wouldn't it be possible to "enable" the rules that work now and then consider limitations in the future? It will be possible to use AdGuard URL Tracking Protection list...

Generally, it won't affect anyone. The rules that use `:remove()` will be automatically converted to the ExtCSS syntax, we just don't want to have this logic in two places (ExtCSS...