Sure, it's possible, but I strongly recommend against it. Users find such non-intuitive features extremely disagreeable.

If you want to pursue it, research "JavaScript scrolltop" to point you in the right direction.

The issue is this: when thousands of users visit hundreds of thousands of pages, and the vast majority handle navigation a certain way, then, right or wrong, that becomes the expected way. It's called "User Expecatation" or "The User Model". Then, when your site violates that expectation, it creates irritation and annoyance: an unpleasant experience.

The only way to break through this is if your site COMPLETELY breaks the User Model - nothing is as expected, and the user is forced to "start over" and explore the new model. Some good examples are Flash sites: http://www.nike.com/nikeskateboarding/v2/main.html

So unless you want a completely avant-garde site, avoid scrolling menus!

Guess, I'll bear in mind your suggestion in that case.

In fact, the reason, I thought of doing so, was cos of having a rather LONG page (such as "Whisky"), so in order to visit to different page, the user would've to scroll all the way up, which some might find little annoying.

However, in order to get rid of this frustration, I'll simply "split" such long pages into different pages, so user can access the sub-section through the "sub-menus" (as is the case, presently).

I'm thinking (theoretically) you could accomplish this using only CSS (no JavaScript) by encasing the menu in a <div> and absolutely positioning relative to the top left coordinate of the browser window? Not entirely sure if it will scroll with you this way though ... I guess you would need to introduce DHTML or JavaScript or such.

The "conventional" method is to split the pages into separate pages, or to provide a "back to top" anchor at the end of each section. You can also investigate "frames", but they don't work well with drop-down or pop-out menus.

Dani: nope, it won't scroll. That's why sites that implement these awful scrolling menus always have a "delayed reaction". The user scrolls, and then the menu catches up. It's event-driven, and requires Javascript. I think it's tacky in the extreme. I find myself trying to read the content, and then the menu appears over it, so I scroll a bit, the menu jumps around... bad.