iya-sts
    Preparing search index...

    The card's stylesheets. A static utility class of constants.

    Index
    ACCOUNTS_CSS: string = ...

    The account control every public surface draws beside the chooser with several accounts on (#561, web_accounts.ts): small and to one side, as the chooser is, its panel a short list and one link. No page draws it with the setting off, so these rules then style nothing.

    BRAND_CSS: string = ...

    THE THREE LAYOUTS AND THE BRAND HEADER (#717): keyed on <html data-sts-layout>, which a shell carries only for a realm whose appearance differs from the service's, so none of these rules applies anywhere else. The header (sts-brand) is drawn before the card by the runtime; the card and its form are untouched in every layout.

    • centered — the header above the card, both in the middle.
    • banner — the header a band in the accent colour across the top, the card below it.
    • split — the header a panel in the accent colour beside the card, above it on a screen narrower than 720 pixels.
    CARD_CSS: string = ...

    The stylesheet of the sign-in screen and the federation chooser, shared with the consent screen; the wide card's rules after the chooser's. Every colour a realm may set is a custom property (themed()), and the layouts' rules come last (#717).

    CHOOSER_CSS: string = ...

    The language chooser's stylesheet (#539), small and to one side: a page's first business is its own form. A constant of its own because the second factor pages carry stylesheets of their own, and each appends this one — their button{width:100%} and input{width:100%} would otherwise stretch the chooser across the card.

    CLIENT_CSS: string = ...

    WHO IS ASKING (#1300, authn/web_client_display.ts): the client's logo, name and documents at the head of a sign-in page or the consent screen — the logo bounded, since the client chose its size, and centred above the name.

    CONSENT_CSS: string = ...

    The CONSENT SCREEN's card (#576): the rules oauth-oidc/consent_screen.ts appended to the card while it drew the page, scoped to .card.consent so no other page of the card changes — a wider card for the scope rows, each scope and authorization detail in a box of its own, a detail's members as a grid, a detail's limits (#432 phase 5), and the fold of what was already agreed.

    DESCRIBE_CSS: string = ...

    The protocol families' description pages (#584): /saml2, /saml11, /xacml, /ssf, /scim and /spiffe, each a long page of tables that the server drew in a stylesheet of its own until then — a wider card, a note, the lists, a third-level heading. Scoped to .describe, the class the surface's card carries, so no other page of the card changes.

    DIAG_CSS: string = ...

    The DIAGNOSTIC pages (#583): the TLS pages, which carried these in the <style> of their own server-drawn shell (tls_server.js's pageShell()) until they became static surfaces — a verdict's band, the truststore's PEM box, a list's indent — scoped to .diag, the class their card carries, and the TLS page's wider card to .tls, so no other page changes. The SPNEGO demonstration pages drew in it too until they left the runtime for the companion (#595).

    FOLD_CSS: string = ...

    The console's prose fold (WebKit.note(), rcbj 2026-10-12): the sign-in screen's explanations — the federation, Kerberos and wallet blurbs and the notes at its foot — are each a <p class="note"> or, longer than a line, a <details class="note fold"> whose summary is the first sentence. The palette is the text's own (a fold reads as the sentence it summarises), the marker the console's triangles.

    GNAP_CSS: string = ...

    GNAP's interaction pages (#578), which carried these in a <style> of their own (gnap_interact.ts's PAGE_CSS) until they became a static surface: the wider card, the client's line and logo, the rights as a list of boxes, a right's limits under it, and the user code's field. Every rule is scoped to .gnap, the class the surface's card carries, so no other page of the card changes.

    STEP_CSS: string = ...

    What the sign-in surface's steps draw beyond the screen (#572, #573): the notice a resend leaves, the warning of a set of recovery codes running low, the set-up step's headings, a code's wide field, the ways round a factor, the technical fold (the QR code's rule is the wallet's, #574). They were in each step page's own stylesheet while the server drew the steps.

    WIDE_CSS: string = ...

    The WIDE card (#575): the SPNEGO sign-in's pages carry tables — the service principal, the ticket's flags, the acceptor's checks — that do not fit the 380-pixel card, so .card.wide lifts the width and every rule below is scoped to it, leaving every other page of the card as it was. The values are kerberos/spnego.js's page shell's, where these pages were drawn until #575.

    • A REALM'S SIGN-IN APPEARANCE (#717, common/branding.ts): every colour the card is drawn in, read through a custom property whose fallback is the literal it replaced — so with no /web/theme.css linked (every realm that set nothing) the card is drawn exactly as before, and a realm's theme sets the properties. Applied to the finished stylesheet rather than written into each rule, so the rules above stay readable and one table says which literal means what. The order matters: the accent first, then the text on it.

      Parameters

      • css: string

        the card's stylesheet as written

      Returns string

      the same rules, each colour a custom property with its fallback