/*
 * knc-24h-widget.css — utility rules missing from our copy of 24h.com.vn's
 * match-widget CSS (fixtures /lich-thi-dau-bong-da-*.html, standings
 * /bang-xep-hang.html and every other page that embeds the scraped fragment).
 *
 * The knc:fetchStanding / knc:fetchUpcoming scrapers keep only
 * div.livescore-soccer-main-body, dropping the <style> blocks in 24h's <head>.
 * The hand-maintained inline copy in
 * app/Http/Components/Upcoming/MenuAndBanner.php covers the row layout but
 * lacks the utilities below, which 24h's current markup relies on (audited on
 * the live C1 fixtures + standings pages, Sep 2026). Values are lifted from
 * 24h's head CSS; the two deliberate deviations are noted inline.
 *
 * Rules here are strictly ADDITIVE: never redefine a selector already
 * provided by MenuAndBanner.php, MainContainerStanding.php or the other
 * files in resources/css/, and use no bare element/universal selectors, so
 * this file cannot restyle our own (non-widget) markup. Our components emit
 * none of these class names (audited) — they only occur inside the scraped
 * 24h fragments.
 *
 * .d-none/.d-block are scoped under the fragment root because 24h's rows
 * carry `d-flex ... d-none` together, and MenuAndBanner's later-in-body
 * `.d-flex{display:flex!important}` would win the cascade against an unscoped
 * selector — the same reason 24h itself scopes them under `.livescore-html`.
 */

/* Display utilities (Bootstrap-4 semantics; our bootstrap.css is v3.3.7,
 * which predates the d-* utilities). .d-none hides 24h's duplicate
 * round-header rows — the "ghost rows" reported on the fixtures pages. */
.livescore-soccer-main-body .d-none{display:none!important}
.livescore-soccer-main-body .d-block{display:block!important}

/* Flex utilities. */
.flex-1{flex:1}
.flex-wrap{flex-wrap:wrap}

/* Left column of a match row (kick-off time + TV channel): fixed basis like
 * on 24h (same min-width breakpoint, scoped to the widget's list container). */
@media screen and (min-width:736px){
.cate-24h-foot-home-sche-content__list .box-l{flex:0 0 100px}
}

/* Margin utilities (24h's mar-* scale; mar-t-20 is the class FetchStanding
 * appends to the standings fragment root). */
.mar-t-5{margin-top:5px!important}
.mar-b-5{margin-bottom:5px!important}
.mar-r-5{margin-right:5px!important}
.mar-r-10{margin-right:10px!important}
.mar-r-20{margin-right:20px!important}
.mar-t-20{margin-top:20px!important}
.margin-bottom-20{margin-bottom:20px!important}

/* Spacing utilities for the widget's quick-links banner (ls-menu-link). */
.padd-l-15{padding-left:15px!important}
.padd-r-15{padding-right:15px!important}
.overflow-h{overflow:hidden}

/* .link-ls-table is 24h's invisible full-row click overlay. Unpositioned, its
 * "Home vs Away" text renders inline on top of the score box (the overlapping
 * ghost text from the bug report), so it gets the overlay treatment. */
.link-ls-table{position:absolute;top:0;left:0;right:0;bottom:0;text-indent:-99999px;z-index:1}

/* The score digits ARE the text content of the a.link-over-full anchors
 * inside .match-fs_a/.match-fs_b — on 24h these links stay visible and
 * centered (they are NOT overlays). */
.match-fs_a a.link-over-full,
.match-fs_b a.link-over-full{width:100%;text-align:center;height:unset}

/* Score boxes: compact, no grow/shrink (24h values). Scoped like 24h's rule
 * so it outranks MenuAndBanner's `.cate-24h-foot-home-sche-content__match-score
 * span{flex:1;...}`, which would otherwise stretch both boxes across the
 * score area. */
.cate-24h-foot-home-sche-content__match-score .match-fs_a,
.cate-24h-foot-home-sche-content__match-score .match-fs_b{flex:0 0 auto}
.cate-24h-foot-home-sche-content__match-score .match-fs_a{margin:0 3px 0 0}
.cate-24h-foot-home-sche-content__match-score .match-fs_b{margin:0 0 0 3px}

/* Color utilities (24h scopes the team-name red to the fixtures table). */
.color-white{color:#fff}
.cate-24h-foot-box-sche-table .color-danger{color:#D9001B!important}

/* Font-weight utilities. 24h implements these by swapping to its
 * Roboto-Medium / Roboto-Bold @font-face families, which our site does not
 * load — so use the equivalent Bootstrap weight values instead (the one
 * deliberate value substitution in this file; everything else is verbatim). */
.fw-medium{font-weight:500!important}
.fw-bold{font-weight:700!important}
