/* These styles are applied by the REGULAR master page. 
    To get the most out of CSS, create styles based on the item to style, and not the style 
    you're going for.  For example, imgGift is easy to maintain because we know it will only 
    affect gift images.  fontSize12 is not ideal because at some point in the future we may 
    decide that 12pt is too big/small, or that for ADA a set-size font is not acceptable.  At 
    that time, we would need to :
      - change the class' font size, which makes the name 'fontsize12' misleading, or
      - change the class' name, which requires every content page (that uses it) to be modified.
    A better solution is to use our fontSizeA-E classes, or (even better) a sectional class
    like 'breadcrumbs' or 'sectiontext' that can manage its own text styles.  Also remember that,
    now that portal is here, we can't just change the markup to fix a style.  We have to use
    CSS for positioning!
*/ 

/* =Content panes */
form {padding:0;margin:0;}
body {padding:0;margin:4px;}
#BodyTable {vertical-align:top;width:100%;}

.iTopPane {text-align:left;vertical-align:middle;white-space:nowrap;}
.iLeftPane {vertical-align:top;width:174px;overflow:hidden;display:table;}
.iContentPane {vertical-align:top;width:100%;}
.iFooterPane {font-size:small;text-align:center;}
.iLeftPane .shoppingcart {display:block;border-bottom: 1px solid #999999;}
.search_v, .Vnav, .shoppingcart {width:100%;}

/* Do not force portal to override default link styles. */
A:link {color:#000099;text-decoration:none}
A:visited {color:#000099;text-decoration:none}
A:hover {color:#0000FF;text-decoration:none}
A:active {color:#FFCC00;text-decoration:none}

/* Does this go to masterbase or masterR? */
.toTopImg {vertical-align:bottom;text-align:right;}
.search_v, .Search_v, .Search_h {font-size:small;font-style:normal;font-weight:normal;font-family:Arial;}