Even sometimes I don't pay much attention to it and when after reading other tabs I come back to this tab; all I see is that pop-up standing there, asking for attention. It even makes me forget why I even opened this tab in the first place and makes me leave immediately.
I'll give the ublock list a try.
Your link is exactly right!
Kryptonite would be sticky footers, but if you're on a site that uses those you should just close the tab anyway. :)
That being said I do have a few generic cosmetic filters as part of the list (you can see them near the top of the list) that don't target any specific domain but I don't use the "position: absolute" rule on any of them.
For example I'm working on one site now where a modal lets you sign in (which involves selecting from or searching through a long list of third parties) and if it wasn't a modal it would have to take you to a new page which would be a poor UX.
So long as they're not used for those awful "sign up for our mailing list" purposes, have been set up to work well on all browsers and viewport sizes, and are accessible, I think they can be okay.
A new page is the correct UX design choice and with HTML5 features can make the experience seamless and far less jarring than a modal that needs heaps of testing to get right across all browsers and screen forms.
But that was essentially my original point. Modals, when used by sign up to spam are annoying. When used to do anything else they're essentially trying to replicate a desktop experience that quite frankly isn't required of a website - even on "web 2.0" or full on web applications.
Also, please link an example of a modal done well across all browsers / screen sizes. I simply have never seen one in the wild that works better than an inline page element would have.
Quite often the stickied elements disappear entirely, possibly hidden below other elements or outside of the window--I've never felt the need to check where they go.
Which kind of illustrates my point; I hope your filter list is a whitelist, because in 99.9% of cases, absolutely nothing is lost from these sticky elements. I could've set them to `display:none` or removed them entirely and I think it will still cover my use case perfectly.
I don't think it would be so terrible if `fixed` and `sticky` would go the way of the blink-tag. Except that people would probably reimplement it with JS at expense of performance, because they like nagging people at cost of UX.
[0] it used to be just `fixed`, but `sticky` is used for the same webdisease
My two cents is to automatically apply, but make sure to have a notice when it actually changed something. The only thing worse than a site not functioning correctly is when it's only not functioning correctly for you, and nobody has any idea why, including you.
https://chrome.google.com/webstore/detail/video-autoplay-blo...
My project/uBO filter list removes the "annoying" elements noted above as well as other "features" of websites (e.g. social share bars, cookie notices, etc) through a filter list that works with uBlock Origin.
I update the list often, and admittedly am probably entering into an arms race but I'm just really sick of websites hijacking (what I think) the web was built for (information).
Feel free to subscribe to the filter list by pasting the URL below[1] into the 'Custom' section under the '3rd-party filters' tab of uBlock Origin.
This filter list also works on mobile Firefox for Android with uBlock Origin installed.
[0] Project Homepage https://github.com/yourduskquibbles/webannoyances
[1] https://raw.githubusercontent.com/yourduskquibbles/webannoya...