» Forums
» DynarchMenu forum
» Support
» Odd namespace poisoning issue with Opera
Odd namespace poisoning issue with Opera
2005/05/20 09:10
Viewed 5082 times
Replies: 0/0

I've been playing around trying to get context menus working on images, with a different menu for each part of the image and with the ability to process information about the part of the image the menu was activated from (it's for drill down grpahing in case anyone is wondering). Anyway, I've pretty much got it working the way I want but ran into an issue with Opera that stumped me for a bit and I thought I would report it.

My test script is located here... http://mrchook.homeip.net:1500/~mca/test/context_menu/img_context.htm

To do what I wanted I used custom parameters on the AREA tags in the image map to hold the arguments relating to the area and custom parameters on the LI tag that forms the menus to determine the menu action and then used a custom javascript handler to process the action like this...

  function my_handler(action) {
var item = action.info;
var triggerElement = item.menu.target;
var arg1 = triggerElement.getAttribute("arg1");
var arg2 = triggerElement.getAttribute("arg2");
alert("menu_action = " + action.params.getAttribute("menu_action") + "\narg1 = " + arg1 + "\narg2 = " + arg2);
};

This works very well.  Now to the problem, if I replace the custom attribute name with "action" (which I originally used, hence this problem) instead of "menu_action" then Opera 8 thinks that the action is, for example "http://mrchook.homeip.net:1500/~mca/test/context_menu/action_1" instead of just "action_1".  It works fine in FF and IE with either name.


The only other problem I can see is that the context menu should work for both left and right click, however for IE it only works on the left click.  I can't seem to see where I have gone wrong on that (also, Opera only works on the right click but that's another issue I already know about)


Cheers,

Michael

Google