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

/* ── Trix WYSIWYG ─────────────────────────────────────────────────────────── */
trix-editor.form-control {
  padding: 0.375rem 0.75rem;
  border-radius: var(--bs-border-radius);
}

trix-editor.form-control:focus {
  outline: 0;
  box-shadow: 0 0 0 0.25rem rgba(13, 110, 253, 0.25);
  border-color: #86b7fe;
}

trix-toolbar .trix-button-group {
  margin-bottom: 0.25rem;
}

/* ── Dark mode palette ────────────────────────────────────────────────────── *
 * Bootstrap's `.table-light` / `.table-dark` utilities are fixed colors by
 * design (they don't flip with data-bs-theme), but this app uses `.table-light`
 * as its standard table-header style everywhere. Remap it to Bootstrap's own
 * theme-reactive surface variables so every table head follows the same
 * palette as the rest of the page in dark mode, with no per-view changes. */
[data-bs-theme="dark"] .table-light {
  --bs-table-color: var(--bs-body-color);
  --bs-table-bg: var(--bs-tertiary-bg);
  --bs-table-border-color: var(--bs-border-color);
  --bs-table-striped-bg: var(--bs-secondary-bg);
  --bs-table-striped-color: var(--bs-body-color);
  --bs-table-active-bg: var(--bs-secondary-bg);
  --bs-table-active-color: var(--bs-body-color);
  --bs-table-hover-bg: var(--bs-secondary-bg);
  --bs-table-hover-color: var(--bs-body-color);
}
