/*
Organico Child — RTL overrides
==============================
Loaded ONLY on RTL locales (Arabic) by organico_child_enqueue_styles(), AFTER the
parent rtl.css and the child style.css (see functions.php), so these win on ties.
The parent rtl.css already mirror-flips the THEME's layout; this file flips ONLY
the directional rules the CHILD theme adds in style.css. Centered / symmetric /
flex-direction-aware rules in style.css are already RTL-safe and are not repeated.
Each block notes the style.css region it mirrors. `!important` is used so the flip
wins regardless of the original rule's specificity / !important.
*/

/* style.css ~L13-22 — Quick View popup close button: inset top-RIGHT → top-LEFT. */
div.pp_default .pp_close,
body div.pp_woocommerce.pp_pic_holder .pp_close,
body div.ftc-product-video.pp_pic_holder .pp_close,
body .ftc-lightbox.pp_pic_holder a.pp_close,
body div.ftc-size_chart .pp_close {
	right: auto !important;
	left: 12px !important;
}

/* style.css ~L375-379 — Labelled address (My Account → Addresses): the gap after
   the field label moves to the other side of the label in RTL. */
.lm-labelled-address .lm-address-label {
	margin-right: 0 !important;
	margin-left: 6px !important;
}

/* Product attributes: the standalone Additional Information tab was removed;
   its data is now a <details> disclosure in the Description tab (functions.php
   + style.css), built with logical properties, so it is RTL-correct with no
   mirror needed here. */

/* Shipping & Delivery tab (custom tab): the builder stamps the section
   headings text-align:left, so on Arabic they stranded ~340px left of their
   right-aligned body text. Right-align them to sit above their paragraphs. */
#tab-ftc_custom .ftc-heading,
#tab-ftc_custom .ftc-heading .heading-title,
#tab-ftc_custom h1,
#tab-ftc_custom h2,
#tab-ftc_custom h3,
#tab-ftc_custom h4 {
	text-align: right !important;
}

/* (2026-07-05) The single-product buy row now uses flex `gap` (child style.css),
   which is direction-agnostic — the old RTL margin-flip for Buy Now was removed;
   re-adding a margin here would DOUBLE the spacing. */

/* style.css ~L1122-1198 (mobile ≤991px) — Shop toolbar + filter drawer. */
@media (max-width: 991px) {
	/* Row alignment (the row is flex; this also covers inline content). */
	body .before-loop-wrapper {
		text-align: right !important;
	}
	/* Auto-margin pins the relocated "Filter" button to one end; flip the side
	   that gets `auto` so Filter sits on the RIGHT (Sort on the left) in RTL. */
	.before-loop-wrapper .button-sidebar.lm-relocated {
		margin: 0 0 0 auto !important;
	}
	/* Filter-drawer close (×): top-RIGHT → top-LEFT. */
	aside.ftc-sidebar .lm-drawer-close {
		right: auto !important;
		left: 16px !important;
	}
	/* Widget collapse arrow (parent responsive.css ~L1792 pins it right:0):
	   the widget title is right-aligned in RTL (rule below), so the arrow
	   moves to the LEFT edge of the title row. */
	.widget-title-wrapper a.block-control {
		right: auto !important;
		left: 0 !important;
	}
}

/* ═══════════════════════════════════════════════════════════════════════════
   Shop sidebar widgets. Parent style.css ~L7159-7176 hardcodes text-align:left
   on `.widget-title` and `.widget-container ul > li a` (the "التصنيف" heading,
   category links, YITH origin-filter links, price title), and the parent
   rtl.css never flips them — so the Arabic shop sidebar read left-aligned.
   Scoped to the archive sidebar so footer/header widget styling is untouched.
   ═══════════════════════════════════════════════════════════════════════════ */
aside.ftc-sidebar .widget-title,
aside.ftc-sidebar .widget-container ul > li,
aside.ftc-sidebar .widget-container ul > li a {
	text-align: right !important;
}

/* ═══════════════════════════════════════════════════════════════════════════
   Shop toolbar — RTL internals only (2026-07-18). The toolbar is now a FLEX
   row in child style.css (count static at the inline start, Sort pinned to
   the inline end with margin-inline-start:auto) — direction-proof, so the old
   desktop mirrors that lived here (count left:30%/45% !important, ordering
   float/margin !important) are GONE: the count ones went inert the moment the
   count stopped being absolute, and the ordering margin !important would have
   FOUGHT the flex end-pinning on Arabic desktop. Only the control's INTERNAL
   mirrors remain (label/dropdown float order inside the Sort control).
   ═══════════════════════════════════════════════════════════════════════════ */
@media (min-width: 992px) {
	.woocommerce .woocommerce-ordering .orderby,
	.woocommerce-page .woocommerce-ordering .orderby,
	.woocommerce .woocommerce-ordering .orderby-title,
	.woocommerce-page .woocommerce-ordering .orderby-title {
		float: right !important;
	}
	/* The 19px label↔dropdown gap moves to the label's other side. */
	.woocommerce-page .woocommerce-ordering .orderby-title {
		margin: 6px 0 6px 19px !important;
	}
}

/* ═══════════════════════════════════════════════════════════════════════════
   Shop sort control + origin-filter checkboxes (user report 2026-07-05).
   ▸ Sort: parent style.css ~L7012/7063 pins the ▾ arrow at right:15px and gives
     .orderby-current a 20px RIGHT padding as its inset — but in RTL the Arabic
     value starts from that same right edge, so "الترتيب الافتراضي" printed OVER
     the arrow. Mirror both: arrow to the LEFT edge, and the 20px arrow inset
     moves to the left padding. Unscoped by width — the mobile toolbar reuses
     the exact same control and had the same overlap.
   ▸ Checkboxes: the ☐ is the filter link's :before glyph with margin-right:7px
     (parent ~L24659). In RTL the glyph renders at the reading start — to the
     RIGHT of the label — so that margin lands on its OUTER (far-right) edge and
     the label touched the box. Move the 7px gap to the glyph's LEFT, between
     box and label; zeroing the right margin also re-flushes the row with the
     other right-aligned sidebar items. The checked state (li.chosen, parent
     ~L21988) only swaps the glyph, so this covers it too.
   ═══════════════════════════════════════════════════════════════════════════ */
.woocommerce .woocommerce-ordering .orderby > li:after,
.woocommerce-page .woocommerce-ordering .orderby > li:after {
	right: auto !important;
	left: 15px !important;
}
.woocommerce .woocommerce-ordering .orderby > li .orderby-current,
.woocommerce-page .woocommerce-ordering .orderby > li .orderby-current {
	padding: 4px 15px 4px 20px !important;
}
/* Phones/tablets: same pill-height fix as the EN side (child style.css) — 6px
   vertical padding puts the sort pill at the Filter button's ~38px height.
   Re-declared here because the RTL padding mirror above resets all four sides
   with !important, which cancelled the style.css rule on Arabic views. */
@media (max-width: 991px) {
	.woocommerce .woocommerce-ordering .orderby > li .orderby-current,
	.woocommerce-page .woocommerce-ordering .orderby > li .orderby-current {
		padding-top: 6px !important;
		padding-bottom: 6px !important;
	}
}
.woocommerce .yith-woocommerce-ajax-product-filter.widget_layered_nav ul.yith-wcan-list li a:before {
	margin-right: 0 !important;
	margin-left: 7px !important;
}

/* Contact page hero (owner design 2026-07-06): Arabic uses a MIRRORED copy of
   the photo — the calm white area lands on the RIGHT — and the text moves to
   the right half over it (style.css puts English in the left half). The
   mirrored file ships with the child theme (images/back3-flipped.jpg), so it
   deploys with the code. !important: the builder prints its background-image
   with !important. Desktop only — phones stack the photo above the text. */
@media (min-width: 768px) {
	/* doubled class: the builder's background-image is !important and prints
	   after this sheet — higher specificity wins the tie */
	.title-contact4.title-contact4 {
		background-image: url('images/back3-flipped.jpg') !important;
	}
	/* The client's header photo (app repo docs/plans/133): the same photo on the LEFT, not
	   mirrored (the bag carries the logo). Only rows marked lm-contact-app-order by the
	   plan-133 migration; others keep the mirrored photo above. */
	.title-contact4.title-contact4.lm-contact-app-order {
		background-image: url('images/contact-header-app-order-rtl.webp') !important;
	}
	.title-contact4 .wpb_text_column {
		margin-left: auto;
		margin-right: 0;
	}
}

/* Contact form (user report 2026-07-06): Contact Form 7 prints its wrapper
   with dir="ltr" — the form entity was authored under the ENGLISH locale — so
   on Arabic pages the labels' colon/asterisk scrambled and the inputs and
   their placeholders anchored LEFT. CSS `direction` beats the dir attribute.
   Scoped to every CF7 form (this file loads on Arabic views only). */
.wpcf7,
.wpcf7 form {
	direction: rtl;
}
.wpcf7 input[type="text"],
.wpcf7 input[type="email"],
.wpcf7 input[type="tel"],
.wpcf7 input[type="url"],
.wpcf7 textarea,
.wpcf7 select {
	direction: rtl;
	text-align: right;
}

/* Price widget label (user report 2026-07-05): WooCommerce pins `.price_label`
   to LTR, so on Arabic the row scrambled — the colon jumped to the label's
   left (":السعر") and the amounts read backwards. Restore the natural RTL flow:
   "السعر: Ɖ0 — Ɖ130" (digits stay LTR runs inside, as bidi intends) — and make
   the label a full-width right-anchored block so the text STARTS at the card's
   right edge with no dead space before it (the row itself is text-align:left). */
.woocommerce .widget_price_filter .price_label,
.woocommerce-page .widget_price_filter .price_label {
	direction: rtl !important;
	unicode-bidi: isolate;
	display: block !important;
	width: 100%;
	text-align: right !important;
}

/* Category widget (التصنيف) — history: a 2026-07-05 fix compensated the last
   row's indent, later zeroed for the flat panel. As of the 2026-07-18 pill
   rows (style.css, ID-weighted li rule) every row carries its own padding and
   out-ranks the theme's last-child indent in both directions — no RTL
   compensation needed anymore, so this block is intentionally gone. */

/* style.css ~L1290-1306 (mobile ≤767px) — Single-product variation label aligns
   to the right edge in RTL. */
@media (max-width: 767px) {
	body.single-product .variations .Variable-box,
	body.single-product .variations .label {
		text-align: right !important;
	}
}

/* ═══════════════════════════════════════════════════════════════════════════
   Single product (mobile ≤991) — docs/32 M-034.
   ═══════════════════════════════════════════════════════════════════════════ */
@media (max-width: 991px) {
	/* M-034 — the gallery zoom "+" badge stays in the image's bottom-LEFT
	   corner (parent style.css:26938 pins left:15px); mirror to bottom-right.
	   The hover width-expansion (parent :hover width:120px) then grows leftward
	   from the right edge on its own. */
	.single-product .details-img .ftc_lightbox {
		left: auto !important;
		right: 15px !important;
		text-align: right !important;
	}
}

/* M-032 (retired 2026-07-06) — the Buy-Now icon↔label gap is now a
   direction-agnostic flex column-gap on the buttons themselves (child
   style.css, stacked buy box), with the glyph's physical margins zeroed —
   no RTL flip needed anymore. */

/* ═══════════════════════════════════════════════════════════════════════════
   Shop / product-archive two-column layout. The Bootstrap grid (parent
   default.css ~L1843) floats every .col-sm-* LEFT, and float direction does not
   follow dir="rtl" — so on the Arabic shop the filter sidebar (#left-sidebar,
   first in the DOM) stayed on the LEFT. Float both archive columns RIGHT so the
   sidebar sits on the RIGHT and the product grid on the left — the mirror of the
   English layout. Desktop/tablet only: below 768px the columns stack full-width
   and the sidebar becomes the filter drawer (handled above), nothing to flip.
   (rtl.css loads on Arabic views only, so the English shop is unaffected.)
   ═══════════════════════════════════════════════════════════════════════════ */
@media (min-width: 768px) {
	aside#left-sidebar.ftc-sidebar,
	aside#left-sidebar.ftc-sidebar + #main-content {
		float: right !important;
	}
}

/* Header language switcher — desktop spacing is owned by the icon row's flex
   `gap` (style.css .lm-header-right), which is direction-agnostic, so the old
   RTL margin flip is gone. Only the ≤991px fallback below remains. */
@media (max-width: 991px) {
	/* M-002 — on the MOBILE header the dropdown row is hidden and the switcher's
	   only neighbour is the cart basket on its RIGHT (RTL flow puts the cart at
	   the row's right edge, probe: switcher.right == cartIcon.left == 57px, zero
	   gap → "English" touched the basket). The 10px gap therefore belongs on the
	   switcher's RIGHT side on phones/tablets, not the left as on desktop. */
	.lm-lang-switcher--inline { margin: 0 10px 0 0 !important; }
}

/* ═══════════════════════════════════════════════════════════════════════════
   Phase 2 (docs/31) — mobile appbar: slide-out menu drawer. The parent theme
   builds the drawer for LTR only (docs/32 M-002 family + user report):
   ▸ parent style.css:11633 pins .ftc-mobile-wrapper to the LEFT edge and hides
     it with translate3d(-300px) — on Arabic it must slide in from the RIGHT;
   ▸ parent rtl.css:3153 forces the القائمة title bar back to direction:ltr and
     parent style.css:11711 floats its close (×) button right;
   ▸ the Mega Main Menu inside renders with .language_direction-ltr (plugin
     setting), so item labels hug the LEFT edge;
   ▸ the drawer search field keeps LTR text/button sides (style.css:11779 pins
     the magnifier right:15px);
   ▸ parent rtl.css:3155 sets .header-mobile-social{text-align:left}.
   All rules unprefixed + !important: the forced-AR WC pages have no `rtl` body
   class (is_rtl() false there), and !important beats the parent's .rtl-prefixed
   rules on the natural /ar/ pages. This file never loads on EN views.
   Drawer exists only below 992px (parent hides it above).
   ═══════════════════════════════════════════════════════════════════════════ */
@media (max-width: 991px) {
	/* M-001 (user report 2026-07-03: white band beside the appbar + green
	   sliver + horizontal scroll at 390). WPBakery's row-stretch JS writes a
	   FIXED pixel width (= window width) onto every [data-vc-full-width] row.
	   Harmless in LTR (rows anchor left), but on the RTL home any transient
	   canvas widening during load (slider init) latches into a stable wrong
	   fixpoint: a 390px row right-aligns inside the widened 397px canvas at
	   [7,397], which itself holds scrollWidth at 397 — page scrolls sideways,
	   the 390px-wide header leaves a white band, and the drawer edge peeks
	   into the exposed strip. Real mobile Chrome masks it by zooming out ~2%;
	   DevTools at 100% shows it raw. Clamping the page wrapper kills the bad
	   fixpoint: the canvas can never widen, so WPBakery's first-pass math
	   stays valid and RTL right-alignment lands every stretched row exactly
	   on [0, viewport]. (#page wraps header/content/footer; the drawer is
	   fixed OUTSIDE it and never contributes to scrollWidth.) */
	#page.site {
		/* `clip`, not `hidden` (2026-07-18): hidden pairs to `hidden auto`,
		   making #page a SCROLL CONTAINER — that silently killed every
		   position:sticky inside it on the Arabic site (shop toolbar, sidebar).
		   clip clamps the canvas exactly the same for M-001's purposes but
		   creates no scroll container, so sticky positioning survives. */
		overflow-x: clip;
	}
	/* Parent rtl.css (≤1024px) sets `body.rtl { overflow-x: hidden }` for the
	   same horizontal-bleed reason — same sticky-killing side effect, same
	   swap. This sheet loads after the parent's, so the later value wins. */
	body.rtl {
		overflow-x: clip;
	}
	/* M-001 (cont.) — even with the canvas clamped, WPBakery's RTL pass leaves
	   its stretched rows 7px off-left ([-7,383]): it bakes `left:<px>` values
	   computed against the transiently-widened canvas. Deterministic box fix
	   that ignores the JS pixel math entirely: full-viewport width plus a
	   self-adapting pull of `calc(50% - 50vw)` (resolves to −15px inside the
	   padded .container, 0 inside full-bleed wrappers — any centered parent).
	   In RTL the over-constrained margin resolves from the RIGHT margin, so
	   the pull goes on margin-right; inline `left` is zeroed (stale relative
	   shift). Content paddings are left to WPBakery — only the box moves. */
	.vc_row[data-vc-full-width] {
		left: 0 !important;
		width: 100vw !important;
		max-width: 100vw !important;
		margin-right: calc(50% - 50vw) !important;
	}
	/* Header hamburger + basket cell (user report 2026-07-03: "hamburger
	   alignment wrong on cart/checkout"). Parent rtl.css:3180 aligns the ☰
	   glyph to the RIGHT edge of its header cell and :3162 lets the tiny-cart
	   shrink to its content — but both are `.rtl`-prefixed, so they are inert
	   on the cookie-forced cart/checkout/my-account views (no `rtl` body
	   class): the ☰ hugged the LEFT edge of its ~72px cell, ~56px adrift of
	   the right padding edge. Unprefixed twins so every AR view matches the
	   natural /ar/ pages (idempotent there — same values). */
	.mobile-button {
		text-align: right !important;
	}
	.ftc-shop-cart {
		width: auto !important;
	}
	/* Drawer docks to and slides from the RIGHT edge. */
	.ftc-mobile-wrapper {
		left: auto !important;
		right: 0 !important;
		-webkit-transform: translate3d(300px, 0, 0) !important;
		transform: translate3d(300px, 0, 0) !important;
	}
	body.has-mobile-menu .ftc-mobile-wrapper {
		-webkit-transform: none !important;
		transform: none !important;
	}
	/* القائمة title bar reads RTL: ☰ + label start from the right, × moves to
	   the LEFT end (its float:right + the bar's forced direction:ltr undone). */
	.ftc-mobile-wrapper .menu-text {
		direction: rtl !important;
		text-align: right !important;
	}
	.ftc-mobile-wrapper .menu-text .btn-toggle-canvas.btn-danger {
		float: left !important;
	}
	/* The 3px icon↔label gap follows the ☰ icon to the label's right side. */
	.ftc-mobile-wrapper .menu-text > i {
		padding-right: 0 !important;
		padding-left: 3px !important;
	}
	/* Menu items right-aligned (Mega Main Menu renders language_direction-ltr). */
	.ftc-mobile-wrapper .mega_main_menu_ul {
		direction: rtl !important;
	}
	.ftc-mobile-wrapper .mega_main_menu .item_link,
	.ftc-mobile-wrapper .mega_main_menu .item_link .link_content,
	.ftc-mobile-wrapper .mega_main_menu .item_link .link_content .link_text {
		text-align: right !important;
	}
	/* Drawer search: Arabic text/placeholder start at the right, magnifier
	   button mirrors to the left end of the field. */
	.ftc-mobile-wrapper .ftc_search_ajax input[type="text"] {
		direction: rtl !important;
		text-align: right !important;
	}
	.ftc-mobile-wrapper .ftc_search_ajax .search-button {
		right: auto !important;
		left: 15px !important;
	}
	/* Account/Login/Logout rows + social row align to the right edge. */
	.ftc-mobile-wrapper .footer-menu {
		text-align: right !important;
	}
	.ftc-mobile-wrapper .header-mobile-social {
		text-align: right !important;
	}
	/* Modern drawer skin (child style.css) — RTL side flips. */
	.lm-drawer-modern .ftc-mobile-wrapper .ftc_search_ajax input[type="text"] {
		padding: 0 18px 0 46px !important; /* magnifier sits at the field's LEFT in RTL */
	}
	/* Owner 2026-08-16: ✕ at the top-LEFT on Arabic (English keeps top-right —
	   style.css floats it right; this overrides both that and the base
	   float:left rule above for the modern drawer). */
	.lm-drawer-modern .ftc-mobile-wrapper .menu-text .btn-toggle-canvas.btn-danger {
		float: left !important;
	}
}

/* ═══════════════════════════════════════════════════════════════════════════
   RevSlider hero (home10-ar / home50-ar) — NOT RTL-aware. The sliders have
   rtl=false and position their layers + compute the (fullscreen) height with
   LTR math. On the Arabic page (`dir:rtl`) the slider inherits rtl, which breaks
   the hero's height/layout. Force the slider containers + their layout layers
   back to LTR so the hero renders at its designed size; the translated Arabic
   layer text still displays. (True visual mirroring of the hero is a Slider
   Revolution editor task — its per-slider "RTL" toggle.)
   ═══════════════════════════════════════════════════════════════════════════ */
.rev_slider_wrapper, .rev_slider, .tp-simpleresponsive, .tp-revslider-mainul,
.forcefullwidth_wrapper_tp_banner, .tp-fullwidth-forcer,
rs-module-wrap, rs-module, rs-slides, rs-slide, rs-layer {
	direction: ltr !important;
}

/* ═══════════════════════════════════════════════════════════════════════════
   Home "Our Story" section (row el_class "Our story"). The client copy was
   dropped into the EN template, which hardcodes inline text-align:left on the
   heading/subtitle/description, and the Shop-now button inherits left — so on the
   Arabic page the block reads left-aligned. Right-align the text + button for RTL.
   (rtl.css is Arabic-only, so the English home is unaffected.)
   ═══════════════════════════════════════════════════════════════════════════ */
.Our.story h2,
.Our.story h3,
.Our.story p,
.Our.story .wpb_wrapper,
.Our.story .wpb_text_column,
.Our.story .vc_column-inner {
	text-align: right !important;
}

/* ═══════════════════════════════════════════════════════════════════════════
   Footer (mobile ≤991) — docs/32 M-013 / M-056 (user request 2026-07-03:
   "fix the RTL alignment in footer for mobile"). Unprefixed + !important so
   the rules hold on the forced-AR WC pages too (no `rtl` body class there).
   ═══════════════════════════════════════════════════════════════════════════ */
@media (max-width: 991px) {
	/* M-013 — the معلومات / حسابي widget headings rendered CENTERED over their
	   right-aligned link lists. The heading box is shrink-wrapped
	   (parent style.css:6522 display:inline-block; at ≤480 the Customizer CSS
	   turns it into a flex container) and parent responsive.css:6635 centers
	   it inside the column. Make the box full-width and align its content to
	   the right; justify-content covers the ≤480 flex variant (RTL main-start
	   = right). EN keeps its own look — this file never loads there. */
	footer#colophon .ftc-footer .widget-title {
		display: block !important;
		width: 100% !important;
		text-align: right !important;
		justify-content: flex-start !important;
	}
	/* M-056 — contact-block icons (pin / mobile / phone / envelope) sat flush
	   against the first character (measured 2px). The gap the EN layout gets
	   from the icon's margin-right belongs on the icon's LEFT in RTL (icon
	   sits to the right of its text). */
	footer#colophon .info-company li i {
		margin-right: 0 !important;
		margin-left: 14px !important;
	}
}

/* Cart page since the 2026-07-06 redesign: the two-card layout in child
   style.css uses grid + logical properties (start/end), which mirror on their
   own under the `rtl` body class — the old M-043/M-046 stacked-table patches
   went with the old layout. Only exception below: the summary-card coupon
   input renders LTR (theme input default), so its Arabic placeholder hugged
   the wrong side. */
body.rtl .lm-coupon input.input-text {
	direction: rtl;
	text-align: right;
}

/* Checkout billing fields type RTL on Arabic views — the theme leaves the
   inputs LTR, so Arabic text and placeholders ("رقم المنزل واسم الشارع…")
   started at the left edge (owner 2026-07-06). Email and phone keep LTR
   content (latin/digits) but align right to sit with the rest. */
body.rtl form.woocommerce-checkout input.input-text,
body.rtl form.woocommerce-checkout textarea {
	direction: rtl;
	text-align: right;
}
body.rtl form.woocommerce-checkout #billing_email,
body.rtl form.woocommerce-checkout #billing_phone {
	direction: ltr;
	text-align: right;
}

/* Checkout checkbox rows ("Ship to a different address?", "Create an
   account?"): the theme hangs the box outside the label text with a
   physical margin-left:-20px — on Arabic that pulled it INTO the first
   characters (owner 2026-07-06). Mirroring the hang (-20px right) poked the
   box past the card border on phones (the label sits flush to the card
   padding there), so on Arabic the box just sits INLINE before the text
   with a small gap — inside the card at every width. */
body.rtl form.woocommerce-checkout .woocommerce-form__label-for-checkbox input[type="checkbox"] {
	margin-left: 8px !important;
	margin-right: 0 !important;
}

/* ═══════════════════════════════════════════════════════════════════════════
   My Account (forced-Arabic WC page). The parent floats BOTH columns left
   (physical), so the Arabic layout kept the navigation tabs on the LEFT
   (QA 2026-07-06) — float them right instead: the nav (first in DOM) takes
   the reading side, the content lands to its left. Widths untouched.
   ═══════════════════════════════════════════════════════════════════════════ */
body.rtl.woocommerce-account .woocommerce-MyAccount-navigation,
body.rtl.woocommerce-account .woocommerce-MyAccount-content {
	float: right !important;
}

/* Edit-address form (my-account → Addresses → Edit): inputs typed LTR by the
   theme, so Arabic text + placeholders (e.g. "رقم المنزل واسم الشارع…") hugged
   the left (QA 2026-07-06). Type RTL; email/phone keep LTR content, aligned
   right. The Save button floated left — send it to the reading (right) side. */
body.rtl .woocommerce-address-fields input.input-text,
body.rtl .woocommerce-address-fields textarea {
	direction: rtl;
	text-align: right;
}
body.rtl .woocommerce-address-fields #billing_email,
body.rtl .woocommerce-address-fields #billing_phone {
	direction: ltr;
	text-align: right;
}
body.rtl .woocommerce-address-fields button[name="save_address"] {
	float: right;
}

/* Account-details form (my-account → Account details): same as the address
   form — the theme types inputs LTR, so Arabic values/placeholders hugged the
   left (QA 2026-07-06). Text fields RTL; email + password stay LTR content,
   aligned right. */
body.rtl .woocommerce-EditAccountForm input.input-text,
body.rtl .woocommerce-EditAccountForm textarea {
	direction: rtl;
	text-align: right;
}
body.rtl .woocommerce-EditAccountForm #account_email,
body.rtl .woocommerce-EditAccountForm input[type="password"] {
	direction: ltr;
	text-align: right;
}

/* Login / Register forms (logged-out my-account). The theme left the inputs
   text-align:left, so the Arabic placeholders ("اسم المستخدم…", "كلمة
   المرور…") hugged the left (QA 2026-07-06). All the fields take latin input
   (username/email/password) so keep LTR content but align right, which floats
   the Arabic placeholder to the right. */
body.rtl .woocommerce-form-login input.input-text,
body.rtl .woocommerce-form-register input.input-text {
	direction: ltr;
	text-align: right;
}

/* Remember-me ↔ Lost-password row: EN spreads them to opposite ends
   (remember-me block on the left, lost-password floated right). The physical
   float:right kept lost-password on the right in Arabic too, squeezing
   remember-me against it. Mirror: lost-password to the left (reading end),
   remember-me falls to the right (reading start). */
body.rtl .woocommerce-form-login .woocommerce-LostPassword.lost_password {
	float: left !important;
	text-align: left !important;
}
body.rtl .woocommerce-form-login p.form-row .woocommerce-form-login__rememberme {
	float: right;
}

/* ═══════════════════════════════════════════════════════════════════════════
   Checkout (forced-Arabic WC page). The parent's custom checkout block
   (parent style.css ~L31242-31460) is laid out for LTR and parent rtl.css
   never touches it — on the Arabic checkout the order-review table read
   left-aligned with its header cells overlapping. Mirror the layout.
   ═══════════════════════════════════════════════════════════════════════════ */
/* Two-column layout: billing form takes the RIGHT half (reading start), the
   sticky order review the LEFT half — the 15px column gutter flips with them. */
.checkout.woocommerce-checkout > div {
	float: right !important;
	padding-right: 0 !important;
	padding-left: 15px !important;
}
.checkout.woocommerce-checkout .woocommerce-checkout-review-order {
	float: right !important;
	padding-left: 0 !important;
	padding-right: 15px !important;
}
/* …but the gutters are a DESKTOP thing: the LTR base zeroes them when the
   columns stack (≤991px), and these flips were leaking into Arabic phones —
   the billing card sat 15px off the left, the order column's cards 15px off
   one side too (owner 2026-07-06, twice). */
@media (max-width: 991px) {
	.checkout.woocommerce-checkout > div {
		padding-left: 0 !important;
	}
	.checkout.woocommerce-checkout .woocommerce-checkout-review-order {
		padding-right: 0 !important;
	}
}
/* Order-review table. The theme displays the .product-name cells as FLEX,
   which breaks them out of the table's column grid — the header cells
   physically overlap. Invisible in LTR (each text hugs its opposite edge) but
   in RTL both header texts landed in the overlap zone ("المنتج" printed over
   "المجموع الفرعي") and every tfoot label+amount met in the middle
   ("الشحنةشحن مجاني"). Restore the header cell to table-cell and mirror all
   edges: labels/product info to the RIGHT edge, amounts to the LEFT edge. */
.woocommerce-checkout .woocommerce-checkout-review-order-table {
	/* The theme's FLEX cells make auto table-layout misplace the columns (they
	   overflowed the card's padding on the amounts side). Fixed layout sizes
	   the columns from the header row below and contains the flex cells. */
	table-layout: fixed !important;
}
.woocommerce-checkout .woocommerce-checkout-review-order-table thead > tr > th.product-name {
	display: table-cell !important;
	text-align: right !important;
	width: 64% !important;
}
.woocommerce-checkout .woocommerce-checkout-review-order-table thead > tr > th:last-child {
	text-align: left !important;
	width: 36% !important;
}
.woocommerce-checkout .woocommerce-checkout-review-order-table tfoot .cart-subtotal > th,
.woocommerce-checkout .woocommerce-checkout-review-order-table tfoot .woocommerce-shipping-totals th,
.woocommerce-checkout .woocommerce table.shop_table.woocommerce-checkout-review-order-table .order-total th {
	text-align: right !important;
}
.woocommerce-checkout .woocommerce-checkout-review-order-table tfoot .cart-subtotal td,
.woocommerce-checkout .woocommerce-checkout-review-order-table .woocommerce-shipping-totals td,
.woocommerce-checkout .woocommerce-checkout-review-order-table tfoot > tr.order-total > td,
.woocommerce .woocommerce-checkout .woocommerce-checkout-review-order-table tbody tr.cart_item td.product-total {
	text-align: left !important;
}
/* With the header cell back in the column grid, table auto-layout gives the
   amounts column its min-content width — Arabic labels/prices then wrap mid-
   phrase ("المجموع الفرعي", "₼ / 8,00" stacked). Keep them atomic so the
   column sizes to one clean line. */
.woocommerce-checkout .woocommerce-checkout-review-order-table thead > tr > th:last-child,
.woocommerce-checkout .woocommerce-checkout-review-order-table tfoot th,
.woocommerce-checkout .woocommerce-checkout-review-order-table .woocommerce-Price-amount {
	white-space: nowrap !important;
}
/* Payment methods: the radio circle + inner dot are pinned LEFT with a 25px
   left text-inset (parent ~L31377/31392); both move to the RIGHT for RTL.
   The pay-for-order page draws the same circle under its own selector
   (style.css "Pay-for-order page", QA ACC-049) and is flipped by the same rules. */
.woocommerce-checkout .woocommerce-checkout-payment input[type=radio] + label,
.woocommerce-checkout.woocommerce-order-pay #payment input[type=radio] + label {
	padding-left: 0 !important;
	padding-right: 25px !important;
}
.woocommerce-checkout .woocommerce-checkout-review-order-table input[type=radio] + label:before,
.woocommerce-checkout .woocommerce-checkout-payment input[type=radio] + label:before,
.woocommerce-checkout.woocommerce-order-pay #payment input[type=radio] + label:before {
	left: auto !important;
	right: 0 !important;
}
.woocommerce-checkout .woocommerce-checkout-review-order-table input[type=radio] + label:after,
.woocommerce-checkout .woocommerce-checkout-payment input[type=radio] + label:after,
.woocommerce-checkout.woocommerce-order-pay #payment input[type=radio] + label:after {
	left: auto !important;
	right: 5px !important; /* centred in the 18px ring (style.css, plan 113 #10) */
}
/* "Ship to a different address?" heading: the parent reserves 20px padding
   for its LTR checkbox hang. This used to flip the reserve to the RIGHT for
   the mirrored hang — but the Arabic checkbox is INLINE now (see the
   checkbox rules above), so a right-side reserve just inset this row's
   checkbox 20px off the "Create an account?" column (owner 2026-07-06).
   Keep the reserve on the left, matching the parent's intent. */
.woocommerce-checkout .checkout .col-2 h3#ship-to-different-address {
	padding-left: 20px !important;
	padding-right: 0 !important;
}

/* ═══════════════════════════════════════════════════════════════════════════
   Arabic typography — Cairo (self-hosted; @font-face in style.css). RTL-only, so
   this applies to Arabic pages only and leaves the English (LTR) site on Roboto.
   body → Cairo cascades to all text that has no explicit font-family; elements
   the theme sets to Roboto/Roboto Slab (headings, buttons, inputs, titles, menu)
   are overridden too. Icon fonts (FontAwesome / IcoFont / Simple-line-icons) are
   NOT targeted — they keep their own font via their direct .fa/.icon-* rules.
   ═══════════════════════════════════════════════════════════════════════════ */
body {
	font-family: 'Cairo', "Roboto", -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif !important;
}
/* Force Cairo on EVERY text element so it wins over theme/plugin rules that set
   their own font-family with higher specificity. The chained :not() both EXCLUDES
   icon fonts (so FontAwesome / IcoFont / Simple-Line-Icons keep their glyph font)
   and raises this selector's specificity above the theme's. ::before/::after icon
   pseudo-elements are not matched by `*` — but they INHERIT font-family from their
   host element, so hosts whose pseudo-elements draw glyphs must be excluded too:
   WooCommerce star ratings (.star-rating + descendants, review-form p.stars) draw
   their stars as the letters s/S in the "star" glyph font — forcing Cairo on them
   rendered literal "Sssss" on the Arabic shop. Struck prices (del + descendants)
   are excluded too: they hold only digits, and Cairo's strikethrough sits above the
   digits' middle — exempting them lets the plain `del` rule below give them the
   Latin font so the line-through centres (everywhere, incl. the Quick View popup,
   which lives outside #page). The Dirham currency span is exempt for the same
   glyph-font reason: it holds only the U+E900 symbol drawn by the 'Laymoun
   Dirham' web font (css/aed-symbol.css) — Cairo has no glyph there, so forcing
   it rendered a tofu box on every non-struck Arabic price (the del prices
   escaped via the del exclusion, which is how the gap was spotted;
   owner 2026-07-15). */
body *:not(i):not(.fa):not(.fas):not(.far):not(.fab):not(.fal):not(.fad):not(.fa-solid):not(.fa-regular):not(.fa-brands):not([class^="fa-"]):not([class*=" fa-"]):not(.icofont):not([class*="icofont-"]):not([class^="icon-"]):not([class*=" icon-"]):not(.sli):not([class^="pe-"]):not([class*=" pe-"]):not([class*="ftc-icon"]):not(.star-rating):not(.star-rating *):not(.stars):not(.stars *):not(del):not(del *):not(.woocommerce-Price-currencySymbol) {
	font-family: 'Cairo', "Roboto", -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif !important;
}
/* Struck price number → Latin font (see exclusion note above). */
del .woocommerce-Price-amount,
del .woocommerce-Price-amount bdi {
	font-family: "Roboto", -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
}

/* Quick View popup (prettyPhoto) on Arabic: right-align the text details, and keep
   the close button on the RIGHT. Its default position flips to the top-left in RTL,
   which lands it over the product image (image stays on the left in this layout). */
.pp_woocommerce .pp_details,
.pp_woocommerce .product_title,
.pp_woocommerce .stock,
.pp_woocommerce .woocommerce-product-rating,
.pp_woocommerce .woocommerce-review-link,
.pp_woocommerce .price,
.pp_woocommerce .ftc-social-sharing {
	text-align: right !important;
}
/* Keep the close button on the right; its RTL default flips to the top-left, landing
   over the product image (which stays on the left in this popup layout). */
.pp_pic_holder.pp_woocommerce .pp_details .pp_close {
	left: auto !important;
	right: 12px !important;
}
/* The theme reserves 80px on the title's RIGHT (invisible in LTR where the title is
   left-aligned) — in RTL the right-aligned title showed that as a dead gap. */
.pp_woocommerce .product_title {
	margin-right: 0 !important;
}
/* "Share:" is hardcoded English in the template (a <span>, not a gettext string, so
   the AR map can't reach it) — swap it to Arabic on RTL. */
.pp_woocommerce .ftc-social-sharing > span { display: none !important; }
.pp_woocommerce .ftc-social-sharing::before { content: "مشاركة: "; }
/* Lay the row out with flex so it flows right-to-left naturally: the label
   (::before) sits rightmost, icons follow to its left. The theme floats the
   icons left, which stranded them at the far-left edge away from the label. */
.pp_woocommerce .ftc-social-sharing {
	display: flex !important;
	align-items: center;
	gap: 10px;
}
.pp_woocommerce .ftc-social-sharing li {
	float: none !important;
	margin: 0 !important;
}

/* M-050 — input/textarea PLACEHOLDER text rendered in the browser's serif
   fallback on the Arabic checkout/account forms: ::placeholder is a
   pseudo-element, so the element-selector chain above never matches it and
   Chrome does not reliably inherit the forced font into it. Style it directly. */
input::placeholder,
textarea::placeholder {
	font-family: 'Cairo', "Roboto", -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif !important;
}
input::-webkit-input-placeholder,
textarea::-webkit-input-placeholder {
	font-family: 'Cairo', "Roboto", -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif !important;
}

/* ── Testimonials — space the name off the avatar (RTL, side-by-side only) ─────
   The card is `.content-info` (flex) → [.avatar (image), .testimonial-info (name)].
   The theme gives the name box `margin-left:15px`, which in LTR sits between the
   image (left) and the name (right). In RTL the flex row flips (avatar right, name
   left) so that left margin lands on the name's OUTER edge and the name ends up
   flush against the avatar. Flip it to a right margin so the gap falls between the
   name and the image.

   Scope to ≥1081px: the theme stacks the card at max-width:1080px (avatar on top,
   name centred UNDER it — responsive.css). In that stacked layout a horizontal
   margin shoves the name off-centre, so let the gap apply only while the name is
   actually beside the avatar; below 1080px the theme's centred stack takes over. */
@media (min-width: 1081px) {
	.content-info .testimonial-info {
		margin-left: 0 !important;
		margin-right: 20px !important;
	}
}

/* ── Footer menu titles — align with their menus on Arabic phones ─────────────
   Parent theme's rtl.css adds, at ≤480px, an RTL-only inset to footer widget
   titles: `.rtl .footer-mobi .col-active .heading-title { padding-right:35px }`.
   (Its LTR twin in responsive.css correctly uses 0 — only the RTL copy is wrong.)
   That 35px pushed the "معلومات" / "حسابي" titles left of the right edge while the
   menu links beneath them stayed flush, so the titles looked shifted (the Contact
   column has no `.col-active`, so it was never affected). Reset the inset to 0 so
   the titles line up with their menus. Same selector + !important as the parent
   rule, and the child rtl.css loads after it, so this wins. */
@media (max-width: 480px) {
	.rtl .footer-mobi .col-active .heading-title {
		padding-right: 0 !important;
	}
}

/* ── About + Contact heroes (Arabic) — phone edge gutter ──────────────────────
   Both heroes are builder "stretch" rows: their JS re-positions the row with
   inline left/width, and in RTL that leaves the row (and its column) hanging
   ~8px past BOTH screen edges — the LTR pages land on 0 (About) or keep the
   row's own 8px side padding (Contact). With the shared 22px column gutter
   (style.css) the Arabic hero text sat ~8-16px closer to the edge than the
   rest of its page. Widen just these rows' columns so the Arabic heroes line
   up with their pages: About → 22px like its other sections, Contact → 30px
   like its form fields and office block. */
@media (max-width: 767px) {
	body.page-id-17889 #content .vc_custom_1774900793899 > .wpb_column {
		padding-left: 30px !important;
		padding-right: 30px !important;
	}
	body.page-id-17886 #content .title-contact4 > .wpb_column {
		padding-left: 38px !important;
		padding-right: 38px !important;
	}
}

/* ── Quick View popup (Arabic): SKU/Category line ─────────────────────────────
   The popup content inherits prettyPhoto's text-align:left, and while most
   summary elements get their own RTL alignment, the SKU/Category meta block
   (.content) doesn't — التصنيف sat on the left edge. Right-align it; the
   wrapper class exists only inside the popup, so the product page (already
   correct) is untouched. */
.ftc-quickshop-wrapper .summary .content,
.ftc-quickshop-wrapper .summary .sku-wrapper {
	text-align: right;
}

/* ── Product page (Arabic): "مشاركة" share row ────────────────────────────────
   The share row's children (label + icons) are all `float: left`, and floats
   ignore direction — so on Arabic pages the row rendered left-to-right,
   starting at the left edge. Flex ignores floats and follows direction: the
   label leads from the RIGHT, icons flow leftward — same as the Quick View
   popup, which is already flex and mirrors correctly. The label's 15px gap
   was on its right (after it, LTR-style); move it to the left so it sits
   between the label and the first icon. */
.woocommerce div.product .summary .social-sharing .ftc-social-sharing {
	display: flex;
	align-items: center;
}
.woocommerce div.product .summary .social-sharing .ftc-social-sharing > span {
	margin-right: 0;
	margin-left: 10px;
}

/* ── Review form (Arabic): "save my name…" consent row polish ─────────────────
   The row is a flex pair (checkbox + 3-line label). Direction already flows
   RTL (box on the right), but the box hung vertically centred beside the
   block and the label's alignment was left over from LTR. Pin the box to the
   first line and right-align the sentence so the row reads naturally. */
.comment-form-cookies-consent {
	direction: rtl !important;   /* pin the row's flow: checkbox on the RIGHT */
	align-items: flex-start !important;
	gap: 8px;
}
.comment-form-cookies-consent input {
	margin-top: 5px !important;   /* optical alignment with the first text line;
	   !important: the DB blob's checkbox `margin: 0` prints after this sheet */
	margin-right: 0 !important;  /* parent gives the input a 7px LTR gap; flex gap handles it */
}
.comment-form-cookies-consent label {
	text-align: right !important;
}

/* ── Review form (Arabic): fields must TYPE right-to-left ─────────────────────
   The name / email / review inputs kept the browser default LTR direction —
   Arabic text entered left-to-right with the caret on the wrong side (owner
   report 2026-07-06). Same treatment the contact form's CF7 fields already
   have. The validation tips (js/review-form.js) align right with them. */
#commentform input[type="text"],
#commentform input[type="email"],
#commentform textarea {
	direction: rtl;
	text-align: right;
}
#commentform .lm-field-tip {
	text-align: right;
}



/* ── AR desktop: breathing room at the RIGHT screen edge (owner 2026-08-16).
   The full-width frame surfaces (header, footer, shop sidebar) share a 24px
   inline-START inset tuned on the English view — there the 24 hugs the LEFT
   edge (dibajj look: logo/content close to the start edge) and reads
   naturally. Mirrored to Arabic, the start side IS the right screen edge and
   24px reads cramped (owner: home/shop logo + shop sidebar content "too close
   to the right edge"; boxed pages like About sit in the 1170px container and
   were fine). Balance the Arabic start side at 40 to match the end side —
   English keeps its approved look. (This sheet loads after style.css, so the
   same selectors win the cascade.) */
@media (min-width: 992px) {
	.site-header .header-content > .container {
		padding-inline-start: 40px;
	}
	.site-footer .container {
		padding-inline-start: 40px;
	}
	/* the Arabic shop's sidebar renders as #left-sidebar (DOM-order name; the
	   float flip above puts it on the RIGHT) — cover both ids */
	.archive aside#right-sidebar.ftc-sidebar .widget-container,
	.archive aside#left-sidebar.ftc-sidebar .widget-container {
		padding-inline-start: 40px;
	}
}

/* ── AR mobile filter drawer docks on the RIGHT (owner 2026-08-16). The theme
   hard-anchors the shop filter drawer to the LEFT edge (responsive.css:
   fixed left:0, hidden at translate3d(-300px)) — an LTR design. On the Arabic
   shop it slid out on the left while the whole RTL page lives right-anchored
   (owner: the filter panel "to the left, not in the same align"). Mirror it:
   dock right, slide from the right. !important because responsive.css loads
   AFTER this sheet; the show-popup reset then needs it too, or the drawer
   could never open. */
@media (max-width: 991px) {
	aside.ftc-sidebar:not(.product-category-top-content) {
		left: auto !important;
		right: 0 !important;
		border-right: 0 !important;
		border-left: 1px solid #ebebeb !important;
		-webkit-transform: translate3d(300px, 0, 0) !important;
		transform: translate3d(300px, 0, 0) !important;
	}
	aside.ftc-sidebar:not(.product-category-top-content).show-popup {
		-webkit-transform: none !important;
		transform: none !important;
	}
}
