/* Inline <style> blocks from the live page /about/dmca-policy (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. */
@media screen and (min-width: 1200px) {
.recipes-details .image-slider .image {
min-height: 850px !important;
}
}
/* break out of the shared shell's .container-fluid__full 1170px cap (see
   _app-wd-legacy-content.scss's own doc comment — that cap is load-bearing for other
   consumers of this shell and must stay) so the whole entry — hero AND card — bleeds full
   viewport width like live (live's .Page_Desc/.dmca-policy is unconstrained; the card's own
   80px/32px/24px padding above already reproduces the visual margins live gets from its
   full-width layout). */
.dmca-policy {
    width: 100vw;
    position: relative;
    left: 50%;
    right: 50%;
    margin-left: -50vw;
    margin-right: -50vw;
    }
#herotitle {
    display: flex;
    background: var(--wd-color-surface-alt) !important;
    align-items: center;
    justify-content: space-between;
    }
    #herotitle h1 {
    text-align: initial;
    margin: 0px 0px 0px 80px;
    color:var(--wd-color-text);
    }
    @media (max-width:767px){
    #herotitle h1 {
    text-align: center;
    margin: 24px;
    }
    #herotitle {
    display: flex;
    background: var(--wd-color-surface-alt) !important;
    flex-direction: column-reverse;
    }
    .head_section{
    height:140px;
    }
    }
    .container-fluid {
    width: 100%;
    margin: 0;
    max-width: 100%;
    }
    @media (min-width: 768px){
    .container {
    width: 100%;
    }
    }
    .divTitle_Desc1 {
    padding: 0px;
    }
    .dmca-policy .card {
    width: 100%;
    padding: 42px 80px 24px 80px;
    margin-left: auto;
    margin-right: auto;
    text-align: justify;
    font-size: 16px;
    line-height: 18.34px;
    color:var(--wd-color-text);
    }
    @media  (max-width:767px){
    .dmca-policy .card {
    padding:24px !important;
    text-align: initial;
    }
    }
    @media (min-width:768px) and (max-width:1024px){
    .dmca-policy .card {
    padding:42px 32px  24px 32px !important ;
    }
    #herotitle h1 {
    margin:0px 0px 0px 32px;
    }
    #herotitle p {
    margin:16px 5px 0px 32px !important;
    }
    }
    .card.card-privacy-policy h3 {
    color: var(--wd-color-brand-red);
    font-size:1.375em
    }
    .card.card-privacy-policy a {
    text-decoration: none;
    color: var(--wd-color-brand-red) !important;
    }
    @media (min-width: 100px){
    .Page_Desc {
    margin: 0 ;
    }
    }
    .dmca-policy ol{
    list-style: auto;
    list-style-type: decimal;
    margin-left: 18px;
    }
    .dmca-policy li{
    list-style: auto;
    list-style-type: decimal;
    }
    /* NOT reattached from live here (unlike every other rule in this file): live's own
       ".push{height:auto}" is almost certainly WHY live itself shows no social-icons/app-badge
       row in its footer on this one route (see the ".footer__social{display:none}" rule below
       for the full story) — this app's shared MainLayout relies on the global
       ".push{height:210px}" (bundles/css/app-wd-global.css) to offset ".Contain_Main"'s own
       "margin:0 auto -210px" negative-bottom-margin sticky-footer trick
       (_app-wd-legacy-content.scss:92-103); overriding it to auto/0 pulls SiteFooter up into the
       still-floated ".rgtContent"/.mainContentAlign region, and the footer's own
       ".footer__social{overflow:hidden}" (a BFC) then shrinks to avoid that overlapping float
       instead of laying out at full width. Reattaching this override verbatim DOES reproduce a
       squeeze locally (confirmed: 135px), but not live's exact 0px — the underlying float
       arithmetic depends on exact DOM/CSS geometry that differs enough between this app's shell
       and live's own markup that the accidental collapse doesn't land at the same pixel. Left
       OUT here (rather than reattached) so it can't cause a smaller, still-visible version of
       the same bug elsewhere on this shell; the explicit ".footer__social{display:none}" rule
       below is what actually reproduces live's visible (or rather invisible) result reliably. */
    #herotitle p {
    margin: 16px 5px 0 80px;
    font-size: 18px;
    text-align: initial;
    color:var(--wd-color-text);
    font-family: var(--wd-font-body);
    }
    .dmca-policy #herotitle img {
    margin-left: auto;
    }
    @media (min-width:1025px){
    .dmca-policy .card{
    font-size:18px;
    color:var(--wd-color-text);
    font-family: var(--wd-font-body);
    line-height:20.63px !important;
    }
    .dmca-policy .card p {
    font-size:18px;
    color:var(--wd-color-text);
    }
    }
    @media (max-width:767px){
    #herotitle p {
    margin: 10px 0;
    font-size: 16px;
    text-align: center;
    }
    }
    a.ConInfoLnk:hover {
    text-decoration: underline;
    }
    a.ConInfoLnk {
    text-decoration: none !important;
    color: var(--wd-color-brand-red) !important;
    }
    a.ConInfoLnk:hover,a.ConInfoLnk:focus {
    text-decoration: underline !important;
    }
    .alphasub li {
    list-style: lower-alpha;
    }
    .alphasub {
    margin-left: 25px !important;
    }
    .dmca-policy p {
    color: var(--wd-color-text);
    }
.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;
		}

/* Matches live: on /about/dmca-policy specifically (confirmed via a fresh live fetch — every
   other route, including the sibling /about/coupon-policy, renders this row normally at full
   width), live's own footer never shows the social-icons/"Download the Winn-Dixie Mobile App"/
   back-to-top row at all — getBoundingClientRect on live returns a genuine 0×0 box for
   ".footer__social" there (screenshot-confirmed: the red footer starts directly at the
   Winn-Dixie/About/Customer service/Legal/Corporate nav columns, no row above them). Live's own
   ".push{height:auto}" override (see that rule's own doc comment above) is almost certainly the
   cause on live's side, but reattaching it here only reproduces a smaller, still-visible squeeze
   (135px, not live's 0px) rather than a true match, so it's deliberately left out; this explicit
   rule reproduces live's actual visible (i.e. invisible) result directly and reliably instead of
   depending on that fragile, geometry-sensitive float collapse. */
.footer__social {
    display: none;
    }