/* ======== Default global, non-custom, mechanical rules; defines the actual menu component ======== */





	
#NavigationItem, #NavigationItem li ul {
	padding: 0;
	margin: 0;
	height: auto;
	text-align: center;
	list-style: none;
	text-indent: 0px;
	margin-left: 0px;
}

#NavigationItem a {
	display: block; 
	padding: 0; 
	text-align: center;
	margin-left: 0px;
	text-decoration: none;
	padding-top: 10px;
}
	
#NavigationItem a:hover {
	text-align: center;
	left: auto;
}	
	
#NavigationItem li {
	float: left; 
	left: auto;
	margin: 0; 
	text-indent: 0px;
}	
	
#NavigationItem li ul {
	position: absolute;
	left: -10000px; 
	margin-left: -1px;
	text-indent: 0px;
	width: 100px;
	z-index: 1000;
	margin-top: 0px;					
	border: solid 1px silver;	
	border-top: #ccc;
}

#NavigationItem ul li a.subMenu {
	z-index: 10000;
	left: auto;
	text-decoration: none;
	text-align: left;
	font-family: arial, verdana;
	font-size: 11px;
	color: #787878;
	padding: 5px;
	padding-left: 0px;
	padding-right: 0px;
	margin-left: 0px;
	margin-top: 0px;
	height: auto;
	width: 130px;
	text-indent: 3px;				
	background: #f3f3f3;
	border-top: solid 1px silver;
	background: url('images/backgrounds/nav.gif') repeat-x;
}	

#NavigationItem ul li a.first {
	/*background: url('images/backgrounds/nav.gif') repeat-x;*/
}

#NavigationItem ul li a._subMenu:hover {
	color: #888;
	background: #ebebeb;
}

#NavigationItem li:hover ul, #NavigationItem li.sfhover ul {
	left: auto;
}	
	
#NavigationItem li:hover, #NavigationItem li.sfhover {
	background: none;
}	
	
#NavigationItem a.on {  }



/**
 *	NOTE: some seemingly silly rules are needed to be here for the menu to work perfectly.
 *	For example, the rule: "#NavigationItem li ul" needs to have "background:#fff;"
 *	(the background can be anything other than 'transparent' or 'none') for the submenu to work correctly in IE 6.
 *	Apparently in IE 6, 'background' is what defines a DIVs region (as a box) and not simply just a DIV itself.
 *	Anyway, i stripped out all definitions that do not need to be here, so whatever rules are here are needed
 *	for the hmenu to work correctly with no overhead or junk rules. Styling rules are defined in the actual
 *	hmenu.cfm file itself; you should never need to modify the rules above.
 */

/* Please refer to hmenu.cfm for the front-end specific style rules */
 
 
/*
FRONT-END SPECIFIC STYLE RULES DOCUMENTATION AND NOTES
(refers to hmenu.cfm; documentation is just placed here)
======================================================
*/
 
/** NOTE 1:
 *	-------------------------------------------------------------------------------------------------------------
 *	The styles for NavigationBlock rarely needs to be changed, however the most common changes for this DIV
 *	are the margin: and width: properties. all menu items are floating to the left, which disregards the
 *	text-align: property for this DIV. in other words, if you need to center the menu items, you will not be able
 *	to use the text-align:center value to center them. you will have to set an explicit width on NavigationBlock,
 *	then set the margin to margin:auto; or margin:0 auto; (the left and right margins need to be 'auto').
 *	margin:auto; is the default margin values for this DIV anyway, the point is however, you need to set an
 *	explicit with for margin:auto; to work. In summary, the procedure for getting the menu itms centered
 *	is setting the width of the NavigationBlock	and ensuring the horizontal margins for NavigationBlock are auto.
 *
 *	Please note, there is a root DIV #navigation laid out in index.cfm as part of the overall shell.
 *	this DIV should define the boundaries (placement and possibly height) and background image/color
 *	for the entire hmenu bar and its rules are defined in global.css
 */

/** NOTE 2:
 *	-------------------------------------------------------------------------------------------------------------
 *	one of the few times you'll have to go down into the code below and change something is
 *	when working with a site that requests a style for currently active menu item styles...
 *	the a.navMenuOn class works fine but the coldfusion logic is that when 'page is links[i]'
 *	then the class becomes a.navMenuOn. The problem is, menu items who have the same page name
 *	(such as page=search) will BOTH/ALL get the class a.navMenuOn, in which case to make a.navMenuOn
 *	work totally correct, you will have to set ADDITIONAL conditions in the CF code below to go further
 *	than just one-layer logic 'if(page==links[i])'. The thing is, these conditions are somewhat custom
 *	and depend on the front-end's menu choice so it's one of, if not the only, things you will
 *	actually have to edit below, otherwise you should almost always be interfacing with the CSS only
 */