/* no overrides defined */

/* ---------------------------------------------------------------------------
 * Sitemap footer (WCAG 2.4.5 Multiple Ways)
 *
 * Mirrors style-override.css. Rendered by the @SitemapFooter Tapestry
 * component inside the user-web-tools footer. Collapsed: a "▸ Sitemap"
 * disclosure-link anchored to the right edge of the footer. Expanded: a
 * popover above the summary with every user-web-tools link the current user
 * can reach (filtered by ConfigManager, group-limits, print-module licensing,
 * etc.).
 * ------------------------------------------------------------------------ */
#footer {
    position: relative;
}

.sitemap-footer {
    position: absolute;
    top: 50%;
    right: 1.5em;
    margin-top: -0.75em;
    font-size: 12px;
}

.sitemap-footer summary {
    cursor: pointer;
    color: #0D7621;
    list-style: none;
}

.sitemap-footer summary::-webkit-details-marker {
    display: none;
}

/* Visual-only open/closed marker. aria-hidden="true" on the <span> keeps it
   out of the summary's accessible name. */
.sitemap-footer .sitemap-marker {
    display: inline-block;
    width: 1em;
}

.sitemap-footer .sitemap-marker::before {
    content: "\25B8";
}

.sitemap-footer[open] .sitemap-marker::before {
    content: "\25BE";
}

.sitemap-footer summary:hover,
.sitemap-footer summary:focus-visible {
    text-decoration: underline;
}

.sitemap-footer summary:focus-visible {
    outline: 2px solid #0D7621;
    outline-offset: 2px;
}

/* Anchored to the trigger via position: absolute on .sitemap-footer (which is
   itself absolute, so it acts as the containing block). bottom: calc(100% +
   0.5em) opens the popover just above the trigger. The earlier position: fixed
   approach (bottom: 4em from viewport) failed when #footer rendered taller
   than ~3em - the trigger sat above the popover's bottom edge and the popover
   covered it. Absolute keeps the popover anchored to the trigger regardless
   of footer height. #container's overflow: hidden does not clip in practice
   because the popover (~150px content, max 70vh) fits within the available
   space above #footer in realistic viewports. */
.sitemap-footer[open] > nav {
    position: absolute;
    bottom: calc(100% + 0.5em);
    right: 0;
    background: #ffffff;
    border: 1px solid #cccccc;
    border-radius: 6px;
    box-shadow: 0 4px 16px rgba(0, 0, 0, 0.15);
    padding: 1em 1.25em;
    width: 360px;
    max-width: 90vw;
    max-height: 70vh;
    overflow-y: auto;
    z-index: 50;
    line-height: 1.5;
}

/* Mirrors style-override.css. User-web-tools sitemap is flat (each nav link
   IS a page) so .sitemap-children rules are present for symmetry but will
   typically not render. column-fill: auto + an explicit height fills
   column 1 first, then column 2 starts at the top - without this, Safari's
   default balanced fill leaves an orphan gap at the top of column 2.
   Sized for the current ~10-link user nav split across two columns; raise
   if the nav grows. */
.sitemap-footer[open] .sitemap-sections {
    columns: 2;
    column-gap: 2em;
    column-fill: auto;
    height: 130px;
    margin: 0;
    padding: 0;
    list-style: none;
}

.sitemap-footer[open] .sitemap-sections > li {
    break-inside: avoid;
    padding: 0;
    margin: 0 0 0.4em 0;
}

/* Scoped under #footer to beat the user-web-tools base a:link rule, mirroring
   the admin override. Section links use #222 bold so they read as primary
   navigation and clear WCAG AA comfortably (the brand green at #0D7621 sits
   right on the 4.5:1 threshold on white). */
#footer .sitemap-footer[open] .sitemap-section-link {
    display: block;
    padding: 1px 0;
    color: #222222;
    font-weight: 700;
    text-decoration: none;
}

#footer .sitemap-footer[open] .sitemap-section-link:hover,
#footer .sitemap-footer[open] .sitemap-section-link:focus-visible {
    text-decoration: underline;
    color: #0D7621;
}

#footer .sitemap-footer[open] > nav a[aria-current="page"] {
    font-weight: 700;
    border-left: 2px solid #0D7621;
    padding-left: 0.5em;
    margin-left: -0.65em;
}

/* Inset (negative offset) keeps the focus ring inside the link's box, so it
   doesn't get clipped by the popover's overflow:auto edges or extend past
   the right border on column-2 links. */
#footer .sitemap-footer[open] > nav a:focus-visible {
    outline: 2px solid #0D7621;
    outline-offset: -2px;
    border-radius: 2px;
}

.sitemap-footer[open] .sitemap-children {
    list-style: none;
    margin: 0.15em 0 0 0.9em;
    padding: 0 0 0 0.75em;
    border-left: 1px solid #e2e2e2;
}

.sitemap-footer[open] .sitemap-children li {
    padding: 1px 0;
}

#footer .sitemap-footer[open] .sitemap-children a {
    color: #0D7621;
    text-decoration: none;
    font-weight: 400;
}

#footer .sitemap-footer[open] .sitemap-children a:hover,
#footer .sitemap-footer[open] .sitemap-children a:focus-visible {
    text-decoration: underline;
}