/*
Theme Name: GeneratePress Child
Theme URI: https://generatepress.com
Description: GeneratePress child theme.
Author:
Author URI:
Template: generatepress
Version: 1.0.0
License: GNU General Public License v2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Text Domain: generatepress-child
*/

.ixbrl-lp a:not(.btn):not(.nav-link):not(.dropdown-item):not(.stretched-link){ text-decoration:none; }
.ixbrl-lp a:not(.btn):hover{ text-decoration:underline; }
.ixbrl-lp section[id] { scroll-margin-top: 80px }

/* MDB5 navbar: force the logo's rendered height. Needed because the
Customizer custom-logo is an SVG with only a viewBox (no width/height on the
root <svg>), so the_custom_logo() can't read its dimensions and bakes
width="1" height="1" onto the <img> tag itself -- !important guarantees this
rule wins over those inline attributes regardless of specificity elsewhere. */
/* .navbar-brand img { */
.custom-logo{
	height: 18px !important;
	width: auto !important;
}

/* the_custom_logo() wraps the <img> in its own <a class="custom-logo-link">
(see the note in template-parts/mdb-navbar.php on why that can't be nested
inside another <a>) -- that inner anchor is a plain inline element, not a
flex container, so its image is vertically positioned by inline-baseline
rules (reserving descender space from .navbar-brand's inherited font
metrics) instead of being centered directly. Making it flex too puts the
<img> in exactly the same position as the reference Vue app, where
MDBNavbarBrand IS the <a class="navbar-brand"> and centers its <img>
directly with no intermediate non-flex wrapper. */
.navbar-brand .custom-logo-link {
	display: flex;
	align-items: center;
}

/* Mobile navbar toggler: MDB/Bootstrap's default hover/focus/active state is
a neutral gray outline (box-shadow uses currentColor, resting color is
--mdb-navbar-color) -- fill it with MDB's primary color and switch the icon
to white instead, leaving the resting (untouched/unfocused) state as-is.
box-shadow:none avoids a mismatched gray ring showing on top of the fill. */
.navbar-toggler:hover,
.navbar-toggler:focus,
.navbar-toggler:active {
	color: #fff;
	background-color: var(--mdb-primary);
	border-color: var(--mdb-primary);
	box-shadow: none;
}

/* GeneratePress's own Customizer-generated CSS (generate-style-inline-css)
adds 30px of padding to these structural wrappers below 768px -- same class
of collision as the .container background-color bug (see the CLAUDE.md note
on it): GP's own #content/.site-content/.inside-article markup is still what
our header.php/footer.php/page templates render into, so this rule always
applies regardless of which "Container" layout (One Container vs Separate
Containers) is selected in the Customizer. Our own sections/cards already
carry their own MDB padding (.py-6, .card-body p-4, etc.), so this extra 30px
just doubles up. !important is deliberate here, not habit: this specific rule
is regenerated by GP itself whenever Customizer settings change (colors,
container width, spacing), so a plain specificity-based override could stop
winning after an unrelated Customizer edit reorders or rewrites that inline
block -- !important is what stays correct regardless. */
@media (max-width: 768px) {
	.separate-containers .inside-article,
	.separate-containers .comments-area,
	.separate-containers .page-header,
	.separate-containers .paging-navigation,
	.one-container .site-content,
	.inside-page-header {
		padding: 0 !important;
	}
}

.separate-containers .inside-article, .separate-containers .comments-area, .separate-containers .page-header, .one-container .container, .separate-containers .paging-navigation, .inside-page-header {
    background-color: inherit !important;
}