/**
 * Helper variables for media queries. Makes sure we use standard queries and not make up our own
 */
@font-face {
  font-family: "Open Sans";
  font-display: swap;
  src: url("../styles/fonts/open-sans-regular.woff") format("woff"), url(".woff") format("woff");
  font-style: normal;
  font-weight: normal;
}
@font-face {
  font-family: "Open Sans";
  font-display: swap;
  src: url("../styles/fonts/open-sans-semibold.woff") format("woff"), url(".woff") format("woff");
  font-style: normal;
  font-weight: 600;
}
@font-face {
  font-family: "Open Sans";
  font-display: swap;
  src: url("../styles/fonts/open-sans-bold700.woff") format("woff"), url(".woff") format("woff");
  font-style: normal;
  font-weight: bold;
}
html {
  font-size: 16px;
}

/**
 * As of 2019-12-10, W3C has put forward a standard for the css rule inset-inline-start
 * (which should be used instead of right/left to support right-to-left languages).
 * However, as it's not supported yet in Safari, and is still in experimental mode for Chrome,
 * we're stuck with this mixin for now. See also mixin, inset-inline-end.
 */
/**
 * As of 2019-12-10, W3C has put forward a standard for the css rule inset-inline-start
 * (which should be used instead of right/left to support right-to-left languages).
 * However, as it's not supported yet in Safari, and is still in experimental mode for Chrome,
 * we're stuck with this mixin for now. See also mixin, inset-inline-start.
 */
/**
 * Most browsers do not yet support float with relative values (inline-start).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support float with relative values (inline-end).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support clear with relative values (inline-start).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support clear with relative values (inline-end).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-top-right-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-bottom-right-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-bottom-left-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-top-left-radius (in LTR).
 */
/**
 * Wrap _reflexive-property with support for both ltr and rtl cases.
 * @param $ltr-property the property you'd expect in ltr
 * @param $rtl-property the property you'd expect in rtl
 * @param $left-value the value that the property should have when ltr
 * @param $right-value the value that the property should have when rtl
 */
/**
 * Despite Angular scoping, and bug causing nested host-context declarations to fail,
 * select elements that are preceeded by an ancestor which sets dir
 * @param $dir the direction to look for
 * @param $property the property to set the value for
 * @param $value the value that the property should have
 * Due to a bug in Angular related to the usage of host-context with or (,)
 * we use two cases of @at-root instead.
 */
/**
 * Set sticky position
 */
/**
 * As of 2019-12-10, W3C has put forward a standard for the css rule inset-inline-start
 * (which should be used instead of right/left to support right-to-left languages).
 * However, as it's not supported yet in Safari, and is still in experimental mode for Chrome,
 * we're stuck with this mixin for now. See also mixin, inset-inline-end.
 */
/**
 * As of 2019-12-10, W3C has put forward a standard for the css rule inset-inline-start
 * (which should be used instead of right/left to support right-to-left languages).
 * However, as it's not supported yet in Safari, and is still in experimental mode for Chrome,
 * we're stuck with this mixin for now. See also mixin, inset-inline-start.
 */
/**
 * Most browsers do not yet support float with relative values (inline-start).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support float with relative values (inline-end).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support clear with relative values (inline-start).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support clear with relative values (inline-end).
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-top-right-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-bottom-right-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-bottom-left-radius (in LTR).
 */
/**
 * Most browsers do not yet support border with relative values.
 * Therefore, we are forced to rely upon our own mixin, if we are to support right-to-left languages.
 * This one replaces border-top-left-radius (in LTR).
 */
/**
 * Wrap _reflexive-property with support for both ltr and rtl cases.
 * @param $ltr-property the property you'd expect in ltr
 * @param $rtl-property the property you'd expect in rtl
 * @param $left-value the value that the property should have when ltr
 * @param $right-value the value that the property should have when rtl
 */
/**
 * Despite Angular scoping, and bug causing nested host-context declarations to fail,
 * select elements that are preceeded by an ancestor which sets dir
 * @param $dir the direction to look for
 * @param $property the property to set the value for
 * @param $value the value that the property should have
 * Due to a bug in Angular related to the usage of host-context with or (,)
 * we use two cases of @at-root instead.
 */
body {
  height: 100vh;
  max-height: 100vh;
  margin: 0px;
}

.container {
  width: 100%;
  display: grid;
  font-family: "Open Sans", sans-serif;
}

.background-img-lg {
  position: fixed;
  height: 100vh;
  width: 100vw;
  left: 0;
  top: 0;
  z-index: -1;
  -ms-background-size: cover;
  -o-background-size: cover;
  -moz-background-size: cover;
  -webkit-background-size: cover;
  background-size: cover;
  background-repeat: no-repeat;
  background-position: 50% 0;
  background-color: black;
}
@media only screen and (max-width:959px) {
  .background-img-lg {
    display: none;
  }
}
.background-img-lg.ifs-is-phone {
  display: none;
}

.background-img-sm {
  position: fixed;
  height: 100vh;
  width: 100vw;
  left: 0;
  top: 0;
  z-index: -1;
  display: none;
}
@media only screen and (max-width:959px) {
  .background-img-sm {
    background: black;
    display: block;
  }
}

.background-fill {
  position: fixed;
  height: 100vh;
  width: 100vw;
  left: 0;
  top: 0;
  background: rgba(0, 0, 0, 0.5);
  z-index: 1;
}

.header {
  width: 100%;
  z-index: 2;
}

.page-content {
  width: 100%;
  margin-top: 9rem;
  z-index: 3;
}
.ifs-logo {
  position: absolute;
  left: 0;
  top: 0;
  width: 10rem;
  height: 5.5rem;
}
@media only screen and (max-width: 599px) {
  .ifs-logo {
    width: 10.5rem;
    height: 7rem;
  }
}
.ifs-logo::before {
  content: " ";
  position: absolute;
  left: 0;
  top: 0;
  z-index: -1;
  width: 10rem;
  height: 5.5rem;
  background-repeat: no-repeat;
  background-image: url("../resources/logos/IFS_LOGO_BG.svg");
  -ms-background-size: contain;
  -o-background-size: contain;
  -moz-background-size: contain;
  -webkit-background-size: contain;
  background-size: contain;
}
@media only screen and (max-width: 599px) {
  .ifs-logo::before {
    display: none;
  }
}
.ifs-logo::after {
  content: " ";
  position: absolute;
  z-index: 0;
  height: 3rem;
  width: 6.5rem;
  left: 0;
  right: 0;
  margin: auto;
  top: 0;
  bottom: 0;
  -ms-background-size: cover;
  -o-background-size: cover;
  -moz-background-size: cover;
  -webkit-background-size: cover;
  background-size: cover;
  background-repeat: no-repeat;
  background-image: url("../resources/logos/IFS_LOGO_NEGATIVE_RGB.svg");
}

.titles-header {
  color: white;
  text-align: center;
  width: 100%;
  font-weight: bold;
  font-size: 1.5rem;
  line-height: 2.25rem;
  text-transform: uppercase;
}

.titles-section {
  color: white;
  text-align: center;
  width: 100%;
  font-weight: bold;
  font-size: 1rem;
  line-height: 1.5rem;
}

/*# sourceMappingURL=base.css.map */