/* gp-fluentroadmap-styling.css
 * Fixes 3 visual mismatches between the FluentRoadmap board widget and the
 * FluentSupport tickets widget directly above it on customer-facing pages
 * (e.g. /support), confirmed live via devtools inspection as a switched-in
 * production customer (rob@landsalesbulletin.com) on 2026-10-15:
 *
 * 1. PADDING/ALIGNMENT: the Gutenberg Group block wrapping the
 *    [fluent-roadmap] shortcode on this page carries an inline
 *    style padding-left:20px (page-content-level, not a stylesheet rule)
 *    that the matching block around the tickets widget does NOT have --
 *    confirmed via getComputedStyle: tickets container left=24/width=1137,
 *    roadmap wrapper left=44/width=1117 (exactly that 20px gap). Overriding
 *    with !important here is required because inline styles otherwise beat
 *    any external stylesheet rule regardless of selector specificity.
 *
 * 2. BORDER RADIUS: FluentSupport's .fs_tickets_container is a single
 *    white box with a uniform 16px radius (left=24,width=1137,height=568).
 *    FluentRoadmap splits into .frm_board_navigations (white, but only
 *    5px 5px 0 0) and .frmap_route_view_stage below it (fully
 *    transparent, 0 radius) -- so the board never reads as one rounded
 *    card. Matching the 16px value and giving the body panel a white
 *    background + bottom radius recreates the same single-card look.
 *
 * 3. TEXT COLOR: idea-card links (e.g. the idea title link in the Pending
 *    list) inherit color #fff from a low-specificity theme default meant
 *    for dark hero sections, rendering invisible white-on-white. Fix
 *    confirmed/specified directly by Joe via devtools: the override rule
 *    a:where(:not(.wp-element-button)) with specificity (0,0,1).
 */

/* IMPORTANT: must be direct-child (>) only. A plain :has(.fluent_board_app_wrapper)
 * (no >) matches ANY ancestor containing that class anywhere in its descendants --
 * including the outer page-section Group block that wraps both the tickets AND
 * roadmap widgets -- which zeroed the whole page's left padding out to the
 * browser edge (confirmed live, 2026-10-15, Joe caught it immediately). Only the
 * one Group block that directly wraps the roadmap shortcode should lose its
 * extra padding; everything above it keeps its normal page padding. */
.wp-block-group:has(> .fluent_board_app_wrapper) {
  padding-left: 0 !important;
}

.fluent_board_app_wrapper .frm_board_navigations {
  border-radius: 16px 16px 0 0;
}

.fluent_board_app_wrapper .frmap_route_view_stage {
  background: #fff;
  border-radius: 0 0 16px 16px;
  /* The inner .frm_ideas list wrapper carries its own mismatched 5px bottom
   * radius, and this container defaults to overflow:visible, so that inner
   * 5px radius was showing through instead of this box's 16px -- a visible
   * seam at the very bottom (caught live by Joe, 2026-10-15). overflow:hidden
   * forces this box's own 16px radius to actually clip its children. Safe
   * here specifically because the dropdowns/search live in .frm_board_navigations
   * (the header above this box), not inside this list body. */
  overflow: hidden;
}

.fluent_board_app_wrapper a:where(:not(.wp-element-button)) {
  color: #000;
}