Recent Questions
Q: I am interested in purchasing your product for use in my company's website code. My clients are not tech-savy, and I do not want to include any code that will generate concern or problems on the user end.
Is there a way to use the JavaScript menus without generating the warning as mentioned in the subject? I know how to allow the active content on my web browser, but I want code that will not require such actions on their browsers.
A: Thanks for your interest in our products.
Your clients should check browser settings.
Unfortunately, we can't affect on the browser behavior in this case.
Q: I have another question concerning pop-up windows. If I do the following:
1) Use the Deluxe Tuner to create a pop-up window.
2) Change the location of the gif, css, and js files from all of them being within "deluxe-popup-window.files" to the files being in separate directories and
3) Update the "deluxe-popup-window.js" file and the "jaw_skin_windowsvista_graphite.css" file so that they contain the new directory locations
Will the html window function properly? Thanks for the help.
A: If you change all paths in jaw_skin_windowsvista_graphite.css and deluxe-popup-window.jsfiles correctly your popup window should work fine.Q: Is there a way to hide a menu options using either CSS or the java api based on the site user for the mouseover menu?
A: Deluxe Menu supports Javascript API.
You can find more info here:
http://deluxe-menu.com/dynamic-functions-sample.html
You can try to use API functions in that case:
function dm_ext_changeItemVisibility (menuInd, submenuInd, itemInd, visibility)
To disable items you should set the target parameter to "_".
You can try to use the following function
function disable() {
dm_ext_changeItem(0, 1, 1, ["", "", "", "", "", "_"]);
}
to disable your items.
Q: I appreciate your assistance with this problem. I am 98% of the way happy with this product. When I made the changes you suggested, the copyright error went away, however the site no longer validates. It does not like the <noscript> tags. Is there a fix for this?
A: Matt, you can move your <noscript> tag into the <body> tag.
Try that.