@media (max-height: 700px) {
.My-Sticky-Header-Selector {
position: absolute;
}
}Kill Sticky Headers (2013)
11–20 of 84 posts
Re: Kill Sticky Headers (2013)
#12Even without that feeling, sticky headers kill the feeling that I'm moving through a viewport of a webpage. It makes your website look like it's not of the "webpage" medium that I've been familiar with for 20 years. Humans have a very good eye for relative movement. The visual processing part of your brain considers movement much more contrasting than color. So a fixed header when you're scrolling at 1cm/second is visually equivalent to a big bar moving upward at 1cm/second while you're trying to read an article. It's hard not to pay attention to it. But navbars don't contain content, so they shouldn't steal attention from the page content.
Re: Kill Sticky Headers (2013)
#13Re: Kill Sticky Headers (2013)
#14Re: Kill Sticky Headers (2013)
#15Great hack to manipulate the DOM with a bookmark!
javascript:(function(){
document
.querySelectorAll(
'[style*="font"]'
).forEach(elem =>
elem.removeAttribute(
'style'))
})()Re: Kill Sticky Headers (2013)
#16I'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.
I guess you can make the same argument that it's possible that people don't use PgDown/PgUp either, but that's besides the point, I think.
Generally, interfaces have a lot of features by default and when a particular interface breaks or removes them for no good reason (and I don't think I've ever seen a sticky header that could justify it), well that at least leaves a very bad impression. It's wasteful.
Same goes for links and buttons which are made to work only when clicking with the mouse, when by default they work with the keyboard too. Same goes for text which is set with a fixed width and necessitates a large minimum window width to read properly when by default text adjusts to a window's width. etc.
Nobody is average, so the world would suck if it only worked for the average.
For the record, I do scroll with the spacebar. I like to skim pages as quickly as possible, and PgDown is in different positions in different keyboards, so I just find spacebar to be super-accessible.
Re: Kill Sticky Headers (2013)
#17there's a more advanced version of this that is an extension. it offers a fixed delay, adjustable per site. so you can nuke slide-overs and html5 popups as well. it isn't perfect but it's still a useful tool. sorry i don't have the link handy as i'm not using that extension currently.
Re: Kill Sticky Headers (2013)
#18I'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.
Re: Kill Sticky Headers (2013)
#19I'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.
The issue that was raised isn't just about the Spacebar. It's about scrolling by full-pages, so PgDown/PgUp would also have the same problem when a page has Sticky Headers. I guess you can make the same argument that it's possible that people don't use PgDown/PgUp either, but that's besides the point, I think. Generally, interfaces have a lot of features by default and when a particular interface breaks or removes th…