﻿/* kc-v2 v1.5.7 -- tables & lists */
/* Full class contract and conventions: see README.md and kc-v2-base.css. */

/* ---------------------------------------------------------------------------
 * Tables & Lists
 *
 * border-collapse: collapse disables border-radius on the <table> itself, so
 * the wrapper (not the table) owns the radius/border and clips with
 * overflow: hidden. overflow-x: auto on the wrapper is a safety net for
 * genuinely-too-wide content -- the TABLE scrolls, never the page.
 * ------------------------------------------------------------------------- */

.kc-v2-table-wrapper {
  box-sizing: border-box;
  overflow-x: auto;
  border: 1px solid var(--kc-v2-ink-200);
  border-radius: var(--kc-v2-radius-lg);
  /* min-width: 0 is what makes overflow-x: auto actually work inside a flex container (1.5.0,
     KENT-56).
     A flex item's min-width defaults to `auto`, meaning "do not shrink below my content's min-content
     width". So a wrapper holding a wide table inside a .kc-v2-stack (which is display: flex) grows to
     the table's min-content instead of staying at the column width -- and once the box is that wide,
     overflow-x has nothing to overflow. The scroll silently moves from the wrapper to the PAGE, which
     is the opposite of the point.
     Same root cause as the min-width: 0 on .kc-v2-fieldset: an element that refuses to shrink hands
     its overflow to an ancestor.
     HONEST NOTE ON EVIDENCE: the fieldset fix is demonstrated -- before it the suite named
     FIELDSET at 724px as extending past the viewport, and after it nothing does. This one is
     correct by construction rather than by measurement: it did not move the residual 375px
     page-overflow number on the employee-details screen, which is recorded as an open item in
     bl-details-test.js. Kept because a flex item with overflow-x: auto and min-width: auto cannot
     scroll, which is a real defect wherever it occurs, not because it closed that particular gap. */
  min-width: 0;
}

.kc-v2-table {
  width: 100%;
  border-collapse: collapse;
  border-spacing: 0;
  font-family: var(--kc-v2-font-family);
}

/* Bootstrap's bare `table { margin-bottom: â€¦ }` / `table { margin-top: â€¦ }` was
   adding a 9.375px top margin to every kc-v2 table. */
.kc-v2-table {
  margin: 0;
}

/* Community.css ships a bare `tr { vertical-align: top; }`, which is (0,0,1) and
   loses to this (0,1,1) selector -- but only because kc-v2 now declares the
   property. Without it, every cell in a kc-v2 table top-aligned instead of
   centring (KENT-59 Phase 0 spike). site.css also styles bare `th` and `td`. */
.kc-v2-table tr,
.kc-v2-table th,
.kc-v2-table td {
  vertical-align: middle;
}

.kc-v2-table th {
  padding: 14px 22px;
  background-color: var(--kc-v2-ink-900);
  color: var(--kc-v2-white);
  font-size: 12.5px;
  font-weight: 600;
  text-align: left; /* UA default for th is center -- Figma's headers are left-aligned */
  white-space: nowrap;
}

/* line-height declared so row height is the component's decision, not the host body's (site.css
   gives 17.9px, Bootstrap 20px). KENT-44 audit. */
.kc-v2-table td {
  padding: 18px 22px;
  line-height: 20px;
  border-top: 1px solid var(--kc-v2-ink-100);
  font-size: 14px;
  /* ink-600, the same ink every other piece of kc-v2 body text uses (.kc-v2-prose, and the
     .kc-v2-segmented buttons that sit in these very rows). This was ink-500, which put TWO
     different inks in a single row of the city-fees grid -- the city name and fee read as
     secondary text beside their own controls. Measured: cells rgb(91,107,122) against segmented
     rgb(51,70,86). Also raises contrast on white from 5.48:1 to roughly 9:1.
     Reported on the city fees / service type grid; fixed on the component so every kc-v2 table
     gets it, since the earnings grid had the same discrepancy.

     KENT-44 QA reported the city-selection text as "closer to the background color than I would
     like" and this was briefly darkened to ink-800 in response. Reverted after measuring: ink-600
     on the segmented track was already 8.68:1 and on white 9.76:1, so there was no contrast defect
     to fix. The real cause was the segmented options having no fill and no border, which made their
     labels read as low-emphasis text rather than controls -- fixed there, in kc-v2-forms.css.
     Darkening here would also have broken the three-way match between cells, segmented and prose
     that the license suite asserts. */
  color: var(--kc-v2-ink-600);
  overflow-wrap: anywhere; /* long account numbers/emails must not force page-level horizontal scroll */
}

.kc-v2-table tbody tr:nth-child(even) {
  background-color: #F9FBFD; /* a one-off zebra tint, not reused elsewhere,
                                 so not promoted to a token */
}

/* EXPLICIT alternate row, for grids where nth-child cannot work (1.5.1, KENT-44 QA).
   Shared/_CityFeesGrid.cshtml emits TWO <tr> per city -- the data row and a per-city detail row that
   is hidden unless the filer picks Location or Both. So every data row is an odd child and the rule
   above only ever tints the hidden one: the Annual city-selection grid rendered with no striping at
   all, while the Business License grids -- whose detail forms were moved outside the table in
   KENT-56 -- striped correctly. QA reported exactly that asymmetry.
   The page marks its own data rows from the Knockout index instead, which is immune to however many
   sibling rows sit between them. Same tint, so a grid using this is indistinguishable from one using
   nth-child. */
.kc-v2-table tbody tr.kc-v2-table__row--alt {
  background-color: #F9FBFD;
}

/* ---------------------------------------------------------------------------
 * Totals row (KENT-44 1.2.0)
 *
 * A <tfoot> summarising the columns above it. Previously the annual-return earnings step put its
 * totals in a SECOND, detached table beside the Back/Next buttons, so a figure and the column it
 * totalled were never vertically aligned and the reader had to map them by name.
 *
 * The zebra rule above is scoped to tbody, so a tfoot row is not caught by it and needs its own
 * fill. Emphasised with the tinted background and heavier weight because it is a conclusion, not
 * another data row.
 * ------------------------------------------------------------------------- */
.kc-v2-table tfoot td {
  padding: 16px 22px;
  border-top: 2px solid var(--kc-v2-ink-200);
  background-color: var(--kc-v2-ink-50);
  color: var(--kc-v2-ink-800);
  font-size: 14px;
  font-weight: 700;
  line-height: 20px;
}
/* An UNEMPHASISED totals row (1.5.0). Renders as an ordinary body row: no tint, no heavy rule above
   it, normal weight.
   The emphasised default earns its keep on the Annual earnings grid, where the totals row is the
   conclusion of a dense numeric table. It is wrong on the Business License city grid, where the
   "total" is a running subtotal beside a column of small fees and the tint plus a dark row-header
   read as a footer bar bolted to the bottom of the card. Both flows' grids opt out.
   (0,2,2) against the base rule's (0,1,2), so it wins on class count without an !important. */
.kc-v2-table tfoot.kc-v2-table__foot--plain td {
  padding: 14px 22px;
  border-top: 1px solid var(--kc-v2-ink-200);
  background-color: transparent;
  font-size: 14px;
  font-weight: 400;
}

/* The grand total: the one figure a filer is looking for.
 *
 * Element-qualified because `.kc-v2-table tfoot td` above is (0,1,2) and the bare modifier was
 * (0,1,0) -- so the component's own base rule beat its own modifier and the total rendered in
 * ink-800 like every other totals cell. Nothing to do with a host stylesheet; a self-inflicted
 * specificity loss, caught by asserting the colour rather than only the class. `td.` makes this
 * (0,2,1), which wins on class count. */
.kc-v2-table td.kc-v2-table__cell--total {
  color: var(--kc-v2-blue);
  font-size: 15px;
}

.kc-v2-table th.kc-v2-table__cell--label,
.kc-v2-table td.kc-v2-table__cell--label {
  overflow-wrap: normal;
  word-break: normal;
}

/* ---------------------------------------------------------------------------
 * Editable cells (KENT-44 1.2.0)
 *
 * A cell whose content is an input rather than text. Padding is tightened because the control
 * brings its own, and the row would otherwise be ~80px tall across an 18-row grid.
 *
 * .kc-v2-input--compact is the control itself: shorter than the 43px standalone height, and
 * right-aligned to line up with the read-only numerics either side of it. Element-qualified for the
 * same reason as input.kc-v2-input -- Returns.css's input[type="text"] rule is (0,1,1) and would
 * otherwise win the height back.
 * ------------------------------------------------------------------------- */
.kc-v2-table__cell--input {
  padding: 8px 12px;
}

/* Dense grid: many input columns. Headers wrap and padding tightens so the whole row fits without
   horizontal scrolling, and inputs fill their cell rather than sizing to a default width. */
.kc-v2-table.kc-v2-table--dense th {
  padding: 10px 12px;
  white-space: normal;
}
.kc-v2-table.kc-v2-table--dense td {
  padding: 8px 12px;
}
.kc-v2-table--dense .kc-v2-input--compact {
  width: 100%;
  min-width: 0;
}
/* BOTH classes named, deliberately: this must win on SPECIFICITY, not on load order.
   `input.kc-v2-input--compact` alone is (0,1,1) -- exactly the same as `input.kc-v2-input` in
   kc-v2-forms.css, which sets height: 43px / padding: 0 14px / font-size: 16px. An element carrying
   both classes matched both rules with the tie broken purely by which file the host happened to link
   last. Every current host links forms before tables so it worked, but kc-v2-base.css states the
   contract as "then the component files (any order)" and kc-v2-pagination.css repeats it -- and for
   this one pair that was false.
   Reversing the link order, alphabetising it, or bundling the files would jump every compact input
   from 34px/14px to 43px/16px. Counted: 72 occurrences of the class across 10 views -- _ScheduleX,
   _ScheduleY, _NetSchedule, _GrossSchedule, _AnnualEarnings, _AnnualConfirmation, _QuarterlyEarnings,
   _QuarterlyEmployees, BusinessLicenseAdd/_AddressConfirm, and the styleguide. The RENDERED count is
   higher, because several of those sit inside Knockout foreach templates and repeat per row.
   Those grids are tuned to fit without horizontal scroll, so ~26% taller rows and a wider
   min-content would reintroduce exactly the page-level sideways scroll this library exists to
   prevent.
   `input.kc-v2-input.kc-v2-input--compact` is (0,2,1) and wins in either order, which makes the
   documented contract true again. Swept the other twelve files: this was the only cross-file
   element-qualified collision. */
input.kc-v2-input.kc-v2-input--compact {
  height: 34px;
  padding: 6px 10px;
  font-size: 14px;
  text-align: right;
  font-variant-numeric: tabular-nums;
}

/* A dense-grid money input that must not shrink below a six-figure amount (KENT-115). Below that
   width the table scrolls inside its wrapper instead of clipping the figure. */
.kc-v2-table--dense input.kc-v2-input--compact.kc-v2-input--amount {
  min-width: 104px;
}
/* A zero amount, muted so the figures that were actually entered stand out (KENT-115). ink-500, not
   ink-400: this is text, and ink-400 is under 3:1 on white. */
.kc-v2-table--dense input.kc-v2-input--compact.kc-v2-input--zero {
  color: var(--kc-v2-ink-500);
}
/* A figure the page has a soft concern about -- the filer may still continue. Invalid input is
   aria-invalid, which keeps its red: the :not() stops this amber from painting over it. */
.kc-v2-table--dense input.kc-v2-input--compact.kc-v2-input--warning:not([aria-invalid="true"]) {
  border-color: var(--kc-v2-warning);
  background-color: var(--kc-v2-warning-bg);
}

input.kc-v2-input.kc-v2-input--compact.kc-v2-input--start {
  text-align: start;
  font-variant-numeric: normal;
}

select.kc-v2-select.kc-v2-select--compact {
  height: 34px;
  padding: 0 30px 0 10px;
  font-size: 14px;
}

.kc-v2-table--dense .kc-v2-select-wrapper::after {
  right: 12px;
}

/* ---------------------------------------------------------------------------
 * Sortable column headers (KENT-44 1.2.0)
 *
 * The header cell stays a <th>; the control inside it is a real <button>, so sorting is reachable by
 * keyboard. The previous markup put a click binding on the <th> itself with a jQuery-UI icon span,
 * which no keyboard user could operate.
 *
 * aria-sort on the <th> is the state hook (README rule 4: native/ARIA attribute before a modifier
 * class), and the arrow is drawn from it, so the visual and the announced state cannot disagree.
 * ------------------------------------------------------------------------- */
/* min-height is a WCAG 2.5.8 (AA) fix, added in 1.4.0 after measuring these buttons at 18px tall in
   the Quarterly earnings grid. The target minimum is 24x24 CSS px, and with `font: inherit` and no
   padding these collapsed to the line box of a 12.5px header font. The `th` around them has padding,
   but padding on an ancestor is not part of the target -- clicking the cell does not sort, only the
   button does -- so the measured target really was 18px. Width is never the problem here: a column
   label is always wider than 24px. */
.kc-v2-table__sort {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  min-height: 24px;
  appearance: none;
  -webkit-appearance: none;
  margin: 0;
  padding: 0;
  border: 0;
  background: none;
  color: inherit;
  font: inherit;
  cursor: pointer;
}
.kc-v2-table__sort:hover { text-decoration: underline; }
.kc-v2-table__sort:focus-visible {
  outline: var(--kc-v2-focus-ring-width) solid var(--kc-v2-focus-ring-color);
  outline-offset: 2px;
}
/* Neutral state: both arrowheads, dimmed -- "sortable, not currently sorted". */
.kc-v2-table__sort::after {
  content: "\2195";           /* up-down arrow */
  opacity: 0.55;
  font-size: 11px;
}
.kc-v2-table th[aria-sort="ascending"] .kc-v2-table__sort::after {
  content: "\2191";
  opacity: 1;
}
.kc-v2-table th[aria-sort="descending"] .kc-v2-table__sort::after {
  content: "\2193";
  opacity: 1;
}

.kc-v2-table__cell--numeric {
  text-align: right;
  font-variant-numeric: tabular-nums; /* Montserrat carries the 'tnum' OpenType
                                          feature -- confirmed in spike 0.2 */
  /* Numbers must never be broken across lines. `.kc-v2-table td` sets
     `overflow-wrap: anywhere` -- correct for the long account numbers and email addresses it was
     added for in 1.1.0, but applied to a numeric cell it split withholding rates mid-digit
     ("0.00125" over "0"), which is worse than a scrollbar in every case. Restated here rather than
     narrowed there, because the text columns still want the old behaviour. */
  white-space: nowrap;
  overflow-wrap: normal;
}

.kc-v2-table__cell--numeric > .kc-v2-error-text,
.kc-v2-table__cell--numeric > .kc-v2-helper-text,
.kc-v2-table__cell--numeric > .validationMessage {
  white-space: normal;
  overflow-wrap: break-word;
  width: min-content;
  min-width: 100%;
}

.kc-v2-table__empty {
  padding: var(--kc-v2-space-5) var(--kc-v2-space-4);
  text-align: center;
  color: var(--kc-v2-ink-500);
  font-size: 14px;
}

/* Definition list -- term/detail pairs, e.g. office hours, phone, address.
   A detail left genuinely empty (not just whitespace) renders an em-dash via
   :empty, so a page doesn't have to remember a placeholder -- and the row
   still gets a min-height so it never collapses to zero. */
/* margin is declared because these are <dl>/<dt>/<dd>: the UA gives a <dl> `margin: 1em 0` and a
   <dd> `margin-left: 40px`, while Bootstrap zeroes the indent and sets `margin-bottom: 20px`. The
   row's spacing was therefore entirely at the host's discretion -- 16px/16px standalone, 0/20px
   under Bootstrap. Declaring it makes the component's rhythm its own. KENT-44 audit. */
.kc-v2-definition-row {
  display: flex;
  gap: var(--kc-v2-space-4);
  min-height: 24px;
  margin: 0;
  padding: var(--kc-v2-space-3) 0;
  border-top: 1px solid var(--kc-v2-ink-100);
}
/* Container for a run of rows. Exists so `:first-child` below resolves against the rows rather
   than whatever else shares the card body (an eyebrow heading, say), and so the list's own outer
   margin is declared rather than inherited. */
.kc-v2-definition-list {
  margin: 0;
  padding: 0;
}

/* Two columns of pairs (1.5.1, KENT-44 QA).
   A list of short read-only facts does not need one full-width row each -- six of them is most of a
   card's height for six values that are each a dozen characters. QA reported the Annual filing-period
   card "takes up a ton of space"; this halves it without shrinking any type.
   Collapses back to one column below 640px, where two columns of term+detail have nowhere to go. */
.kc-v2-definition-list--2col {
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  column-gap: var(--kc-v2-space-4);
}
/* The first-child reset below would only clear the top border on the very first cell, leaving a
   stray rule above the second column's first row. In two-column mode the first TWO are the top row. */
.kc-v2-definition-list--2col > .kc-v2-definition-row:nth-child(-n + 2) {
  border-top: none;
  padding-top: 0;
}
/* A pair that takes the whole width of a two-column list (1.5.2, KENT-58).
   For the one value in a set of short facts that is not short -- a business name, which wrapped
   onto three lines inside a half-width cell while the numbers beside it used a fraction of
   theirs. Only worth it for a genuine outlier: spanning every row is just a one-column list. */
.kc-v2-definition-list--2col > .kc-v2-definition-row--span {
  grid-column: 1 / -1;
}
/* A spanning row at the head of the list IS the entire first visual row, so the pair after it
   begins the SECOND one and has to keep its rule. The nth-child(-n + 2) reset above assumes the
   first two cells share the top row -- true normally, exactly wrong here, and it would clear the
   left cell of the second row while the right one kept its border: half a rule across the card. */
.kc-v2-definition-list--2col > .kc-v2-definition-row--span:first-child ~ .kc-v2-definition-row:nth-child(-n + 3) {
  border-top: 1px solid var(--kc-v2-ink-100);
  padding-top: var(--kc-v2-space-3);
}

@media (max-width: 640px) {
  .kc-v2-definition-list--2col {
    grid-template-columns: minmax(0, 1fr);
  }
  /* Back to one column, so only the true first row loses its border again. */
  .kc-v2-definition-list--2col > .kc-v2-definition-row:nth-child(2) {
    border-top: 1px solid var(--kc-v2-ink-100);
    padding-top: var(--kc-v2-space-3);
  }
}

/* Borderless, compact pairs (1.5.1, KENT-44 QA).
   The summary cards across the top of the Annual and Quarterly returns are meant to read as three
   matching panels of plain text, per the mock. The middle one was a bordered definition list, so it
   carried a rule between every pair and stood ~200px taller than the Account card beside it -- QA:
   "the boxes are different sizes... remove the grid dividers and use the smaller font like the
   mockup."
   Same term/detail structure, so nothing about the markup or its semantics changes; this only drops
   the rules and tightens the rhythm to match the prose in the card next to it. */
.kc-v2-definition-list--flush > .kc-v2-definition-row {
  border-top: none;
  padding: var(--kc-v2-space-1) 0;
  min-height: 0;
  font-size: 13px;
}
.kc-v2-definition-list--flush > .kc-v2-definition-row:first-child {
  padding-top: 0;
}
.kc-v2-definition-list--flush .kc-v2-definition-term {
  flex: 0 0 130px;
}

.kc-v2-definition-row:first-child {
  border-top: none;
  padding-top: 0;
}
.kc-v2-definition-term {
  flex: 0 0 160px;
  color: var(--kc-v2-ink-800);
  font-family: var(--kc-v2-font-family);
  font-size: 14px;
  font-weight: 600;
  line-height: 20px;
}
/* margin: 0 for the same reason as the row -- a <dd>'s UA `margin-left: 40px` would indent every
   value away from its label wherever Bootstrap is absent to zero it. line-height so the pair sits
   on a rhythm the component controls rather than one inherited from the host body. */
.kc-v2-definition-detail {
  flex: 1 1 auto;
  min-width: 0;
  margin: 0;
  color: var(--kc-v2-ink-600);
  font-family: var(--kc-v2-font-family);
  font-size: 14px;
  line-height: 20px;
  overflow-wrap: anywhere;
}
.kc-v2-definition-detail:empty::after {
  content: "\2014"; /* em-dash */
  color: var(--kc-v2-ink-500);
}

@media print {
  .kc-v2-table thead {
    display: table-header-group; /* repeat the header on every printed page */
  }
  .kc-v2-table tr {
    break-inside: avoid;
  }
  .kc-v2-table-wrapper {
    border-color: #000;
    overflow: visible; /* the screen's overflow-x:auto scroll affordance is
                           meaningless on paper; let the table print at its
                           natural width instead of clipping */
  }
}

/* A cell holding a nested panel rather than a value -- the expandable per-city detail row on the
   business-license step (KENT-44 1.2.0). Padding is looser than a data cell because it contains a
   bordered sub-form, and the tinted fill separates the panel from the rows above and below it.
   Element-qualified (td.) so it beats `.kc-v2-table td` (0,1,2) on padding; a bare modifier at
   (0,1,0) would lose, which is contract rule 11 in reverse -- here the modifier is the one that
   needs the qualification. */
.kc-v2-table td.kc-v2-table__cell--nested {
  padding: var(--kc-v2-space-3) var(--kc-v2-space-4) var(--kc-v2-space-4);
  background-color: var(--kc-v2-ink-50);
  white-space: normal;
}

/* ---------------------------------------------------------------------------
 * Light-header table (KENT-115)
 *
 * For a small table inside a .kc-v2-record card, whose own head already carries the emphasis -- a
 * dark bar per record would outweigh the data under it. Small muted headers, no zebra (a record holds
 * a handful of rows), and tighter gutters, because the cells are mostly money inputs that bring their
 * own padding. The outer edges keep 12px.
 * ------------------------------------------------------------------------- */
.kc-v2-table.kc-v2-table--light th {
  padding-top: 8px;
  padding-bottom: 8px;
  border-bottom: 1px solid var(--kc-v2-ink-200);
  background-color: transparent;
  color: var(--kc-v2-ink-500);
  font-size: 11px;
  line-height: 14px;
  vertical-align: bottom;
}
/* `.kc-v2-table th` sets text-align: left at (0,1,1), which beats the bare --numeric modifier. */
.kc-v2-table.kc-v2-table--light th.kc-v2-table__cell--numeric {
  text-align: right;
}
.kc-v2-table.kc-v2-table--light tbody tr:nth-child(even) {
  background-color: transparent;
}
.kc-v2-table.kc-v2-table--light th,
.kc-v2-table.kc-v2-table--light td {
  padding-left: 6px;
  padding-right: 6px;
}
.kc-v2-table.kc-v2-table--light th:first-child,
.kc-v2-table.kc-v2-table--light td:first-child {
  padding-left: 12px;
}
.kc-v2-table.kc-v2-table--light th:last-child,
.kc-v2-table.kc-v2-table--light td:last-child {
  padding-right: 12px;
}

/* A label row introducing the rows under it ("City breakdown ..."). Not a <th>: it describes a run of
   rows rather than heading a column, and it carries a sentence of explanation after its title. */
.kc-v2-table tr.kc-v2-table__section-row td {
  padding-top: 10px;
  padding-bottom: 2px;
  color: var(--kc-v2-ink-500);
  font-size: 11px;
  line-height: 14px;
}
.kc-v2-table tr.kc-v2-table__section-row + tr td {
  border-top: 0;
}
.kc-v2-table__section-title {
  margin-right: 6px;
  color: var(--kc-v2-ink-800);
  font-weight: 700;
  letter-spacing: 0.5px;
  text-transform: uppercase;
}

/* ---------------------------------------------------------------------------
 * Help trigger inside a column header (KENT-44 1.3.0)
 *
 * A small button that opens a dialog explaining what a column means. Used on the Annual earnings
 * grid's Fee Type column, whose explanation was a Bootstrap popover before the kc-v2 conversion.
 *
 * .kc-v2-table th is --kc-v2-ink-900 with white text, which rules out the ghost button used for the
 * same job on light backgrounds, and rules out letting the icon keep its own colour:
 * Images/information.svg strokes #00509D -- the same value as --kc-v2-blue -- which sits at roughly
 * 1.9:1 against that header and is effectively invisible. The filter below drives the artwork to
 * white so it matches the header text it sits beside, without keeping a second recoloured copy of
 * the file. The focus ring keeps the standard green token, which measures about 7.9:1 on the header
 * and so needs no override.
 * ------------------------------------------------------------------------- */
.kc-v2-table__help {
  /* The host ships bare `button` styling (Bootstrap) and site.css sizes buttons, so appearance,
     border, background and margin are all restated rather than assumed. */
  appearance: none;
  -webkit-appearance: none;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  margin: 0 0 0 6px;
  padding: 2px;
  border: 0;
  border-radius: var(--kc-v2-radius-sm);
  background: none;
  cursor: pointer;
  /* line-height 0 stops the button's own line box from lifting the icon off the header baseline. */
  line-height: 0;
  vertical-align: middle;
}

.kc-v2-table__help img {
  display: block;
  width: 15px;
  height: 15px;
  /* brightness(0) flattens the artwork to black whatever colour it ships as; invert(1) lifts it to
     white. Written as a pair because brightness alone cannot lighten a mid-tone to white. */
  filter: brightness(0) invert(1);
}

.kc-v2-table__help:hover img {
  opacity: 0.8;
}

.kc-v2-table__help:focus-visible {
  outline: var(--kc-v2-focus-ring-width) solid var(--kc-v2-focus-ring-color);
  outline-offset: 1px;
}
