@charset "iso-8859-1";



/*******************************************************************************
 * General Menu Mechanics
 *
 * Below is a set of rules which is applicable to any list used within
 * this dropdown menu system. You could apply just these rules and get
 * a basic dropdown menu system working just fine in FireFox, Opera,
 * Safari, and most other modern browsers.
 */

ul.menu, ul.menu ul, ul.menu li, ul.menu a
{
	display: block;		/* make these objects blocks so they're easier
				   to deal with */
	margin: 0;
	padding: 0;		/* get rid of padding/margin values that these
				   elements may have by default */
	
}

ul.menu, ul.menu li, ul.menu ul
{
	list-style: none;	/* proper browsers don't require this because
				   block elements (see previous rule set) cannot
				   take any list-style property. meaning 
				   existing list-style properties are removed
				   when they are set to display: block. IE7 
				   seems to ignore this fact under certain
				   situations so we explicitly set it here
				   even though it's, technically, incorrect 
				   CSS (but it will validate). */
}
ul.menu ul
{
	display: none;		/* hide the sub-menus until needed */
	position: absolute;	/* remove the sub-menus from the flow of the
				   layout so when they pop they don't cause any
				   disfiguration of the layout */
}
ul.menu li
{
	position: relative;	/* so sub-menus position relative to their 
				   parent LI element */
}
ul.menu li:hover
{
	z-index: 1;		/* make sure this and any sub-menus that pop 
				   appear above everything else on the page */
}
ul.menu li:hover > ul
{
	display: block;		/* show the sub-menu */
}

/*******************************************************************************
 * Extended Menu Mechanics
 *
 * These rules exist only for specific menu types, such as horizontal or
 * vertical menus, right or left aligned menus.
 */

ul.menu-ver li
{

	float: none;		/* clear this so vertical sub-menus that are
				   children of horizontal menus won't have
				   their LI widths set to auto. */
}
ul.menu-ver, ul.menu-ver ul
{	
	width: 194px;		/* sub-menus need a defined width, especially
				   vertical sub-menus. salt to taste. */
}

/*******************************************************************************
 * DROP POSITIONS
 *
 * This handles where sub-menus drops relative to the parent element. The same
 * attributes should be set in all rule sets in this section so that cascading
 * rules don't create problems.
 */

ul.menu-ver ul
{
	left: 194px;
	right: auto;
	top: 0px;
	/*margin-top: -0.5em;	 i prefer top: 80% but this creates a problem
				   in iCab so negative top margin must be used.
				   salt to taste. */
}
 

/*******************************************************************************
 * PRESENTATION : General
 *
 * This is where the visual presentation of the menu is handled. If you try to
 * alter the borders width or location of placement pay close attention to the
 * notes provided with the existing CSS rules in this section. There are key
 * reasons behind borders and negative margins being placed where they are.
 */
 
 

ul.menu li a
{	height:26px;
	
	
		border: solid 1px #ffffff; /* border around all anchor tags */
		border-right: solid 0px #ffffff; /* border around all anchor tags */
}

ul.menu-ver li
{	z-index: 100;
	margin-left: 0px;		/* remove any negative bottom margin if the
				   horizontal menu is child of a vertical 
				   menu */
	margin-top: 0px;	/* negative borders on LIs to make borders on
				   child A elements overlap. they go here and
				   not on the A element for compatibility
				   reasons (IE6 and earlier) */
}
ul.menu-ver
{	
	/*border-top: solid 1px #fff;	 compensate for the 1px left jog created by
				   the above negative margin. */
}
ul.menu li a
{	border-bottom: solid 1px #fff;
	padding: 0px 0px 0px 0px;	 
	
}

ul.menu li a:link, ul.menu li a:hover, ul.menu li a:visited, ul.menu li a:active
{	text-decoration: none;
	text-align:right;
	height:26px;
	
	font-size:10px;
	font-family:verdana, arial, sans-serif;
	
}
ul.menu li a:link, ul.menu li a:visited
{ 	color:white;
}
ul.menu li a:hover, ul.menu li a:active
{	color:black;
}
ul.menu li.sfhover a:active,
ul.menu li:hover a:active
{	color: #97C00E;
	background-color: #CBDC8F;
}
ul.menu li
{	height:28px;
	background-color: #97C00E;	/* default background color of menu items */
}
ul.menu li:hover,
ul.menu li.sfhover
{	
	background-color: #97C00E;	/* background color for parent menu items of
				   the current sub-menu. includes the sfhover
				   class which is used in the suckerfish hack
				   detailed later in this stylesheet. */
}
ul.menu li a:hover
{
	background-color: #CBDC8F;
}
.nav_text
{
	display:block;
	position:relative;
	top:5px;
	font-weight:bold;
}
.nt_image
{
right:4px;
}
.nt_no_image
{
right:27px;
}

ul.menu li.no-border a
{	border-bottom: solid 0px #ffffff;
	padding: 0px 0px 0px 0px;	 
	height:28px;
}
/*******************************************************************************
 * PRESENTATION : Expand
 *
 * the bits below implement a graphic to appear on those anchor elements which 
 * have the rMenu-expand class assigned. this is something you have to do
 * manually on any LI element containing a UL element that is to be a dropdown 
 * menu. there is no mechanism to do this automatically.
 *
 * the seemingly redundant CSS is done for reasons similar to the suckerfish
 * css. it's to deal with all sorts of nested menu issues. it'll work as far
 * as three levels deep, after that all bets off.
 */




ul.menu li.menu-expand a
{	
	padding-right: 25px;
	background-image: url("images/arrow.gif");
	background-repeat: no-repeat;
	background-position: 171px 50%;
}
ul.menu li.menu-expand a:hover
{	
	padding-right: 25px;
	background-image: url("images/arrow2.gif");
	background-repeat: no-repeat;
	background-position: 171px 50%;
}
ul.menu li.menu-expand  li a
{
	background-image: none;
	padding-right: 0px;	/* reset padding */
	padding-left: 0px;	/* reset padding */
}
ul.menu li.menu-expand  li a:hover
{
	background-image: none;
	padding-right: 0px;	/* reset padding */
	padding-left: 0px;	/* reset padding */
}

/*******************************************************************************
 * HACKS : General
 *
 * These are rules specifically targeted to resolve bugs/quirks that some
 * browser exhibit.
 */
* html ul.menu
{
	display: inline-block;	/* this is for IE/Mac. it forces IE/Mac to 
				   expand the element's dimensions to contain 
				   its floating child elements without a 
				   clearing element. */
	/* \*/ display: block;	/* override above rule for every other 
				   browser using IE/Mac backslash hack */
	position: relative;	/* IE 5.0/Mac needs this or it may clip the
				   dropdown menus */
	/* \*/ position: static;/* reset position attribute for IE/Win as it
				   causes z-index problems */
}
* html ul.menu ul
{
	float: left;		/* IE/Mac 5.0 needs this and IE/Win 6 and earlier
				   don't show any problems with applying this 
				   rule. */
}
ul.menu ul
{
	background-color: #fff;	/* IE/Win (includeing 7) needs this on an object 
				   that hasLayout so that it doesn't "look through"
				   the menu and let any object (text) below the 
				   menu to gain focus, causing the menu to 
				   disappear. application of this rule does not
				   cause any rendering problems with other browsers
				   as the background color his covered by the
				   menu itself. */
}
* html ul.menu-ver li
{
				/* the second selector in this rule is there 
				   because of problems IE/Mac has with 
				   inheritance and what rules should take
				   precedence. and to serve as a reminder on
				   how to work around the issue if it's 
				   encountered again down the road. */
	
	width: 100%;
	float: left;
	clear: left;		/* IE6 (and earlier?) stick space below any LI
				   in :hover state with a sub-menu. floating
				   the LIs seems to work around this issue. But
				   note that this also triggers hasLayout 
				   because we need a width of 100% on floats.
				   But hasLayout on LIs breaks the menu in IE7.
				   So we really need to be careful not to let
				   floats get into anything other than IE6
				   and earlier. IE Mac seems to need this
				   too for some other reason. */
}
ul.menu-ver li a
{
	min-width: 0;		/* trigger hasLayout for IE7 on anchor 
				   elements. without hasLayout on anchors
				   they would not expand the full width 
				   of the menu. this rule may not trigger
				   hasLayour in later versions of IE and
				   if you find this system broken in new
				   versions of IE, this is probably the
				   source. */
}
* html ul.menu-ver li a
{
	height: auto;		/* triggers hasLayout for IE/Mac */
	/* \*/ height: 100%;	/* trigger hasLayout for IE6 and earlier. does
				   not work for IE7 */
}

/*******************************************************************************
 * HACKS : Suckerfish
 *
 * IE6 and earlier do not support the :hover pseudoclass and so javascript is 
 * used to add the "sfhover" class of any LI element that the mouse is currently 
 * over. This method is called suckerfish and you can read up on it at:
 * http://www.htmldog.com/articles/suckerfish/dropdowns/
 *
 * NOTE: this allows for support of dropdown menus up to 3 levels deep. if you 
 *	 want to support greather menu depth you need to alter these selectors. 
 *	 read the above mentioned website for more info on how to do that.
 */
* html ul.menu li.sfhover
{
	z-index: 999;
}
* html ul.menu li.sfhover ul 
{ 
	display: none;		/* IE/Suckerfish alternative for browsers that
				   don't support :hover state on LI elements */
}
* html ul.menu li.sfhover ul
{
	display: block;		/* ^ ditto ^ */
}

/*******************************************************************************
 * HACKS : Clearfix
 *
 * Clearfix provides a means to for an element to contain all it's floated 
 * children even if it's not normally tall enough to do so. For more information
 * on clearfix please see:
 * http://www.positioniseverything.net/easyclearing.html
 */
.clearfix:after
{
    content: "."; 
    display: block; 
    height: 0; 
    clear: both; 
    visibility: hidden;
}
.clearfix
{
	min-width: 0;		/* trigger hasLayout for IE7 */
	display: inline-block;
	/* \*/	display: block;	/* Hide from IE Mac */
}
* html .clearfix
{
	/* \*/  height: 1%;	/* Hide from IE Mac */ 
}

/******************************************************************************/