Web Menus Floating Tree by Deluxe-Tree.com
Web Menus Floating Tree


Buy Now!  Free Trial Download

Menu Screenshots Web Menus Floating Tree

Web Menus Floating Tree Tree Dropdown With Graphics

Features Web Menus Floating Tree

Professional Look-n-feel
  • Entirely customizable look-n-feel
  • A lot of pre-designed web menus floating tree samples
  • Hundreds of visual effects
  • Custom CSS styles can be applied for all menu settings
Unrivalled Features
  • Scrollable, dragable, floating
  • Unique Java Script API for altering menu "on-the-fly", without page reloading
  • AJAX technology - loads menu data from the server "on-fly and on-demand".
Tree Menue Tutorial Web Menus Floating Tree
Compatibility              
  • Full cross-browser compatibility including IE, Netscape, Mozilla, Opera, Firefox, Konqueror and Safari on Windows, Mac OS and Linux
  • Menu can be populated from a database using ASP, PHP, etc.
  • Search engine friendly
  • Support for any doctypes
  • Fits for secure sites
Cost Effective
Seamless Integration
  • Visible over flash, select boxes, iframes, java applets
  • Multiple menus on the same page
  • Amicable to other scripts and css styles
  • Any HTML code can be used inside menu items
Buy Now!  Free Trial Download

Javascript Tree Menu. Expandable Menu.

  • Good menu is an essential part of website commercial success. If people can't find their way around the site, they will fast give up seeking and retire, never to return. So, it's extreme serious that your website has a accurate, precise, prompt, and navigation of immaculate appearance.
    Don't let your web site guests to get lost. Try Javascript/DHTML Tree!

Recent Questions Web Menus Floating Tree

Q: When I open my site in Internet Explorer 6.0 The main menu showsup nicely but the drop-down sub-menus are separated. The menu work very nicely in a Firefox browser but not in IE.


A: There are some problems also with your css.
The problem is that the script can't get css properties of the object if they are described in separate .css block (or file).
In other words, you can't get the value of "position" attribute of the object if the object doesn't have this property within inline style(style="position:relative"). To get the value you should move .css style into style="" attribute.

Please, try to add your
css file -> inline css, for example:

You should add style="position:relative;"

to the

<DIV id="right">

So, you'll have:

<DIV id=right style="POSITION: relative;">

Check that.


Q: How can I have the sub tab option that initiated the action highlighted once the new page is reloaded?  I want to highlight the tab which is done with 'bselectedItem', please tell me about the sub-tab option.

A: See you cannot create subitems in
  var tabMode=0;
it is not correct.

You should set
  var tabMode=1;

The following parameters set the pressed items for top items andsubitems:

  var bselectedItem=0; //top items
  var bselectedSmItem=2; //subitems

where 0,1,2... is the index of the item in bmenuItems.

- delete   var bselectedItem=1; and   var bselectedSmItem=2; parameters from your data file
- set correct parameters on each page before you call data file, forexample:

<noscript><a href="http://deluxe-tabs.com">Javascript Menu by Deluxe-Tabs.com</a></noscript>
<script type="text/javascript" src="menudir/dtabs.js"></script>
<script type="text/javascript">  var bselectedItem=3;
  var bselectedSmItem=5; </script>
...
<script type="text/javascript" src="menudir/data.js"></script>




Q: We use the state saving feature of your menu on our site. I wanted to know if this implements cookies at all, or how it interacts with visitors to the site. This is only so we can have an accurate privacy policy.


A: Javascript/DHTML Tree saves it's state using cookies.


Q: I'm testing the trial version and I'm having a little problem with the state saving. Everytime it navigates to another page, it does not save the state, even with

  var tsaveState=1;

In fact, it actually opens up a different menu other than the one I originally clicked.


A: See, if you open pages (with menus) from different folder it means that you open different menus. So, when you change a state, for example, of the first menu within "newzap/" folder and then open another page with the menu within "newzap/learn/", browsers looks for another cookie file and can't find it and the second menu stays in a default state.

Try to set different

  var tsavePrefix="menu1";
  var tsavePrefix="menu2";
  var tsavePrefix="menu3";

for different menus.
That should work.