/* BTA33KAR — bta-mobile-actions-1.0.css (UI-P2D-B1, 2026-09-17)
   Immutable path. Once served, these bytes are never rewritten: a correction
   ships as bta-mobile-actions-1.1.css and the registration moves to it.

   SCOPE. Mobile listing surfaces only. The listing marker is the container id
   the two listing shortcodes emit — verified live: #properties-list appears on
   /properties, /ar/properties and /properties/city/*; #projects-list on
   /projects, /ar/projects and /projects/city/*; NEITHER appears on the homepage
   (EN or AR), on a property detail page, or on an agent page. .action_footer is
   a direct child of <body> on every page, so the scope has to come from the
   body, not from a listing ancestor. @supports selector(:has(*)) guards it:
   where :has() is unsupported the current presentation is kept unchanged.
   Everything is inside max-width:767.98px, so desktop is untouched — confirmed
   at 768 and 1440, where the targets stay at their existing 154.3x35.5 / 34x34.

   TARGETS. Measured before: phone link 154.3x35.5, back-to-top 34x34.
   min-block-size + inline-flex centring take both to the 44px contract without
   touching the number: text "01101848466" and href "tel:01101848466" are
   unchanged, rendered on ONE visual line (the two client rects the range API
   reports in RTL share the same top — bidi runs, not a wrap) and not clipped
   (scrollWidth == clientWidth).

   ATTRIBUTION. The Leaflet attribution and the fixed CTA can only be made
   non-overlapping by horizontal separation: the CTA is viewport-fixed while the
   attribution rides the map's bottom edge, so for any vertical arrangement some
   scroll offset aligns them. Corner audit: the map's bottom-right holds ONLY
   the attribution; bottom-left and top-right are empty; zoom is top-left. So in
   RTL — where the CTA is physically right, the same corner — the attribution
   container moves to the physically-left corner, colliding with nothing.
   padding-inline:6px narrows the CTA box (not its text) by 12.2px, which is what
   turns a 4.7px overlap into clearance. Measured clearance, both directions:
   7.5px at 375, 32.5px at 400, 90.5px at 458.
   Before: AR 375 overlapped 2,414px2 (72.6% of the control) at scrollY 57, with
   the OpenStreetMap link 100% covered and 5 of 10 hit points blocked; EN 375
   overlapped 78px2. After: 0px2 and 0 blocked points in every measured cell.
   ========================================================================== */
@supports selector(:has(*)) {
    @media (max-width: 767.98px) {
        body:has(#properties-list) .action_footer a[href^="tel:"],
        body:has(#projects-list) .action_footer a[href^="tel:"] {
            min-block-size: 44px;
            display: inline-flex;
            align-items: center;
            justify-content: center;
            padding-inline: 6px;
            white-space: nowrap;
        }

        body:has(#properties-list) .action_footer .cd-top,
        body:has(#projects-list) .action_footer .cd-top {
            min-inline-size: 44px;
            min-block-size: 44px;
            display: inline-flex;
            align-items: center;
            justify-content: center;
            padding: 0;
        }

        /* RTL property listings only: the CTA sits in the same physical corner
           as the attribution. body[dir="rtl"] is the page's own attribute, not
           an injected one. */
        body[dir="rtl"]:has(#properties-list) #properties-list .leaflet-bottom.leaflet-right {
            right: auto;
            left: 0;
        }
    }
}
