/* /Components/Layout/MainLayout.razor.rz.scp.css */
/* SLOW-5 3.1 - real bug found live via a trial-click Playwright test (CompanyPagesTests.
   CompanySelect_CreateNewCompanyButton_Navigates), not just a visibility assertion, exactly the
   class of bug the workspace's own standing rule warns ToBeVisibleAsync() can't catch.

   Root cause: MudBlazor's own `.mud-main-content { padding-top: calc(var(--mud-appbar-height) - ...) }`
   rule is what reserves space so page content clears the fixed MudAppBar - but MudBlazor's utility
   classes are `!important`-flagged (`.pa-4 { padding: 16px !important; }`), and MainLayout.razor used
   `<MudMainContent Class="pa-4">` for its side/bottom padding. `!important` always wins regardless of
   selector order, so `pa-4` silently collapsed the appbar-height top padding down to a flat 16px on
   EVERY page (not just this one, not just phone-width) - about 40px less than the appbar's real
   height, hidden under a "position:fixed" AppBar (z-index 1300) and the EnvironmentBanner
   (z-index 10000, also fixed-to-top on desktop widths) sitting even higher. Content near the top of
   any page - like CompanySelect's heading + action buttons - was rendered UNDER both, unclickable.
   Never noticed before because ShellHome's own demo content happens to start low enough (a heading +
   descriptive paragraph) that nothing needed a real click in that dead zone.

   Fix: give MudMainContent this scoped class instead of the MudBlazor "pa-4" utility - it reproduces
   the same visual side/bottom padding WITHOUT touching padding-top, so MudBlazor's own
   appbar-height reservation rule is left completely intact. */
.sb-main-content[b-mrxzp4mj1m] {
    padding-left: 16px;
    padding-right: 16px;
    padding-bottom: 16px;
}
/* /Components/Pages/TransactionsIndex.razor.rz.scp.css */
/* SLOW-413: this page's own override of the shared .sb-table's middle vertical-align (app.css),
   scoped to just this page via Blazor CSS isolation.

   Root cause: SLOW-146 added chips + Confirm/Undo buttons into the Category cell, on top of the
   Classify/Match/Find Match buttons already there - on the iPhone13 viewport (narrow column) those
   wrap onto 2-3 lines, making the row much taller than the Actions cell's own content (just the
   view-details icon + the "Row actions" kebab). With td { vertical-align: middle } the kebab button
   sat roughly mid-row - so when its MudMenu popover didn't fit below (near the bottom of a short
   mobile viewport) and MudBlazor's overflow-flip-always kicked in, it flipped upward from that
   mid-row point and landed on top of this SAME row's own Category buttons above it, not merely
   beside them - reproduced live via Playwright's own hit-test log ("Split..." intercepting a click
   meant for "Exclude") and a screenshot showing the flipped popover painted over the Find Match
   button. Top-aligning every cell keeps the kebab level with the top of whatever content the
   Category cell wraps to, so an upward flip lands above the row (into whitespace/the header), never
   back into the row's own content. A forced click would have hidden this same overlap from a real
   user tapping at that viewport. */
.sb-table td[b-w4vj041wsh] { vertical-align: top; }
/* /Views/Shared/_Layout.cshtml.rz.scp.css */
/* Please see documentation at https://learn.microsoft.com/aspnet/core/client-side/bundling-and-minification
for details on configuring this project to bundle and minify static web assets. */

a.navbar-brand[b-0rekl62xx9] {
  white-space: normal;
  text-align: center;
  word-break: break-all;
}

a[b-0rekl62xx9] {
  color: #0077cc;
}

.btn-primary[b-0rekl62xx9] {
  color: #fff;
  background-color: #1b6ec2;
  border-color: #1861ac;
}

.nav-pills .nav-link.active[b-0rekl62xx9], .nav-pills .show > .nav-link[b-0rekl62xx9] {
  color: #fff;
  background-color: #1b6ec2;
  border-color: #1861ac;
}

.border-top[b-0rekl62xx9] {
  border-top: 1px solid #e5e5e5;
}
.border-bottom[b-0rekl62xx9] {
  border-bottom: 1px solid #e5e5e5;
}

.box-shadow[b-0rekl62xx9] {
  box-shadow: 0 .25rem .75rem rgba(0, 0, 0, .05);
}

button.accept-policy[b-0rekl62xx9] {
  font-size: 1rem;
  line-height: inherit;
}

.footer[b-0rekl62xx9] {
  position: absolute;
  bottom: 0;
  width: 100%;
  white-space: nowrap;
  line-height: 60px;
}
