﻿/* Customer RM global base.

   Until 2026-10-01 this file was still the stock Blazor template: it set no font, no colour and no link
   colour, and it carried three rules referring to Bootstrap variables (--bs-secondary-color) that this
   host never loads. Anything the scoped .razor.css files did not reach therefore fell back to browser
   defaults - which is exactly what Stefaan saw on the sign-in page: a serif heading and a system input.

   The typography block below is the KOEPEL's, copied deliberately rather than invented, so a customer
   moving between customer.ezgroups.com and the office hosts reads the same letters.

   Deliberately NOT here: a global `* { box-sizing: border-box }`. The koepel has one, but this portal
   already has screens that were laid out and approved against the browser default, and a global change
   would move them all. Components that need it set it on their own elements (see Login.razor.css).

   Layout chrome stays in the scoped .razor.css files - this file is the floor, not the furniture. */

/* THIS APP'S TILE COLOUR, as the platform records it (2026-10-05).

   Every koepel app gets --mg-tile from <AppTint/>, which looks the running app's address up in MODULES and
   emits the tile's own colour. It cannot answer here, and measuring says why rather than guessing: there is
   no MODULES row for customer-rm at all - it is not a Frontdoor tile but a customer-facing host of its own -
   and this login is denied on those tables anyway (same reason Home.razor draws its tiles by hand).

   So the value is written here, from the platform's other register of per-app tile colours: the favicon
   system (.claude/docs/brand/favicon-system.md) records Customer RM as JADE, #50aa60 -> #27532f. Light is
   the tile, dark is its hover/ink - the same two ends as the icon, so the panel tabs, the browser tab and
   the home-screen icon are one colour family.

   Stefaan asked for it on the panel tabs (2026-10-05): grey ones "zien er triestig uit ... trekken de
   aandacht niet". Anything saying var(--mg-tile, <its old colour>) follows along by itself. */
:root {
    --mg-tile: #50aa60;
    --mg-tile-ink: #27532f;
    --mg-tile-fg: #ffffff;

    /* DE ZIJLADE DRAAGT HET DONKERE EIND VAN DIEZELFDE FAMILIE (2026-10-07).

       Stefaan, met de live tab voor zich: "Search is niet goed leesbaar." Nagemeten, niet geschat:
       wit op jade #50aa60 is 2,89:1 en leesbare tekst vraagt 4,5:1. Op een TEGEL geeft dat niets -
       daar staat een groot icoon op - maar de tab draagt .68rem hoofdletters, en die verdwenen.

         wit op jade  #50aa60 : 2,89:1   te weinig
         donker op jade       : 3,07:1   ook te weinig, dus de tekst omkleuren lost niets op
         wit op ink   #27532f : 8,88:1   <- dit

       Daarom het donkere eind als achtergrond en de jade als HOVER: dezelfde twee kleuren als de
       tegel en het favicon, alleen omgewisseld, zodat de lade nog altijd bij deze app hoort en de
       muis nog altijd iets ziet gebeuren.

       VERWORPEN: de jade lichter of donkerder stemmen tot ze net haalt. Dan wijkt het portaal af van
       het faviconregister (.claude/docs/brand/favicon-system.md) dat deze twee waarden vastlegt, en
       staat er een derde groen in omloop dat nergens opgeschreven is. */
    --mg-rail-tab: #27532f;
    --mg-rail-tab-fg: #ffffff;
    --mg-rail-tab-hover: #50aa60;
}

html, body {
    margin: 0;
    font-family: system-ui, -apple-system, "Segoe UI", Roboto, sans-serif;
    color: #1f2d32;
    background: #fff;
}

a { color: #14607a; }

h1, h2, h3 { line-height: 1.2; font-weight: 300; }

h1:focus {
    outline: none;
}

/* Form validation (Blazor's EditForm classes). */
.valid.modified:not([type=checkbox]) {
    outline: 1px solid #26b050;
}

.invalid {
    outline: 1px solid #e50000;
}

.validation-message {
    color: #e50000;
}

/* Blazor's default error toast. Same shape as the koepel's, so a fault looks the same everywhere. */
#blazor-error-ui {
    display: none;
    position: fixed;
    bottom: 0;
    left: 0;
    right: 0;
    background: #ffe08a;
    color: #3b2f00;
    padding: .6rem 1rem;
    box-shadow: 0 -1px 4px rgba(0,0,0,.2);
    z-index: 1000;
}
#blazor-error-ui .reload { color: #14607a; margin-left: .5rem; }

.blazor-error-boundary {
    background: #b32121;
    padding: 1rem;
    color: white;
}

    .blazor-error-boundary::after {
        content: "An error has occurred."
    }

/* =====================================================================================================
   ON PAPER (2026-10-05). The portal has one page meant to be printed - the rooming sheet a tour operator
   hands to a school - and the shell around it is the one thing that must not come along. Global rather
   than scoped on purpose: the shell lives in the host and the sheet in the class library, so no scoped
   stylesheet can reach both. Everything about the sheet ITSELF is in RoomingSheet.razor.css.
   ===================================================================================================== */
@media print {
    .shell, .officeview, #blazor-error-ui { display: none !important; }
    /* The body carries the portal's grey; paper does not. */
    .shell__body { min-height: 0 !important; background: #fff !important; }
    body { background: #fff !important; }
    @page { margin: 14mm; }
}
