Kill Sticky Headers (2013)
alisdair.mcdiarmid.org
Kill Sticky Headers (2013)
1–10 of 84 posts
Re: Kill Sticky Headers (2013)
#2Re: Kill Sticky Headers (2013)
#3Re: Kill Sticky Headers (2013)
#4Re: Kill Sticky Headers (2013)
#5Re: Kill Sticky Headers (2013)
#6Re: Kill Sticky Headers (2013)
#7I'm gonna go out on a limb and say that the majority of users don't use spacebar for scrolling in 2019. Besides that (and the screen real estate), I'm not sure it's bad enough to need a bookmarklet to kill it.
Like halal food, or kosher food in New York, it's not about how many people use a browser feature. It's about how much they care.
Re: Kill Sticky Headers (2013)
#8I'm gonna go out on a limb and say that the majority of users don't use spacebar for scrolling in 2019. Besides that (and the screen real estate), I'm not sure it's bad enough to need a bookmarklet to kill it.
> that the majority of users don't use spacebar for scrolling in 2019
I don't use the spacebar for scrolling, too. But I'm pretty sure there are people who do; and those people care.
> I'm not sure it's bad enough to need a bookmarklet to kill it.
Well, it's bad enough for me that medium.com has a too-giant banner that covers over 30% of the viewport...
At the very least, it was bad enough that I submitted this page, even when I usually don't think that web-trends (like npm, 4MB of JS, 'modern' look of applications, etc...) are bad (opposed to the HN crowd).
Re: Kill Sticky Headers (2013)
#9I'm gonna go out on a limb and say that the majority of users don't use spacebar for scrolling in 2019. Besides that (and the screen real estate), I'm not sure it's bad enough to need a bookmarklet to kill it.
If you are designing the web for people of all abilities, then consideration of space bar scrolling is important.
Imagine the frustration of a user that expects certain behavior of the space bar and experiences something else.
Re: Kill Sticky Headers (2013)
#10I'm gonna go out on a limb and say that the majority of users don't use spacebar for scrolling in 2019. Besides that (and the screen real estate), I'm not sure it's bad enough to need a bookmarklet to kill it.