A few sites have recently deployed scrolling nav bars. (Twitter is one example.) A scrolling nav bar starts at the top of the page and then follows you as you scroll down and up the page.

I think this design pattern makes a lot of sense when mimicking an application command bar or where there will be a high level of interaction or notifications. (I'm actually surprised Facebook hasn't adopted this yet.) Beyond that, I'm not sure when it should be used.

When should scrolling navigation bars be employed?

1 Answer 1


Generally, while contents that don't fit the screen should be scrolling, controls that affect display or modify content should not. In the "early www", scrolling on-page navigation controls out of view were a result of the limited presentation capabilities, but they also made it simpler: You always scroll the entire page.

The "classic" desktop solution is a non-scrolling region. The in-browser solution of frames or iframes has some usability drawbacks though, e.g. with respect to bookmarking and forward/backward navigation.

The "float animation" draws attention to the navigation controls, in most cases this is excessive in my opinion, as it makes the controls appear more important than the content. (But probably it's the best possible solution). OTOH it is an interesting option to promote new or changed functionality.

From these thoughts I'd conclude: For a nonlinear page with nontrivial controls (i.e. more than just simple page navigation), fixed-location controls are advisable. Try to avoid undue flashiness of the animation involved.

  • Don't like those "floating" things either. Very distracting. And most of the time unecessarily, as the links aren't that important and can always be found by a simple Ctrl-Home to get to the top of the page. Apr 16, 2011 at 20:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.