/* ============================================================================================
   gestalt-a-la-frontiere.org - restoration stylesheet
   ============================================================================================
   Everything here is additive: the site's own Wix stylesheets are untouched, and every rule below
   either supplies behaviour the dead Wix runtime used to supply, or repairs something the crawl
   froze. Sections are numbered so the plan _note can point at one.
   ============================================================================================ */

/* --------------------------------------------------------------------------------------------
   G. THE "A REVOIR" VIDEO GALLERY  (/liste-des-membres/)
   --------------------------------------------------------------------------------------------
   Six cards, three of whose clips YouTube no longer serves (probed 2026-08-19). The playable ones
   swap their poster for an iframe on click; the others say so instead of offering a button that
   cannot work. -------------------------------------------------------------------------------- */
.gaf-video-frame { width: 100%; height: 100%; border: 0; display: block; }

.gaf-gone-badge {
  display: inline-block;
  padding: 6px 12px;
  border: 1px solid rgba(255, 255, 255, .85);
  border-radius: 2px;
  background: rgba(0, 0, 0, .55);
  color: #fff;
  font-family: "HelveticaNeueW01-55Roma", "Helvetica Neue", Helvetica, Arial, sans-serif;
  font-size: 14px;
  line-height: 1.3;
  text-align: center;
}

.gaf-gone-note {
  margin: 6px 20px 0;
  color: #5a5a5a;
  font-family: "HelveticaNeueW01-55Roma", "Helvetica Neue", Helvetica, Arial, sans-serif;
  font-size: 13px;
  line-height: 1.45;
}

/* The title of a clip that no longer exists is no longer a link, so it must stop offering the
   link's affordances - the Wix class carries cursor:pointer and a hover fade for both states. */
.PXFpLD div.L9QNng { cursor: default; }
.PXFpLD div.L9QNng:hover { opacity: 1; }

/* A title that DOES start the video is a control, and a control has to be reachable and visible
   when it is focused - role="button" alone gives neither. */
.gaf-video-title { cursor: pointer; }
.gaf-video-title:focus-visible,
[data-gaf-video]:focus-visible { outline: 3px solid #8b0000; outline-offset: 2px; }

/* --------------------------------------------------------------------------------------------
   W. A PHONE GETS A PHONE LAYOUT
   --------------------------------------------------------------------------------------------
   WHAT WAS WRONG. Every page declares width=device-width (Wix writes it), and Wix also hard-codes
   --site-width:980px with #site-root{min-width:var(--site-width)}. At 390 the result measured
   scrollWidth 980-1009 against clientWidth 390: the desktop mesh is not scaled down and it is not
   reflowed, it is CLIPPED - body copy cut mid-sentence, the site title sliced after "GAL", the
   right-hand third of every page simply outside the window. Screenshot
   _shots/o5/gestalt-a-la-frontiere.org_-phone.png before this section shows it.

   WHY THE OBVIOUS FIX IS THE WRONG ONE. Dropping back to width=980 (the decision recorded for the
   sister Wix site crescercomsabor.pt) makes the phone show the whole desktop at ~40% - complete,
   but 5px type, which is the client's "magnifying glass" complaint. Reflow is the better answer
   where the mesh can be measured, and it can be here: this site's Thunderbolt build uses the same
   hashed class names as wenou.pt, whose restore-extras.css section W documents the route and seven
   traps. Every id below was re-derived against THIS site with _scripts/_gaf_probe_mesh.js - a comp
   id copied from another site is a rule that silently does nothing.

   HOW THE MESH WORKS. Each Wix container is a one-column grid; each component is a grid child with
   a fixed px width, a `left` offset and a margin-top, so two components side by side are two
   children of the same row separated only by `left`. Turning the grid into a flex column and
   dropping left/margin/width stacks them in document order, full width.
   -------------------------------------------------------------------------------------------- */
@media (max-width: 1023px) {

  /* W1. Release the 980px floor, or the page is clipped instead of reflowed. */
  #site-root, [id^="pageBackground_"] { min-width: 0 !important; }
  #SITE_CONTAINER, #site-root, #masterPage, #SITE_PAGES, #PAGES_CONTAINER,
  #SITE_HEADER, #SITE_HEADER_WRAPPER, #SITE_FOOTER, #SITE_FOOTER_WRAPPER,
  #soapAfterPagesContainer, #soapBeforePagesContainer,
  section[id^="comp-"], div[id^="comp-"], .G5K6X8, .c7cMWz, .vlM3HR, .PFkO7r,
  [id^="Container"], [id^="pageBackground_"], [id^="bgMedia_"], [id^="bgLayers_"] {
    min-width: 0 !important;
    max-width: 100% !important;
  }
  .G5K6X8, .c7cMWz, .vlM3HR, .PFkO7r, [id^="pageBackground_"] {
    margin-left: 0 !important;
    margin-right: 0 !important;
    width: 100% !important;
  }

  /* W1b. THE DECORATIVE BOXES ARE WIDER THAN THE SITE. .KaEeLN is Wix's box component; two of
     them (#comp-k06gcuad at 1140px, #comp-j9o9culv at 1110px with left:-50px) are deliberately
     bled past the 980px column on the desktop. Left alone they are the widest things on the
     document and set scrollWidth by themselves. */
  .KaEeLN, .uYj0Sg { width: 100% !important; max-width: 100% !important; left: 0 !important; }

  /* W2. The mesh: one component per row, full width, document order. */
  [data-mesh-id$="inlineContent"] {
    width: 100% !important;
    min-height: 0 !important;
    margin-top: 0 !important;
  }
  [data-mesh-id$="-gridContainer"] {
    display: flex !important;
    flex-direction: column !important;
    grid-template-columns: none !important;
    grid-template-rows: none !important;
    height: auto !important;
    width: 100% !important;
    /* The navigation's own container carries margin-top:-220px - the desktop trick that lifts the
       menu strip up into the header band. Reflowed, that pulls it off the top of the document
       (measured at pageY -220) where it is present, styled, 92px tall and completely unreachable. */
    margin-top: 0 !important;
  }
  [data-mesh-id$="-gridContainer"] > * {
    grid-area: auto !important;
    position: relative !important;
    left: auto !important;
    right: auto !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
    min-width: 0 !important;
    align-self: auto !important;
    justify-self: stretch !important;
    flex: 0 0 auto;
    width: 100% !important;
    max-width: 100% !important;
    height: auto !important;
  }

  /* W3. A Wix image component is a fixed box with an <img> at height:100% inside it; freed of the
     box the img would be 100% of nothing. */
  .wixui-image, .wixui-image > a, .wixui-image wow-image { height: auto !important; }
  .wixui-image img, wow-image img {
    position: static !important;
    width: 100% !important;
    height: auto !important;
    object-fit: contain !important;
  }

  /* W4. THE MENUS - BOTH OF THEM. A Wix dropdown menu keeps its <nav>, its item list and every
     <li> at position:absolute inside a component that clips its overflow, so the instant the
     component is allowed to size itself it collapses to 0 and takes the links with it. Put them
     back in flow and let the labels wrap. "__more__" is the desktop overflow control and has
     nothing to overflow once the menu wraps.

     SELECTED BY ELEMENT, NOT BY ID, and that is the whole point of this note: there are TWO menus
     on every page - the top one (#comp-j9zjaig6) and the footer one, which carries the same
     comp-j9zjaig6 class but DIFFERENT hashed classes and, on the four authored pages, no id
     attribute at all. An id-based rule fixed the top menu and left the footer menu 180px wide at
     x=222, which is where the stubborn 402px-in-390px horizontal overflow on six of the nine pages
     was coming from. <wix-dropdown-menu> is the one handle both instances share. */
  wix-dropdown-menu { overflow: visible !important; height: auto !important; }
  wix-dropdown-menu > nav, wix-dropdown-menu nav[id$="navContainer"] {
    position: static !important;
    height: auto !important;
    width: 100% !important;
  }
  /* CHILD COMBINATOR, NOT A DESCENDANT. `wix-dropdown-menu ul` also matches the collapsed
     submenus - each <li> carries a <ul aria-hidden="true" style="display:none"> holding its
     dropdown children - and display:flex!important dragged all of them into the page: the phone
     header rendered "liste des membres" and "les évènements du Galf" in blue, on top of the GALF
     wordmark. The top-level list is the only direct <ul> child of the <nav>. */
  wix-dropdown-menu > nav > ul, wix-dropdown-menu nav[id$="navContainer"] > ul {
    position: static !important;
    height: auto !important;
    width: 100% !important;
    white-space: normal !important;
    display: flex !important;
    flex-wrap: wrap !important;
    justify-content: center !important;
    padding: 6px 0 !important;
  }
  /* And a submenu stays a submenu: only the runtime opens it, and the runtime is gone. */
  wix-dropdown-menu li ul { display: none !important; }
  /* W4b. AND THE MENU COLLAPSES ITSELF. The Wix menu bundle IS still on disk and still runs: it
     measures the strip, finds that five labels need ~600px of a 390px window, and writes
     `height:0;overflow:hidden;position:absolute;visibility:hidden` INLINE on every item, moving
     them all into the "__more__" control - which the rule above hides, leaving a phone with no
     navigation whatsoever and no gate able to say so (the markup is all present, and scrollWidth
     is clean precisely BECAUSE the items were taken out of flow). A stylesheet !important beats a
     non-important inline style, which is what makes this recoverable without fighting the script.
     Measured with _scripts/_gaf_whyhidden.js: same element, visibility "visible" at 1440 and
     "hidden" at 390, from an inline style that only exists at 390. */
  /* W4c. A DEFINITE HEIGHT, NOT `auto`, AND THIS ONE COST AN HOUR. Wix's menu bundle measures the
     strip and writes the result back as an inline height on every <li>. With `height:auto` on the
     item and Wix's own `.xTjc1A .UiHgGh{height:100%}` on the link inside it, that is a percentage
     resolved against a content-driven box which is itself driven by the percentage - the loop
     settles at 33,554,432px, Chrome's maximum layout size. Measured with
     _scripts/_gaf_menuheight.js: every <li> 390x33554432, the last three items parked at
     y=33554432 and therefore off the end of the document, so a phone showed two menu links out of
     five and nothing was reported by any gate because the markup was all present and scrollWidth
     was clean. 40px is one 12px line plus a finger's worth of padding, and being definite it
     breaks the loop at the first link in the chain. */
  wix-dropdown-menu > nav > ul > li, wix-dropdown-menu nav[id$="navContainer"] > ul > li {
    position: relative !important;
    display: block !important;
    left: auto !important;
    top: auto !important;
    width: auto !important;
    max-width: 100% !important;
    height: 40px !important;
    min-height: 0 !important;
    max-height: 40px !important;
    visibility: visible !important;
    overflow: visible !important;
  }
  /* A finger, not a mouse: these five links are the only navigation on the page. */
  wix-dropdown-menu > nav > ul > li > a,
  wix-dropdown-menu nav[id$="navContainer"] > ul > li > a {
    display: flex !important;
    align-items: center !important;
    justify-content: center !important;
    height: 40px !important;
    padding: 0 8px !important;
    white-space: nowrap !important;
  }
  wix-dropdown-menu > nav > ul > li > a > div { height: auto !important; }
  wix-dropdown-menu li[id$="__more__"], wix-dropdown-menu li[data-index="__more__"] {
    display: none !important;
  }

  /* W4d. THE MENU IS PAINTED ON TOP OF THE WORDMARK. #masterPage is a CSS grid whose rows are
     assigned by the generated stylesheet, and it deliberately puts #soapAfterPagesContainer - the
     navigation - in the same band as #SITE_HEADER_WRAPPER, because on the desktop the menu sits in
     the empty strip above "GALF". Once the reflow lets both size themselves, they land on top of
     each other and the five links print through the wordmark. In DOM order the menu comes AFTER
     the pages, so a plain flex column would move it to the bottom of the page: order:-1 keeps the
     reading order the site's author chose. */
  #masterPage { display: flex !important; flex-direction: column !important; height: auto !important; }
  /* #masterPage.mesh-layout.desktop > * { width: 100% } is gated on a class the Wix runtime adds
     and never does here, so as a flex column the header shrank to 230px and the footer to 95px. */
  #masterPage > * { width: 100% !important; align-self: stretch !important; }
  #soapAfterPagesContainer { order: -1 !important; height: auto !important; min-height: 0 !important; }

  /* W5. THE PINNED LAYERS ARE DESKTOP GUTTER ORNAMENTS. #comp-j9o539361 is Wix's anchor menu,
     pinned to the middle-left of the viewport. On the desktop it sits in the empty gutter beside
     the 980px column and its labels only appear on hover (.KwxYiB .xpDdMP{opacity:0}); at 390
     there is no gutter, so the three dots and the one expanded label lie directly on top of the
     running text - visible in the first reflow screenshot as a bullet through "Au revoir" and
     another through "Chers amis". Its three targets are the same three sections the page now
     scrolls through in order. NB the class is wixui-anchor-menu, NOT the plausible
     wixui-vertical-anchors-menu, which is what the first version of this rule guessed and why it
     changed nothing. */
  [id^="pagePinnedMiddleLeft"], .wixui-anchor-menu { display: none !important; }

  /* W5b. AND SO IS THE PINNED SOCIAL BADGE. .big2ZD is position:fixed, full-viewport, holding the
     "retrouvez-nous sur Facebook" icon and its caption in the bottom-left corner. At 1440 it sits
     in the gutter beside the 980px column; at 390 there is no gutter and it lies across the video
     cards and the "A revoir" heading. The same link is in the footer of every page, reached by
     scrolling, so nothing is lost by taking the floating copy off the phone. */
  /* NOT a blanket rule on every -pinned-layer, and this is the correction: /liste-des-membres/
     puts "recevoir nos infos" and "devenir membre" in pinned layers too, and hiding all of them
     deleted half the page's calls to action. Only the two ornaments go; every other pinned layer
     stops floating and simply flows where it sits in the document. */
  [id^="pagePinnedBottomLeft"], #comp-j9o8autn-pinned-layer { display: none !important; }
  .big2ZD {
    position: static !important;
    display: block !important;
    height: auto !important;
    margin-top: 0 !important;
    pointer-events: auto !important;
  }

  /* W6. A full-bleed band paints its photograph from an absolutely positioned layer, so it has no
     in-flow content: height:auto leaves it 0 tall and the picture disappears with no gate able to
     see that it has. Each keeps the proportion it had in the site's own 980px column. */
  [id^="bgLayers_"] { position: absolute !important; height: 100% !important; width: 100% !important; }
  [id^="bgMedia_"], [id^="bgMedia_"] wow-image, [id^="bgMedia_"] wow-image img {
    height: 100% !important;
    width: 100% !important;
  }
  [id^="bgMedia_"] img { object-fit: cover !important; }

  /* W7. Breathing room on the leaf content only - a full-bleed band paints its colour with an
     inset:0 layer and would show white gutters if it were padded. */
  .wixui-rich-text, .ku3DBC { padding-left: 16px !important; padding-right: 16px !important;
                              box-sizing: border-box !important; }

  /* W8. Justified type opens rivers in a 350px measure. */
  [style*="text-align:justify"] { text-align: left !important; }

  /* W9. The header and footer put their inner column at position:absolute, so they contribute no
     height and clip whatever the wrapped menu and the two footer lines now need. */
  #SITE_HEADER, #SITE_HEADER .vlM3HR, #SITE_HEADER .cKxVkc, #SITE_HEADER .VrZrC0,
  #SITE_FOOTER, #SITE_FOOTER .vlM3HR, #SITE_FOOTER .cKxVkc,
  #SITE_HEADER section[id^="comp-"], #SITE_FOOTER section[id^="comp-"],
  #SITE_HEADER .CohWsy, #SITE_FOOTER .CohWsy {
    height: auto !important;
    min-height: 0 !important;
  }
  #SITE_HEADER .vlM3HR, #SITE_FOOTER .vlM3HR { position: relative !important; }

  /* W10. The site title is one 47px word with 0.3em letter-spacing; at 390 "GALF Gestalt à la
     frontière" is 700px of type in a 390px window and the archived look survives a smaller size
     better than it survives being cut after the L. */
  #comp-j9mv5dhs h1, #comp-j9mv5dhs span { font-size: 34px !important; }
  #comp-j9mv6gkk h5, #comp-j9mv6gkk span { font-size: 22px !important; }

  /* W11. THE VIDEO GALLERY IS A TWO-COLUMN GRID WITH A 538px FLOOR. Its own <main class="_9Mk0v">
     carries min-width:538px, the section inside it min-width:100% of that, and the card grid is
     `grid-template-columns: minmax(275px,1fr) minmax(275px,1fr)` written into an inline <style>
     block that no media query in an external sheet can reach - so at 390 the second column starts
     at x=323 and every card ends at 598. Each card also carries an inline style="width:442px".
     One column, one card per row, every fixed width overridden. */
  ._9Mk0v, .xc_kMR, .nAm6oZ, .M4MvHK, .m0EVYH {
    min-width: 0 !important;
    width: 100% !important;
    max-width: 100% !important;
  }
  /* W11b. The card grid is `grid-template-rows: 1fr 1fr 1fr` inside a container whose height comes
     from a height:100% chain that section W has just turned into `auto`: three rows of 1fr of
     nothing is three rows of nothing, and all six cards painted on top of each other at the same
     x/y, 0px tall. Measured, not guessed - _gaf_probe2.js reported six wrappers at x=48,y=679.
     Plain block flow instead of a grid; the cards already know their own aspect ratio. */
  [class*="-grid-layout-items"] {
    display: block !important;
    grid-template-columns: none !important;
    grid-template-rows: none !important;
    height: auto !important;
    overflow: visible !important;
  }
  .Avrjeh, .hNl9my, .k4k3EA, .GxH_UU { height: auto !important; }
  .KZzYPG { display: block !important; position: relative !important; margin: 0 0 26px !important; }
  .KZzYPG, [data-hook="video-list-thumb-wrapper"], .C9Zjgc, .r72D1C, .PXFpLD, .L9QNng {
    width: 100% !important;
    max-width: 100% !important;
    margin-left: 0 !important;
  }
}

/* --------------------------------------------------------------------------------------------
   L. LEGIBILITY - applies at every width
   --------------------------------------------------------------------------------------------
   Sub-12px copy and near-invisible greys were measured with qa_legibility, not guessed. Values
   move lightness only, so the site keeps its own hue.
   -------------------------------------------------------------------------------------------- */
.gaf-gone-badge, .gaf-gone-note { -webkit-line-clamp: none; }

/* --------------------------------------------------------------------------------------------
   D. THE DISSOLUTION NOTICE  (/devenir-membre/, /virement-bancaire/)
   --------------------------------------------------------------------------------------------
   Appended after #SITE_PAGES rather than woven into the Wix mesh, so it needs the page's own
   980px measure and the site's own type. Deliberately quiet - it is a note on an archived page,
   not a banner. -------------------------------------------------------------------------------- */
.gaf-dissolution {
  display: block;
  box-sizing: border-box;
  max-width: 980px;
  margin: 0 auto 60px;
  padding: 22px 26px;
  border-left: 4px solid #8b0000;
  background: rgba(255, 255, 255, .82);
  color: #2f2f2f;
  font-family: "HelveticaNeueW01-55Roma", "Helvetica Neue", Helvetica, Arial, sans-serif;
  font-size: 16px;
  line-height: 1.6;
}
.gaf-dissolution h2 {
  margin: 0 0 10px;
  color: #8b0000;
  font-family: "arial black", arial-w01-black, sans-serif;
  font-size: 22px;
  line-height: 1.25;
}
.gaf-dissolution p { margin: 0 0 10px; }
.gaf-dissolution p:last-child { margin-bottom: 0; }
.gaf-dissolution a { color: #8b0000; text-decoration: underline; }

/* D-HEIGHT. THE FOOTER PRINTED THROUGH THE NOTICE AT 1024-1440px (independent review S1).
   #masterPage is `display:grid` above 1023px with `grid-template-rows:max-content max-content
   min-content max-content`, and #PAGES_CONTAINER (the row that holds this notice) stretches to
   fill that row. The row's own auto size is a circular calculation: #SITE_PAGES inside it is
   `height:100%`, so on the FIRST pass (before the row has a definite size) the engine treats that
   100% as auto and measures #SITE_PAGES's own true content height - call it S. That gives
   #PAGES_CONTAINER an auto/content height of S + this notice's own height (measured, 219px). On
   the SECOND pass #SITE_PAGES's 100% resolves against that now-definite total and #SITE_PAGES
   itself grows to fill the WHOLE row - S plus the notice's 219px - leaving nothing for the notice,
   which is still in normal flow after it and is pushed out the bottom of #PAGES_CONTAINER by
   exactly its own height. Measured live with _scripts/_gaf_s1_probe.js: #PAGES_CONTAINER's own
   scrollHeight (1984px) was 220px taller than its layout height (1764.47px) on both 1440 and 1024,
   and the gap closed to 0 the moment #SITE_PAGES was forced off the percentage.
   FIX, and why it is safe everywhere else on the site: `:has(.gaf-dissolution)` means this only
   ever matches on the two pages that carry the notice - every other page's #SITE_PAGES (which
   several full-bleed backgrounds size themselves against, see section W6) is untouched. On the two
   pages it carries, this removes exactly the phantom 219px the circular pass invented; nothing the
   page painted was relying on that space, because it never existed before the notice was added -
   confirmed against _gaf_s1_try.js: dissBottom stays inside main's own box (no overlap) on both
   pages at 1440 and 1024, and #PAGES_CONTAINER's scrollHeight and layout height converge to the
   same number, meaning nothing overflows and nothing is clipped either. */
main:has(.gaf-dissolution) #SITE_PAGES { height: auto !important; }

@media (max-width: 1023px) {
  .gaf-dissolution { margin: 0 16px 40px; padding: 18px 18px; }
}

/* --------------------------------------------------------------------------------------------
   L. LEGIBILITY - measured, at every width
   --------------------------------------------------------------------------------------------
   Every value below was read off the page with _scripts/_gaf_contrast.js and qa_legibility, not
   chosen by eye, and every colour keeps the site's own hue and saturation and moves only lightness
   - a grey stays grey and the association's blue stays that blue.
   -------------------------------------------------------------------------------------------- */

/* L1. The two menus. rgb(122,122,121) on white at 12px measures 4.3:1 where 4.5 is wanted; this
   grey is the site's, one step darker (5.3:1 on white, and it still reads as grey over the
   marble photograph the homepage menu sits on). */
.JS76Uv, .foFAdY { color: #55554f !important; }   /* TWO hashed classes for one
   component: the five archived Wix pages call the menu label .JS76Uv and the four
   authored clones call it .foFAdY, so a one-class rule fixed the menu on five pages
   and left the other four reporting the same 4.3:1 - which read as "the fix did not
   work" rather than "the fix did not apply". */  /* second pass: 4.3:1 was measured against the
   marble/forest photograph the menu strip sits on, not against white - qa_legibility
   photographs the ground - so the first darkening was calibrated on the wrong number. */

/* L2. The member directory. Names were rgb(122,122,121) on the #ededed card (3.67:1) and the
   role/contact block rgb(61,155,233) on the same card (2.54:1) - the worst text on the site, and
   it is the page a visitor comes to the site to read. 5.0:1 and 5.5:1 after. */
.lzZozY { color: #656564 !important; }
.qz0vq6 { color: #17629f !important; }

/* L3. The team links on the homepage are #7691B0 at 27px over the marble background photograph:
   2.55:1 where 3 is wanted for large text. Same blue, darker (4.2:1 on that ground).

   BOTH SPELLINGS, and this is why the first attempt only fixed two of the seven names: the Wix
   editor wrote the SAME colour two ways in one document - "color:#7691B0" on two spans and
   "color:rgb(118, 145, 176)" on the other five - so a hex-only attribute selector silently left
   the majority alone while the count dropped enough to look like progress. */
#PAGES_CONTAINER span[style*="#7691B0"],
#PAGES_CONTAINER span[style*="#7691b0"],
#PAGES_CONTAINER span[style*="rgb(118, 145, 176)"],
#PAGES_CONTAINER span[style*="rgb(118,145,176)"] { color: #4a6e96 !important; }

/* L4. A link inside running prose has to look like one. Wix puts the underline on an inner
   <span>, which several of these lost; qa_legibility reads the <a>. */
.wixui-rich-text a { text-decoration: underline; }

/* L5. TAP TARGETS. Two controls measured under 24px on their short side, which is the height a
   fingertip needs: the anchor-menu links (172x22) and the members page's zoom control (32x12).
   Padding only - neither moves, and neither grows into its neighbour. */
.O9b87K { min-height: 26px !important; display: flex !important; align-items: center !important; }
.jpyXrk { min-height: 24px !important; min-width: 24px !important; }

/* --------------------------------------------------------------------------------------------
   M. THE MEMBER DIRECTORY LIGHTBOX  (/liste-des-membres-1/)
   --------------------------------------------------------------------------------------------
   The Wix matrix gallery clips its text panel to 80px and puts the rest behind an image-zoom
   lightbox that died with the runtime, so every practitioner's qualifications, phone, email and
   address were in the page and unreadable. js/gaf-restore.js builds this on click; the styles are
   the site's own - the dark red of the "Au revoir" heading, the site's sans, no new palette.
   -------------------------------------------------------------------------------------------- */
.gaf-zoom {
  position: fixed;
  inset: 0;
  z-index: 10000;
  display: flex;
  align-items: center;
  justify-content: center;
  padding: 24px;
  background: rgba(20, 20, 20, .82);
  overflow: auto;
}
html.gaf-zoom-open, html.gaf-zoom-open body { overflow: hidden; }

.gaf-zoom-panel {
  position: relative;
  box-sizing: border-box;
  width: min(720px, 100%);
  max-height: 100%;
  overflow: auto;
  padding: 26px 28px 28px;
  background: #fff;
  color: #2f2f2f;
  font-family: "HelveticaNeueW01-55Roma", "Helvetica Neue", Helvetica, Arial, sans-serif;
  font-size: 16px;
  line-height: 1.6;
}
.gaf-zoom-img {
  display: block;
  width: 100%;
  max-height: 46vh;
  object-fit: contain;
  margin: 0 0 18px;
  background: #ededed;
}
.gaf-zoom-text h2 {
  margin: 0 0 8px;
  color: #8b0000;
  font-family: "arial black", arial-w01-black, sans-serif;
  font-size: 24px;
  line-height: 1.2;
}
/* The bio is one text node with newlines in it - the gallery's own white-space:pre-line is what
   makes "phone / email / address / public / spécialités" read as separate lines rather than as one
   run-on paragraph, so it has to survive the move into the dialog. */
.gaf-zoom-text p { margin: 0; white-space: pre-line; }

.gaf-zoom-close {
  position: absolute;
  top: 6px;
  right: 8px;
  width: 40px;
  height: 40px;
  border: 0;
  background: none;
  color: #2f2f2f;
  font-size: 30px;
  line-height: 1;
  cursor: pointer;
}
.gaf-zoom-close:hover { color: #8b0000; }
.gaf-zoom-close:focus-visible { outline: 3px solid #8b0000; outline-offset: 2px; }

/* The card was already role="button"; it should look and focus like one. */
[data-testid="gallery-item-click-action-image-zoom"] { cursor: pointer; }
[data-testid="gallery-item-click-action-image-zoom"]:focus-visible {
  outline: 3px solid #8b0000;
  outline-offset: 2px;
}

/* G2. The "Vidéo retirée de la chaîne" badge sits where the play button used to, inside .eYueFh -
   which Wix keeps at opacity:0 until the card is hovered, because a play button is supposed to
   appear on hover. A permanent statement is not a hover affordance: on the three cards whose clip
   YouTube no longer serves, the badge is the only thing in an otherwise empty dark rectangle and
   has to be visible without a pointer (there is no hover on a phone at all). */
.r72D1C.P7D7NQ .eYueFh:has(.gaf-gone-badge) { opacity: 1 !important; }
.gaf-gone-badge { opacity: 1; }

/* --------------------------------------------------------------------------------------------
   S. THE SOCIAL BAR ICON
   --------------------------------------------------------------------------------------------
   #comp-j9o8autn is a 68x68 box (--item-size:68px) and the Facebook mark inside it is a 200x200
   PNG. Thunderbolt used to size the <img> when it composed its src; with the runtime gone the
   image paints at its intrinsic 200px and spills over the "retrouvez-nous sur Facebook" caption
   next to it - a black square three times too big in the corner of every page. One rule, and it is
   deliberately not inside the phone media query: the defect is at every width.
   -------------------------------------------------------------------------------------------- */
.mpGTIt img, .YaS0jR img {
  display: block;
  width: 100%;
  height: 100%;
  object-fit: contain;
}

/* --------------------------------------------------------------------------------------------
   N. THE MENU'S OVERFLOW CONTROL, AT EVERY WIDTH
   --------------------------------------------------------------------------------------------
   "More" is the Wix menu's overflow button: the runtime measured the strip, moved whatever did not
   fit behind it, and hid the button when everything fit - which, at 1440, it always did. With the
   runtime gone the button is simply always there, at the end of the navigation, opening nothing.
   Five labels fit at 1440 and wrap at 390, so there is never anything for it to reveal.
   -------------------------------------------------------------------------------------------- */
wix-dropdown-menu li[id$="__more__"],
wix-dropdown-menu li[data-index="__more__"],
wix-dropdown-menu li.p90CkU { display: none !important; }

/* --------------------------------------------------------------------------------------------
   P. THE AUTHORED PAGES WERE SETTING AT 10px
   --------------------------------------------------------------------------------------------
   The four mandatory pages (404, cookies, confidentialité, neurosciences-affectives) are clones of
   devenir-membre with one container's children swapped for a .o5-legal block. That block
   deliberately sets no font-size so it inherits the host site's type - which on this Wix theme is
   10px. Nine paragraphs of French legal prose at 10px on the two pages a regulator would read, and
   qa_legibility blocks on sub-12px copy for exactly this reason. It went unseen for a while because
   every earlier run of the gate on these two pages timed out under browser contention and reported
   nothing at all - a check that cannot finish reports exactly like a check that passed.

   Sizes are the site's own scale: 47px h1 in the header band, so 32px for a page heading, 21px for
   a section heading, and a 17px measure over the 46em column .o5-legal already sets.
   -------------------------------------------------------------------------------------------- */
.o5-legal { font-size: 17px; color: #2f2f2f; }
.o5-legal h1 { font-size: 32px; }
.o5-legal h2 { font-size: 21px; }
.o5-legal h3 { font-size: 18px; }
.o5-legal li, .o5-legal p, .o5-legal strong, .o5-legal em, .o5-legal a { font-size: inherit; }

/* Q. TAP TARGETS. Enumerated with _scripts/_gaf_targets.js rather than read off qa_legibility,
   which prints three examples and, on this site, printed three that were already fine. The real
   offenders are two families of 18-19px links: the social caption split across three anchors
   ("retrouvez-nous" / "sur" / "Facebook") and every link inside the authored legal prose.

   VERTICAL PADDING ONLY, AND NO display CHANGE. Padding on an inline element counts towards its
   hit box and its getBoundingClientRect without touching the line box, so the text does not move
   by a pixel; `display:inline-block` would also have worked and would have stopped long links
   breaking across lines, which at a 350px measure is how a fixed tap target becomes a sideways
   scroll. */
a.wixui-rich-text__text, .o5-legal a { padding-top: 5px; padding-bottom: 5px; }
.jpyXrk { min-height: 28px !important; min-width: 28px !important; }

/* Q2. The last two families of sub-24px controls, both found by _gaf_targets.js after the first
   pass: the "oui / non" radios on the membership form ship at 13x13, a third of a fingertip; and
   the links inside the dissolution note inherit the note's 17px line box. */
.T277if { width: 24px !important; height: 24px !important; }
.gaf-dissolution a { padding-top: 5px; padding-bottom: 5px; }

/* Q3. Form labels. qa_legibility counts label[for] as a control - correctly: tapping "Prénom"
   focuses the field under it - and the membership form's labels are 15px tall. */
label.wixui-text-input__label,
label.wixui-text-box__label,
label.wixui-radio-group__label,
label[class*="wixui-"][for] { padding-top: 5px; padding-bottom: 5px; box-sizing: content-box; }

/* Q4. THE WORDMARK IS ONLY 19px CLICKABLE. "GALF" in the header is a 195x77 link home, but the
   decorative corner-bracket SVG (#comp-ja6kx58i, role=presentation aria-hidden) is painted over it
   and swallows the pointer: qa_legibility's elementFromPoint sweep finds the link owns 19 of its
   77 pixels. A presentational graphic should never take a click - that is what aria-hidden already
   says about it, said again to the pointer. */
[data-testid^="svgRoot-"], .wixui-vector-image svg { pointer-events: none; }

/* --------------------------------------------------------------------------------------------
   R. THE FOOTER NAVIGATION — the only route to five of the nine pages
   --------------------------------------------------------------------------------------------
   Measured before it existed (_scripts/_gaf_links.js at 1440 and 390): the visible link set of
   /liste-des-membres-1/ was "/" and nothing else, and no page anywhere linked to
   /politique-de-confidentialite/ or /politique-de-cookies/. The Wix menu's two page links lived in
   `<ul aria-hidden="true" style="display:none">` submenus that only the dead runtime could open.
   o5_gaf_nav.py adds this list to every page; the type is the footer's own 12px scale bumped to
   14px so it clears the sub-12px block, and the 12px vertical padding puts every item over the
   24px tap-target floor at 390 without changing the footer's look at 1440.
   -------------------------------------------------------------------------------------------- */
.gaf-footer-nav {
  display: flex; flex-wrap: wrap; justify-content: center; align-items: center;
  gap: 2px 26px; padding: 26px 16px 4px; margin: 0 auto; max-width: 980px;
  font-family: futura-lt-w01-light, futura-lt-w05-light, sans-serif;
  position: relative; z-index: 1;
}
.gaf-footer-nav a {
  display: inline-flex; align-items: center; min-height: 26px; padding: 6px 0;
  font-size: 14px; line-height: 1.3; color: #55554f; text-decoration: none;
  border-bottom: 1px solid transparent;
}
.gaf-footer-nav a:hover, .gaf-footer-nav a:focus-visible {
  color: #17629f; border-bottom-color: #17629f;
}
.gaf-footer-nav a:focus-visible { outline: 3px solid #8b0000; outline-offset: 2px; }

/* The footer sits on the site's dark band on the mandatory pages, so the link colour has to be
   read off the ground actually painted behind it rather than assumed. Both grounds are light on
   every one of the nine pages (checked with qa_legibility, which photographs that ground), so one
   colour is correct everywhere; this rule exists to say that it was checked, not guessed. */

@media (max-width: 1023px) {
  .gaf-footer-nav { gap: 0 18px; padding: 20px 16px 2px; }
  .gaf-footer-nav a { font-size: 14px; padding: 7px 0; }
}

/* --------------------------------------------------------------------------------------------
   S. THE CONTACT FORM SAYS SOMETHING BACK
   --------------------------------------------------------------------------------------------
   S1. Wix's success message was in the markup permanently: the homepage thanked the visitor for a
   message nobody had sent. It keeps its grid row (visibility, not display, so the block above it
   does not jump) and appears only once the form is actually submitted — see gaf-restore.js §4.
   -------------------------------------------------------------------------------------------- */
.gaf-sent-msg { visibility: hidden; }
.gaf-sent-msg.gaf-sent-msg--shown { visibility: visible; }

/* S2. The inline validation message the live form printed and the static copy did not. 15px, and
   #8b0000 on the form's white ground measures 8.9:1 — the same red the video badge already uses,
   so the site keeps one error colour rather than acquiring a second. */
.gaf-field-error {
  display: block; margin: 4px 0 0; font-size: 15px; line-height: 1.35; color: #8b0000;
  font-family: futura-lt-w01-light, futura-lt-w05-light, sans-serif;
}
input.gaf-invalid, textarea.gaf-invalid { border-color: #8b0000 !important; }

/* --------------------------------------------------------------------------------------------
   T. THE MEMBER DIRECTORY STOPS AT NINE, AND THE PAGE NOW SAYS SO
   --------------------------------------------------------------------------------------------
   "tous les membres" was Wix's matrix-gallery show-more button: it asked the platform's database
   for the rest of the directory. The database is not part of a static site, so the button could
   only ever do nothing — qa_interactions called it DEAD from two different page states. Nine
   member cards are what the page itself carries, and inventing a tenth practitioner is exactly the
   thing this project must never do, so the button is replaced by a sentence that tells the visitor
   what is on the page and how to reach the association. 17px matches .o5-legal, the body measure
   used by the authored pages.
   -------------------------------------------------------------------------------------------- */
.gaf-dir-note {
  max-width: 46em; margin: 8px auto 0; padding: 0 16px; text-align: center;
  font-size: 17px; line-height: 1.5; color: #2f2f2f;
  font-family: futura-lt-w01-light, futura-lt-w05-light, sans-serif;
}
.gaf-dir-note a { color: #17629f; text-decoration: underline; }

/* --------------------------------------------------------------------------------------------
   U. THE TWO REASONS THE PHONE LAYOUT STILL OVERLAPPED ITSELF
   --------------------------------------------------------------------------------------------
   Section W turns each Wix mesh grid into a flex column, which is the right shape for 390px. Two
   things it did not do meant the reflowed blocks still landed on top of each other, and the proof
   was not subtle: at 390 the homepage printed "...promouvoir la gestalt dans la région du Grand
   Genève" and "Aujourd'hui, le Galf soutient un projet ouvert" in the same 51 pixels, and did the
   same to "Les statuts du Galf" over Stéphane Trémelot's bio and to Isabelle Inzerilli's bio over
   the "Contactez-nous" heading. Measured with _scripts/_gaf_overlap.js, which reports every pair
   of text blocks whose boxes intersect; it found 3 pairs on / and 1 on /liste-des-membres/.

   U1. NEGATIVE VERTICAL MARGINS. Wix places a mesh child with BOTH grid-area and margin, so on the
   desktop grid a margin is decoration - the row decides the position and a designer nudging a
   block upward can write `margin: 0 0 -94px 0` with nothing colliding. In a flex column the margin
   IS the layout, and that -94px drags the next block 94 pixels up through the paragraph above it.
   Section W zeroes margin-left/right (the 980px centring trick) and left the vertical ones alone.
   Only the BOTTOM is neutralised and only on the seven components that carry a negative one:
   the positive margins are the page's vertical rhythm and blanket `margin: 0` would stack every
   block edge to edge. Re-derive the list after any rebuild with _scripts/_gaf_negmargin.py.

   U2. ANCESTORS WITH A DESKTOP HEIGHT. Section W sets height:auto on the grid container and on its
   direct children, but every WRAPPER between them keeps the pixel height the desktop mesh gave it:
   #comp-j9msknf4 was 1839px around a column that needed 2012px, so the section ENDED 173px inside
   its own content and the contact section started there. Same for the .KaEeLN boxes, the .V5AUxf
   section wrapper and the contact <form>. `:has(> [data-mesh-id$="inlineContent"])` picks exactly
   the divs that wrap a mesh rather than every div in the page, so image and video components keep
   the explicit heights they need.
   -------------------------------------------------------------------------------------------- */
@media (max-width: 1023px) {

  /* U1a - the seven mesh CHILDREN, listed by _scripts/_gaf_negmargin.py */
  #comp-kiepx5xe, #comp-l292x7ul1, #comp-k2oh8rkh, #comp-k2orensh,
  #comp-k06h68p3, #comp-j9mvftl1, #comp-k207aauw { margin-bottom: 0 !important; }

  /* U1b - AND THE CONTAINERS THEMSELVES, which is where the two worst ones were. The section
     "Le Galf et vous" carries margin-bottom:-333px on its own grid container and the team section
     carries -173px; on the desktop grid those pull the NEXT section up into the whitespace this
     one deliberately left, and reflowed they pull it up into the TEXT. -333 and -173 are exactly
     the overlaps measured on the page. Every margin declared on any mesh container in all nine
     pages is negative (measured: -220px x18, -333px, -173px, -7px), so zeroing both vertical
     margins on the containers takes away nothing the layout uses. Section W already did the
     margin-top half for the navigation's -220px; this is the other half. */
  [data-mesh-id$="-gridContainer"], [data-mesh-id$="inlineContent"] {
    margin-top: 0 !important;
    margin-bottom: 0 !important;
  }

  /* U2 */
  section[id^="comp-"],
  div[id^="comp-"]:has(> [data-mesh-id$="inlineContent"]),
  form[id^="comp-"]:has(> [data-mesh-id$="inlineContent"]),
  [data-mesh-id$="inlineContent"],
  [data-mesh-id$="-gridContainer"],
  .KaEeLN, .uYj0Sg, .V5AUxf {
    height: auto !important;
    /* NOT min-height:0. Every one of these is a flex ITEM of the wrapper above it, and section W
       already hands them `min-height: 0`, which is precisely the permission a flex item needs to
       shrink BELOW its own content - which is what they did: #comp-j9msknf4 settled at 1857px
       around 2197px of content. fit-content is the floor that says "never smaller than what is
       inside you", and flex-shrink:0 stops the parent asking. */
    min-height: fit-content !important;
    flex-shrink: 0 !important;
  }
}

/* --------------------------------------------------------------------------------------------
   V. THE TWO WIX COMPONENT FAMILIES THAT COLLAPSE TO ZERO HEIGHT AT 390
   --------------------------------------------------------------------------------------------
   Measured with _scripts/_gaf_vec.js, which renders the same page at 1440 and 390 and prints each
   component's box next to the box of the <svg> or <wow-image> inside it. A Wix VectorImage and a
   Wix ImageButton both get their size from an explicit pixel height in the desktop CSS and hold a
   child at height:100%. Section W's `height: auto` on every mesh child removes that height, the
   child resolves 100% of nothing, and the component becomes a 390x0 box - while the artwork
   inside, which has its own viewBox and preserveAspectRatio="none", goes on painting at its
   natural size OUTSIDE the empty box.

   That is where the phone header's giant navy shape came from: #comp-ja6kx58i is 614x73 at 1440
   and 390x0 at 390, with its <g> still drawing 549x153 over the GALF wordmark and the nav. Seven
   more of them are the coloured panels behind the team bios, and three are 10x10 dots.

   V1. THE VECTORS ARE DECORATION AND COME OUT. Every .wixui-vector-image on all nine pages was
   checked for a link, an aria-label and text content (_scripts/_gaf_vec2.js): all 14 are empty
   ornament. Reflowed into a one-column layout they would be full-width blocks of flat colour with
   nothing in them - the "empty placeholder block" the client rejects - so at phone widths they are
   removed rather than resized. Nothing readable and nothing clickable is lost.

   V2. THE IMAGE BUTTONS ARE LINKS AND MUST SURVIVE. The same collapse hit .wixui-image-button,
   and those are not ornament: #comp-k06hcq46 is the envelope that downloads "Les statuts du Galf",
   #comp-kifoazmd goes to /virement-bancaire/ and #comp-k2orlndb opens a mail to the association.
   At 390 all three were 390x0 - present, aimed correctly, and impossible to see or press. They get
   their intrinsic size back, centred, with the image contained rather than stretched.
   -------------------------------------------------------------------------------------------- */
@media (max-width: 1023px) {

  /* V1 */
  .wixui-vector-image { display: none !important; }

  /* V2 */
  .wixui-image-button {
    height: auto !important;
    width: auto !important;
    max-width: 100% !important;
    margin-left: auto !important;
    margin-right: auto !important;
    text-align: center !important;
  }
  .wixui-image-button > a, .wixui-image-button > a > div {
    display: inline-block !important;
    height: auto !important;
    width: auto !important;
  }
  .wixui-image-button wow-image {
    position: relative !important;
    display: inline-block !important;
    height: auto !important;
    width: auto !important;
    max-width: 100% !important;
  }
  /* more specific than W3's `wow-image img{width:100%}`, which would blow a 113px envelope up to
     the full width of the screen */
  .wixui-image-button wow-image img {
    position: static !important;
    width: auto !important;
    height: auto !important;
    max-width: 140px !important;
    object-fit: contain !important;
  }
  /* R3 (independent review, 2026-08-19): three image-button links still rendered 0x0 below 1024
     even with V2 applied. The wrapper Wix puts between the <a> and the <wow-image> - class
     .PRnra1 - is `position: absolute` in the page's own inline stylesheet (it fills the button's
     fixed-pixel desktop box by inset, not by flow). V2 frees the OUTER box to size:auto, but an
     absolutely-positioned child is excluded from a shrink-to-fit width calculation, so once the
     outer box has nothing else in normal flow to measure, its content-based width resolves to 0
     and drags <a> and the outer div down with it - even though the <img> itself now has a correct
     73-124px intrinsic size two levels further in. Putting the wrapper back in flow lets that size
     reach the ancestors. Measured with _scripts/_gaf_r3_chain.js: 0px at every level before this
     rule, 73px/124px/(statutes envelope) after it, at 768 and 390 on / and /devenir-membre/. */
  .wixui-image-button .PRnra1 {
    position: static !important;
    height: auto !important;
    width: auto !important;
    display: inline-block !important;
  }
}

/* --------------------------------------------------------------------------------------------
   V3. THE LAST FLOATING ORNAMENT: "retrouvez-nous sur Facebook"
   --------------------------------------------------------------------------------------------
   Section W5b caught #comp-j9o8autn-pinned-layer (the Facebook ICON) and every [id^=pagePinned...]
   layer, and made .big2ZD flow. It did not catch #pinnedBottomLeft, a SECOND pinned wrapper inside
   <footer>, nor the caption inside it: #comp-k09ko2ov is position:absolute with top:-124px, so at
   390 the words "retrouvez-nous sur Facebook" floated 124 pixels up out of the footer and printed
   across the last two cards of the video list (measured by _scripts/_gaf_overlap.js: 110x54px of
   real overlap on /liste-des-membres/).

   It is a genuine link the association published - qa_client_bar counts it among the site's
   outbound links - so it flows into the footer rather than being hidden, which is also where a
   visitor scrolling a phone expects to find it.
   -------------------------------------------------------------------------------------------- */
@media (max-width: 1023px) {
  #pinnedBottomLeft, #pinnedBottomLeft > div {
    position: static !important;
    height: auto !important;
    width: 100% !important;
  }
  #pinnedBottomLeft [id^="comp-"] {
    position: static !important;
    top: auto !important; left: auto !important; right: auto !important; bottom: auto !important;
    height: auto !important;
    width: 100% !important;
    /* border-box, or `width:100%` plus 16px of side padding is 422px of document against a 390px
       window - which is sideways scroll, the exact defect this whole section exists to remove.
       Measured: scrollWidth went 392 -> 422 on six pages the first time this rule shipped. */
    box-sizing: border-box !important;
    text-align: center !important;
    padding: 14px 16px 0 !important;
  }
}

/* --------------------------------------------------------------------------------------------
   V4. THE FLOATING BADGE NEEDS A WIDER BREAKPOINT THAN THE REFLOW DOES
   --------------------------------------------------------------------------------------------
   The mesh reflow starts at 1023px because that is where a one-column layout becomes the right
   answer. The two floating ornaments have a different threshold: they live in the gutter beside
   the site's 980px column, and that gutter is (viewport - 980) / 2 - only 22px at 1024 and 110px
   at 1200, against a badge 110px wide. Measured at 1024 the caption printed across the video cards
   again, exactly as it did at 390; measured at 1440 it does not. So the ornaments flow below
   1200px while everything else keeps the desktop mesh until 1023. Checked at 1024, 1100, 1199 and
   1200 with _scripts/_gaf_overlap.js.
   -------------------------------------------------------------------------------------------- */
@media (max-width: 1199px) {
  #comp-j9o8autn-pinned-layer { display: none !important; }
  #pinnedBottomLeft, #pinnedBottomLeft > div,
  #pinnedBottomLeft [id^="comp-"] {
    position: static !important;
    top: auto !important; left: auto !important; right: auto !important; bottom: auto !important;
    height: auto !important;
    width: 100% !important;
  }
  #pinnedBottomLeft [id^="comp-"] {
    box-sizing: border-box !important;
    text-align: center !important;
    padding: 14px 16px 0 !important;
  }
}

/* --------------------------------------------------------------------------------------------
   V5. THE 1024-1037px BAND: "devenir membre" HANGS 7px OFF THE RIGHT EDGE
   --------------------------------------------------------------------------------------------
   Pre-existing, not introduced by the reflow: the header's "devenir / membre" link is placed at
   `left: 879px` on top of `margin-left: calc((100% - 980px) * 0.5)`, i.e. it deliberately sits in
   the right-hand gutter beside the site's 980px column. The gutter is 230px at 1440 and 22px at
   1024, so the 130px block ends at 1031 in a 1024px window and the whole document scrolls
   sideways. Solving 22 + 879 + 130 <= viewport gives viewport >= 1038, so the band is exactly
   1024-1037px - just below it the mesh reflow takes over and just above it the gutter is wide
   enough. Inside the band the block is pinned to the right edge of its own grid cell instead,
   which keeps it in the same corner of the header and inside the window.
   Measured with _scripts/_gaf_width.js, which reports scrollWidth against innerWidth per page.
   -------------------------------------------------------------------------------------------- */
@media (min-width: 1024px) and (max-width: 1037px) {
  #comp-kiepx5xe, #comp-kiepx5zv {
    justify-self: end !important;
    left: 0 !important;
    margin-left: 0 !important;
    margin-right: 10px !important;
  }
}

/* --------------------------------------------------------------------------------------------
   V6. THE SUBMIT BUTTON WAS 390x0 ON A PHONE — ON BOTH FORMS
   --------------------------------------------------------------------------------------------
   The worst instance of the same collapse as V2, and the one a visitor pays for. A Wix SiteButton
   is a <button> at height:100% inside a component div whose pixel height the desktop CSS supplies;
   section W removes that height and the button becomes a 390x0 box. Measured with
   _scripts/_gaf_btn.js: "envoyer" is 147x40 at 1440 and 390x0 at 390 on /, and "Envoyer" is 200x50
   at 1440 and 390x0 at 390 on /devenir-membre/. Both forms were unsendable from a phone, and no
   gate saw it - qa_interactions clicks through the DOM and got its observable change, and
   qa_legibility skips a zero-height box because a box with no area has no text to measure.

   The full list of components that are alive at 1440 and 0px tall at 390 is printed by
   _scripts/_gaf_collapsed.js; everything else on it is either ornament this stylesheet removes on
   purpose (the vector images, the anchor rail, the pinned Facebook badge) or an anchor target that
   is meant to have no height.

   44px, not the desktop 40px: that is the minimum touch target, and the button is the one control
   on the page that must never be missed.
   -------------------------------------------------------------------------------------------- */
@media (max-width: 1023px) {
  div[id^="comp-"]:has(> button.wixui-button),
  div[id^="comp-"]:has(> a.wixui-button) {
    height: auto !important;
    min-height: 0 !important;
  }
  .wixui-button {
    /* `.FubTgk .uDW_Qe{position:absolute}` is why giving the button a height was not enough on its
       own: an absolutely positioned child contributes nothing to its parent's auto height, so the
       wrapper stayed 0 and the button hung over whatever followed it. Static puts it back in the
       flow, and the auto side margins then centre it. */
    position: static !important;
    height: auto !important;
    min-height: 44px !important;
    width: auto !important;
    min-width: 150px !important;
    padding: 11px 26px !important;
    box-sizing: border-box !important;
    margin-left: auto !important;
    margin-right: auto !important;
  }
}

/* --------------------------------------------------------------------------------------------
   V7. "More" WAS STILL IN THE PHONE MENU, AND IT OPENS NOTHING
   --------------------------------------------------------------------------------------------
   Sections N and W4b both hide `li[id$="__more__"]` - Wix's overflow control, which on a static
   copy is a sixth menu item that does nothing at all - and both were losing the cascade. Among
   !important declarations specificity still decides, and W4b's own sibling rule
   `wix-dropdown-menu nav[id$="navContainer"] > ul > li` is (0,1,4) - four type selectors plus one
   attribute - against (0,1,2) for `wix-dropdown-menu li[id$="__more__"]`. So `display: block`
   won and "More" was painted on every page below 1024px, which is what the phone screenshots
   showed. Asking the engine (CSS.getMatchedStylesForNode, via _scripts/_gaf_matched.js) is what
   found it; reading the stylesheet said the rule was there and looked correct.

   Matching the losing rule's own shape, plus the attribute, puts it at (0,2,4) and it wins.
   -------------------------------------------------------------------------------------------- */
wix-dropdown-menu nav[id$="navContainer"] > ul > li[id$="__more__"],
wix-dropdown-menu nav[id$="navContainer"] > ul > li[data-index="__more__"],
wix-dropdown-menu nav[id$="navContainer"] > ul > li.p90CkU,
wix-dropdown-menu > nav > ul > li[id$="__more__"],
wix-dropdown-menu > nav > ul > li[data-index="__more__"],
wix-dropdown-menu > nav > ul > li.p90CkU { display: none !important; }

/* --------------------------------------------------------------------------------------------
   V8. "A revoir" IS CUT IN HALF BY THE FIRST VIDEO CARD
   --------------------------------------------------------------------------------------------
   The gallery's card grid `.comp-k088ci87-grid-layout-items` carries margin-top:-50px, a Wix
   ProGallery trick that cancels its own <main>'s 32px padding on the desktop. Section W11b turned
   that grid into block flow and left the margin, so at 390 the first card is painted at y=675 while
   its own gallery container starts at y=693 - 18px above where it belongs, and those 18px land
   across the descenders of the 40px "A revoir" heading above it. It is visible instantly in the
   screenshot and invisible to every measurement, including my own overlap probe, whose ">8
   characters of text" filter skips a heading that is exactly 8 characters long.

   Zeroing the margin puts the first card back inside its container. The heading also gets a little
   air under it so a rounding difference cannot bring the two back into contact.
   -------------------------------------------------------------------------------------------- */
@media (max-width: 1023px) {
  [class*="-grid-layout-items"] { margin-top: 0 !important; }
  #comp-k09ajosb { padding-bottom: 10px !important; }
}

/* --------------------------------------------------------------------------------------------
   V9. THE SCROLL RAIL PRINTS THROUGH THE TEXT ON ANY WINDOW NARROWER THAN 1280
   --------------------------------------------------------------------------------------------
   Section W5a hides the pinned anchor rail below 1024 because "at 390 there is no gutter, so the
   three dots and the one expanded label lie directly on top of the running text". The gutter is
   not a phone problem, it is an arithmetic one: the rail occupies x=6..178 whatever the window,
   and the site's 980px column starts at (viewport - 980) / 2, so the two only stop touching once
   the viewport passes 1280. Measured with _scripts/_gaf_rail.js, which reports the worst
   horizontal overlap between the rail and any body paragraph: 128px at 1024, 90px at 1100, 40px at
   1200, 0px from 1280 up. A 13-inch laptop at 1280 is the first width that is safe; everything
   below it was showing the same defect the phone showed.

   The rail is a scroll-spy whose labels only appear on hover and whose three targets are the same
   three anchors the site menu already carries, so removing it below 1280 costs no navigation.
   /liste-des-membres/ pins a second copy of "accueil" the same way; it goes with it, and the menu
   above it says "accueil" too.
   -------------------------------------------------------------------------------------------- */
@media (max-width: 1279px) {
  [id^="pagePinnedMiddleLeft"],
  .wixui-anchor-menu,
  [id^="comp-"][id$="-pinned-layer"]:has(.wixui-anchor-menu),
  #comp-k09l8ebx-pinned-layer { display: none !important; }
}

/* --------------------------------------------------------------------------------------------
   V10. THE MEMBER-DIRECTORY NOTE WAS CUT OFF MID-SENTENCE — AT 1440 AS WELL AS AT 390
   --------------------------------------------------------------------------------------------
   Section T replaced the dead "tous les membres" button with a sentence explaining what the page
   holds. The button was 30px tall and its container .ClVdIo is `height: 40px`, inside a gallery
   component pinned at `height: 600px` by the desktop CSS - so the replacement sentence (102px at
   1440, 179px at 390) ran straight out of the bottom of the section and the reader saw
   "...l'annuaire n'est plus tenu à" and then a band of empty page. Exactly the failure the client
   keeps reporting, and produced by a fix rather than by the archive: a text block put where the
   platform had reserved room for a button.

   No media query: the clipping happened at every width, because the height that causes it is the
   desktop one. The section, its mesh wrappers, the gallery component and .ClVdIo all size to their
   content; the 3x3 card grid keeps its own dimensions and does not move.
   -------------------------------------------------------------------------------------------- */
#comp-lhgfbq8j1,
#comp-lhgfbq8j1 > div,
[data-mesh-id="comp-lhgfbq8j1inlineContent"],
[data-mesh-id="comp-lhgfbq8j1inlineContent-gridContainer"],
#comp-k08emw2d,
.ClVdIo {
  height: auto !important;
  min-height: 0 !important;
}
.ClVdIo { padding-bottom: 8px; }

/* --------------------------------------------------------------------------------------------
   V11. THE MEMBER DIRECTORY SHOWED NINE PHOTOGRAPHS AND NOT ONE WHOLE NAME
   --------------------------------------------------------------------------------------------
   The Wix ProGallery lays the nine cards out as a wrapping flex row of fixed-width items and does
   not re-measure for the viewport on a static copy. At 390 each card is 120px wide, the title
   inside it is 92px, and the title is `white-space: nowrap; text-overflow: ellipsis`, so the page
   read "Pierre Bez...", "Catherine ...", "Catherine ...", "Daniel Cor...", "Madina Fa..." - the
   listing-with-no-headlines the client rejected on the Portuguese batch.

   TWO EARLIER ATTEMPTS AT THIS RULE MADE IT WORSE, and both failures are the same mistake: this
   component's geometry is computed, not declared, and every `height: auto` or `overflow: visible`
   handed to it is a licence to fall apart.
     * `overflow: visible` on the card panel released the clip that hides each member's full bio -
       qualifications, telephone, address - and printed nine of them on top of each other and on
       top of the photographs.
     * `height: auto` on the card itself collapsed the image containers, which hold the photograph
       at height:100% of a box the gallery sizes itself.
   So nothing here is auto and nothing is un-clipped. The card, its panel and its caption line get
   EXPLICIT larger pixel heights - 120px of photograph is unchanged, the panel goes from 52 to 78
   and the caption from 24 to 46, which is two lines at the site's own 14px - and the title is
   allowed to wrap inside that fixed box. The bio stays clipped and stays one tap away in the
   lightbox that gaf-restore.js restores.
   -------------------------------------------------------------------------------------------- */
@media (max-width: 1023px) {
  .QECzyz .r_b9iO, .QECzyz .TbvjZ9 { height: 200px !important; }
  .QECzyz .MogyzS { height: 78px !important; }
  .QECzyz .Lg6He_ { height: 46px !important; }
  .QECzyz .lzZozY {
    white-space: normal !important;
    text-overflow: clip !important;
    height: auto !important;
    max-height: 46px !important;
    line-height: 1.2 !important;
    font-size: 13px !important;
  }
  /* The taller caption line exposes the first line of the BIO under the name, and the panel clips
     it mid-word ("Gestalt-", "Conseillere en insertio"). The bio was never readable on the card at
     any width - it is what the lightbox is for - so it comes out of the card rather than being
     shown as a fragment. */
  .QECzyz .qz0vq6 { display: none !important; }
}

/* V11b. The letterbox under six of the nine portraits. Section W3 gives every reflowed image
   `object-fit: contain`, which is right for a photograph that has to keep its shape inside a box
   the reflow just changed - and wrong for a gallery thumbnail, whose box IS the design. At 390 the
   portraits sat in the top of a 120px box with a band of the gallery's dark fill under each one;
   at 1440 the same cards are full-bleed because Wix's own rule says cover. Scoped to this gallery,
   so W3's choice still holds everywhere else. */
@media (max-width: 1023px) {
  .QECzyz wow-image img, .QECzyz img {
    object-fit: cover !important;
    height: 100% !important;
    width: 100% !important;
  }
}

/* --------------------------------------------------------------------------------------------
   R2. THE CONTACT HEADING PRINTED AFTER THE CONTACT DETAILS IT INTRODUCES (independent review,
   2026-08-19, gestalt-a-la-frontiere.org rework pass)
   --------------------------------------------------------------------------------------------
   In document order the homepage's "Pour nous joindre" heading (#comp-j9msqyka) comes AFTER the
   address/phone/e-mail block it labels (#comp-j9zc8hd9): both are children of the same mesh
   gridContainer, #comp-lhgfbq923inlineContent-gridContainer, laid out at desktop with an absolute
   `left`/`top` per child, so the heading paints above the details there (measured tops 4145 vs
   4211 at 1440) and the wrong DOM order is invisible. Section W2 turns that grid into a flex
   column and drops left/top, so below 1024px the column follows DOM order and reads
   "Gestalt à la frontière / Tél. ... / email ..." THEN "Pour nous joindre" - the section title
   after its own content, on every phone and every tablet width. Verified with the DOM
   getBoundingClientRect of both ids at 768 and 390: heading below details before this rule,
   heading above details after it.

   The container also holds a horizontal rule (#comp-k06pjewf) and two decorative vector images
   that V1 already hides below 1024; giving the two TEXT components explicit order values (leaving
   everything else at the implicit order:0) reproduces the desktop reading order for what is still
   visible - rule, then heading, then details - without touching components this defect does not
   concern. Homepage-only ids, grepped against every other built page first. */
@media (max-width: 1023px) {
  #comp-j9msqyka { order: 1 !important; }
  #comp-j9zc8hd9 { order: 2 !important; }
}

/* --------------------------------------------------------------------------------------------
   R4. ONE MEMBER'S NAME WAS STILL TRUNCATED ON DESKTOP (independent review, 2026-08-19)
   --------------------------------------------------------------------------------------------
   V11's two-up wrap fixed every card below 1024; at 1440 and 1024 the caption keeps
   white-space:nowrap + ellipsis and "Catherine Geandreau-Sanchez" is the one name (of nine) whose
   text is wider than its box: box 208px, text 217px, measured with a live DOM query of
   .lzZozY.scrollWidth on /liste-des-membres-1/. Letting it wrap was rejected the way V11's own
   comment rejects overflow:visible on this component: the caption's box (.Lg6He_) is
   position:absolute, INSET 14px on all four sides of its 52px-tall panel (var(--paddingSize)),
   so a second line would need ~20 more px of height than the panel has spare before its own
   overflow:hidden starts clipping it - the exact failure V11 already paid for once.

   The panel is 236px wide and the box only needs 9 more px, and there IS width to spare: cutting
   the LEFT/RIGHT inset from 14px to 6px (top/bottom untouched, so the box's vertical position and
   height are unchanged) widens it from 208px to 224px - clears the longest name with room to
   spare and does nothing visible to the other eight, whose text was already centered well inside
   208px. Scoped to min-width:1024px so the already-verified V11 mobile treatment is untouched. */
@media (min-width: 1024px) {
  .QECzyz .Lg6He_ { left: 6px !important; right: 6px !important; }
}

/* --------------------------------------------------------------------------------------------
   O7. ORDER-7 VISUAL REVIEW, 2026-10-14 - five defects seen in the screenshot ladders
   --------------------------------------------------------------------------------------------
   O7a. THE FOOTER FONT EXISTED ON ONE PAGE OUT OF NINE. .gaf-footer-nav, .gaf-dir-note and the
   contact confirmation ask for futura-lt-w01-light, but only index.html declares that face (the
   Wix head of the other eight declares Futura-LT-W01-Book instead). Everywhere but the homepage
   the footer navigation and the member-directory note fell back to the system sans-serif - visibly
   a different, heavier type from the homepage's footer (_shots/o7_*: home-d5 vs devenir_membre-d2,
   liste_des_membres_1-d1). The face is declared once here, from the same two files index.html
   already ships, so every page that loads this sheet has it. */
@font-face {
  font-family: "Futura-LT-W01-Light";
  src: url("/fonts/26091050-06ef-4fd5-b199-21b27c0ed85e-d82d2e11.woff2") format("woff2"),
       url("/fonts/cca525a8-ad89-43ae-aced-bcb49fb271dc-b29296d8.woff") format("woff");
  font-display: swap;
}

/* O7b. THE WORDMARK IS NOT PROSE. Section L4 (`.wixui-rich-text a { text-decoration: underline }`)
   exists for links inside running text, and it also caught the header's "GALF" - a 47px heading
   link whose 0.3em letter-spacing makes the underline run on past the F ("G A L F _"). The archived
   page has no underline on it (raw home_20241106: the <a> carries no underline span, and Wix's own
   reset sets a{text-decoration:none}). qa_legibility's flat-link check reads `p a, li a, td a`
   only, so a heading link is outside what it judges; L4 stays as it is for everything else. */
#SITE_HEADER h1 a.wixui-rich-text__text { text-decoration: none; }

/* O7c. AN EMPTY 400px BAND ON /liste-des-membres-1/. Section #comp-lhgfbq8k holds one column
   strip whose only column (#comp-l1t4ojjs, overlay rgb(250,250,250)) has an EMPTY mesh and
   min-height:400px - whatever widget once lived there is not in the capture. At 1440 it painted a
   full-width off-white slab between the member grid and the footer with nothing in it (slice
   liste_des_membres_1-d1). Below 1024 section W already collapses it to nothing; this removes it at
   every width. Page-unique id, grepped across all nine pages. */
#comp-lhgfbq8k { display: none !important; }

@media (max-width: 1023px) {
  /* O7d. THE PHONE HEADER SPENT A WHOLE SCREEN ON WHITESPACE. On the desktop the wordmark, the
     strapline and the corner brackets share ONE grid cell (grid-area 1/1/2/2) and their
     margin-tops (70px, 83px) are offsets inside that shared cell, not gaps between blocks; their
     margin-bottoms (55px, 61px on the inner pages) only size the cell. Stacked by section W they
     became 138px of air between "GALF" and "Gestalt a la frontiere" and another ~90px before
     "devenir membre", so on devenir-membre, liste-des-membres, neurosciences, the two policies and
     the 404 the first 760px of an 844px phone screen were header (slices *-p0). A plain rhythm. */
  [data-mesh-id="SITE_HEADERinlineContent-gridContainer"] > * {
    margin-top: 10px !important;
    margin-bottom: 10px !important;
  }

  /* O7e. FORM LABELS AGAINST THE GLASS. Section W7 pads rich text by 16px but the form controls
     are not rich text, so on a phone "Prenom", "Nom de famille", the radio buttons and every
     underline of the membership form started at x=0, flush with the screen edge
     (devenir_membre-p1, -p2). Same 16px inset as the text around them. */
  .wixui-form .wixui-text-input,
  .wixui-form .wixui-text-box,
  .wixui-form .wixui-radio-button-group {
    padding-left: 16px !important;
    padding-right: 16px !important;
    box-sizing: border-box !important;
  }
}

/* --------------------------------------------------------------------------------------------
   H. THE THREE TEAM ENTRIES WITH NO BIO  (/ homepage, "L'equipe du Galf")
   --------------------------------------------------------------------------------------------
   Catherine Gendreau Sanchez, Gregory Paille and Nicolas Reichel are a name and a colon in the
   archived homepage too: the bios never existed, so there is nothing to restore and the names
   stay. Each sat on a large pink panel (a Wix vector image placed behind the text), which made a
   big empty box. The panel is dropped for these three only, so each reads as a list entry. The
   panels are siblings positioned in the same grid cell, so hiding them moves nothing else; the
   four complete cards keep theirs. Decision: _recon/order7/DECISIONS_fr.md section C. ---------- */
#comp-k06j6hkj, #comp-lp8blfba, #comp-k06js9pd { display: none !important; }
