/* NATIVE-BROWSER-PRINT ONLY — the per-page Brieffuß running-footer mechanism.

   This file MUST NEVER be passed to the paged.js Previewer (see
   components/faktura-core/beleg-paged-preview.tsx — its stylesheet array stays
   ['/beleg-print.css'] and that file ALONE). paged.js applies whatever CSS it is
   given to the <article> it fragments; the display:table switch below turns the
   <article> into a CSS table, which paged.js then cannot fragment → the whole Beleg
   collapses onto ONE page ("Kassenzettel"/one-page regression, Stefan-Bug
   2026-06-08). Keeping this rule in a SEPARATE file loaded only via a media="print"
   <link> in app/layout.tsx guarantees the native-print path gets the running footer
   while the on-screen paged.js preview never sees it.

   NATIVE browser print: the <article> becomes a CSS table and the <footer> a
   table-footer-group, so Chrome repeats the Brieffuß at the bottom of EVERY page
   IN FLOW — content reserves space, so it never overlaps the body. (position:fixed
   anchored the footer inside the page CONTENT area, where bottom:6mm rode UP into
   the text — Stefan-Bug 2026-06-08. The running table-footer-group is the reliable
   cross-browser per-page-footer mechanism.) The data-beleg-running attribute keys
   the table-switch so it cannot leak onto other print surfaces. */
[data-beleg-running] {
  display: table !important;
  width: 100% !important;
  /* collapse → no spurious border-spacing gaps between the anonymous table rows
     the content blocks fall into when the article becomes a table. */
  border-collapse: collapse !important;
}
[data-beleg-footer] {
  display: table-footer-group;
}