/*
 * foundation-overrides.css
 *
 * Theme customisations layered on Foundation's own selectors, extracted from the
 * dc monolith (sites/dc/dc-child/style.css) and tokenised per the colour rules.
 * Loads AFTER foundation.css. Colour is always var(--token); no hex in base-theme.
 *
 * Source site: dc. Only two genuine, generic Foundation-selector overrides exist in
 * the dc monolith: the global form-control reset and the .pagination restyle.
 * (.course-tabs .tabs* is course-block-scoped, not a generic Foundation override -
 *  it belongs with the courses block, not here. See agent report.)
 *
 * Phase 3c-1 Foundation-conflict resolution (brief §Foundation):
 *   1. Link colour. Foundation shipped #1779ba on links; the theme's base
 *      anchor colour lives in typography.css (var(--blue-text)) which loads
 *      after this file, but Foundation's own component links (.breadcrumbs a
 *      kept in the fork) still carry #1779ba, so the token link colour is set
 *      here too as the belt-and-braces default. Underlying Foundation rule the
 *      later trim can delete: `.breadcrumbs a { color:#1779ba }` and the base
 *      anchor colour (already extracted to typography.css).
 *   2. Buttons / forms / cards / tables were DELETED from the fork (not
 *      overridden), so no override entry is needed for them.
 *   3. .button.tiny / .button.small collapse (Phase 2.5) is moot now the
 *      .button component is gone.
 */

/* 1. Foundation link colour -> token (conflict #1). The base anchor colour is
   owned by typography.css (loads after this file); Foundation's kept component
   link (.breadcrumbs a, still #1779ba in the fork) is overridden here. */
.breadcrumbs a {
  color: var(--blue-text);
}

/* Form controls - reset Foundation's native input/select/button/textarea chrome.
   Source dc L3858-3888. No colour. */
input[type="text"],
input[type="email"],
input[type="submit"],
input[type="button"],
select,
option,
button,
textarea {
  -moz-appearance: none;
  text-indent: 0.01px;
  text-overflow: "";
  -webkit-appearance: none;
  border-radius: 0;
  border: none;
}
/* The `:focus { outline: none }` block that used to live here is REMOVED, not
   moved. `button:focus` is (0,1,1) and out-specified the global
   `:focus-visible` rule in base.css (0,1,0), so eleven components rendered with
   no keyboard focus indicator at all: a WCAG 2.4.7 failure at AA.
   Suppressing the mouse-click ring is what :focus-visible is for; it does that
   already. Do not reintroduce a blanket focus reset. */

/* Pagination - theme fully restyles Foundation's .pagination (WP paginate_links markup).
   Source dc L6944-6982. */
.pagination {
  background-color: var(--surface-alt);
  overflow: hidden;
  padding: 2rem 0;
  margin: 0;
}
.pagination ul {
  margin: 0;
  padding: 0;
  text-align: center;
}
.pagination ul li {
  margin: 0 0.2rem;
  text-align: center;
  line-height: 1;
  text-indent: inherit;
  font-size: 1.1rem;
  padding-left: 0;
}
.pagination ul li a {
  background: var(--neutral-200);
  padding: 1rem 1.5rem;
  color: var(--text);
  transition: all 0.2s ease;
  text-align: center;
  display: block;
}
.pagination ul li a:hover {
  background-color: var(--surface-brand);
  color: var(--text-on-dark);
  transition: all 0.2s ease;
}
.pagination ul li.active a {
  background-color: var(--surface-brand);
  color: var(--text-on-dark);
}
.pagination ul li:before {
  content: none;
}