News for hackers. Stuff that matters.
Re:Ask HN: Projects that don't make you money but you're doi... by tripzilch on Friday August 11, 2017 @12:46PM (#14991721)
I've been using a bookmarklet approach (named "FIXEDFIXER") that aggressively changes all `position:fixed` and `position:sticky`[0] to `position:static`. (I've posted the one-liner code a couple of times before already, can repost on request)

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

Re:Ask HN: Projects that don't make you money but you're doi... by kbenson on Friday August 11, 2017 @02:52PM (#14993009)
> 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.

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.