A couple lines of code, some definitions of the menu titles, and action codes, and suddenly a fully functional pop-up menu is part of the application. Try the same thing on a Web page, and you have a different story entirely. It is only in this fashion that you can arrive at something that behaves like a menu, without having a menu object available. It can be done. Just don't think that it will be easy.
Menus are fairly complex objects.
You need to define carefully how and where the menu will display, you need to hook into the event model to provide proper mouse and keyboard support, you need to be able to determine how and when to bring up submenus, and you need to determine when to cancel the menu object to get it out of the way. All of this doesn't even deal with actually making a menu selection, how to change highlighting, or how to notify some procedure as to which menu item was selected. All of which might make you think that eating with your fingers may not be such a bad idea after all. Robert Hess hosts the MSDN Show . While Hess's article could be looked at as mildly philosophically entertaining, the point he is missing is that HTML in particular, and the web in general, has no need for pop-up menus.