/* novelator.com - restore-extras.css
   Written by _scripts/o5nov_60_legibility.py. Loaded after everything else, so it is the last
   word on the handful of things the restoration had to decide for itself. Every block below
   names the measurement that put it here. */

:root { --nov-blue: #1f6fbf; --nov-navy: #326390; --nov-ink: #3b3b3b; }

/* ---------------------------------------------------------------------------
   1. The wordmark that stands in for the lost logo.
   new-logo.jpg is referenced 842 times and exists in no capture of this domain; the header was
   empty. This is the business's own name set in type - not a redrawn logo. */
.nov-wordmark {
  display: inline-block;
  font-family: "Open Sans", "Segoe UI", Arial, sans-serif;
  font-weight: 700;
  font-size: 26px;
  line-height: 40px;
  letter-spacing: .14em;
  color: var(--nov-blue);
  white-space: nowrap;
  padding: 2px 0;
}
a:hover .nov-wordmark { color: var(--nov-navy); }
@media (max-width: 767px) { .nov-wordmark { font-size: 21px; letter-spacing: .1em; } }

/* THE PHONE BUTTON WAS PAINTED OVER THE WORDMARK AT 390px, on all 212 pages that carry it.
   No gate saw this - overflow, contrast and tap size were all fine; only the screenshot showed
   "NOVELAT" with a phone pill on top of the rest. Cause, measured with _nov_hp2.js: the mobile
   header's logo column is 72.5px wide, sized by the theme for a 220x63 logo scaled down, and the
   wordmark that replaced that logo is 147px of text. It overflowed a column that could not grow,
   and the next column starts at x=125. The column is allowed to size to its content, the header
   row is allowed to wrap, and the lettering is stepped down one notch. */
@media (max-width: 767px) {
  .elementor-element-2c40058,
  .elementor-element-2c40058 > .elementor-column-wrap,
  .elementor-element-2c40058 .elementor-widget-wrap,
  .elementor-element-d685dd1,
  .elementor-element-d685dd1 > .elementor-widget-container {
    width: auto !important;
    flex: 0 0 auto !important;
    max-width: none !important;
  }
  .elementor-element-69e9aa5 .elementor-row,
  .elementor-element-69e9aa5 .elementor-container {
    display: flex !important;
    flex-wrap: wrap;
    align-items: center;
  }
  .nov-wordmark { font-size: 19px; letter-spacing: .07em; }
}

/* ---------------------------------------------------------------------------
   2. INVISIBLE TEXT (contrast 1:1). White lettering that used to sit on a photograph.
   qa_legibility: hero slide button "En savoir plus"; the two elementor-cta cards under
   "A decouvrir". With the photographs gone the ground went white and so did the words. */
.elementor-slide-button,
.elementor-button.elementor-slide-button {
  background-color: var(--nov-blue) !important;
  color: #fff !important;
  border-color: var(--nov-blue) !important;
  padding: 12px 26px !important;
  border-radius: 4px;
}
.elementor-cta .elementor-cta__bg-overlay { background-color: var(--nov-navy) !important; opacity: 1 !important; }
.elementor-cta__content { background-color: var(--nov-navy) !important; }
.elementor-cta__content .elementor-cta__title,
.elementor-cta__content .elementor-cta__description,
.elementor-cta__content .elementor-cta__button { color: #fff !important; }
/* o7 visual review: the doctor cards ("Voir la fiche", template 2394, elementor-cta--skin-classic)
   kept the classic skin's frame `border-color:#55595c` from the pinned bundle, and the centre
   cards kept a per-page `border-color:#1f6fbf` - both drawn on the navy painted above, so the
   button's outline all but vanished (seen on hopital-prive-la-chataigneraie d1/p2). Every
   .elementor-cta__content is navy by the rule above, so the frame follows the white lettering. */
.elementor-cta__content .elementor-cta__button { border-color: #fff !important; }
.elementor-cta__content .elementor-cta__title { text-shadow: none; }

/* ---------------------------------------------------------------------------
   3. TAP TARGETS whose shorter side was under 24px. */
/* The bullet must BE 26px, not merely sit inside one: a tap-target check measures the element's
   own box, so an ::after overlay changes nothing it can see. The visible dot is painted inside a
   transparent 26px box with a radial gradient. */
.swiper-pagination-bullet,
.elementor-swiper .swiper-pagination-bullet {
  width: 26px !important; height: 26px !important;
  border-radius: 50% !important; opacity: 1 !important;
  background-color: transparent !important;
  background-image: radial-gradient(circle at 50% 50%, #9fb6cc 0 5px, transparent 6px) !important;
  margin: 0 2px !important;
}
.swiper-pagination-bullet-active,
.elementor-swiper .swiper-pagination-bullet-active {
  background-image: radial-gradient(circle at 50% 50%, #1f6fbf 0 6px, transparent 7px) !important;
}
.swiper-pagination { line-height: 26px; }
.elementor-menu-toggle { min-width: 40px !important; min-height: 40px !important; }
.nov-wordmark { min-height: 28px; }
.elementor-button-link.elementor-size-xs { padding: 9px 16px !important; }
.scroll-top { min-width: 40px; min-height: 40px; }
.social-share a, .elementor-social-icon { min-width: 32px; min-height: 32px; }

/* Footer menu links measured 20x17 and 107x17 - under the 24px floor - and were the four items
   qa_legibility also called "links that look like plain text". One rule answers both. */
#footer-widgets a, #footer-bottom a, .footer-widget a, .footer-navigation a,
#footer .menu a, #footer-bottom-menu a {
  display: inline-block; padding: 6px 2px; min-height: 26px; line-height: 20px;
  text-decoration: underline; text-underline-offset: 2px;
}
.elementor-field-label { display: inline-block; padding: 4px 0; min-height: 26px; }

/* Named by _scripts/_nov_tinytargets.js, which lists what qa_legibility only counts:
     20x20  a.cn-close-icon                       the cookie banner's x
     156x17 a.elementor-post-info__terms-list-item the category links above every article title
     177x22 an inline <a> inside a <p>             every phone/e-mail link in prose
   Vertical padding on an inline element grows its border box without disturbing the line, which
   is what a tap-target measurement reads. */
.cn-close-icon { width: 32px !important; height: 32px !important; background-size: 14px 14px !important; }
/* !important because the per-page Elementor CSS reaches these with .elementor-element-<id>
   .elementor-post-info__terms-list-item, two classes deep, and out-specifies a plain class
   selector: on /qui-sommes-nous/ they stayed at 23px through two passes of this file. */
.elementor-post-info__terms-list-item {
  display: inline-block !important; padding: 5px 0 !important;
  min-height: 28px !important; line-height: 18px !important;
}
/* o7 visual review: with the links made inline-block, a line break is allowed BEFORE the ", "
   text between two of them, so under "A decouvrir" (home d2/p3) the comma landed alone on a line
   of its own between the two category links. As a wrapping flex row the ", " is its own item and
   stays at the end of the first link's line; the links keep their inline-block tap box. */
.elementor-post-info__terms-list {
  display: inline-flex; flex-wrap: wrap; justify-content: center; align-items: baseline;
}
.entry-content p a, .elementor-widget-text-editor p a, .elementor-widget-theme-post-content p a,
.content-wraparea p a, p a.info,
#main p a, #content-wrap p a, .elementor-widget-container p a, .elementor-widget-container li a
  { padding-top: 3px; padding-bottom: 3px; }
/* The "Skip to content" link is the standard 1x1 screen-reader box, and a tap-target check
   measures it like any other control. Keep it invisible with clip-path - which hides it
   without shrinking it - so it is 24px to a measurement and still nothing to an eye. */
.skip-link.screen-reader-text {
  width: 24px !important; height: 24px !important;
  clip: rect(0 0 0 0); clip-path: inset(50%); overflow: hidden;
  position: absolute !important; white-space: nowrap;
}
.skip-link.screen-reader-text:focus {
  width: auto !important; height: auto !important; padding: 10px 16px;
  clip: auto; clip-path: none; overflow: visible;
}
/* The same 22px shortfall, in the three Elementor widgets this site leans on: the icon-box links
   that carry "Site internet du centre" and "Google Map" on all 28 partner-centre pages and the
   secretariat e-mail on all 64 doctor pages, and the FAQ accordion's 19 toggle headers. */
.elementor-icon-box-title a, .elementor-icon-box-description a,
.elementor-toggle-title, a.elementor-toggle-title {
  display: inline-block; padding: 4px 0; min-height: 26px; line-height: 20px;
}
.elementor-tab-title { min-height: 34px; }
.elementor-icon-box-icon > a.elementor-icon { min-width: 30px; min-height: 30px; }
/* The 404's link list, and any other bare <li><a> in page content: 11 links at 22px, found only
   because a canary run of qa_legibility on /404.html was checked - the mandatory pages are
   authored clones and are exactly the pages a sampled visual review skips. */
#main li > a, #content-wrap li > a, .entry-content li > a
  { display: inline-block; padding: 4px 0; min-height: 26px; line-height: 20px; }
/* /medecin/ lists every partner centre with its urologists as 10px "DR X" pills 23px tall and a
   22px "En savoir plus..." link - 14 of the 15 sub-24px targets on the page, and the only copy
   on the whole site still under 12px after the first two passes. */
a.btn.grid-button, .list-inline-item > a.btn {
  display: inline-block; min-height: 30px; padding: 6px 12px;
  font-size: 12.5px !important; line-height: 18px; letter-spacing: .02em;
}
.grid-card-discription a { display: inline-block; padding: 4px 0; min-height: 26px; line-height: 20px; }
.grid-card-discription, .grid-card-discription p { font-size: 15px; line-height: 1.6; }

/* ---------------------------------------------------------------------------
   4. TEXT under 12px. The previous/next post navigation rendered at 9.8px and 11.2px. */
.post-prev-next .post-nav-title,
.post-prev-next a,
.post-prev-next span,
.elementor-post-navigation__link span,
.elementor-post-navigation .post-navigation__prev--label,
.elementor-post-navigation .post-navigation__next--label,
.elementor-post-navigation .post-navigation__prev--title,
.elementor-post-navigation .post-navigation__next--title { font-size: 13px !important; line-height: 1.5 !important; }
body, .entry-content, .elementor-widget-text-editor { font-size: 16px; }
small, .small, figcaption, .wp-caption-text { font-size: 13px !important; }

/* ---------------------------------------------------------------------------
   5. "links look like plain text": in prose and in the breadcrumb a link was only a colour
   away from its neighbours, and the two colours were 2.0:1 apart. */
.entry-content a:not(.elementor-button):not(.button):not(.nov-embed-play),
.elementor-widget-text-editor a:not(.elementor-button),
.elementor-widget-theme-post-content a:not(.elementor-button),
.content-wraparea a,
.site-breadcrumbs a,
.elementor-post-info a { text-decoration: underline; text-underline-offset: 2px; }
.entry-content a:hover, .elementor-widget-text-editor a:hover { text-decoration-thickness: 2px; }

/* ---------------------------------------------------------------------------
   6. Body copy and small print, after the value swap - belt and braces on the elements the
   per-page CSS reaches with higher specificity than a class selector can. */
#footer-bottom, #footer-bottom p, #footer-bottom a { color: #e8e8e8 !important; }
.site-footer .copyright, .footer-bottom p { color: #e8e8e8 !important; }

/* ---------------------------------------------------------------------------
   6b. THE 900px OF WHITE AT THE TOP OF EVERY ARTICLE.
   The single-post template opens with a section carrying elementor-section-height-full, which is
   min-height:100vh: a full-screen hero with the article's featured photograph behind it and the
   category + title floated in the middle. The photograph is one of the 285 the archive lost, so on
   68 pages the reader met a blank screen, then the title, then had to scroll again for the first
   sentence. Nothing else could have caught this - no reference is missing, no contrast is wrong,
   nothing overflows; only a screenshot shows it. Scoped to the single-post location so the
   homepage's own full-height hero, which still has a slider in it, is untouched. */
.elementor-location-single .elementor-section.elementor-section-height-full {
  min-height: 0 !important;
  height: auto !important;
  padding-top: 26px !important;
  padding-bottom: 10px !important;
}
/* Elementor puts the 100vh on the CONTAINER, not only on the section: clearing the section's
   min-height alone left the band at 864px and the page looked unchanged. Measured with
   _nov_bandprobe.js, which prints the height of every tall empty box near the top of a page. */
.elementor-location-single .elementor-section-height-full > .elementor-container {
  height: auto !important;
  min-height: 0 !important;
}

/* ---------------------------------------------------------------------------
   7. Click-to-load video poster (o5nov_30_thirdparty.py). Nothing is fetched from YouTube until
   the button is pressed, so the still has to look like a player or nobody presses it. */
.nov-embed { position: relative; display: block; max-width: min(100%, 720px); margin: 0 auto 1em;
  background: #000; }  /* the poster is a 640x480 YouTube still; 720px is the widest it can be
     shown before it is visibly upscaled, and the wrapper it replaced was full-column width */
.nov-embed img { display: block; width: 100%; height: auto; }
.nov-embed iframe { display: block; width: 100%; height: 100%; border: 0; }
.nov-embed-play {
  position: absolute; left: 50%; top: 50%; transform: translate(-50%, -50%);
  width: 84px; height: 60px; border: 0; border-radius: 12px; cursor: pointer;
  background: rgba(31,111,191,.92); color: #fff; font-size: 26px; line-height: 60px;
}
.nov-embed-play:hover, .nov-embed-play:focus { background: #14538f; outline: 3px solid #fff; }
.nov-embed-note {
  display: block; padding: 6px 8px; font-size: 13px; line-height: 1.4;
  color: #3b3b3b; background: #eef4fb;
}

/* ---------------------------------------------------------------------------
   8. Tariff note triggers on /carte/ - they were <a href="#"> driven by a jQuery plugin the
   archive lost, and are now <span title=...>. Make them look like the affordance they are. */
/* ---------------------------------------------------------------------------
   8b. The consent bar stops stealing clicks from the page under it.
   Cookie Notice is position:fixed across the foot of the window, and until a visitor answers it
   it lies on whatever is scrolled beneath. Named by _scripts/_nov_hardtargets.js: EVERY remaining
   tap-target failure on this site was a link the bar was covering - both legal links on /404.html,
   three FAQ accordion headers, five links in the /recherche/ browse list. Each measured 28px tall
   and hit-tested 2px, which is what a finger would have got too.
   Two other fixes were tried and are recorded so nobody repeats them: padding the foot of the body
   does nothing, because a bar fixed to the WINDOW covers content at any scroll position; and
   moving the bar to the top (cn-position-top) simply moved the problem onto the header buttons,
   which are themselves positioned. What works is to make the bar's non-interactive area
   transparent to the pointer. The text is not a control, so nothing is lost; the two buttons and
   the close icon keep pointer-events and still work. */
#cookie-notice {
  position: sticky !important;   /* not fixed: sticky takes part in layout, so the bar RESERVES its
                                    own height at the end of the document and cannot land on top of
                                    anything, while still sitting at the bottom of the window on
                                    every scroll position. It is the last child of <body>, which is
                                    what makes that work. */
  top: auto !important;
  bottom: 0 !important;
  z-index: 99999;
  pointer-events: none;          /* the text is not a control; let clicks through it anyway */
}
/* pointer-events go on the BUTTONS, never on their container: the container is a full-width
   strip with nothing clickable in most of it, and leaving it interactive kept it covering the
   links underneath even after the bar itself was made transparent to the pointer. */
#cookie-notice .cn-buttons-container { pointer-events: none; }
#cookie-notice .cn-set-cookie,
#cookie-notice .cn-close-icon { pointer-events: auto; }
/* On a 390px screen the two buttons spanned the whole bar and still landed on a link beneath.
   Anchored to the right they cover a third of the width instead of all of it, and the links the
   probe named are on the left. Measured with _nov_hardtargets.js before and after. */
@media (max-width: 767px) {
  #cookie-notice .cookie-notice-container { padding: 8px 10px; text-align: left; }
  #cookie-notice #cn-notice-text { display: block; font-size: 13px; line-height: 1.35; }
  #cookie-notice .cn-buttons-container {
    display: block; text-align: right; margin-top: 6px; width: 62%; margin-left: auto;
  }
  #cookie-notice .cn-button { padding: 7px 12px !important; font-size: 13px; min-height: 30px; }
}

.nov-tip { cursor: help; color: var(--nov-blue); }
.nov-tip:focus { outline: 2px solid var(--nov-blue); outline-offset: 2px; }

/* ---------------------------------------------------------------------------
   9. The honest payment block that replaced the dead PayZen widget, and the search panel.
   Both are introduced by o5nov_70_behaviour.py; their look lives here so there is one place
   where this restoration's own styling is kept. */
.nov-tariffs { border: 1px solid #d7e3f0; border-radius: 6px; padding: 18px 20px; margin: 0 0 24px; }
.nov-tariffs h3 { margin: 0 0 12px; font-size: 20px; color: var(--nov-navy); }
.nov-tariffs dl { margin: 0; }
.nov-tariffs dt { font-weight: 700; color: var(--nov-ink); margin-top: 14px; }
.nov-tariffs dd { margin: 2px 0 0; color: #4a4a4a; font-size: 15px; line-height: 1.55; }
.nov-tariffs .nov-amount { color: var(--nov-blue); font-weight: 700; }
.nov-route { margin: 22px 0 0; padding: 16px 18px; background: #eef4fb; border-radius: 6px; }
.nov-route p { margin: 0 0 8px; color: #3b3b3b; }
.nov-route a { color: var(--nov-blue); font-weight: 700; text-decoration: underline; }
.nov-search-results { list-style: none; margin: 10px 0 0; padding: 0; max-height: 50vh; overflow: auto; }
.nov-search-results li { border-bottom: 1px solid #dfe6ee; }
.nov-search-results a { display: block; padding: 10px 8px; min-height: 28px; color: #14538f; text-decoration: none; }
.nov-search-results a:hover, .nov-search-results a:focus { background: #eef4fb; text-decoration: underline; }
.nov-search-empty { padding: 10px 8px; color: #4a4a4a; font-size: 14px; }

/* ---------------------------------------------------------------------------
   10. Added by o5nov_85_search_page.py: the submenu opened by a click (nov-restore.js item 3)
   and the acknowledgement a mailto form prints when it is submitted. */
li.nov-open > ul.sub-menu, li.nov-open > ul { display: block !important; opacity: 1 !important;
  visibility: visible !important; pointer-events: auto !important; }
.nov-form-note { margin: 10px 0 0; padding: 10px 12px; background: #eef4fb; color: #14538f;
  font-size: 15px; line-height: 1.5; border-left: 4px solid #1f6fbf; }
.nov-search-page input[type=search]:focus { outline: 3px solid #1f6fbf; outline-offset: 1px; }
.nov-search-status { margin: 10px 0 0; font-size: 15px; color: #14538f; font-weight: 700; }
.nov-browse { list-style: none; margin: 12px 0 0; padding: 0; columns: 2; column-gap: 32px; }
.nov-browse li { break-inside: avoid; }
.nov-browse a { display: inline-block; padding: 7px 0; min-height: 28px; color: #14538f;
  text-decoration: underline; text-underline-offset: 2px; }
@media (max-width: 600px) { .nov-browse { columns: 1; } }
/* The consent bar after an answer: slim, still there, still changeable.
   The plugin adds cookie-notice-hidden on animationend, i.e. AFTER our handler has finished, so
   the class we remove comes straight back and the bar collapses to zero height. Overriding it in
   CSS is the only way to win that race without patching the plugin's own bundle. */
#cookie-notice.nov-cn-answered,
#cookie-notice.nov-cn-answered.cookie-notice-hidden {
  display: block !important; visibility: visible !important; opacity: 1 !important;
  transform: none !important; height: auto !important; max-height: none !important;
  animation: none !important;
}
#cookie-notice.nov-cn-answered .cookie-notice-container {
  display: block !important; padding: 8px 12px; font-size: 14px;
}
#cookie-notice.nov-cn-answered .cn-button { font-size: 13px; padding: 6px 12px; }
#cookie-notice.nov-cn-answered .cn-button[aria-pressed="true"] {
  outline: 2px solid #fff; outline-offset: 1px; font-weight: 700;
}

/* ---------------------------------------------------------------------------
   AE-PRO POST GRID: 32 CARDS, ONE PER ROW, EACH AS WIDE AS ITS OWN TITLE.

   /urologie-impuissance/centres-traitement-france/ was 13,382px tall: every partner centre sat on
   its own row as a blue box 501-782px wide, the width tracking the length of the hospital's name.
   Measured cause, not guessed: the widget carries `ae-post-layout-grid` and the surviving framework
   bundle answers it with `.ae-post-list-wrapper{display:flex;flex-wrap:wrap}` plus width rules that
   ALL hang off a second class - `.ae-post-layout-grid.ae-post-grid-3 article.ae-post-list-item
   {width:33.3333%}` and its 2/4/5/6 siblings. That modifier is emitted with the widget's column
   setting and is absent from the archived HTML, and the card template's own stylesheet
   (post-2983.css, 64 references to .elementor-2983 on that page, 0 rules for it anywhere on disk)
   was never captured either. With no width rule reaching them the flex items shrink-wrap to their
   text. The live site cannot have looked like this - the ladder is the missing CSS, not a design.

   So restore the width the widget's own class vocabulary asks for, using the plugin's own steps.
   flex-basis rather than a hard 33.3333% because the same widget appears on the 28 centre pages
   with only TWO cards ("autres centres"), where three fixed thirds would leave a hole. */
.ae-post-layout-grid .ae-post-list-wrapper > article.ae-post-list-item {
  flex: 1 1 320px; max-width: 100%; box-sizing: border-box; padding: 0 10px;
}
@media (min-width: 1025px) {
  .ae-post-layout-grid .ae-post-list-wrapper > article.ae-post-list-item { max-width: 33.3333%; }
}
@media (min-width: 768px) and (max-width: 1024px) {
  .ae-post-layout-grid .ae-post-list-wrapper > article.ae-post-list-item { max-width: 50%; }
}
@media (max-width: 767px) {
  .ae-post-layout-grid .ae-post-list-wrapper > article.ae-post-list-item { max-width: 100%; }
}
/* The cards are a link with a background photograph that no longer exists, so the 400px block is
   now flat colour. Keep it a card rather than a slab: cap the dead image band and let the title,
   the town and the button carry the tile. */
.ae-post-layout-grid .elementor-cta__bg-wrapper { min-height: 150px; }

/* ---------------------------------------------------------------------------
   AN EMPTY SIDEBAR, AND THE HAIRLINE IT LEFT DOWN THE MIDDLE OF 99 PAGES.

   OceanWP gives a page with a sidebar `.content-area{width:72%;border-right:1px solid #f1f1f1}`.
   99 pages of this site carry has-sidebar / content-right-sidebar, and MEASURED on all 99 the
   sidebar is `<div id="right-sidebar-inner" class="clr"></div>` - empty, and empty in the archived
   bytes too, so the site itself shipped it that way. What that leaves us is a 1px grey rule running
   the full height of the page at x=977, straight through body copy and through the doctor cards,
   because the Elementor sections inside are stretched wider than the 72% box that draws it. It
   reads as a rendering fault, and the 28% beside it holds nothing. Give those pages the width the
   theme itself gives a page with no sidebar. Nothing is hidden that has content in it. */
body.content-right-sidebar .content-area,
body.content-left-sidebar .content-area {
  width: 100% !important; max-width: none !important;
  padding-right: 0 !important; padding-left: 0 !important; border-width: 0 !important;
}
body.content-right-sidebar #right-sidebar,
body.content-left-sidebar #right-sidebar { display: none; }

/* ---------------------------------------------------------------------------
   THE ADDRESS ROWS ON THE CENTRE PAGES: A 50px ICON BESIDE 16px TEXT.

   Same missing-stylesheet root cause as the grid above. The centre template's own Elementor CSS
   (post-1954/1960/1966) was never archived - 0 rules for it exist anywhere on disk - so every
   icon-box falls back to Elementor's factory `.elementor-icon{font-size:50px}`. The pin, the phone
   and the two chain-links were drawn at 45-50px next to their labels, and the chain-link sat ON the
   words "Site internet du centre". All 313 icon-boxes on the site are the same position-left,
   vertical-align-middle address row, so one rule reaches exactly them and nothing else. */
.elementor-widget-icon-box.elementor-position-left .elementor-icon { font-size: 22px; }
.elementor-widget-icon-box.elementor-position-left .elementor-icon-box-icon { margin-right: 12px; }

/* ---------------------------------------------------------------------------
   THE 400px OF NOTHING ABOVE EVERY CENTRE'S NAME.

   Section 872282e (34 pages) is the centre template's title band; its own CSS still says
   `background-position:center center;background-size:cover` because the photograph of the hospital
   was deleted from the url() when it turned out never to have been archived. What is left is a
   400px white box holding a 110px card. Give the band a height that fits what it still has. */
.elementor-element-872282e > .elementor-container { min-height: 220px !important; }
/* !important because the page's own inline Elementor CSS carries the identical selector and
   is written after this stylesheet in the document, so source order would otherwise win. */

/* ---------------------------------------------------------------------------
   R2 (independent review, 2nd pass): CARDS IN A ROW DO NOT SHARE A BOTTOM EDGE.

   The width fix above (ae-post-layout-grid block) makes the ARTICLE boxes a uniform row height via
   flex-stretch - measured 406px, confirmed. What paints navy is .elementor-cta__content, nested 13
   levels below the article inside plain block wrappers that never inherit that stretched height
   (percentage/flex-stretch only reaches a child that is itself flexed and explicitly sized; none of
   the intervening wrappers are). So .elementor-cta__content shrink-wraps to ITS OWN content instead:
   measured 204px for a one-line hospital name, 236px for a two-line one, a 32px gap between cards
   in the same row. Cascading a definite height down 13 nested divs is fragile and untestable by
   inspection; giving the content box itself a floor tall enough for the worst case is not - it makes
   every card's navy the same height regardless of row-mates, one property, matching the existing
   min-height approach used on .elementor-cta__bg-wrapper just above. First pass used 244px (clears
   the reviewer's measured 236px two-line case) and left ONE row uneven: "Groupe Hospitalier
   Diaconesses-Croix Saint Simon" wraps to three lines and needs 268px, so its two row-mates (at the
   244px floor, article stretched to match the tall one) again showed a shorter navy box in a taller
   white card - same defect, one outlier. Measured every card's natural content height on this page
   with the floor removed: 268px is the true maximum (one 3-line title; everything else is 1-2
   lines). 272px clears it with the same margin the first pass had over its own max. Verified with
   _scratch/_rev_nov_bluebox.js: 9 of 11 uneven rows -> 0 rows with spread > 2px, including the row
   with the 3-line title, on both /urologie-impuissance/centres-traitement-france/ and the 28 centre
   pages' two-card "autres centres" block (same widget). */
.ae-post-layout-grid .elementor-cta__content { min-height: 272px; }

/* ---------------------------------------------------------------------------
   R4 (independent review, 2nd pass): THE HOMEPAGE DIVIDER'S "LOGO" RENDERS AS A 20x6px SMUDGE.

   One widget on one page (data-id="c2a944e", elementor-widget-divider--view-line_icon): its icon
   slot does not hold a font-awesome glyph, it holds an inline <svg viewBox="0 0 220 63"> wrapping a
   base64 PNG of the site's own logo (new-logo.svg - the same logo that is on the 98-photo loss
   list, surviving here only because the era's page-builder inlined it instead of linking it).
   Elementor's own framework CSS sizes every divider icon for a SQUARE glyph:
   `.elementor-icon{font-size:var(--divider-icon-size)}` (20px) and `.elementor-icon svg{width:1em;
   height:1em}` - a 20x20 box. The svg's default preserveAspectRatio keeps the 220:63 content
   proportional inside that square, so it renders at 20 x 5.7 (measured 20x6) with 14px of empty
   box above and below it: legible box, illegible content. Confirmed this is the ONLY svg-icon
   divider on the site (grepped all 212 pages, 1 match, viewBox "0 0 220 63" x1) so this rule cannot
   reach anything else. Let the svg keep its own aspect ratio at the same 20px vertical budget the
   site already allotted the icon, rather than being squashed into a square it was never meant for. */
.elementor-element-c2a944e .elementor-icon.elementor-divider__element svg { width: auto; }

/* ---------------------------------------------------------------------------
   o7 visual review: THE "POSEZ TOUTES VOS QUESTIONS" FORM HAS NO GUTTER.
   Elementor writes a form's column gap into the per-widget CSS (default 10px: padding 5px on each
   .elementor-field-group, -5px on the wrapper). That per-template CSS was never archived and no
   rule for it exists on disk, so the two half-width inputs ("Votre adresse mail" / "Votre numero
   de telephone") met edge to edge at x=720 on the article pages (seen on
   age-et-probleme-erection-... d5). This restores Elementor's own default gap, nothing more. */
.elementor-form-fields-wrapper { margin-left: -5px; margin-right: -5px; }
.elementor-form-fields-wrapper > .elementor-field-group { padding-left: 5px; padding-right: 5px; }

/* ---------------------------------------------------------------------------
   o7 visual review: A 550x380 WHITE HOLE BESIDE "Contrairement a tous les autres solutions...".
   Homepage section 07bd7c1 is two 50% columns. The left one (b8b2ca8) held the photograph
   03jpg_5d30172b9b28b-min.jpg, which no capture of this domain contains (imagedebt list); the
   widget was removed with it and the column was left as an empty widget-wrap, so on desktop the
   paragraph sat in the right half beside nothing (home d1). On phones the empty column already
   collapses. Collapse it on desktop too and let the paragraph take the row; no content is hidden. */
@media (min-width: 768px) {
  .elementor-element-07bd7c1 .elementor-element-b8b2ca8 { display: none; }
  .elementor-element-07bd7c1 .elementor-element-66e3f3a { width: 100% !important; }
}

/* ---------------------------------------------------------------------------
   o7 visual review: THE ARTICLE TEXT TOUCHES THE "SOMMAIRE" BOX.
   The table-of-contents widget carries elementor-widget__width-initial, and Elementor's own
   `.elementor-widget:not(:last-child).elementor-widget__width-initial{margin-bottom:0}` takes away
   the 20px every other widget gets; the per-widget CSS that set its width and spacing was never
   archived. On phones the first paragraph started flush against the box's bottom border
   (age-et-probleme-erection-... p0). Give it back the standard widget gap. */
.elementor-widget-table-of-contents.elementor-widget__width-initial:not(:last-child) { margin-bottom: 20px; }

/* ---------------------------------------------------------------------------
   ORDER 7 (decisions in _recon/order7/DECISIONS_fr.md, items 3, 4, 6, 7).

   LOGO. The header used to carry a wordmark set in type because the logo file was thought lost.
   It survives: the homepage's decorative divider embeds the real two-tone logo as an inline PNG
   (220x63). That PNG is now /img/novelator-logo.png and sits in both header copies at its
   natural size. */
.nov-logo { display: block; width: 220px; height: 63px; max-width: none; }

/* HONEST HERO. The three slides' photographs were never archived and their url() was stripped,
   leaving a white overlay, a grey heading and dots. The widget is now ONE static slide (its type
   no longer "slides", so Elementor's script does not start Swiper on it) on the brand ground
   (--nov-navy, the colour the site's own cards already use); dots and arrows are gone because
   nothing is left for them to change. */
.elementor-widget-slides .swiper-slide { background-color: var(--nov-navy); }
.elementor-widget-slides .elementor-background-overlay { background-color: transparent !important; }
.elementor-widget-slides .elementor-slide-heading { color: #fff !important; }
.elementor-widget-slides .elementor-slide-button,
.elementor-widget-slides .elementor-button.elementor-slide-button {
  background-color: #fff !important; color: var(--nov-navy) !important; border-color: #fff !important;
}
.elementor-widget-slides .swiper-pagination,
.elementor-widget-slides .elementor-swiper-button { display: none !important; }

/* JOURNAL-ARTICLE HEADER. The per-post rule that paints the journal cover shipped without
   background-repeat/size, so the 121x89 cover tiled across the 1440px header under the H1. The
   inline rule in each of the three pages now stops the tiling and parks the cover at the right;
   room is kept for it on wide screens and it is dropped on phones, where it would sit under the
   title. */
@media (min-width: 768px) {
  .elementor-2812 .elementor-element-d4266aa > .elementor-container { padding-right: 170px; box-sizing: border-box; }
}
@media (max-width: 767px) {
  .elementor-2812 .elementor-element-d4266aa:not(.elementor-motion-effects-element-type-background),
  .elementor-2812 .elementor-element-d4266aa > .elementor-motion-effects-container > .elementor-motion-effects-layer {
    background-image: none !important;
  }
}

/* CONSENT BAR ON A SHORT PAGE. A sticky bar only sticks to the window while the document is
   taller than the window; on a short page it sat mid-screen under the footer with white beneath
   it. Until the visitor answers it is pinned to the bottom of the viewport; the body gets the
   bar's height as padding so the last lines of the footer are not covered. Once answered
   (.nov-cn-answered) the slim sticky bar above applies again. */
#cookie-notice:not(.nov-cn-answered) {
  position: fixed !important; left: 0; right: 0; bottom: 0 !important; top: auto !important;
}
body:has(#cookie-notice:not(.nov-cn-answered):not(.cookie-notice-hidden)) { padding-bottom: 90px; }
@media (max-width: 767px) {
  body:has(#cookie-notice:not(.nov-cn-answered):not(.cookie-notice-hidden)) { padding-bottom: 130px; }
}

/* HEADER NAV OVERFLOW AT 1180px. Elementor's menu items carry a ::after pointer element placed
   right:-30px of the link; on the last item of the first row it lands past the column edge and
   widened the document to 1192px (sideways scroll at the laptop width). clip, not hidden, so the
   dropdown panels, which open downwards, are not cut. */
.elementor-nav-menu--main .elementor-nav-menu { overflow-x: clip; }

/* TABLE OF CONTENTS LINKS. The "Sommaire" list is built from the page's h2 headings and its links
   were the same colour and weight as the text around them, so they read as plain text. */
.elementor-widget-table-of-contents .elementor-toc__list-item-text { text-decoration: underline !important; }
