/* Styles for status report documents
 * The first section contains styles used when Google Docs documents are included via AJAX.
 * For older content that had manual style classes added see /css/status_report.css.
 * DD July 2015
 */

/* Styles used for included Google Docs
 * Don't let Google styles mess up UPC styles
 */

#tabs #header,
#tabs #footer {
	display: none;
}

#header {
	padding: 0 !important;
	border-bottom: none !important;
	background: none !important;
}

.gdoc_include h1, .gdoc_include h2, .gdoc_include h3, .gdoc_include h4, .gdoc_include strong {
	/*color: #034250 !important; */
	color: #666666 !important; /* Match status_report.css */
	font-family: "UbuntuRegular", "Lucida Grande", Verdana, Arial !important;
}

.gdoc_include h1 {
	color: #666666 !important;
	font-family: "UbuntuRegular", "Lucida Grande", Verdana, Arial !important;
}

.gdoc_include h3 {
	font-size: 1.1em;
}

.gdoc_include h4 {
	font-size: 1.0em;
	margin-bottom: 0 !important;
  font-style: italic;
}

.gdoc_include #contents {
	line-height: 150% !important;
}

.gdoc_include div#contents > div > p {
  /* DD: prior to 14Oct2020 this was set to 'none', but something changed and display
      was not being turned back on (all p text disappeared). Mysterious. */
  display:block;
}

.gdoc_include li::before {
	content: "" !important;
}

/*
.gdoc_include ol {
	/*margin-left:3em !important; 
}
*/

/* ---------
 *
 * This rule is for the "Strategic Focus Areas" section of status reports, but may mess other stuff up.
 *
 * 17 July 2017: Okay, yes, it does mess stuff up. This rule is now applied only
 * to documents with 'statusreports' in the URL -- see include_google_doc.js
 *
 * .gdoc_include ol li span:first-of-type:not(:only-of-type) {font-weight: bold;}
 *
 --------- */

.gdoc_include h4 {
	font-size: 1em;
	font-weight: bold;
	border-bottom: none;
}

.gdoc_include pre.monospace {
	overflow-x: scroll;
}
.gdoc_include pre.monospace p {
	font-family: monospace !important;
}

.gdoc_include table td,
.gdoc_include table th,
.gdoc_include table {
	border: 1px solid #C9CCD8;
}

.gdoc_include h1 + p,
.gdoc_include h1 + p + p,
.gdoc_include hr + p {
	font-style:italic;
	font-size: 1.2em;
	margin: 3px 0 0 0;
	text-align:center;
}
.gdoc_include h1 + p + p {
	margin-bottom:1em;
}

/*
 * When publishing, Google docs does not preserve nesting in lists, but rather
 * styles the sections for nesting level with a unique class. List classes appear
 * to always start with 'lst-' and end with "-" and an integer representing the nesting
 * level (-0 for first level etc.). The following attempts to handle this in CSS
 * so that the nesting levels are preserved.
 * DD 7 April 2017
 */
.gdoc_include ul[class*="lst-"],
.gdoc_include ol[class*="lst-"] {
  margin-top:0;
  margin-bottom:0;
}

.gdoc_include ul[class*="lst-"][class*="-1"] {
  /*color: blue; */
  margin-left: 1em;
  list-style-type: circle;
}

.gdoc_include ol[class*="lst-"][class*="-1"] {
  /*color: blue; */
  margin-left: 1em;
}

.gdoc_include ul[class*="lst-"][class*="-2"] {
  /*color: green; */
  margin-left: 2em;
  list-style-type: square;
}

.gdoc_include ol[class*="lst-"][class*="-2"] {
  /*color: green; */
  margin-left: 2em;
}

.gdoc_include ul[class*="lst-"][class*="-3"] {
  /*color: orange; */
  margin-left: 3em;
  list-style-type: disc;
}

.gdoc_include ol[class*="lst-"][class*="-3"] {
  /*color: orange; */
  margin-left: 3em;
}

/*2024_09 images are being included in a span with an explicit width/height. Override the element formatting.  */
.gdoc_include span[style*="overflow: hidden"] {
  width:auto !important;
  height: auto !important;
}

.gdoc_include img {
  width: 100% !important;
  height: auto !important;
}

/*
 * Starting in October 2017, I was seeing a flash of unstyled stuff when documents
 * (specifically the agenda) are loaded from Google Docs. This is new behavior since
 * the April 2017 committee meetings, and I can't figure it out. Setting the following
 * css rule here minimizes the problem, but if you look closely at the tabs on the
 * left when switching to a tab that is loaded from a Google doc, you'll see some
 * slight differences while the spinner is visible. (Turn off this rule to see it
 * in a more obvious way)
  */
ul#pageNav li {
	background-color: #C9CCD8 !important;
}

/*
 * Starting in summer of 2021 (due to Google document security changes?) a new 
 * div id=banners has been added with some document information. This removes it.
 */

 .gdoc_include div#banners {
   display:none;
 }