/*
  demo-overrides.css — the only CSS written for the Insights Summary port.

  Loaded LAST, after summary.css, so it wins on the few rules that assume app
  chrome this page doesn't have. summary.css itself is a byte-for-byte copy of
  the app's css/destiny-2/insights/summary.css and is not edited, which is what
  keeps the demo looking like the product.

  Same approach as ../../assets/css/demo-overrides.css on the analytics demo.
*/

/* --- Offsets ------------------------------------------------------- */
/*
  The app reserves 72px for its fixed header; the demo topbar is ~57px and
  sticky, i.e. in normal flow, so both the tab row and the grid move up.

  The subtlety worth writing down: report-shell.css gives .tab-nav
  `position: relative; top: 60px`. A relative offset shifts an element
  visually but leaves its flow box where it was, so it reserves no space —
  push .chat-grids up far enough and the grid slides underneath the tabs
  rather than below them. That is exactly what a first pass at 40px did.

  So the two are set together: the tabs drop just clear of the topbar, and the
  grid clears the tabs' 37px flow box plus their 16px shift.
*/
.tab-nav {
    top: 16px;
}

.chat-grids {
    top: 40px;
    padding-bottom: 48px;
}

/* --- Performance Trends affordances -------------------------------- */
/*
  Three "View Trend" links and the second tab point at a page this demo does
  not include. They are marked aria-disabled in the markup; this is what makes
  that state legible rather than a link that silently does nothing.

  Kept as a single rule keyed off the attribute so restoring the page is purely
  an HTML change — put the hrefs back and these stop matching.
*/
.tab-link[aria-disabled="true"],
.trend-link[aria-disabled="true"],
.gs-trend-link[aria-disabled="true"],
.kt-trend-link[aria-disabled="true"] {
    opacity: 0.4;
    cursor: not-allowed;
    pointer-events: none;
}

/* --- Recent Matches rows ------------------------------------------- */
/*
  Rows link through to the match drilldown (see note 4 in summary.js). The app
  gets its pointer cursor from the real anchor it renders inside the action
  cell; the demo keeps that, and this just makes the whole row read as live.
*/
.rm-row {
    cursor: pointer;
}