It seems as if not all divs that can be blocked by ublock origin, appear via the GUI as filterable option

[rubyFeedback]

Off-topic comment first - you can safely skip the first paragraph that comes next:

Ok first off - I had to create this discussion, because when I tried to create a new issue here,
the strange pop-up constantly redirected me to "report here instead" and I could never (!!!)
find where I could file a new issue. Perhaps to those who handle those 8 templates or
so - could you guys perhaps consider going back to oldschool simplicity? I have beein
using github issue trackers for many years, and those gazillion templates that try to
redirect people, are so annoying. At the least add a simple "report issue here (blank)"
or something like that. I understand you guys want people to classify in categories,
but HOW should they find the correct category WHEN THEY ARE CONSTANTLY REDIRECTED
and then upon trying again, "add issue", the same template is opened? That is just
annoying. And no, I don't see where I should report it because of that added complexity.

Keep. It. Simple. Guys.

Now to the issue at hand.

First you may be able to see it on webpages like this:

https://www.studocu.com/de-at/document/universitat-wien/vegetationsokologie-und-landschaftsokologie/vegetationsoko-altfragen/23630262

These guys use annoying custom pop-ups to distract people and try to force them to "switch
to paid version", so that these pop-ups and slide-ins don't appear.

Thankfully, using ublock origin, we can filter these evil and distracting slide-ins. But interestingly
enough, this does not work for all elements. Some elements I can not click at all.

I have a partial screenshot for this:

https://i.imgur.com/uhh5RqJ.png

So if you go there, the issue are those colourful round boxes:

green, purple and blue.

When I open ublock origin, I can not detect them. I have not looked at the source,
I assume these are special divs that may be overlaid by other divs?

I can try to look at it at a later time. For now I'd just like to report this,
that ublock origin can not always select the correct div. It may be nice to
be able to select different layers or however this is done by such websites.

It is not the end of the world, as I can scroll and thus focus on readable
text that is not blocked, but still I think it would be better if ublock
origin itself would be a bit more powerful. Keeping the UI simple is
good, so I don't mind that, but I think it would be nice to be able
to select such sneaky div elements in a more flexible manner too. Perhaps
there could be an additional option or so, "scroll through div elements"
via the middle mouse button; or anything like that. I think this may
already be possible, actually, but I haven't found the proper option
yet - I'll do more research after that, as I am sure this will annoy me
in the coming weeks too.

[Yuki2718]

I don't see such any colorful staff.

[gothic-bum]

Unable to reproduce using multiple browsers that have only uBO installed. There are no "colourful round boxes" as shown in your screenshot.

Test again using a new browser profile (Firefox ideally) with only uBO installed. Keep everything at the default settings.

[freezer2022]

I can reproduce (tried only on Firefox), it's a duplicate of:

• studocu.com: nuisance uAssets#24663
• www.studocu.com AdguardTeam/AdguardFilters#171393

to reproduce I needed to spend few minutes on the page, and scroll the page down and up few times, perhaps to click / interact with few buttons, then the popup has been triggered.

it's a paywall, so it's not going to be addressed, but the same old custom filters provided in the aforementioned threads seem to be still partially working, but they need to be updated to work at 100%.

---

rubyFeedback: It is not the end of the world, as I can scroll and thus focus on readable text that is not blocked, but still I think it would be better if ublock origin itself would be a bit more powerful

You judge too quickly and too hastily - uBO is powerful enought, it's just websites sometimes use some tricks to make it difficult for uBO, and then it's required to use some advanced syntax to fix the issue, which you're unaware of. Next time wait for response from uBO devs before judging in the advance.