/* _content/LearningPlatform.Web/Views/Shared/_Layout.cshtml.rz.scp.css */
/* Please see documentation at https://learn.microsoft.com/aspnet/core/client-side/bundling-and-minification
for details on configuring this project to bundle and minify static web assets. */

a.navbar-brand[b-uktkrh6nam] {
  white-space: normal;
  text-align: center;
  word-break: break-all;
}

a[b-uktkrh6nam] {
  color: #0077cc;
}

.btn-primary[b-uktkrh6nam] {
  color: #fff;
  background-color: #1b6ec2;
  border-color: #1861ac;
}

.nav-pills .nav-link.active[b-uktkrh6nam], .nav-pills .show > .nav-link[b-uktkrh6nam] {
  color: #fff;
  background-color: #1b6ec2;
  border-color: #1861ac;
}

.border-top[b-uktkrh6nam] {
  border-top: 1px solid #e5e5e5;
}
.border-bottom[b-uktkrh6nam] {
  border-bottom: 1px solid #e5e5e5;
}

.box-shadow[b-uktkrh6nam] {
  box-shadow: 0 .25rem .75rem rgba(0, 0, 0, .05);
}

button.accept-policy[b-uktkrh6nam] {
  font-size: 1rem;
  line-height: inherit;
}

/* Removed a leftover default-template ".footer { position: absolute;
   bottom: 0; ... }" rule here. It implemented the old pre-flexbox
   "sticky footer" technique, but this app's real footer positioning is
   the flexbox one in site.css (body: d-flex flex-column min-vh-100;
   main: flex-grow-1; footer: mt-auto). The two techniques conflict:
   the absolute-positioned footer is removed from normal flow, so
   in-flow content (e.g. Workbook Details' Related Workbooks section)
   isn't aware of it and can render underneath/through it. Confirmed via
   computed-style measurement: footer.position was "absolute" and its
   top edge sat ~13px above the bottom of the related-workbooks content,
   overlapping it. Deleting this dead/conflicting rule lets the existing,
   correct flexbox footer take over everywhere. */