7 ms·

Is the header sticky for anyone else? It seems to take up ~30% of my screen (Windows 7, Chrome Stable) [0]. [0] http://puu.sh/pNYUH/d42d8395fc.jpg http://puu.

Is the header sticky for anyone else? It seems to take up ~30% of my screen (Windows 7, Chrome Stable) [0]. [0] http://puu.sh/pNYUH/d42d8395fc.jpg http://puu.sh/pNYUH/d42d8395fc.jpg

thesimon 10y ago
Same on Chrome & Safari on Mac, but didn't notice it while reading, only when I read your comment :)
- miahi 10y ago
  Exactly the same. I had to open the page again to see that there's a huge header.
- alexpetralia 10y ago
  Same here, just noticed upon rechecking
ipp 10y ago
It leaves just a little over half of a laptop screen for actual article content.
stephengillie 10y ago
Try disabling JavaScript. Without that, other than some iframe code up top, everything seems to display correctly on mobile Chrome.
- deleted 10y ago
  [deleted]
wlesieutre 10y ago
This bookmarklet was well received last time I mentioned it, so I'll link it again: https://alisdair.mcdiarmid.org/kill-sticky-headers/ https://alisdair.mcdiarmid.org/kill-sticky-headers/ Finds anything with position:fixed and deletes it. Reload the page to get the elements back if needed.
- ivanca 10y ago
  A more sensible solution would be to convert all fixed elements into "position: absolute" ones. That is less prone to cause errors and avoids impeding navigation.
  - tokensimian 10y ago
    You are correct. However, the sites that do the overkill of a sticky header tend to also have poorly thought out site navigation and user experiences. Let's say on a normal site, killing any absolute nav would result in a 5%* decrease in UX. On a site like this, killing any absolute nav might result in a 5% increase in UX.
  - 746F7475 10y ago
    But that doesn't work as well, since for example on this page there is JS event tied to scrolling the page that moves the header with you. So you'd have to tie your own anti-move trigger to the same event, which might mean same script won't be universal. If you just remove the header with a script, you can still get to the navigation by refreshing the page.
    - ivanca 10y ago
      I actually just tried in this page and it works perfectly even before any scrolling has happened by just using "position:absolute !important" in the "position:fixed" elements;
  - wlesieutre 10y ago
    You'd think so, but I've seen a lot of websites that dump a sticky "social sidebar" on top of the content, and if it's absolutely positioned you can't read the stuff that it's stuck in front of.
nchelluri 10y ago
It bothered me as well so I unchecked the width rule on the col-sm-7 CSS class (in the browser inspector) and then saw more text per screen which helped.
krallja 10y ago
Yes. Firefox Reader View fixed that problem for me.
- kalleboo 10y ago
  Safari Reader Mode worked a treat over here
rmsaksida 10y ago
Yep. Had to right click, inspect element, delete the header element. Article is unreadable otherwise.

Is the header sticky for anyone else? It seems to take up ~30% of my screen (Windows 7, Chrome Stable) [0]. [0] http://puu.sh/pNYUH/d42d8395fc.jpg http://puu.sh/pNYUH/d42d8395fc.jpg

thesimon 10y ago

Same on Chrome & Safari on Mac, but didn't notice it while reading, only when I read your comment :)

miahi 10y ago
Exactly the same. I had to open the page again to see that there's a huge header.
alexpetralia 10y ago
Same here, just noticed upon rechecking

ipp 10y ago

It leaves just a little over half of a laptop screen for actual article content.

stephengillie 10y ago

Try disabling JavaScript. Without that, other than some iframe code up top, everything seems to display correctly on mobile Chrome.

deleted 10y ago
[deleted]

wlesieutre 10y ago

This bookmarklet was well received last time I mentioned it, so I'll link it again: https://alisdair.mcdiarmid.org/kill-sticky-headers/ https://alisdair.mcdiarmid.org/kill-sticky-headers/ Finds anything with position:fixed and deletes it. Reload the page to get the elements back if needed.

ivanca 10y ago
A more sensible solution would be to convert all fixed elements into "position: absolute" ones. That is less prone to cause errors and avoids impeding navigation.
- tokensimian 10y ago
  You are correct. However, the sites that do the overkill of a sticky header tend to also have poorly thought out site navigation and user experiences. Let's say on a normal site, killing any absolute nav would result in a 5%* decrease in UX. On a site like this, killing any absolute nav might result in a 5% increase in UX.
- 746F7475 10y ago
  But that doesn't work as well, since for example on this page there is JS event tied to scrolling the page that moves the header with you. So you'd have to tie your own anti-move trigger to the same event, which might mean same script won't be universal. If you just remove the header with a script, you can still get to the navigation by refreshing the page.
  - ivanca 10y ago
    I actually just tried in this page and it works perfectly even before any scrolling has happened by just using "position:absolute !important" in the "position:fixed" elements;
- wlesieutre 10y ago
  You'd think so, but I've seen a lot of websites that dump a sticky "social sidebar" on top of the content, and if it's absolutely positioned you can't read the stuff that it's stuck in front of.

nchelluri 10y ago

It bothered me as well so I unchecked the width rule on the col-sm-7 CSS class (in the browser inspector) and then saw more text per screen which helped.

krallja 10y ago

Yes. Firefox Reader View fixed that problem for me.

kalleboo 10y ago
Safari Reader Mode worked a treat over here

rmsaksida 10y ago

Yep. Had to right click, inspect element, delete the header element. Article is unreadable otherwise.