@charset "iso-8859-1";

/*******************************************************************************
*  hnav2.css : Level 2 Horizontal Menu
* ------------------------------------------------------------------------------
*  responsible for the horizontal navigation elements, one of which is usually
*  placed below the masthead but on top of the columns.
*
*  this seems awfully complex for something seemingly so simple, no? the big
*  issue here is we need to make the menu items inline elements. we could make
*  them block elements and float them left or right, but that creates a lot of
*  problems with compatibility and how elements are ordered on-screen versus
*  source. just trust me on this, inline is the way to go here.
*
*  the main reason people would float these elements rather than go inline is
*  because padding and margin values have an effect on surrounding elements.
*  meaning if an element is 20 pixels tall, and has 5 pixels of padding on
*  top and bottom, a browser is going to treat that element as 30 pixels tall 
*  when rendering the page. but for an inline element (versus a block element)
*  the browser treats it as 20 pixels tall. That padding will still be applied
*  and if you've got a background color on this element, you'll see that color
*  extend 5 pixels into the elements immediately above and below this inline
*  element with padding. 
*
*  in short: vertical padding on inline elements can make things look really
*            bad. 

*  so we need to work around it. thus all of the hacks you see in this 
*  stylesheet.
*******************************************************************************/
.hnav2
{	border-bottom: solid 1px #fff; 
    border: solid 1px black;
    border-left: none;
    border-right: none;
    text-align: left; 
    font-size: 1em;
    line-height: 2.5em;
    padding-left: 8px;
    background-color: silver; gray;
    color: white;}

.hnav2, .hnav2 ul li a
{	/* need to middor veritcal padding on .hnav2 and child anchor elements
	 * because the anchors are _not_ block elements. since they are not
	 * block elements web browsers will not expand .hnav2 to contain them
	 * even with the extra padding. by applying the same padding to both
	 * the parent .hnav2 _looks_ like its containing the child anchor
	 * elements. 
	 */
	padding-top: 3px;
	padding-bottom: 4px;}

.hnav2 ul, .hnav2 ul li
{	display: inline;
	list-style-type: none;
	margin:  0;
	padding: 0; }

.hnav2 ul li a
{	margin: 0;
color: black;
	padding-left:  8px;
	padding-right: 8px;
	border-left:  solid 0px black;
	border-right: solid 0px black; /* #2D5A88;  */
	white-space: nowrap;}

.hnav2 ul li a:link, .hnav2 ul li a:visited, .hnav2 ul li a:active, .hnav2 ul li a:hover
{	text-decoration: none; }

.hnav2 ul li a:hover
{	text-decoration: underline overline; }

.hnav201, .hnav202, .hnav203, .hnav204, .hnav205, .hnav206, .hnav207, .hnav208, 
 .hnav209, .hnav210 {}

.hnav2 ul li span.divider { display: none; }
* html .hnav2 ul li, * html .hnav2 ul li a {
	width: 1%; /* IE/Mac needs this */
	display: inline-block;	/* IE/Mac needs this */
	/* \*/
	width:    auto;
	display:  inline; 
	position: relative;
	/* reset above hack */
}
* html .hnav2, * html .hnav2 ul a
{
	/* \*/ height: 0.01%; /* hasLayout hack to fix render bugs in IE/Win. 
				 IE/Mac will ignore this rule. */
}
* html .hnav2
{	padding: 0;	/* IE5/Win will resize #hnav to fit the heights of its
			   inline children that have vertical padding. So this
			   incorrect case selector hack will be applied only by
			   IE 5.x/Win */ }

/******************************************************************************/