.hero { z-index: 1; } .hp-testimonials .glob-bg { background-position: center; } /* ============================================================================================= * CRRE Featured Properties — ported from the parent (Group C item 3a, 2026-08-01). * * WHY THIS EXISTS * The 3a rebuild renames the two Splide ROOT classes so the parent's properties() mounter * self-gates out (assets/js/scripts.js:209) without editing any parent file: * .hp-property-images -> .crre-fp-images * .fp-content-slides -> .crre-fp-content-slides * Renaming a root orphans every parent CSS rule that selects through it. Exactly FIVE rules in * the parent's compiled homepage.css did so — all of them via .hp-property-images. They are * re-homed here against the new root. * * /!\ .fp-content-slides needed NO port: no parent selector referenced it. The content track's * styling hangs off .fp-content / .fp-content-slide / .fp-pagination / .fp-prev / .fp-next, all * of which the rebuild kept unchanged, so those 15 rules still apply untouched. The ancestor * chain (.fp-qc-wrap > .hp-featured-properties) also survives — it is section/widget wrapper * markup outside the widget body, which the bridge does not replace. * * Cascade: this file is enqueued as `aios-mobile-first-homepage-child` at priority 999 and loads * AFTER both parent homepage sheets (`homepage-style`, `aios-starter-theme-home`), so identical * specificity resolves in the child's favour. Verified in the rendered , not assumed. * ============================================================================================= */ .fp-qc-wrap .hp-featured-properties .crre-fp-images { width: 55.3%; } .fp-qc-wrap .hp-featured-properties .crre-fp-images .fp-image a { display: block; position: relative; } /* /!\ CANVAS -> IMG CONVERSION. The parent held the image box open with an empty * whose intrinsic ratio reserved the space, then stacked the * real on top with position:absolute/inset-0. That is a pre-`aspect-ratio` hack, and it * cost an empty non-semantic element per slide plus an that auditors and crawlers saw as * decorative. * * The rebuild drops the canvas and gives the the ratio directly. The two parent rules this * replaces were: * ... .hp-property-images .fp-image a canvas { display:block; width:100% } * ... .hp-property-images .fp-image a img { position:absolute; top:0; left:0; * width:100%; height:100%; * object-fit:cover; object-position:center center } * Same painted box, same cover crop — but the alt text becomes real and the DOM loses 8 elements. * The intrinsic 685x606 also travels on the width/height attributes, so the space is * reserved before CSS applies (no layout shift). */ .fp-qc-wrap .hp-featured-properties .crre-fp-images .fp-image a img { display: block; width: 100%; height: auto; aspect-ratio: 685 / 606; object-fit: cover; object-position: center center; } @media only screen and (max-width: 991px) { .fp-qc-wrap .hp-featured-properties .crre-fp-images { width: 100%; } } /* ============================================================================================= * CRRE Hero video — replaces the AIOS-slider instance (Phase 2, 2026-08-02). * * WHY THIS EXISTS * Exactly TWO of the parent's thirteen #hero rules died with the slider instance, and they were * the two that gave the hero its height. Both hardcoded the instance ID *and* the plugin's * , so a bare