/*
 * This is a manifest file that'll be compiled into application.css.
 *
 * With Propshaft, assets are served efficiently without preprocessing steps. You can still include
 * application-wide styles in this file, but keep in mind that CSS precedence will follow the standard
 * cascading order, meaning styles declared later in the document or manifest will override earlier ones,
 * depending on specificity.
 *
 * Consider organizing styles into separate files for maintainability.
 */

/* Mobile overflow menu (#390) — belt-and-braces copy for Propshaft :app
 * resolution if the Tailwind build is stale. Source of truth also lives in
 * app/assets/tailwind/application.css. */
.top-nav-menu-button {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 2.5rem;
  height: 2.5rem;
  padding: 0;
  border-radius: 0.375rem;
  border: 1px solid var(--color-border-subtle);
  background: var(--color-primary);
  color: var(--color-text-muted);
  cursor: pointer;
}
.top-nav-menu-button:hover,
.top-nav-menu-button[aria-expanded="true"] {
  color: var(--color-text);
  border-color: var(--color-accent);
}
.top-nav-menu-icon {
  display: flex;
  flex-direction: column;
  justify-content: space-between;
  width: 1.1rem;
  height: 0.85rem;
}
.top-nav-menu-icon > span {
  display: block;
  height: 2px;
  border-radius: 1px;
  background: currentColor;
}
.top-nav-mobile-panel {
  display: flex;
  flex-direction: column;
  gap: 0.75rem;
  padding: 0.85rem 1.25rem 1.1rem;
  border-top: 1px solid var(--color-border-subtle);
  background: var(--color-surface);
}
.top-nav-mobile-panel[hidden] {
  display: none !important;
}
.top-nav-mobile-panel .nav-link {
  display: block;
  padding: 0.35rem 0;
}
@media (min-width: 768px) {
  .top-nav-menu-button {
    display: none;
  }
  .top-nav-mobile-panel {
    display: none !important;
  }
}