keypress.js bug?

Poster: stephen702
Dated: Tuesday November 22 2005 - 18:23:58 GMT

After successfully adding keypress to my own licensed site, I thought I would get our college to buy a license, as well. But for that to happen, I would first have to demonstrate that the menu could be used with the Tab key.

On my first test site for the college, the submenus opened, but you had to use the right-arrow key to get the cursor to move into the submenu. If you kept pressing Tab, the cursor kept going straight down.

After spending time comparing the two menus on the two sites, I realized there was one major difference.

The menu that works is a single horizontal menu.

The menu that doesn't work is one of two horizontal menus, one above the other.

When I removed the first horizontal menu (which is straight html links), the menu below it (which has the drop-down menus and sub-menus) suddenly worked just fine.

Here's where it got interesting: If I reverse the call-order of the two menus inside the menu_data.js file and also reverse the "top=" setting of the two menus (that is, make the bottom menu the top one), the problem menu works, as well. (Note that both changes must be in place. If I just reverse the order, or only reverse the "top=" settings, the problem menu is still a problem.)

So, the drop-down menu works with keypress.js only if it's the first of the two horizontal menus--and I want it to be the second one.

Could this a bug in keypress?


The one that doesn’t work: http://inside.arc.losrios.edu/index-new.html This is the correct order of the two menus, with the red one above the blue one


The one that works: http://inside.arc.losrios.edu/index-new2.html The only difference is that I have reversed the order of the two menu calls within the menu_data.js file and reversed the “top=” setting for the two.