/*
 * Dashboard sidebar nav overrides (2026-08-17 reskin).
 *
 * SimpleBar (data-simplebar on .dashboard-sidebar-inner in
 * template-dashboard.php) renders its own custom scrollbar, not the
 * browser's native one - overriding it means targeting SimpleBar's own
 * .simplebar-track/.simplebar-scrollbar classes, not scrollbar-width.
 * Parent theme's style.css never sets a base (non-mobile-media-query)
 * width for these, so SimpleBar's own default (11px track) was showing.
 */
.dashboard-sidebar-inner .simplebar-track.simplebar-vertical {
	width: 6px;
}

.dashboard-sidebar-inner .simplebar-scrollbar:before {
	left: 1px;
	right: 1px;
}

/*
 * Native-scrollbar fallback. Parent theme's style.css (~33978) sets plain
 * `overflow: auto; height: 100%;` directly on .dashboard-sidebar-inner -
 * SimpleBar is supposed to take over and hide this, but confirmed via
 * screenshot (2026-08-17) it isn't actually initializing on this element in
 * practice (the browser was rendering its own native scrollbar, arrow
 * buttons and all, not SimpleBar's custom thumb). These rules thin the
 * browser's own scrollbar directly so the fix holds regardless of whether
 * SimpleBar ever takes over.
 */
.dashboard-sidebar-inner {
	scrollbar-width: thin;
}

.dashboard-sidebar-inner::-webkit-scrollbar {
	width: 6px;
}

.dashboard-sidebar-inner::-webkit-scrollbar-track {
	background: transparent;
}

.dashboard-sidebar-inner::-webkit-scrollbar-thumb {
	background-color: rgba(0, 0, 0, 0.2);
	border-radius: 3px;
}

/*
 * Hover/active nav row: parent theme's style.css (~34076-34085) uses its
 * default green (#26ae61) for these states, as a light tinted background
 * with green text/icon. Swapped to the child theme's own brand secondary
 * color (--child-theme-secondary-color, defined in style.css/style.min.css
 * :root - the dark blue from the JobsFor logo) as a solid fill with white
 * text/icon, per direct request. !important because this selector was
 * confirmed (screenshot, 2026-08-17) to only partially win against the
 * parent theme's identical-specificity rule in practice - matches this
 * codebase's established pattern for beating parent-theme specificity
 * (see the Elementor typography fix in project memory).
 */
.dashboard-nav ul li.active-submenu,
.dashboard-nav ul li.active,
.dashboard-nav ul li:hover {
	border-color: var(--child-theme-secondary-color) !important;
	background-color: var(--child-theme-secondary-color) !important;
}

.dashboard-nav ul li.active-submenu a,
.dashboard-nav ul li:hover a,
.dashboard-nav ul li.active a {
	color: #fff !important;
}

.dashboard-nav ul li.active-submenu a i,
.dashboard-nav ul li.active a i,
.dashboard-nav ul li:hover a i {
	color: #fff !important;
}