/* Column Dividers — a hairline rule in the gap between columns (row 190).
   ---------------------------------------------------------------------------
   "Section is missing dividers. Expected: Dividers are present for this
   section", against /who-we-are/our-strategy/. The frame draws a 1px rule
   between each pair of columns, running the height of the row.

   The frame gives it as `border-right: 1px solid var(--Neutral-50, #B5B3B8)`,
   so the colour is neutral-50.

   It shipped once as neutral-10 #EDECEE, read off a sample of the frame
   screenshot rather than off the frame. That was the wrong inference in the
   wrong direction: a 1px line antialiased into a white page blends TOWARD the
   background, so a sample of it always reads lighter than the colour drawn, and
   the true value is darker than the #E0DFE1-#EAEAEB the samples gave, not
   lighter. Sampling a hairline out of a JPEG cannot settle its colour; the
   frame can.

   Drawn as a pseudo-element rather than as a real border-right, so the column's
   own border shorthand stays free for page content to use and the line cannot
   be lost to a border reset. Position and effect are identical to the frame's
   border.

   Where the rule sits, and the 12px beside it (row 190 retest)
   ---------------------------------------------------------------------------
   "The padding between the text and the next separating line should be 12px."

   The frame does not centre this rule in the gap. Each column is a vertical
   frame with `border-right: 1px` and `padding-right: 12px` (Figma 4455-15920,
   Frame 3542), so the line sits on the column's own right edge with 12px
   between it and the text, and the whole column gap on its other side. It is a
   column border, not a divider floating in the gutter.

   It shipped centred, which put HALF THE GAP between the text and the line on
   one side (18px at this row's 36px gap) and the same again on the other. With
   the column's own 12px padding on top of that, the reader saw 30px before the
   line and 18 after it - the "extra padding" the retest boxed.

   Now the rule is drawn on the right edge of every column but the last, and the
   12px comes with it, so the component carries the whole look instead of
   depending on the page to pad its own columns. That also retires
   --rhsc-column-divider-gap: the variable existed only to find the middle of
   the gutter, and nothing needs the middle of the gutter any more.

   Columns stack below 782 (core's breakpoint), where a vertical rule between
   them would be meaningless, so both the rule and its padding are dropped
   there. */

/* The gutter is the frame's 32, fixed.

   The block was left on the `large` spacing preset, which is
   clamp(1.5rem, 5vw, 2.25rem) - so the gap between the columns drifted with the
   window: 24px on a narrow one, 36 on a wide one, 32 only by coincidence at
   640px. The frame gives one number for it (Frame 3745 and Text Columns + Icon,
   both gap 32), and with a rule sitting in that gutter the distance either side
   of the line is part of the component's look, not a fluid page-level rhythm.

   Two classes, so this beats the gap on the layout container's own generated
   class without !important. */
.wp-block-columns.is-style-column-dividers {
  column-gap: 32px;
}

.wp-block-columns.is-style-column-dividers
  > .wp-block-column:not(:last-child) {
  position: relative;
  padding-right: 12px;
}

.wp-block-columns.is-style-column-dividers
  > .wp-block-column:not(:last-child)::after {
  content: '';
  position: absolute;
  top: 0;
  bottom: 0;
  right: 0;
  width: 1px;
  background-color: var(--wp--preset--color--neutral-50, #b5b3b8);
}

@media (max-width: 781px) {
  .wp-block-columns.is-style-column-dividers
    > .wp-block-column:not(:last-child) {
    padding-right: 0;
  }

  .wp-block-columns.is-style-column-dividers
    > .wp-block-column:not(:last-child)::after {
    content: none;
  }
}