I'm sorry, but fixed headers are almost always a bad idea, because it make assumptions about the clients that may not be valid. The assumption is that the client has the vertical space for a fixed header.
Even the example is shown for a client that has plenty of vertical space. If the user is on something like a 13" laptop, the fixed header reduces the amount of "usable" space on the page.
Unless you're absolutely sure that the client is on a big monitor, and has a browser window that's higher than it is wide, don't use fixed headers.
Interestingly enough you rarely see website/webapps that utilises the fact that most users are on wide-screen monitors (mobile excluded).
Mmm, I'm one that dislikes fixed position headers as they and take up space most times without providing much added value, but perhaps for some that Github more frequently it could be useful to always have the search and top links available. From the title I was expecting something for blind readers of similar.
Also as side note 'static' in CSS actually refers to to elements that stay in their original position within the flow of a document, while 'fixed' means always display it at the same position in the browser window even while scrolling. The spec terminology could be a bit clearer to be honest.
I'd normally just use a shortcut to search. I'm used to the `/` key for search (I notice Gmail uses it), but for Github the shortcut is `s`. One that I use a lot for Github is `t` to search for files in a repository.
This seems wonderful, especially for mobile. A quick search of AMO and google doesn't turn up anything similar for Firefox. Anyone know of a similar Firefox extension?
Oh! for a second I thought this was an "official" feature release. Not an improvement IMHO.
But for me this illustrates the "killer app" of browser extensions, that you can customize the sites you use every day and are not dependent on them implementing a certain feature.
Better accessibility? Just to note that position fixed with an input element receiving focus will break on iOS. Its a long-standing bug with very few work-arounds.
(that said, I realise you can't apply these styles to iOS anyway, it is a mute point).
Even the example is shown for a client that has plenty of vertical space. If the user is on something like a 13" laptop, the fixed header reduces the amount of "usable" space on the page.
Unless you're absolutely sure that the client is on a big monitor, and has a browser window that's higher than it is wide, don't use fixed headers.
Interestingly enough you rarely see website/webapps that utilises the fact that most users are on wide-screen monitors (mobile excluded).