.themefontcolor
{
    color: black
}

.themebgcolor
{
    background-color: #F7EA48
}

.specialfontcolor
{
    color: black
}

.logosize
{
    width: 100px; height: auto;
}

.countrylogosize
{
    width: 150px; height: auto;
}


@media (min-width: 768px) {
    .navbar-brand-gg
        {
            position: absolute;
            left: 50%;
            transform: translateX(-50%);
        }
    }

.navbar-brand-gg {padding: 0;}
    
.dropdown:hover .dropdown-menu {
    display: block;
    }    

.dashboardImageContainer{
    margin-bottom: 3px;
    min-height: 100px;
    background-color: silver;
    text-align: center;
    font-size: large;
}    

/* Cards */
.CardHeaderInfo
{
    font-weight: bold;
    color: white;
    background-color: gray;
}

.CardHeaderText
{
    font-weight: bold;
    color: #efa404;
    background-color: gray;
}

/* Table */

/* Restore the original pre-Epic bg-secondary + text-white look for
   table-secondary rows/headers (gtn-group1/erp_project#1203 standalone fix,
   no issue). table-secondary is the correct Bootstrap 5 mechanism (commit
   714466f, MR !105) -- it sets --bs-table-bg/--bs-table-color as CSS custom
   properties that cascade to <th>/<td> children -- but Bootstrap 5's own
   default values for it are a light grey tint with black text, not the
   original medium slate-grey/white-text combination. This overrides just
   those colour values, app-wide, loaded after the Bootstrap CDN stylesheet
   so it wins.

   Overriding --bs-table-color (not a plain `color` declaration) matters:
   Bootstrap's own `.table > :not(caption) > * > *` rule sets each cell's
   *own* `color` from `var(--bs-table-color-state, var(--bs-table-color-type,
   var(--bs-table-color)))` -- a `color` set directly on .table-secondary
   (the row) is only inherited text colour and is overridden by that more
   specific per-cell rule, so it never reaches the <th>/<td> text (confirmed
   live via Playwright: header text stayed black despite `color: #fff
   !important` on the row).

   !important is needed on every property here because several page-specific
   nav partials (spotit/spotitnav.html, reports/reportsnav.html,
   proposal/client/clientbase.html, copyscripts/copynav.html,
   copyscripts/copyform/copyformnav.html) call {% bootstrap_css %} a second
   time inside <body>, re-loading Bootstrap's own .table-secondary rule
   *after* this stylesheet -- without !important that later, equal-specificity
   load would win on any page that includes one of those partials (confirmed
   live via Playwright on spotit/bookinglist.html, which includes
   spotitnav.html). */
.table-secondary {
    --bs-table-bg: #6c757d !important;
    --bs-table-border-color: #65707a !important;
    --bs-table-color: #fff !important;
}

/* Remove the default underline from links inside tables (standalone fix,
   no issue, person's own styling preference -- not a Bootstrap-migration
   regression; links have always been underlined by Bootstrap default in
   both v4 and v5). `.table a` (a class plus a type selector, specificity
   0,1,1) is more specific than Bootstrap's own bare `a { text-decoration:
   underline; }` rule (specificity 0,0,1), so it wins the cascade on
   specificity alone, regardless of load order -- including on the
   page-specific nav partials (spotit/spotitnav.html and four others, see
   the .table-secondary override above) that reload Bootstrap's CSS a
   second time inside <body>: no !important needed here, unlike that
   .table-secondary case where both rules share the same selector and
   specificity. The hover/focus state keeps the underline, so a link
   inside a table remains discoverable as clickable (Bootstrap's link
   colour already marks it visually even with the underline gone). */
.table a {
    text-decoration: none;
}

.table a:hover,
.table a:focus {
    text-decoration: underline;
}

/* Remove the default underline from the navbar's app-name brand link
   (standalone fix, person's own styling preference). `.navbar-brand`
   (specificity 0,1,0) already beats Bootstrap's bare `a { text-decoration:
   underline; }` rule (0,0,1) on specificity alone, so no !important needed. */
.navbar-brand {
    text-decoration: none;
}

.my-table-scrollbar-400 {
    position: relative;
    height: 400px;
    overflow: auto;
    }
.table-wrapper-scroll-y {
    display: block;
    }