/*
 * 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.
 */

/*
 * Pagy's series_nav emits a bare <nav> of bare <a>s and no stylesheet of ours
 * ever picked it up, so pagination rendered as run-together text ("<1234567>").
 * Now that the previous/next links spell out "Anterior" and "Próximo" (#96)
 * they need room to be read as buttons. daisyUI variables keep it on theme.
 */
.pagy {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  justify-content: center;
  gap: 0.25rem;
  font-size: 0.875rem;
}

.pagy a {
  display: inline-flex;
  align-items: center;
  min-width: 2rem;
  height: 2rem;
  padding: 0 0.625rem;
  justify-content: center;
  border-radius: var(--radius-field, 0.5rem);
  color: color-mix(in oklab, currentColor 70%, transparent);
  text-decoration: none;
  transition: background-color 0.15s ease, color 0.15s ease;
}

.pagy a:hover:not([aria-disabled="true"]):not([aria-current="page"]) {
  background-color: color-mix(in oklab, currentColor 10%, transparent);
  color: inherit;
}

/* The disabled "Anterior" on page 1 and "Próximo" on the last page: still
   readable, clearly not clickable. Pagy marks the current page disabled too —
   it is not a link either — so that one is excluded and styled below. */
.pagy a[aria-disabled="true"]:not([aria-current="page"]) {
  color: color-mix(in oklab, currentColor 35%, transparent);
  cursor: default;
}

.pagy a[aria-current="page"] {
  background-color: var(--color-primary, currentColor);
  color: var(--color-primary-content, white);
  font-weight: 600;
  cursor: default;
}