/* Inline <style> blocks from the live page /subpoenarequests (winndixie.com), extracted verbatim.
   The live site ships these inside the CMS-authored HTML; the Contentstack entries hold
   only structured content, so they are re-attached here per page. */
/* Not part of the verbatim extract above — added locally. Live also inlines the ENTIRE Font
   Awesome 5 Free library as a giant <style> block (confirmed 2026-08-04, ~85KB across two <style>
   tags) so its .far.fa-file-pdf document icons use "Font Awesome 5 Free" — but the app's global
   bundles/css/all.css is Font Awesome 6, whose free tier dropped most "regular" style icons, so
   without this the icon fell back to a wider/different glyph (measured 16px vs live's 12px).
   Vendoring all 85KB here isn't practical; instead load just the one weight this page's icons
   need, from the exact same CDN URL live's own inline block points to. */
@font-face {
    font-family: "Font Awesome 5 Free";
    font-style: normal;
    font-weight: 400;
    font-display: block;
    src: url(https://ka-f.fontawesome.com/releases/v5.15.4/webfonts/free-fa-regular-400.woff2) format("woff2"),
         url(https://ka-f.fontawesome.com/releases/v5.15.4/webfonts/free-fa-regular-400.woff) format("woff"),
         url(https://ka-f.fontawesome.com/releases/v5.15.4/webfonts/free-fa-regular-400.ttf) format("truetype");
}
.pharmacy-resources-section .far {
    font-family: "Font Awesome 5 Free";
    font-weight: 400;
}
@media screen and (min-width: 1200px) {
.recipes-details .image-slider .image {
min-height: 850px !important;
}
}
.pharmacy-resources-section{
    margin-top: 20px;
    }
    /* Not part of the verbatim extract above — added locally. The copied
       bundles/sass/pharmacy.css (renamed from _pharmacy.min.css — same content, see
       sasscompiler.json) base .pharmacy-resources-section rule also carries
       margin-bottom:30px, but live's actual computed margin-bottom here is 0 (confirmed via
       full-tree geometry diff 2026-08-04 — .rgtContent's own box was 30px taller than its
       content on local only, with every child element position otherwise already pixel-exact). */
    .pharmacy-resources-section {
    margin-bottom: 0;
    }
    /* Not part of the verbatim extract above — added locally. Confirmed via computed-style
       measurement on live 2026-08-03 that .pharmacy-resources-section .pro-inner renders with
       padding:0 (card spans edge-to-edge inside the section), but the copied
       bundles/sass/pharmacy.css lacks the rule that does this (it only zeroes
       .pro-inner-info, and only for .pharmacy-search-section/.pharmacy-help-section's own
       .pro-inner, not this section's) — without it .pro-inner falls back to the global Bootstrap
       .container{padding:0 15px}, insetting the whole card and everything inside it by 15px. */
    .pharmacy-resources-section .pro-inner {
    padding: 0;
    }
    /* Added locally: the copied bundles/sass/pharmacy.css carries its own generic
       .container{max-width:970px} rule (a standard Bootstrap "md" tier) that this site's real
       .container (bundles/css/refresh.min.css) doesn't have — confirmed on /about, which never
       loads pharmacy.css, that the real rule is just .container{max-width:1170px} with no
       min-width gate at all (harmless below 1170px since a max-width doesn't constrain a
       narrower box; it only bites above 1170px), plus a separate 750px tier at >=768px that's
       unaffected here. Re-asserting max-width:1170px at >=992px (a higher-specificity two-class
       selector than the bundle's plain .container) restores that self-scaling behavior for this
       card without needing to guess exact upper-bound breakpoints. */
    @media (min-width: 992px) {
    .pharmacy-resources-section .pro-inner {
    width: auto !important;
    max-width: 1170px !important;
    }
    }
    /* Also added locally, same reason as above: live's actual computed h2/p here (measured
       2026-08-03) are the page's plain baseline heading/paragraph styles — the copied
       pharmacy.css's ".pro-inner-info h2{font-size:2.25em;margin:0 0 16px 0}" /
       ".pro-inner-info p{margin:8px 0 16px 0}" rules don't actually apply on live (or don't
       exist there in this form), so without this override the heading rendered 13px taller
       and the paragraph carried 24px of margin live doesn't have, pushing every element below
       it (table, document-link columns) down by 22px. */
    .pharmacy-resources-section .pro-inner .d-lg-flex .pro-inner-info h2 {
    font-size: 30px;
    margin: 20px 0 10px 0;
    line-height: 1.1;
    color: #333333;
    letter-spacing: normal;
    }
    .pharmacy-resources-section .pro-inner .d-lg-flex .pro-inner-info p {
    margin: 0;
    color: #333333;
    letter-spacing: normal;
    line-height: 22px;
    }
    .pro-inner-info.col-md-12.col-sm-12.col-xs-12 {
    box-shadow: 0 2px 14px 0 rgba(0,0,0,.25);
    padding: 24px;
    background: #fff;
    }
    .pharmacy-resources-section .pro-inner .d-lg-flex .resource-set .resource-list a {
    font-size: 1em;
    }
    ul.sub-list {
    padding-left: 0;
    }
    ul.sub-list li {
    margin-bottom: 24px;
    }
    ul.sub-list li > a {
    color: #c8102e;
    font-size: 0.9em;
    line-height: 1.5;
    }
    @media (max-width: 767px) and (min-width: 100px){
    .pharmacy-resources-section{
    margin-top: 30px;
    }
    }
/*.pro-inner-info.col-md-12.col-sm-12.col-xs-12.headercopy {
    margin-bottom: -60px;
    }*/
    .pharmacy-resources-section .pro-inner .d-lg-flex .pro-inner-info p {
    font-size: 1em !important;
    }
    /* Fixed from live's own broken "@media screen and max-width: (max-width: 767px)" (extra
       "max-width:" before the parenthesis — verified byte-for-byte present in live's served
       HTML). That invalid media-feature syntax makes the whole query never match on any
       browser, so live's .headercopy margin-bottom:auto rule below is permanently dead code.
       Corrected here to valid syntax by explicit request. Confirmed no actual fidelity impact:
       margin-bottom:auto on this block-level div computes to 0px regardless (no competing rule
       sets a different margin-bottom for it), so whether or not this media query ever matches,
       the rendered result is identical to live's — this just resolves the syntax warning, it
       doesn't change any pixel. */
    @media screen and (max-width: 767px) {
    .pro-inner-info.col-md-12.col-sm-12.col-xs-12.headercopy {
    margin-bottom: auto;
    }
    }
.pad{
padding:15px;
}
.pro-inner-info.headercopy a, .pro-inner-info.headercopy a:focus {
    display: initial;
}
.z-banner {
        z-index: 55555 !important;
    }

    .ps-fixed {
        position: fixed !important;
    }

    .bg-yellow-700 {
        background-color: #F8EC74;
        opacity: .92;
    }

    .fc-black {
        color: #000;
    }

    .wmx8 {
        max-width: 64.8205128rem;
    }

    .mx-auto {
        margin-left: auto;
        margin-right: auto;
    }

    .grid {
        display: flex;
    }

    .jc-center {
        justify-content: center;
    }

    .mr12 {
        margin-right: 10%;
        font-size : 1em;
    }

    #cookieBar a {
        cursor: pointer;
        text-decoration: underline;
    }
 #cookieBar p {
    margin-bottom : 0px;
  }
    .svgClose {
        float: right;
        margin-top: -21px;
        margin-right: 33px;
    }

    .paddingBar {
        padding: 20px;
        right: 0px;
        left: 0px;
        bottom: 0px;
    }


    .s-link {
        color: #000 !important;
    }

      @media screen and (min-width:100px) and (max-width:992px) {
        .paddingBar {
            right: -27px;
        }
    }
@media screen and (min-width:320px) and (max-width:568px) {
.svgClose {
    float: right;
    margin-top: -43px;
    margin-right: 20px;
}
.mx-auto {
    margin-left: -7px;
}
}
@media screen and (min-width:375px) and (max-width:667px) {
.mr12 {
    margin-right: 31px;
}
.svgClose {
    margin-top: -30px;
}
}
.async-hide {
			opacity: 0 !important;
		}