/* ============================================================
   THE LMIA BOOK — what this report has that the other five do not.

   Everything else on the page is ListView's and reports.css's: the
   toolbar, the filters, the column picker, the print shell. This file
   adds the BANDS, the two marks the firm's own spreadsheet carries
   (an unfilled seat, a re-submitted file) and a landscape print.

   ON THE COLOURS. Their sheet bands in pink and highlights a re-submitted
   file in orange. Neither colour is reproduced literally — a pink strip in
   a bone-and-gold product reads as an error state, and this page has to sit
   beside the other five reports without looking like a different app. What
   IS reproduced is the SIGNAL: a full-width band that stops the eye, and a
   warm highlight on the exception. Deep green for the band, gold for the
   exception, both from the palette in styles.css.

   2026-09-14: the rules that used to ship as an injected <style
   id="lmrOrangeCss"> inside lmiareport.js now live here, verbatim — same
   selectors, same order. They were written into the JS only because this
   file belonged to another pair of hands at the time; one owner now, one
   place. The print section below is the only part that changed in the
   lift, and it changed because it was wrong. See "the width the page has".
   ============================================================ */

/* ---------- the banner row ----------
   A <th scope="rowgroup"> spanning every column, inserted by
   lmiareport.js. Cursor and hover are switched off explicitly: it sits in
   the tbody, where .tbl gives every row a pointer and a hover tint, and a
   banner is not something you can open. */
.lmr-tbl tbody tr.lmr-band { cursor: default; }
.lmr-tbl tbody tr.lmr-band:hover { background: none; }
.lmr-tbl tbody tr.lmr-band > th {
  background: var(--green);
  color: var(--paper);
  text-transform: uppercase;
  font-family: var(--disp);
  font-weight: 700;
  font-size: 11.5px;
  letter-spacing: .12em;
  text-align: left;
  padding: 9px 16px;
  border-bottom: 0;
  position: relative;
}
/* The band's own count, on the far end. Their sheet does not carry one;
   "how many are we waiting on" is the first thing asked of a band in the
   meeting, and it is the one number the page can answer without being
   asked twice. */
/* Label and count sit together at the left, not at the two ends of the
   row. The band spans a table that is wider than the screen, so a count
   pushed to the far end is a count you have to scroll sideways to read. */
.lmr-tbl .lmr-band-in {
  display: flex; align-items: baseline; gap: 14px;
}
.lmr-tbl .lmr-band-n {
  font-family: var(--body);
  font-weight: 600;
  letter-spacing: .06em;
  white-space: nowrap;
  opacity: .72;
}
/* The first data row under a band keeps a hairline so the band reads as a
   heading over the rows rather than as a row with them. */
.lmr-tbl tbody tr.lmr-band + tr > td { border-top: 0; }

/* ---------- an unfilled seat ----------
   "No Name" is bold on their sheet and bold here. It is not missing data:
   it is a position the firm still has to fill, which is the reason the
   meeting exists. */
.lmr-noname { font-weight: 700; color: var(--ink); }

/* ---------- a re-submitted file ----------
   The exception on the page: this application went back to Service Canada
   under a second number, so its clock restarted and its history is longer
   than one date can say. */
.lmr-tbl tbody tr.lmr-row-resub { background: rgba(216, 184, 119, .22); }
.lmr-tbl tbody tr.lmr-row-resub:hover { background: rgba(216, 184, 119, .32); }
.lmr-resub-tag { color: var(--gold-deep); font-weight: 700; }

/* ---------- values that are read down a column ----------
   File numbers and dates line up digit under digit, because reading a
   column of them out loud is exactly what this page is for.

   And they are ONE VALUE: `9763006` is not "9763006", it is one file
   number, and `2026-03-26` is one date. A line break inside either makes
   a sheet that is carried into a meeting unreadable — and a date will
   break after its hyphens without being asked, because a hyphen is a
   wrap opportunity in every browser. So they say so here, on screen and
   on paper, rather than relying on a column being wide enough. */
.lmr-tbl .lmr-no,
.lmr-tbl .lmr-date { font-variant-numeric: tabular-nums; white-space: nowrap; }
/* ONE VALUE, ONE LINE. lmiareport.js wraps every run of non-space
   characters in the table — in the headings, the cells and the band
   banners — in one of these. A space is still somewhere a line may break,
   so employer and worker names wrap as they always did; a file number, a
   date, a rate or a heading's own word cannot be broken anywhere.

   This is in the DOM rather than left to `word-break: keep-all` because
   Blink honours keep-all for CJK only: with keep-all set on every cell,
   Chrome still split "re-submission" in a column heading. See the long
   note over lmrAtomise() for why not U+2060 word joiners. */
.lmr-tbl .lmr-atom { white-space: nowrap; }
.lmr-tbl .lmr-no { font-weight: 650; }
/* The employer repeats on every seat of a filing, deliberately — but it is
   the widest column on the page, so it is allowed to wrap rather than
   forcing the table wider than the screen.
   The 290px floor was sized for one line carrying legal + operating +
   contact. The longest line in the cell is now roughly 45% shorter (see
   the two-line cell below), so the floor comes down with it and the width
   goes back to the columns that were being squeezed. */
.lmr-tbl td:first-child { min-width: 178px; }
.lmr-tbl .lmr-emp .lv-link { text-align: left; white-space: normal; }
/* Denser than the other lists on purpose. This one is read the way a
   spreadsheet is read — a column at a time, out loud, with somebody
   following it down the page — and rows tall enough to be comfortable one
   at a time put a third as many of them in front of the meeting. */
.lmr-tbl td { padding: 8px 12px; font-size: 13px; }
.lmr-tbl th { padding: 10px 12px; }

/* ============================================================
   ONE RECORD, TWO ROWS OF COLUMNS

   The firm asked for "a two-line report — show the columns in two rows,
   this way we can cover a lot more data". The first rank is the eight
   columns the meeting reads down; the second is drawn by lmiareport.js as
   one spanning cell holding a four-slot grid, and it carries the
   re-submission and the two dates the firm now plans with.

   EVERYTHING HERE IS ABOUT ONE THING: that the two rows read as ONE
   record. A sheet handed round a table cannot come with a legend, so the
   pairing is said four ways — the first row gives up its bottom rule, the
   second is tinted and indented, it opens with a ↳ and the words SAME
   FILING, and on screen hovering either lights both.
   ============================================================ */

/* The hidden heading row. It exists ONLY so reportsend.js, which reads its
   column list off this <thead>, still finds the four columns the second
   rank draws — see the long note in lmiareport.js section 5b. It must stay
   out of the layout: a displayed row here would add four columns to the
   table's grid and take the first rank's widths apart. */
.lmr-tbl thead tr.lmr-head2 { display: none !important; }

/* The first row of a pair keeps its rule for the row BELOW the pair, not
   between the two halves of it. */
.lmr-tbl tbody tr.lmr-has2 > td { border-bottom: 0; }

.lmr-tbl tbody tr.lmr-r2 { cursor: pointer; }
.lmr-tbl tbody tr.lmr-r2 > td.lmr-r2c {
  /* Indented to start where the first column ends — lmiareport.js sets
     --lmr-r2-ind from the same weights it costs the printed columns with,
     so the hang follows the column picker. */
  padding: 1px 12px 8px var(--lmr-r2-ind, 19%);
  background: rgba(30, 58, 51, .05);
}
.lmr-tbl tbody tr.lmr-r2.lmr-row-resub > td.lmr-r2c { background: none; }

/* THE BRACKET. Indent and a ↳ say the second row hangs off the first; this
   says where the record starts and stops. A rail down the left edge of
   both rows turns a pair of table rows into one block the eye can see the
   ends of — which matters most exactly where it is hardest, in the middle
   of a page of rows that are otherwise identical. Drawn with an inset
   shadow rather than a border so it adds no width and cannot move a
   column. */
.lmr-tbl tbody tr.lmr-has2 > td:first-child,
.lmr-tbl tbody tr.lmr-r2 > td.lmr-r2c {
  box-shadow: inset 2px 0 0 rgba(30, 58, 51, .38);
}

/* The four slots. Fixed, so that the fields line up down the page whether
   the record above or below drew a second row or not — which is what makes
   this a rank of COLUMNS and not a run of notes. */
.lmr-tbl .lmr-r2-in {
  display: grid;
  grid-template-columns: auto repeat(4, minmax(0, 1fr));
  align-items: baseline;
  gap: 2px 14px;
}
.lmr-tbl .lmr-r2-tie {
  font-size: 9.5px; letter-spacing: .1em; text-transform: uppercase;
  font-weight: 600; color: var(--ink-faint); white-space: nowrap;
  padding-right: 10px;
}
.lmr-tbl .lmr-r2-arr { font-size: 12px; margin-right: 4px; letter-spacing: 0; }
.lmr-tbl .lmr-r2-f { display: block; min-width: 0; }
.lmr-tbl .lmr-r2-l {
  display: block; font-size: 9.5px; letter-spacing: .08em; text-transform: uppercase;
  font-weight: 600; color: var(--ink-faint); line-height: 1.3;
}
.lmr-tbl .lmr-r2-v { display: block; font-size: 12.5px; line-height: 1.35; }
/* A field with nothing in it still holds its slot — the column has to stay
   a column — but it recedes, so the eye lands on the dates that are set. */
.lmr-tbl .lmr-r2-f.lmr-r2-empty .lmr-r2-l { opacity: .55; }

/* Hover lights the pair, not the half the pointer is over. */
.lmr-tbl tbody tr.lmr-pair-hot,
.lmr-tbl tbody tr.lmr-pair-hot > td.lmr-r2c { background: rgba(216, 184, 119, .08); }
.lmr-tbl tbody tr.lmr-row-resub.lmr-pair-hot,
.lmr-tbl tbody tr.lmr-row-resub.lmr-pair-hot > td.lmr-r2c { background: rgba(216, 184, 119, .32); }

/* ---------- the orange, and the key that explains it ----------
   ON THE COLOUR. Their sheet's orange is a highlighter; this is print
   and screen in a bone-and-gold product, so the SIGNAL is reproduced,
   not the swatch: a burnt orange (#A34A12) that reads as orange and
   clears 4.5:1 against both the paper (5.6:1) and its own wash (4.7:1),
   rather than a highlighter yellow-orange that fails on white at any
   size. And colour never carries the meaning alone — the diamond does
   it on a mono printout and for anyone who cannot separate the two
   colours, the title attribute does it on hover, and .lmr-sr does it
   for a screen reader. Every one of those says the same sentence. */
.lmr-sr { position: absolute; width: 1px; height: 1px; margin: -1px; padding: 0;
  overflow: hidden; clip: rect(0 0 0 0); clip-path: inset(50%); white-space: nowrap; border: 0; }

.lmr-tbl .lmr-paidq, .lmr-legend .lmr-paidq {
  color: #A34A12;
  font-weight: 700;
  background: rgba(196, 106, 32, .14);
  border-radius: 4px;
  padding: 1px 6px 1px 4px;
  white-space: nowrap;
}
.lmr-tbl .lmr-paidq-mk, .lmr-legend .lmr-paidq-mk {
  font-size: .72em; margin-right: 4px; vertical-align: .12em; line-height: 1;
}

/* ---------- the employer, on two lines ----------
   Line one is the operating name — the name said out loud in the
   meeting. Line two is the legal name and the contact, small: on the
   page for anybody checking the sheet against an ESDC letter, and small
   enough that it is not what the eye lands on. */
.lmr-tbl .lmr-emp { display: block; }
.lmr-tbl .lmr-emp-op { display: block; }
.lmr-tbl .lmr-emp-op .lv-link { font-weight: 600; }
.lmr-tbl .lmr-emp-sub {
  display: block;
  margin-top: 1px;
  font-size: 11px;
  line-height: 1.3;
  color: var(--ink-soft);
}

/* ---------- a decision on the second trip ----------
   The cell shows the decision that governs. When that is the
   re-submission's it says so, and the first decision stays on the page
   underneath rather than disappearing. */
.lmr-tbl .lmr-dec-tag,
.lmr-tbl .lmr-dec-1st {
  display: block; font-size: 10.5px; line-height: 1.25; color: var(--ink-soft);
}
.lmr-tbl .lmr-dec-tag { font-weight: 600; letter-spacing: .02em; }
.lmr-tbl .lmr-dec-1st { font-variant-numeric: tabular-nums; white-space: nowrap; }
.lmr-tbl .lmr-dec { display: inline-block; vertical-align: top; }

/* The key. A colour nobody can look up is a colour only the person who
   invented it can read, and this page is handed round a table. */
.lmr-legend {
  display: flex; align-items: flex-start; gap: 10px;
  margin: 0 0 12px; padding: 9px 13px;
  background: var(--bone); border: 1px solid var(--stroke); border-radius: var(--r-sm);
  font-size: 12.5px; line-height: 1.45; color: var(--ink-soft);
}
.lmr-legend b { color: var(--ink); font-weight: 700; }
/* The second sentence — what a second line under a record is — starts a new
   line of its own rather than running on from the orange key, because the
   two are answers to two different questions. */
.lmr-legend { flex-wrap: wrap; }
.lmr-legend .lmr-legend-t { flex: 1 1 320px; }
.lmr-legend .lmr-legend-2 { flex-basis: 100%; padding-top: 5px; border-top: 1px solid var(--stroke); }
.lmr-legend .lmr-legend-k { flex: none; font-variant-numeric: tabular-nums; font-size: 12px; }

/* ---------- on a phone ----------
   styles.css turns a .cardable table into stacked cards below 760px and
   gives every <tr> a white card with a border — which wrapped the band in
   a card of its own, a green strip floating inside a white box. The band
   is a heading over the cards that follow it, so it drops the card and
   becomes a full-width strip. */
@media (max-width: 760px) {
  .lmr-tbl.cardable tbody tr.lmr-band {
    background: none; border: 0; padding: 0;
    margin: 18px 0 10px; border-radius: 12px; overflow: hidden;
  }
  .lmr-tbl.cardable tbody tr.lmr-band > th { display: block; padding: 9px 13px; }
  .lmr-tbl.cardable tbody tr.lmr-band:first-child { margin-top: 0; }
  .lmr-tbl.cardable .lmr-band-n { font-size: 10.5px; }
  .lmr-tbl.cardable .lmr-dec { text-align: right; }

  /* ---------- the pair, as one card ----------
     styles.css gives every <tr> below 760px a white card of its own, which
     would have put the two halves of one record in two separate cards —
     the one thing this change exists to prevent. So the pair is sewn back
     together: the first row loses its bottom edge and its rounding, the
     second loses its top edge and its gap, and the two draw as one card
     with a tinted foot.

     The indent goes to nothing here. A hang that says "this belongs to the
     line above" needs a line above it; inside one card the relationship is
     already stated by the card. */
  .lmr-tbl.cardable tbody tr.lmr-has2 {
    margin-bottom: 0; border-bottom: 0; border-radius: 16px 16px 0 0; padding-bottom: 6px;
  }
  .lmr-tbl.cardable tbody tr.lmr-r2 {
    margin-top: 0; border-top: 0; border-radius: 0 0 16px 16px;
    padding: 0 14px 10px; background: rgba(255, 255, 255, .65);
  }
  .lmr-tbl.cardable tbody tr.lmr-r2 > td.lmr-r2c {
    display: block; padding: 8px 10px !important; border-radius: 10px;
  }
  /* The bracket is what ties two ROWS together; inside one card there are
     no two rows to tie, so it comes off rather than drawing a rail down
     the middle of a card. */
  .lmr-tbl.cardable tbody tr.lmr-has2 > td:first-child,
  .lmr-tbl.cardable tbody tr.lmr-r2 > td.lmr-r2c { box-shadow: none; }
  /* Two slots across, not four: four date columns on a 390px screen is
     four columns of two characters each. */
  .lmr-tbl.cardable .lmr-r2-in { grid-template-columns: 1fr 1fr; gap: 8px 12px; }
  .lmr-tbl.cardable .lmr-r2-tie { grid-column: 1 / -1; padding-right: 0; }
}

/* ============================================================
   PRINT

   reports.css already strips the shell and prints the table; this section
   owns what the LMIA book does differently on paper.

   The page is set landscape by lmiareport.js for the length of one print —
   an @page rule in a stylesheet cannot be scoped to one report and would
   turn every other print in the app landscape too.
   ============================================================ */
@media print {

  /* ---------- 1. NOTHING THAT IS ONE VALUE MAY BREAK ----------
     The firm's printout of 13 September broke `9763006` into `976300` and
     `6` on the next line, and `2026-03-26` into `2026-03-` and `26`. A
     file number split across two lines on the sheet somebody carries into
     a meeting is not a cosmetic problem: it can be read as the wrong
     number, or as two.

     It happened because this file used to say `word-break: break-word` on
     every cell, which tells the browser that any character is a legal
     place to start a new line. That is the right instruction for a
     paragraph and the wrong one for a table of file numbers, dates, money
     and counts.

     The instruction now is the opposite one, and it is set ONCE for every
     cell rather than column by column, so a column added tomorrow is
     covered without anyone remembering to cover it:

       word-break: keep-all   — no break inside a word, and no break after
                                a hyphen, which is what split the dates.
       overflow-wrap: normal  — no last-resort break either.
       hyphens: none          — and nothing invents a hyphen.

     THIS IS THE BACKSTOP, NOT THE GUARANTEE. Blink honours keep-all for
     CJK only: with all three of these in force, Chrome went on splitting
     "re-submission" in a column heading. What actually holds the line is
     .lmr-atom above — lmiareport.js wrapping every token in the table in a
     nowrap span, where no engine gets an opinion. These three stay because
     they are the correct declarations and an engine that honours them
     should.

     What is still allowed is a break at a SPACE, which is how an employer
     name and a worker's name wrap and how a two-word column heading wraps.
     A value with no space in it cannot be broken at all — if a column were
     ever too narrow for one, the value overflows where a reader can SEE
     that something is wrong, instead of quietly changing its own digits. */
  body.rp-printing .lmr-tbl th,
  body.rp-printing .lmr-tbl td,
  body.rp-printing .lmr-tbl th *,
  body.rp-printing .lmr-tbl td * {
    word-break: keep-all !important;
    overflow-wrap: normal !important;
    -webkit-hyphens: none; hyphens: none !important;
  }
  /* Said twice for the values the meeting reads out loud: a right-aligned
     column is a number column, and these two spans are single values
     wherever they are used. */
  body.rp-printing .lmr-tbl td.num,
  body.rp-printing .lmr-tbl .lmr-no,
  body.rp-printing .lmr-tbl .lmr-date { white-space: nowrap !important; }

  /* ---------- 2. THE WIDTH THE PAGE HAS ----------
     This table used to be laid out by the browser's own algorithm, which
     hands each column a share of the page in proportion to how much text
     it is carrying. With break-word in force above, a seven-digit file
     number's minimum width was ONE DIGIT, so the two free-text columns
     took 50% of the sheet between them and LMIA # was left with 58px —
     narrower than the number it holds. That is the whole of the reported
     fault: not a missing column, a column that was never given its width.

     The widths are now fixed, and they are OURS: lmiareport.js writes a
     --lmr-w on each heading from a per-column weight, normalised over
     whatever columns are actually showing. That matters, because the
     firm's own printout had two columns switched off in the picker — and
     the old rules were pinned to `:nth-child()` under a `.lmr-cols-10`
     class that only matched when all ten were up. Switch one off and every
     width silently went away, which is exactly the sheet they sent us.
     Nothing here counts columns or positions any more. */
  body.rp-printing .lmr-tbl {
    table-layout: fixed !important;
    width: 100% !important;
  }
  body.rp-printing .lmr-tbl thead th { width: var(--lmr-w, auto); }
  /* The screen floor under the employer column would fight the share it
     is given above; on paper the share is the answer. */
  body.rp-printing .lmr-tbl td:first-child,
  body.rp-printing .lmr-tbl th:first-child { min-width: 0 !important; }

  /* ---------- 3. THE SIZE IT IS SET AT ----------
     These three rules carry !important and name `table.tbl.lmr-tbl` on
     purpose. reports.css sets `body.rp-printing table.tbl td` with
     !important, and the screen rule above sets `.lmr-tbl td` directly on
     the cell — so the 8.6px this file used to ask for never reached a
     single cell. It was set on the TABLE, and a td with its own font-size
     does not inherit one. The book printed at 13px/19.5px line, which is
     most of the reason the rows were tall enough to push the sheet onto a
     second page.
     9.6px, not the 8.6 that was asked for and never landed: 8.6 is within
     a whisker of the 7.9px legal-name line underneath it, and the two-line
     employer cell depends on those two sizes not looking alike. */
  body.rp-printing table.tbl.lmr-tbl { font-size: 9.6px !important; }
  body.rp-printing table.tbl.lmr-tbl tbody td {
    font-size: 9.6px !important;
    line-height: 1.35 !important;
    padding: 3px 5px !important;
    vertical-align: top;
  }
  body.rp-printing table.tbl.lmr-tbl thead th { padding: 4px 5px !important; }

  /* The column headings are the app's tracked-out uppercase, which at
     print size is wider than the columns it labels — the first proof of
     this printed "POSITIONS" straight across "HOURLY RATE", and the
     firm's printout split it into "POSITION" and "S". They wrap at their
     spaces here, and (rule 1) never inside a word. */
  body.rp-printing .lmr-tbl thead th {
    font-size: 7.2px !important; letter-spacing: .02em; line-height: 1.15;
    white-space: normal; vertical-align: bottom;
  }
  body.rp-printing .lmr-tbl thead th .lv-arrow { display: none; }

  /* The band prints as a bone strip with a rule top and bottom rather than
     as a block of dark green: it survives a mono printer, it reads as a
     heading, and it does not put a solid bar of toner across ten columns. */
  body.rp-printing .lmr-tbl tbody tr.lmr-band > th {
    background: var(--bone-2) !important;
    color: var(--green) !important;
    -webkit-print-color-adjust: exact; print-color-adjust: exact;
    border-top: 1.4px solid var(--green) !important;
    border-bottom: 1.4px solid var(--green) !important;
    padding: 4px 5px !important;
    font-size: 8.6px !important;
    letter-spacing: .1em;
  }
  /* A band with its first row orphaned at the foot of a page is a band
     somebody reads as belonging to the wrong heading. */
  body.rp-printing .lmr-tbl tbody tr.lmr-band { break-after: avoid; page-break-after: avoid; }

  body.rp-printing .lmr-tbl tbody tr.lmr-row-resub {
    background: rgba(216, 184, 119, .30) !important;
    -webkit-print-color-adjust: exact; print-color-adjust: exact;
  }

  /* Paper keeps the colour where the printer has it and the diamond
     where it does not. */
  body.rp-printing .lmr-tbl .lmr-paidq,
  body.rp-printing .lmr-legend .lmr-paidq {
    color: #A34A12 !important;
    background: rgba(196, 106, 32, .18) !important;
    -webkit-print-color-adjust: exact; print-color-adjust: exact;
    padding: 0 3px !important;
  }

  body.rp-printing .lmr-legend {
    background: none !important; border: 0 !important; border-top: 1px solid #1A1B18 !important;
    border-bottom: 1px solid #1A1B18 !important; border-radius: 0 !important;
    padding: 3px 0 !important; margin: 0 0 7px !important; font-size: 8.4px !important;
    color: #1A1B18 !important; break-inside: avoid; page-break-inside: avoid;
  }

  /* ---------- 4. THE SECOND ROW, ON PAPER ----------
     This is the half of the change the firm will actually hold. Three
     things have to be true of it: the pair must not be split across a page
     break, it must read as one record, and it must cost as little height
     as a line of four labelled dates can.

     THE PAIR IS NOT SPLIT. reports.css already asks the browser not to
     break inside a <tr>; a record is now two of them, so the first also
     asks not to be broken AFTER. A second row printed at the top of the
     next page under somebody else's heading is the same failure as a band
     banner orphaned at the foot of one.

     THE RULE BELONGS UNDER THE PAIR. reports.css puts a hairline under
     every cell with !important, which would draw a line BETWEEN the two
     halves of one record — the one line that must not be there. It is
     turned off on the first row of a pair and kept on the second, so the
     block is bounded once, underneath. */
  body.rp-printing .lmr-tbl tbody tr.lmr-has2 {
    break-after: avoid; page-break-after: avoid;
  }
  body.rp-printing .lmr-tbl tbody tr.lmr-has2 > td { border-bottom: 0 !important; }
  /* The bracket, as a real border on paper: a box-shadow is a background
     and the first thing a printer with "background graphics" switched off
     throws away — and this is the mark that says where a record starts
     and stops. */
  body.rp-printing .lmr-tbl tbody tr.lmr-has2 > td:first-child,
  body.rp-printing .lmr-tbl tbody tr.lmr-r2 > td.lmr-r2c {
    box-shadow: none !important;
    border-left: 1.2px solid var(--green) !important;
  }
  body.rp-printing .lmr-tbl tbody tr.lmr-r2 > td.lmr-r2c {
    padding: 0 5px 3px var(--lmr-r2-ind, 19%) !important;
    background: rgba(30, 58, 51, .05) !important;
    -webkit-print-color-adjust: exact; print-color-adjust: exact;
  }
  body.rp-printing .lmr-tbl .lmr-r2-in { gap: 1px 8px; }
  body.rp-printing .lmr-tbl .lmr-r2-l,
  body.rp-printing .lmr-tbl .lmr-r2-tie {
    font-size: 6.4px !important; letter-spacing: .06em; line-height: 1.2;
    color: #1A1B18 !important; opacity: .72;
  }
  body.rp-printing .lmr-tbl .lmr-r2-arr { font-size: 8px !important; }
  body.rp-printing .lmr-tbl .lmr-r2-v { font-size: 8.4px !important; line-height: 1.25; }
  /* The orange mark is a FILING's, so it is on both of that filing's
     numbers; at this size it needs less padding than the first rank's. */
  body.rp-printing .lmr-tbl .lmr-r2-v .lmr-paidq { padding: 0 2px !important; }

  /* THE SECOND LEGEND LINE DOES NOT PRINT. Measured: it is two lines of
     8.4px at the top of the sheet, and on this book those two lines cost a
     WHOLE EXTRA PAGE — 7 sheets became 8. The sentence exists to answer
     "why does that record have two lines"; every second row already
     answers it in its own labels and its ↳ same filing mark, so the paper
     keeps the answer that costs nothing and drops the one that costs a
     sheet. The firm reads it on screen, where height is free. */
  body.rp-printing .lmr-legend .lmr-legend-2 { display: none !important; }

  /* ---------- THE NOC CELL'S TWO LINES COST NOTHING ----------
     The job title under the NOC code is set to the same size as the legal
     name under the employer's operating name — 7.9px, not the 8.5px
     reports.css gives .rp-sub — because the employer cell is already two
     lines on EVERY row of this book, and the taller of the two cells sets
     the row height. At 8.5px with a 1.4 line the new cell was the taller
     one and added a whole sheet to the printed book: 7 pages became 8.
     Same information, same two lines, one sheet less. */
  body.rp-printing .lmr-tbl .rp-strong { font-size: 9.6px !important; line-height: 1.25; }
  body.rp-printing .lmr-tbl .rp-sub {
    font-size: 7.9px !important; line-height: 1.2; margin-top: 0 !important;
    color: #1A1B18 !important; opacity: .78;
  }

  body.rp-printing .lmr-tbl .lmr-emp-sub {
    font-size: 7.9px !important; line-height: 1.2; color: #1A1B18 !important; opacity: .78;
  }
  body.rp-printing .lmr-tbl .lmr-dec-tag,
  body.rp-printing .lmr-tbl .lmr-dec-1st {
    font-size: 7.9px !important; line-height: 1.2; color: #1A1B18 !important; opacity: .78;
  }
}

/* A job title borrowed from the NOC classification because none was recorded.
   Visibly not the firm's own wording — the report is filed from. */
/* THE NOC/JOB-TITLE CELL IS REPORTS.CSS'S, NOT THIS FILE'S. The code is
   .rp-strong and the job title under it .rp-sub, including their print
   sizes — the same two rules the other five reports draw that cell with,
   so it cannot look like a different cell on this page.

   What used to be here was `.lmr-noctitle`, the italic "(NOC)" marker for a
   job title borrowed from the classification. The client has banned the NOC
   description from every report, so there is nothing left to mark: the
   fallback is gone (lmiareport.js section 2b) and a filing with no job
   title prints its code with nothing under it. */
.lmr-tbl .rp-sub { line-height: 1.3; }