/*
 | The way back from a content page follows the reader down (#1385).
 |
 | `LeadsBackToTheResults` puts «Back to the results» in the page header, so
 | on a long content leaving meant scrolling back to the top first.
 | `back-to-results.js` measures how far the header has gone above the topbar
 | and hands the distance over as `--ssmt-follow`; the button is shifted by
 | exactly that much.
 |
 | A transform and not `position: fixed`, on purpose: the button keeps its
 | slot in the header, so the actions beside it do not jump left when it
 | starts following, and its horizontal place is the one it already had —
 | nothing to compute against the sidebar, the viewport or a breakpoint.
 | `position: relative` is there for the `z-index` alone: without it the
 | sections painted after the header cover the button.
 |
 | Translucent while it follows, because then it sits over the content; a
 | pointer on it, or the keyboard's focus, brings it back to full strength.
 | ⚠️ `:focus-visible` is not decoration: a reader on the keyboard does not
 | hover, and without it would tab onto a button at half opacity.
 */
.ssmt-back-to-results {
    position: relative;
    z-index: 20;
    transform: translateY(var(--ssmt-follow, 0px));
    transition: opacity 150ms ease-out;
}

.ssmt-back-to-results.ssmt-back-to-results--following {
    opacity: 0.45;
}

.ssmt-back-to-results.ssmt-back-to-results--following:hover,
.ssmt-back-to-results.ssmt-back-to-results--following:focus-visible {
    opacity: 1;
}