Hi,

No kiddin' :-)

No, we're not.  In fact, NavBar doesn't even care if you have a <form> there or something else.

I'm positive that this is not a NavBar problem.  I just made a quick test and it all works fine--just make sure that your formular is correct (i.e. inside a <form> with the proper action and also make sure that your server-side script doesn't discard arguments that start with an underscore).

So again, HTML inside NavSection-s is totally unrelated to NavBar and if done well, will work well.  If you want to make sure that parameters are passed correctly, just use GET instead of POST (as the form method argument) and you should see all the parameters in the URL.

Well, this is handled outside the main NavBar script--in setupmenu.js, which is just an usage example.  You can figure out a different way to disable the current menu item, i.e. by an ID not by label.  For instance, modify your setupmenu.js like this:

var labels = [
	"label 1",
	"label 2",
	"label 3",
	... /* put all labels from all sections here */
];

function L(id) {
	if (_NavBar_pageID == id)
		return "!" + labels[id];
	else
		return labels[id];
}

And later when calling NavSection, instead of adding “L(label)” each time, add “L(id)”, where “id” is the numerical index of the current label from the “labels” array.  Also, in the page HTML code, instead of using textual ID-s, assign the numeric ID to _NavBar_pageID.

To be more specific, NavBar will disable an item if its label starts with an exclamation sign.  Our "L" function handles this in a transparent way, allowing you to define the page label right in the page HTML (using the _NavBar_pageID global variable) and to define the whole menu in an outside script (which is setupmenu.js).  So the only thing you should do is to add the exclamation sign as the first character in the menu item that has to be disabled--which can be accomplished with code like above, but it's also, external to NavBar--use your imagination. :-p

Thank you, we're glad you like it.  :-)