-
Notifications
You must be signed in to change notification settings - Fork 435
Fail to block non-direct adressed elements #1810
Comments
tested with ###somename sitekeys |
Thanks for reporting an issue. sitekey is not supported. Can you give me a specific use case to help me replicate the issue? |
www.reddit.com###header-bottom-left > .tabmenu > li:nth-of-type(3) > .choice[href="https://www.reddit.com/new/"] an example |
Seems to be my installation related, a little video coming soon. |
Basically |
And yes, i know how to, since using this module long time. |
We are able to replicate this issue. This fix will be included in the next version release (in a couple of days). Thank you very much. |
Thank you |
But for now only reddit is fixed. Tried for example on DA, blocked logo frame (###deviantart-logo > .mark > svg > .wikistick) - as usual don't work for now. |
We haven't released build (v0.9.5.19) yet. It is under QA. I think you will get an update early next week. |
Hi, Can you please verify it your end if you have received v0.9.5.19 update? |
Seems to be site-specific. Will look into it. |
Not working again, same reddit, just noticed. Some sited are good, some - still do not work. Maybe better switch to Origin, there it's fine.... |
Browser related, it just sorta broken now. Gonna reinstall, probably NOT use chrome |
Thanks for your valuable inputs. There is a lot of area of improvement in Element picker. We will target it in the near future. |
Started not so long time ago, latest Chrome (actually detected on some early platform, like 74 at latest builds)
It looks like your rules about blocking of page elements simply don't work, unless it's an image.
The text was updated successfully, but these errors were encountered: