5 ms·

If you haven't noticed, the New Yorker also redesigned their top navigation. It's a brilliant design from https://twitter.com/mimicdecipher https://twitter.com/

If you haven't noticed, the New Yorker also redesigned their top navigation. It's a brilliant design from https://twitter.com/mimicdecipher https://twitter.com/mimicdecipher and implemented by https://twitter.com/erik_erikson https://twitter.com/erik_erikson

conorh 11y ago
I find these sticky top navs extremely annoying. I like to have the entire screen for reading, rather than partially obscured by an unnecessary header, I'm quite capable of going back to the top of the page if I need the nav thank you.
- deleted 11y ago
  [deleted]
ableal 11y ago
My laptop noticed, and started its fan singing in praise. Had to go into reader mode to pull Firefox down from 50% CPU.
- biot 11y ago
  Maybe that's a Firefox bug? Not having to redraw a section of the screen should consume less CPU, not more.
  - Raphmedia 11y ago
    If it's done wrong, it may reposition itself every millisecond while you scroll, which could make it a pain for your browser's performance.
Strilanc 11y ago
That "brilliant design" is permanently wasting 15% of the screen real-estate on showing buttons irrelevant to reading the article. (Why is it pinned??)
- yoodenvranx 11y ago
  I HATE those navigation bars (especially when I read in landscape mode on my mobile) and I wish there would be some kind of "ad-blocker" to get rid of them.
  - pre 11y ago
    I hate them 'em enough to had made a bookmarketlet to zap 'em. https://github.com/revpriest/unfix https://github.com/revpriest/unfix
    - yoodenvranx 11y ago
      Thx for the link!
bazzargh 11y ago
I'm with the others in that I don't like fixed content (particularly in landscape mode on phones), but I have seen a variation that works better; hide the nav when the user scrolls down, show it when the user scrolls back up. Safari on iphone does a similar thing with the back/forward buttons.
- Nemo157 11y ago
  I hate most implementations of those more than fixed bars, I regularly scroll slightly too far when I take a second longer to read a line than I was expecting and need to scroll back to see what I missed; then out of nowhere a massive header pops down and covers both what I was trying to read and the next 3 lines so I have to scroll back even further and any flow state is completely interrupted. Safari on iPhone is one of the few implementations that actually works well, playing round with it a bit now it looks like it has quite a few heuristics to determine when to expand again. I guess most people don't care enough to actually spend the time adding more than just "show on drag down".
- deleted 11y ago
  [deleted]

conorh 11y ago

I find these sticky top navs extremely annoying. I like to have the entire screen for reading, rather than partially obscured by an unnecessary header, I'm quite capable of going back to the top of the page if I need the nav thank you.

deleted 11y ago
[deleted]

ableal 11y ago

My laptop noticed, and started its fan singing in praise. Had to go into reader mode to pull Firefox down from 50% CPU.

biot 11y ago
Maybe that's a Firefox bug? Not having to redraw a section of the screen should consume less CPU, not more.
- Raphmedia 11y ago
  If it's done wrong, it may reposition itself every millisecond while you scroll, which could make it a pain for your browser's performance.

Strilanc 11y ago

That "brilliant design" is permanently wasting 15% of the screen real-estate on showing buttons irrelevant to reading the article. (Why is it pinned??)

yoodenvranx 11y ago
I HATE those navigation bars (especially when I read in landscape mode on my mobile) and I wish there would be some kind of "ad-blocker" to get rid of them.
- pre 11y ago
  I hate them 'em enough to had made a bookmarketlet to zap 'em. https://github.com/revpriest/unfix https://github.com/revpriest/unfix
  - yoodenvranx 11y ago
    Thx for the link!

bazzargh 11y ago

I'm with the others in that I don't like fixed content (particularly in landscape mode on phones), but I have seen a variation that works better; hide the nav when the user scrolls down, show it when the user scrolls back up. Safari on iphone does a similar thing with the back/forward buttons.

Nemo157 11y ago
I hate most implementations of those more than fixed bars, I regularly scroll slightly too far when I take a second longer to read a line than I was expecting and need to scroll back to see what I missed; then out of nowhere a massive header pops down and covers both what I was trying to read and the next 3 lines so I have to scroll back even further and any flow state is completely interrupted. Safari on iPhone is one of the few implementations that actually works well, playing round with it a bit now it looks like it has quite a few heuristics to determine when to expand again. I guess most people don't care enough to actually spend the time adding more than just "show on drag down".
deleted 11y ago
[deleted]