.EventWrapper .card-body.scroll {
	display:block;
    font-size: .98em;
    height: 400px;
    overflow-y: auto;
}
.EventWrapper .card tbody {
	height:423px;
}
.EventWrapper .card thead,
.EventWrapper .card tbody {
    width: calc( 100% )/* scrollbar is average 1em/16px width, remove it from thead width */
}
.EventWrapper .card tbody {
    display:block;
    overflow:auto;
}
.EventWrapper .card thead,
.EventWrapper .card tbody tr {
    display:table;
    width:100%;
    table-layout:fixed;
}
.EventWrapper .card thead {
    width: calc( 100% - 1em )
}

.EventWrapper .interactive-results.card {
    margin:4px;
}

.EventWrapper .interactive-results a {
    text-decoration:none;
    text-align:center;
    font-size:1.1em;
}

/* Event page top-left menu (event-button-options in #easy_nav): dark extras */
body.mso-theme-dark #easy_nav .mso-user-menu .btn-outline-secondary {
    color: var(--mso-white, #f7fbff);
    border-color: var(--mso-line-2, #294b6d);
    background-color: transparent;
}
body.mso-theme-dark #easy_nav .mso-user-menu .btn-outline-secondary:hover,
body.mso-theme-dark #easy_nav .mso-user-menu .btn-outline-secondary:focus {
    color: #64e6ff;
    border-color: #29445f;
    background-color: #10283a;
}
body.mso-theme-dark #easy_nav .mso-user-menu .dropdown-divider {
    border-top-color: var(--mso-line, #1f3043);
}

/* GROK Bot Edit (2026-10-18): Event page sideways scroll (Karl). #MeetInfo_Nav is a Bootstrap .row placed directly in #EventWrapper (no .container padding),
   so its -12px gutters pushed the page 12px wider than the viewport. Zero gutter on this row only: no negative margins, no column padding, nav looks the same. */
#EventWrapper > #MeetInfo_Nav.row {
    --bs-gutter-x: 0;
}

/* GROK Bot Edit (2026-10-18): Live TV cut off at the right of the blue Event nav on phones (Karl). This .navbar has no inner .container, so it has no side padding,
   and below lg Bootstrap gives .nav-link no side padding either: Live TV and its icon ran into the screen edge. Pad the bar like a container (.75rem), below lg only. */
@media (max-width: 991.98px) {
    #MeetInfo_Nav #EventNav > nav.navbar {
        padding-left: .75rem;
        padding-right: .75rem;
    }
}

/* GROK Bot Edit (2026-10-21): Top Scores header out of line with its cells (Karl). The scrolling-card rules above size thead to 100% - 1em to allow for
   the tbody scrollbar, but the tbody only shows a scrollbar when it overflows, and overlay scrollbars (phones) take no width, so the header columns came out
   about 1em narrower than the cells. Instead, both thead and tbody reserve the same scrollbar gutter (scrollbar-gutter: stable): equal width in every case. */
.EventWrapper .card thead {
    display: block;
    width: 100%;
    overflow: hidden;
    scrollbar-gutter: stable;
}
.EventWrapper .card thead tr {
    display: table;
    width: 100%;
    table-layout: fixed;
}
.EventWrapper .card tbody {
    scrollbar-gutter: stable;
}

/* GROK Bot Edit (2026-11-13): Event Comments v1 layout block (MSO Dev Bot 2026-10-31, pending) replaced by v2 below with the card change. */
/* GROK Bot Edit (2026-11-13): Event Comments v2 layout block (MSO Dev Bot 2026-11-13) NOT APPROVED by Karl 2026-11-13 (page padding ~25px, use standard Bootstrap objects); replaced by v3 below. */
/*
 * [Code Review v3]
 * Changed By:  MSO Dev Bot        Date: 2026-11-13
 * Reason:      Karl (Event Comments v2, NOT APPROVED): Need page padding beyond the comments box, maybe 25px; why are we not using standard Bootstrap objects?
 * Change:      Removed the custom #event_comments thread rules (media-list, media margins, media-body background, heading, description, actions).  Those now use standard Bootstrap classes added in Event.xml (px-4 pb-4 on the row, ~24px) and in mso.Events.js onDrawRow (flex-column, bg-light, rounded, small, text-muted, mb-1, ms-4, text-break, mt-1).  The thread markup stays the existing mso.Messaging media objects (not list-group, which would mean changing Messaging).  One leftover rule: hide the h3 mso.Messaging inserts after 10 minutes, because this block does not poll and that node is created in JS.
 * Tested:      Signed out: Dev Bot, 2026-11-13, GET http://local.meetscoresonline.com/2026-VA-In-House-Meet (HTTP 200): #event_comments has px-4 pb-4; this file no longer has the v2 thread rules except the h3 hide.  Visual check of the ~25px padding and thread layout (replies indent, cards, typography): NOT YET TESTED.
 * To Reproduce: Open http://local.meetscoresonline.com/2026-VA-In-House-Meet, scroll below Report Builder / Top Scores: the Comments card has about 25px of space around it.  Signed in, comments stack vertically, replies indent, each comment sits in a light rounded body; the "Refresh browser to continue messaging." heading does not appear.
 * Reviewed By: Karl        Date: 2026-11-14
 * Review:        APPROVED
 * Comment:
 */
/* GROK Bot Edit (2026-11-13): leftover - mso.Messaging inserts this h3 after 10 minutes; this thread does not poll, so hide it. The node is created in JS, so it cannot get a Bootstrap class from markup. */
#event_comments .event-comments-thread > h3 { display: none; }
/*
 * [Code Review v1]
 * Changed By:  MSO Dev Bot        Date: 2026-11-13
 * Reason:      Karl: "Can we do message bubble cards? Probably a little custom CSS but that is ok in this case."
 * Change:      Small #event_comments-scoped rule for the comment bubble fill (#f0f4f8) and a matching tail.  The bubble shape uses standard Bootstrap utilities added in mso.Events.js onDrawRow (rounded, shadow-sm, px-3, py-2, position-relative).  The bubble does not use the bg-light utility because the MSO theme paints .bg-light white with !important (body.mso-theme-system .bg-light).  Avatar stays beside the bubble; name and local time stay in the bubble header; reply indent and border-start are unchanged.  MAX_DEPTH and sort order are unchanged.
 * Tested:      Dev Bot, 2026-11-13: GET http://local.meetscoresonline.com/Event/34429#event_comments and this stylesheet returned HTTP 200 (signed out).  Headless load of that URL: each comment and reply is a rounded light bubble with a small tail toward the avatar; replies stay indented with a left border.  Screenshot: /workspace/event-comments-bubbles.png.  Signed-in Reply form inside a bubble: NOT YET TESTED (no sign-in credentials; threads render signed out).
 * To Reproduce: Open http://local.meetscoresonline.com/Event/34429#event_comments (signed out is fine).  Each comment and reply is a rounded light bubble with a small tail toward the avatar, the name and local time in the bubble header, and replies indented with a left border.
 * Reviewed By: Karl        Date: 2026-11-14
 * Review:        APPROVED
 * Comment:
 */
/* GROK Bot Edit (2026-11-14): top-level bubble fill #dde5ee (subtle greyer blue, not baby blue) and matching tail (Karl); scoped under #event_comments */
#event_comments .event-comment-bubble {
    background-color: #dde5ee;
}
#event_comments .event-comment-bubble::before {
    content: "";
    position: absolute;
    left: -6px;
    top: 12px;
    border-top: 6px solid transparent;
    border-bottom: 6px solid transparent;
    border-right: 6px solid #dde5ee;
}
/*
 * [Code Review v1]
 * Changed By:  MSO Dev Bot        Date: 2026-11-14
 * Reason:      Karl (2026-11-14): "let's make the primary message a subtle blue, not baby blue though."
 * Change:      The existing #event_comments top-level bubble fill and matching tail change from #f0f4f8 to #dde5ee, a slightly deeper grey-blue (not a pastel baby blue).  Reply bubbles stay #fff4ec with the existing nested .media .media selector.  No new CSS helper and no onDrawRow change.
 * Tested:      Dev Bot, 2026-11-14: GET http://local.meetscoresonline.com/Event/34429#event_comments and this stylesheet returned HTTP 200 (signed out).  Headless load of that URL with the Comments tab open: top-level bubble fill is #dde5ee and reply fill is #fff4ec, with tails matching each fill.  Screenshot: /workspace/event-comments-blue-rework.png.
 * To Reproduce: Open http://local.meetscoresonline.com/Event/34429#event_comments.  Top-level comments are a subtle grey-blue (#dde5ee), not a pale baby blue, and replies stay a very light orange (#fff4ec), with tails matching each fill.
 * Reviewed By: Karl        Date: 2026-11-14
 * Review: APPROVED
 * Comment:
 */
/* GROK Bot Edit (2026-11-13): subtle reply bubble fill (Karl); nested .media .media selector, scoped under #event_comments */
#event_comments .media .media .event-comment-bubble {
    background-color: #fff4ec;
}
#event_comments .media .media .event-comment-bubble::before {
    border-right-color: #fff4ec;
}
