/*------------------------------------*\ 
    #PAGES:SEARCH-LANDING
\*------------------------------------*/
.page-wrap {
  margin-top: 20px;
  margin-bottom: 20px;
}

.main-col-wrap {
  margin-bottom: 20px;
}

.search-landing-content {
  width: 100%;
  padding-bottom: 45px;
}
.search-landing-content .landing-forms {
  display: inline-block;
  width: 100%;
}
.search-landing-content .search-type-homefinderai .landing-forms {
  width: 80%;
  margin-left: 10%;
}

.officePhoto img {
  max-width: 100%;
  height: auto;
  display: block;
  margin-right: auto;
  margin-left: auto;
  border: 4px solid #fff;
  /*
      IE9-11 don't properly scale SVG files. For example, if an <img> with an
      SVG file as the src attribute has max-width: 100% and height: auto, the
      image will appear distorted in IE9-11 if the image is larger than its
      container. One solution is to apply width: 100% (or a pixel value equal
      to the SVG's actual width) to the <img>. To apply this fix, we're using
      a few CSS hacks to target these IE versions and style images that have
      an SVG file for their source. Unfortunately, this fix will make SVGs
      that are smaller than their container stretch to the full width of that
      container. In this case, extra styles may be needed. See
      http://caniuse.com/#feat=svg for info on SVG support.

      NOTE: Using services that provide browser detection (e.g. Modernizr,
      Kendo UI) to solve this issue may not be the best idea if they use user
      agent strings to detect browsers as these values aren't always so
      reliable. For example, the Nokia Lumia 930 uses IE11 mobile, but Kendo
      UI's browser detection thought it was Safari 11 which, at the time this
      test was performed, didn't exist yet. The browser returned a user agent
      string that contained "IEMobile/11.0", but also had misleading
      information like "Mobile Safari" and "iPhone OS 7_0_3", and Kendo UI
      incorrectly determined that the browser was Safari 11. User agent
      strings simply aren't reliable. For info on IE11 user agent strings:
      https://blogs.msdn.microsoft.com/ieinternals/2013/09/21/internet-explorer-11s-many-user-agent-strings/

      1.  IE9 hack
      2.  IE10+ hack
  */
}
.officePhoto img[src*=".svg"] {
  width: 100% \9 ; /* [1] */
}
@media screen and (min-width: 0\0 ) {
  .officePhoto img {
    /* [2] */
  }
  .officePhoto img[src*=".svg"] {
    width: 100%;
  }
}
.officePhoto:hover img {
  border: 4px solid #ece9d3;
}

/*
    For content pages that are using this CSS page
*/
.cms-content {
  /*table*/
}
@media (max-width: 767.98px) {
  .cms-content h1 {
    font-size: 24px;
  }
}
@media (max-width: 767.98px) {
  .cms-content h3 {
    font-size: 22px;
  }
}
@media (max-width: 767.98px) {
  .cms-content h4 {
    font-size: 18px;
  }
}
@media (max-width: 767.98px) {
  .cms-content p, .cms-content p.text-sm {
    font-size: 14px;
    line-height: 21px;
  }
}
@media (max-width: 767.98px) {
  .cms-content ul li {
    font-size: 14px;
    line-height: 21px;
  }
}
.cms-content table tbody {
  font-size: 15px;
}
.cms-content table tbody > tr > td {
  padding: 3px 6px;
}
@media (max-width: 767.98px) {
  .cms-content table tbody > tr > td {
    padding: 6px 12px;
  }
}
.cms-content .no-border td {
  border: none;
}
.cms-content .table-small thead tr th {
  padding: 10px 6px;
}
.cms-content .table-small tbody {
  font-size: 12px;
}
.cms-content .table-small tbody > tr > td {
  padding: 3px 6px;
}
@media (max-width: 767.98px) {
  .cms-content .table-small tbody > tr > td {
    padding: 6px 12px;
  }
}
.cms-content .btn {
  white-space: normal;
}
@media (max-width: 767.98px) {
  .cms-content a > button {
    display: table;
    margin: 10px auto !important;
    border-spacing: 0;
    border-collapse: collapse;
  }
}
/*# sourceMappingURL=search-landing.css.map */