Kill-sticky, a bookmarklet to remove sticky elements and restore scrolling

Re:Kill-sticky, a bookmarklet to remove sticky elements and ... by gumby on Tuesday September 27, 2022 @07:30PM (#33002486)

Or those stupid floating bars that cover the top of the screen, so when you press space to scroll a line or two is obscured. What are they thinking?

[ Parent | on HN ]

Re:Kill-sticky, a bookmarklet to remove sticky elements and ... by Lio on Wednesday September 28, 2022 @05:11AM (#33005966)

I've heard them called "vanity flaps", which seems to describe them perfectly.

I guess they're useful when the content is of low quality but you're desperate to keep eyes on the name of your site.

I hate them.

About the only thing worse than self-hiding vanity flap is a floating side bar using a slow animation to slide back into your field of view, just terrible.

[ Parent | on HN ]

Re:Kill-sticky, a bookmarklet to remove sticky elements and ... by wruza on Wednesday September 28, 2022 @06:41AM (#33006486)

slow animation to slide back into your field of view

I have a special section in my uBlock user rules, and it is full of annoyances like this.

Another one is an element with popup on hover, but you can only close it by hover-unhover a popup itself. Fly across such element by accident and enjoy your semi-modal “no idea how to get rid of”-popup without even clicking anywhere.

[ Parent | on HN ]

Re:Kill-sticky, a bookmarklet to remove sticky elements and ... by wruza on Wednesday September 28, 2022 @06:32AM (#33006436)

I believe this is a collective failure. First, developers praise the web/html/css ways to do things and want nothing more. Then they meet a complex layout problem (page-scrolling of an element which is partially covered) and find no solution, because they got what they wanted and nothing more. Nobody reports it as a bug or a FR, or it gets scrutinized as “Do we really need it? Here is a complex way to do that, incompatible with most designs, but doable, right?” and then gets closed as inactive, cause nothing adequate can be commented upon it. Developers develop selective blindness to very obvious layout bugs. The cycle repeats.

So many hours spent on nothing when a simple `viewport-offset-{top,…}: 20px` could solve it once and for all. Instead we will support global nonsense described in the article for years, despite it stays nonsense at any angle.

[ Parent | on HN ]