| Bug reports ¶ | |
| Report any bugs under this thread. | |
| Shortcut keys open browser menu in IE ¶ | |
| Yes, I know this is an IE bug and not the DTHML menu bug, but I believe I have a workaround for it (it annoyed me so much I had to do something :) and I thought I'd share it in case you would want to include it in distribution. The following code when added to createMenuItem() in hmenu.js (line 305 in library version) seems to do the trick: Thanks again for the excellent menu component. | |
| last |
| Re: Shortcut keys open browser menu in IE ¶ | |
| Hey there, thanks for the tip! :-) We were actually thinking about allowing keyboard navigation by using the "accesskey" attribute (instead of having the underscore thing as we do currently) and I think that in that case, this hack shouldn't be needed anymore--but however, we will add it for backwards compatibility. | |
| last |
| Relative urls don't work in IE when attribute lazy is set ¶ | |
| When you use relative urls in IE when the menu is in lazy mode you get redirected to a wrong page. I need to place the links relative because when the user doesn't accept session_cookies, PHP only will add the SID to the relative urls. | |
| last |
| Re: Relative urls don't work in IE when attribute lazy is set ¶ | |
| I am seeing this too. But On one occasion I see that IE throws an error stating there was an error on the page and it could not continue loading. Was an od error...not like a JS popup or the like. If I turn lazy back on the page loads but the 2nd level links are broken unless I use an absolute link. First level works fine. Very odd.. | |
| last |
| JAWS screen reader issue ¶ | |
| Had a user call just now. He is blind and works for the US Dept of Homeland Security. He does Section 508 usability testing on web sites. He uses a tool called JAWS from www.FreedomScientific.com that reads the DOM from IE to the user. The page he is having problems with was working fine for him until I added a new DynarchMenu that is dynamically built from a database. When he views the page, it dumps out and crashes the browser. He verified by having his wife view the page with the reader turned off and the page came up fine. So there is some issue with the DynarchMenu and his JAWS software...whether in the DOM or the Javascript or some combination. | |
| last |
| Re: JAWS screen reader issue ¶ | |
| I'm sorry, I don't know anything about JAWS... Theoretically, if it would ignore JavaScript then pages should be OK, given the fact that the menu is defined by plain HTML lists. If it crashes though, it means that it either tries to execute JavaScript code or tries to use the full existing DOM (after having been modified by DynarchMenu), both of which can be bad. An easy workaround would be to identify a JAWS browser in your server-side scripts and if that's the case, avoid the DynarchMenu.setup line. | |
| last |
| hmenu on an input field in firefox ¶ | |
| I'm getting a strange error when I put an hmenu on an input field. This error does not occur when I place it anywhere else or when I use IE. Do you have any ideas what could be causing this.. Error Details: I get the following error when I move my mouse into the menu that has popped up and then out of the menu.... but only when I move out of the top of the menu. Uncaught exception: Permission denied to getProperty HTMLDivElement.parentNode. Input Details: Context Menu Details: | |
| last |
| Re: hmenu on an input field in firefox ¶ | |
| hmmm posting the code didn't work. I don't think the code is really important though.. it is the same as I use for anywhere else I use it except it is on an input instead of a div tag. | |
| last |
| Re: hmenu on an input field in firefox ¶ | |
| Not sure this will help, but: This appears to be a bug in the current versions of Firefox; hopefully the next branch (starting with 1.5) should fix it, but until then here's a simple “fix”. You need to disable autocompletion on that field. You do it like this:
<input type="text" autocomplete="off" ... /> You can also disable autocompletion on the whole form if you wish: <form action="..." method="post" autocomplete="off"> Please let me know if using this attribute solved the problem. | |
| last |
| Menu doesn't go away when using iframes ¶ | |
| We are using the iframe trick in order to get a fixed position, persistent menu at the top of our page. That is, we have a single HTML page that uses the hmenu at the top, and below that is an iframe for the main page content. The menu dropdown displays correctly, but if one first clicks the menu, and then clicks somewhere in the iframe, the dropdown menu continues to display. You have to click somewhere at the top, on the outer page in order for the hmenu to detect the click and cause the dropdown menu to disappear. I assume that somewhere in your javascript, whenever you add an hmenu to a page, you must set yourself up as a mouseClick listener of some sort on the page so that you know whenever the user has clicked off of your menu... but obviously you're not set up to listen for the same events on an iframe embedded on that same page. But I'm just guessing. Can you please affirm that this is an issue and advise any workarounds. This has become a major issue for us (and yes, we are a paying customer). Thanks in advance, Mike Gorman | |
| last |














