/*
 Theme Name:     Christendom Divi 5
 Theme URI:      https://www.elegantthemes.com/gallery/divi/
 Description:    Christendom College's Divi child theme, updated for Divi 5 compatibility.
 Author:         Elegant Themes
 Author URI:     https://www.elegantthemes.com
 Template:       Divi
 Version:        1.1.0
*/

/*
 Divi 5 compatibility review, August 2026:
 No selectors below were changed. Elegant Themes documents that Divi 5's
 backward-compatibility system keeps emitting the same markup/classes for
 legacy-rendered content (et_pb_*, et_no_sidebar, et_mobile_menu, etc.), so
 these rules are expected to keep matching as-is. The one block flagged
 below (custom mobile menu) targets Divi's mobile-nav markup specifically
 and is worth a visual re-check on staging after the update, since that's
 the part of Divi most likely to change appearance/structure between
 versions. Nothing here needs to change ahead of time -- verify on
 staging, only touch this file if something visibly breaks.
*/


/* =Theme customization starts here
------------------------------------------------------- */

/* Divi Booster icon-escaping fix, August 2026 (staging bug report):
   The Social Media Follow module's X/Twitter icon is mapped to a Font
   Awesome glyph by the Divi Booster plugin's dynamically-generated
   stylesheet (dbdb-social-media-follow-css). That generated rule is
   missing the backslash on its Unicode escape:
     .et-social-twitter a.icon::before { content: "e61b"; ... }
   so the browser prints the literal characters "e61b" instead of the X
   icon glyph. The four other network icons (Instagram, YouTube, Facebook,
   Flickr) use Divi's own ETmodules font with a real embedded glyph
   character, not a hex-string escape, so they're unaffected. This isn't
   caused by the child theme or by Divi 5 -- Divi Booster generates this
   rule -- but it's overridden here with the correctly escaped value so
   the icon renders correctly regardless of whether/when Divi Booster
   patches it upstream. Safe to remove once fixed at the source. */
.et-social-twitter a.icon::before {
    content: "\e61b" !important;
    font-family: "Font Awesome 6 Brands" !important;
}



@media (min-width: 981px), all {
.et_no_sidebar #left-area {
        float: right;
padding-left: 5.5%;
        
    }

}

/*SNOW*/
/* Pure-CSS background-image snow effect, applied via the "divi-life-snow"
   CSS class on any Divi module/row/section. Independent of Divi's render
   pipeline (no PHP/shortcode filter involved), so this is not expected to
   be affected by the Divi 5 upgrade. Separate from the JS-driven
   "falling-snow" effect handled in functions.php. */
.divi-life-snow {
   position: relative;
}
.divi-life-snow:after {
   content: '';
   display: block;
   position: absolute;
   z-index: 6;
   top: 0;
   left: 0;
   right: 0;
   bottom: 0;
   pointer-events: none;
   background-image: url('https://www.christendom.edu/divi-life-snowflakes-b.png'), url('https://www.christendom.edu/snow/divi-life-snowflakes-c.png'), url('https://www.christendom.edu/snow/divi-life-snowflakes-a-1.png');
    animation: divi-life-snow 10s linear infinite;
}
@keyframes divi-life-snow {
 0% {background-position: 0px 0px, 0px 0px, 0px 0px;}
 50% {background-position: 500px 500px, 100px 200px, -100px 150px;}
 100% {background-position: 500px 1000px, 200px 400px, -100px 300px;}
}
@-moz-keyframes divi-life-snow {
 0% {background-position: 0px 0px, 0px 0px, 0px 0px;}
 50% {background-position: 500px 500px, 100px 200px, -100px 150px;}
 100% {background-position: 500px 1000px, 200px 400px, -100px 300px;}
}
@-webkit-keyframes divi-life-snow {
 0% {background-position: 0px 0px, 0px 0px, 0px 0px;}
 50% {background-position: 500px 500px, 100px 200px, -100px 150px;}
 100% {background-position: 500px 1000px, 200px 400px, -100px 300px;}
}



/*custom mobile menu*/
/* FLAG FOR STAGING VERIFICATION: targets Divi's mobile-nav markup
   (.mobile_menu_bar, .et_mobile_menu, .mobile_nav) directly. Re-check the
   mobile menu on staging after the Divi 5 update -- if it looks off,
   inspect the live markup in a browser and adjust the selectors here to
   match, since we can't confirm class names are unchanged without a
   running Divi 5 site to inspect. */
.custom-mobile-menu .mobile_menu_bar {
    left: -45px !important;
    top: 9px;
}
.custom-mobile-menu .et_mobile_menu {
  top: 52px !important;}

.custom-mobile-menu .mobile_nav.opened .mobile_menu_bar:before {
    content: '\4d';
  font-family: ETmodules!important;
}

@media only screen and (max-width: 980px)
{
body #custom-sidebar {
    display:none !important;
}

}

/*end*/