/* ============================================================================
   Customer Support — Spin Lookup
   ============================================================================

   One rule, for an open calendar's paint order.

   The page's width comes from the shared hrd-wide-page class (see
   assets/hrd_components.css), applied on the layout's container — the results
   table carries 14-15 columns and none of them may truncate, so it needs more
   room than the app's default 1300px column gives it.

   ---------------------------------------------------------------------------
   Calendar paint order
   ---------------------------------------------------------------------------
   With results on screen, an open start/end calendar was painted over by the
   results table and appeared cut off mid-month.

   Why it happened: dcc.DatePickerSingle's overlay (.SingleDatePicker_picker)
   ships with z-index: 1, while the DataTable's fixed header and frozen columns
   use z-index values up to 500. The results card comes after the filter card in
   the DOM and neither creates a stacking context, so those table layers won the
   paint order over the calendar.

   The fix: lift the filter card into its own stacking context above 500, so the
   calendar — a descendant of that context — clears the table. Scoped to this
   page's wrapper rather than .hrd-filter-section, which the results card also
   uses (raising both would change nothing).
   ============================================================================ */

.cs-spin-filters {
    position: relative;
    z-index: 600;
}