/* remove any default styles */
.mainNav, .mainNav * {
	margin:0px;
	padding:0px;
	list-style:none;
	font-family:sans-serif;
}

/* top ul.mainNav element */
.mainNav {
	line-height:1.0; /* makes calculating the 'top' value for first submenu easier */
	z-index: 1000;
	position: relative;
}

/* nested submenu ul elements */
.mainNav ul { 
	position:absolute; /* remove from flow and allow positioning */
	top:-999em; /* hide submenu in screen-reader and search-engine friendly way */
	width: 16em; /* VARIABLE. Must have a width for menu items to inherit. Use ems so font scaling does not break design*/
	border-bottom:1px solid #666666;
	border-right:2px solid #666666;
	text-transform:uppercase;
	list-style: none;
	left: -1px;
}
/* submenu items */
.mainNav ul li,
.mainNav a { /* this affects top level anchors too */
	width: 100%;/* stretch submenu items to width of submenu ul width (see .mainNav ul rules above). When link text runs over more than one line, use padding and an explicit width for the anchor instead of width:100% and text-indent. Example below in the SKIN section */
	padding: 2px 0;
	display: block;
	}



/* all li elements */
.mainNav li {
	float: left;
	margin: 0;
	position: relative;
	font-size:12px;
	text-transform:uppercase;
	z-index: 2000;
}

/* ACTIVE TOP LEVEL*/
.mainNav li a.mainNavActive {
	color:#990000;
}

/* all anchor elements */
.mainNav a {
	display:block; /* make IE6 obey width when text-indent is used */
}

/**** Position of second tier of mainNav ****/
.mainNav li:hover ul, /* this pure CSS hover is overridden by the  rules below which are applied only when JavaScript is available. This way, the menu degrades to regular CSS dropdown when JavaScript is umainNavailable */
ul.mainNav li.sfHover ul /* this is the familiar IE6 hover support. With Superfish, all browsers use this rule when JS is available. This is because the JS needs to be able to control hide and reveal delays and animations without the pure CSS rule intruding. Note the tag selector ul.mainNav instead of just .mainNav - this gives it the most specificity of all and makes it trump all other positioning rules, including the  overrides below */
{
	left:0px; /* position first submenu directly under parent li */
	top:18px; /* VARIABLE. This is calculated by adding 1em text height to top and bottom anchor element padding (original skin: .75em top + .75em bottom + 1em text height = 2.5em) */
}

/**** Position of third tier of mainNav ****/
 /* Note that this rule must appear here in the code order in order for it to override previous positioning rules so that this and subsequent nested submenus still remain hidden when the parent submenu is shown. Do not group these selectors with other top:-999em rules */
.mainNav li:hover li ul,
.mainNav li.sfHover li ul {
	top:-999em; /* hide submenu in screen-reader and search-engine friendly way */
}
/* DO NOT attempt to group these selectors with similar earlier rules. The code order is important so the rules override previous ones correctly */
.mainNav li li:hover ul, /* this pure CSS hover is overridden by the  rules below which are applied only when JavaScript is available. This way, the menu degrades to regular CSS dropdown when JavaScript is umainNavailable */
ul.mainNav li li.sfHover ul /* this is the familiar IE6 hover support. With Superfish, all browsers use this rule when JS is available. This is because the JS needs to be able to control hide and reveal delays and animations without the pure CSS rule intruding. Note the tag selector ul.mainNav instead of just .mainNav - this gives it the most specificity of all and makes it trump all other positioning rules, including the  overrides below */
 {
	left:200px; /* VARIABLE. Offset subsequent submenus to the right by the amount you set for the submenu widths (see .mainNav ul rules above) */
	top:-1px; /* position subsequent submenus horizontally aligned to parent li */
}

/**** Position of fourth tier of mainNav (not used on main demo page. You could delete this block for a three tiered mainNav) ****/
 /* Note that this rule must appear here in the code order in order for it to override previous positioning rules so that this and subsequent nested submenus still remain hidden when the parent submenu is shown. Do not group these selectors with other top:-999em rules */
.mainNav li li:hover li ul,
.mainNav li li.sfHover li ul {
	top:-999em; /* hide submenu in screen-reader and search-engine friendly way */
}
/* DO NOT attempt to group these selectors with similar earlier rules. The code order is important so the rules override previous ones correctly */
.mainNav li li li:hover ul, /* this pure CSS hover is overridden by the  rules below which are applied only when JavaScript is available. This way, the menu degrades to regular CSS dropdown when JavaScript is umainNavailable */
ul.mainNav li li li.sfHover ul /* this is the familiar IE6 hover support. With Superfish, all browsers use this rule when JS is available. This is because the JS needs to be able to control hide and reveal delays and animations without the pure CSS rule intruding. Note the tag selector ul.mainNav instead of just .mainNav - this gives it the most specificity of all and makes it trump all other positioning rules, including the  overrides below */
 {
	left:200px; /* VARIABLE. Offset subsequent submenus to the right by the amount you set for the submenu widths (see .mainNav ul rules above) */
	top:-1px; /* position subsequent submenus horizontally aligned to parent li */
}

/**** Position of further tiers of mainNav ****/
/* To add further tiers, you need copy the previous block of code (everything back until the "Position of fourth tier of mainNav" comment) and paste it in here. Then add an extra li just after .mainNav in each of the pasted selectors. So the new block will differ from the copied block in the same way that the block for the fourth tier differs from the block for the third tier.*/

.mainNav {
	/* if you want to change font-size, do it here as opposed to setting it on deeper nested anchor elements for example,  so that the em unit is the same size for all elements in the menu */
	float:left; /* necessary if you don't want this element to collapse */
	font-size:12px;
	z-index:50;
	}
.mainNav li {
	/*background:#cccccc;*/ /* default background colour */
	/*width: 12em;*/ /* affects top level menu items only, as nested li elements have width 100% of their ul parent (see .mainNav ul rules above)*/
	padding-right:20px;
	text-transform:uppercase;
}

.mainNav a:link,
.mainNav a:visited {
	color: #333333;
	padding: 3px 0; /* note that the top and bottom padding will affect the 'top' value (marked with the word "VARIABLE") of the second tier of mainNav (see "essential rules" above and alter accordingly) */
	text-decoration:none;
	text-indent: 5px;
	text-align:left;
}

/* if link text runs over two or more lines, you will want padding in the anchor element instead of relying on text-indent to provide space. The following disabled rule shows how to style the submenu links in this case. Note that the width plus left and right padding must equal the width set above for the submenu (.mainNav ul) */
/*
.mainNav ul a {
	width: 7.45em;
	padding: .75em 1em;
	text-indent: 0;
	}
*/

.mainNav li .manNavActive{
	color:#990000;
}

.mainNav li .manNavActive, .mainNav li:hover, .mainNav li:active .mainNav li.sfHover,
.mainNav a:focus, .mainNav a:Hover, .mainNav a:active{
	/*background:#cccccc;*/ /* hover highlight */
	color:#990000;
}

.mainNav li li {
	background:#cccccc; /* slightly darker shade for nested submenus */
	font-size:10px;
	border-left:1px solid #fff;
	border-top:1px solid #fff;
	background-image:url(../images/top_nav_bg.gif);
}

.mainNav li li li {
	background:#cccccc; /* slightly darker shade for nested submenus */
	font-size:10px;
	border-left:1px solid #fff;
	border-top:1px solid #fff;
	background-image:url(../images/top_nav_bg.gif);
}
.mainNav li li:hover,
.mainNav li li.sfHover,
.mainNav li li li:hover{
	background-image:url(../images/top_nav_hover_bg.gif);
}
.mainNav li li:active,
.mainNav li li li:active{
	background-image:url(../images/top_nav_active_bg.gif);
}