﻿.foo {} /* W3C CSS validator likes CSS files to start with a class rather than a comment. Soooooo.... */

/* This style sheet is intended to contain OFTEN CHANGED rules used when the DetailsView control adapter is enabled. */
/* See FormViewExample.css for comparison of similar rules. */

.faqDetails div.AspNet-DetailsView
{
border: dotted 2px #8DBE44;
background: #EDEDED;
width: 500px; 
}

.faqDetails div.AspNet-DetailsView-Data ul 
{
    
}

/* Please refer to FormViewExample.css for comments on these rules. */
.faqDetails div.AspNet-DetailsView-Header
{
font-size: 13px;
font-weight: bold; 
padding: 5px 0;

}

.faqDetails div.AspNet-DetailsView-Data
{

}

/* Each field defined for the DetailsView generates an individual list item (li) in the rendered HTML. */
/* Each li effectively is a row in a table (though no table tag is generated by the adapter). */
.faqDetails div.AspNet-DetailsView-Data li
{
    padding-left: 10px;
    vertical-align: middle;
    list-style: none;
    min-height:1.4em; /* ADDED for Firefox */
}

/* Every other field is marked as being "Alternate." */
/* This allows you to define an "alternating row" style (though the adapter doesn't actually generate an HTML table). */
.faqDetails div.AspNet-DetailsView-Data li.AspNet-DetailsView-Alternate
{
  
}

/* This corresponds to the HeaderText attribute of an <asp:BoundField>. */
.faqDetails span.AspNet-DetailsView-Name
{
    font-size: 11px;
    vertical-align: middle;
    display: block;
    padding: 3px 0;
    
        
}

/* This corresponds to the DataField attribute of an <asp:BoundField>. */
.faqDetails span.AspNet-DetailsView-Value
{
    font-size: 11px;
}

/* --------------------------------------------------------------------------------------------------- */
/* Please refer to FormViewExample.css for comments on these rules. */
.faqDetails .AspNet-DetailsView-Pagination
{
    color: #F7F6F3;
    background: #E9F5DA;
    font-weight: bold;
    text-align:center;
    color:#465239;
    text-transform:uppercase;
    padding:10px 0;
    width:100%;
    position:relative;
    clear:both;
}

.faqDetails .AspNet-DetailsView-ActivePage
{
    padding:2px;
    color:#999;
    font-family:Verdana, Sans-Serif;
}

.faqDetails .AspNet-DetailsView-OtherPage
{
    padding:2px;
}

.faqDetails a.AspNet-DetailsView-OtherPage:link
{

}

.faqDetails a.AspNet-DetailsView-OtherPage:visited
{

}

.faqDetails a.AspNet-DetailsView-OtherPage:hover
{
    text-decoration:none;
    background:#FFF;
    color:#000;
}

/* --------------------------------------------------------------------------------------------------- */
/* Used when the DetailsView adapter is NOT used. */
/* These styles are used by the DetailsView's skin, found in this theme's skin file. */

table tr.DetailsView-Skin-Header
{
    text-transform:uppercase;
}

table tr.DetailsView-Skin-Row td,
table tr.DetailsView-Skin-Alternating td
{
    border-top: solid 1px #E7E7E7;
    border-right: solid 1px #D2D2D2;
    border-bottom: solid 1px #D2D2D2;
    border-left: solid 1px #E7E7E7;
}

table tr.DetailsView-Skin-Alternating
{
    background:url(bg-fade-light-short.png) repeat-x bottom;
}