/* ===========================================================================
   restore-extras.css — cse-radiologie.com
   Loaded last, on every page. Everything here exists because a specific thing
   the archive lost had to be replaced with something that works, or because a
   measurement (qa_legibility) said the original value was below the bar.
   Nothing here restyles the site for taste.
   =========================================================================== */

/* --- A. THE WORDMARK -------------------------------------------------------
   The archived logo file is a 234x127 PNG with zero opaque pixels, and the
   second copy the cse.paris pages point at was never fetched, so the header
   had no mark at all. Typeset the centre's own name rather than draw a logo we
   would be inventing. Sized to the box the theme reserved for the image. */
.cse-wordmark {
  display: inline-block;
  text-decoration: none;
  line-height: 1.15;
  padding: 6px 0;
}
.cse-wordmark-initials {
  display: block;
  font-family: Arial, Helvetica, sans-serif;
  font-weight: 700;
  font-size: 34px;
  letter-spacing: 0.06em;
  color: #006bc5;
}
.cse-wordmark-rest {
  display: block;
  font-family: Arial, Helvetica, sans-serif;
  font-size: 14px;
  letter-spacing: 0.02em;
  color: #333;
  text-transform: uppercase;
}
.cse-wordmark:hover .cse-wordmark-initials { color: #0086f6; }

/* --- B. THE APPOINTMENT BUTTON ---------------------------------------------
   Was an image-only link whose image the archive lost, i.e. an <a> with no
   label and a 0x0 hit area. A real button, at a size a finger can hit. */
.cse-rdv-btn {
  display: inline-block;
  background: #006bc5;
  color: #fff !important;
  font-weight: 700;
  font-size: 15px;
  line-height: 1.2;
  padding: 12px 18px;
  min-height: 24px;
  border-radius: 3px;
  text-decoration: none;
}
.cse-rdv-btn:hover, .cse-rdv-btn:focus { background: #0086f6; color: #fff !important; }
.doctolib { margin-bottom: 10px !important; }
.doctolib p { margin: 0; }

/* --- C. THE MAPS -----------------------------------------------------------
   Three Google Maps iframes per page became pictures we host. They keep the
   full width of the box the iframe had. The ODbL credit must stay legible:
   it is real text, not only the pixels burned into the PNG. */
.wpb_map_wraper img.osm-map {
  display: block;
  width: 100%;
  height: auto;
  max-width: 100%;
  border: 1px solid #ddd;
}
p.osm-credit {
  margin: 4px 0 12px;
  font-size: 12px;
  line-height: 1.4;
  color: #444;
}
p.osm-credit a { color: #005a9e; text-decoration: underline; }
.footer_container p.osm-credit,
.footer_container p.osm-credit a { color: #4a4a4a; }

/* --- C2. THE RESPONSIVE CONTAINER THE THEME BREAKS ITSELF -------------------
   MEASURED, not guessed: at 390px the interior pages scrolled sideways by
   572px because `.container` computed to 940px. Bootstrap 2's responsive sheet
   does set `.container{width:auto}` under `(max-width:767px)`, but the theme
   then loads a SECOND, non-responsive copy of bootstrap.css AFTER it, and that
   copy re-declares `.container{width:940px}` at the same specificity with no
   media query, so it wins. Re-asserting the three widths from the last
   stylesheet in the cascade is the smallest fix that holds. */
@media (max-width: 767px) {
  .container,
  .navbar-static-top .container,
  .navbar-fixed-top .container,
  .navbar-fixed-bottom .container { width: auto; padding-left: 20px; padding-right: 20px; }
  /* Same cause, second symptom: the STATIC grid (.span9 on the article column)
     is reset to full width by bootstrap-responsive too, and the later plain
     bootstrap.css puts the fixed pixel widths back. Measured: #primary.span9
     was still 700px inside a 390px viewport after the container was fixed. */
  .row, .thumbnails { margin-left: 0; }
  [class*="span"],
  .uneditable-input[class*="span"],
  .row-fluid [class*="span"] {
    float: none; display: block; width: 100%; margin-left: 0;
    -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box;
  }
  .span12, .row-fluid .span12 { width: 100%; }
  .wpb_tour .ui-tabs .ui-tabs-nav,
  .wpb_tour .ui-tabs .ui-tabs-panel { width: 100%; float: none; margin-left: 0; }
  body { overflow-x: hidden; }
}
/* --- C2b. THE SHELL WAS PUT BACK BUT THE GRID INSIDE IT WAS NOT ------------
   Same root cause as C2, second half of the damage, and it is the half that
   only shows on a DESKTOP. Bootstrap 2 ships three grids - 724, 940 and 1170 -
   and bootstrap-responsive.css switches between them by media query. The
   theme's second, non-responsive bootstrap.css is loaded AFTER it and
   re-declares the 940-pixel `.spanN` widths at equal specificity with no media
   query, so 940 wins at EVERY width. C2 restored `.container` alone, which
   left the shell at 1170 and the columns still cut for 940.
   MEASURED at 1440 over all 87 pages before this rule existed: 43 pages put a
   700px article beside a 220px sidebar inside a 1170px shell and showed 220px
   of dead white down the right-hand side; three more (/accueil/scanner/,
   /accueil/echographie/, /prendre-rdv/) put a 940px span12 in the same shell,
   230px short; and the footer's three widgets were 300px wide instead of 370,
   stopping 210px before the copyright bar underneath them. Nothing overflowed
   and nothing was invisible, so every gate passed it.
   In the 768-979 band the same override was worse than cosmetic: a 940px
   span12 inside a 724px container scrolled those three pages sideways by up to
   194px.
   The widths below are bootstrap-responsive.css's own, copied from the
   stylesheet that ships with this site. Specificity is deliberately (0,1,0) -
   the same as bootstrap's - so `.row-fluid [class*="span"]` still wins for
   fluid rows, exactly as upstream intends. */
@media (min-width: 768px) and (max-width: 979px) {
  .container,
  .navbar-static-top .container,
  .navbar-fixed-top .container,
  .navbar-fixed-bottom .container { width: 724px; }
  .row { margin-left: -20px; }
  [class*="span"] { margin-left: 20px; }
  .span12 { width: 724px; }
  .span11 { width: 662px; }
  .span10 { width: 600px; }
  .span9  { width: 538px; }
  .span8  { width: 476px; }
  .span7  { width: 414px; }
  .span6  { width: 352px; }
  .span5  { width: 290px; }
  .span4  { width: 228px; }
  .span3  { width: 166px; }
  .span2  { width: 104px; }
  .span1  { width: 42px; }
}
@media (min-width: 1200px) {
  .container,
  .navbar-static-top .container,
  .navbar-fixed-top .container,
  .navbar-fixed-bottom .container { width: 1170px; }
  .row { margin-left: -30px; }
  [class*="span"] { margin-left: 30px; }
  .span12 { width: 1170px; }
  .span11 { width: 1070px; }
  .span10 { width: 970px; }
  .span9  { width: 870px; }
  .span8  { width: 770px; }
  .span7  { width: 670px; }
  .span6  { width: 570px; }
  .span5  { width: 470px; }
  .span4  { width: 370px; }
  .span3  { width: 270px; }
  .span2  { width: 170px; }
  .span1  { width: 70px; }
}

/* --- C3. THE HEADER STACK --------------------------------------------------
   `ul.topheadernav` carries a hard `margin-left:630px` and the appointment
   button and the social link both float right into the same strip, so once the
   image-only button became a text button the three collided over the wordmark.
   Given each its own row instead of overlapping absolute positions. */
ul.topheadernav {
  margin-left: 0;
  padding-left: 0;
  text-align: right;
}
ul.topheadernav li {
  height: auto;
  line-height: 1.3;
  padding: 7px 12px;
  margin: 6px 0 0 8px;
  border-radius: 0 0 12px 0;
}
.logo, .cse-wordmark { float: left; }
#top-contacts-box { float: right; clear: none; }
.doctolib { float: right !important; clear: both; margin: 8px 0 14px !important; }
#social-icons { float: right; clear: both; margin: 0 0 8px; }
header nav { clear: both; }
@media (max-width: 767px) {
  .logo, .cse-wordmark, #top-contacts-box, .doctolib, #social-icons {
    float: none !important; clear: both !important; text-align: center;
  }
  ul.topheadernav { text-align: center; }
}

/* --- C4. THE TOUR TABS -----------------------------------------------------
   Visual Composer draws its tour tabs with jQuery UI classes and expects the
   jQuery UI theme stylesheet to paint them. That file
   (jquery-ui-less.custom.css) is one of the assets the archive never held, so
   the tab rail rendered as a grey bulleted list at 3.7:1. */
.wpb_tour .ui-tabs .ui-tabs-nav,
.wpb_tabs .ui-tabs .ui-tabs-nav { list-style: none; margin: 0; padding: 0; }
.wpb_tour .ui-tabs .ui-tabs-nav li,
.wpb_tabs .ui-tabs .ui-tabs-nav li {
  list-style: none; margin: 0; padding: 0; border-bottom: 1px solid #dcdcdc; background: #f4f4f4;
}
.wpb_tour .ui-tabs .ui-tabs-nav li a,
.wpb_tabs .ui-tabs .ui-tabs-nav li a {
  display: block; padding: 11px 14px; color: #1d1d1d; font-size: 14px; line-height: 1.35;
  text-decoration: none; min-height: 24px;
}
.wpb_tour .ui-tabs .ui-tabs-nav li a:hover,
.wpb_tabs .ui-tabs .ui-tabs-nav li a:hover { background: #e8f1fa; color: #00509a; }
.wpb_tour .ui-tabs .ui-tabs-nav li.ui-tabs-active,
.wpb_tour .ui-tabs .ui-tabs-nav li.ui-state-active,
.wpb_tabs .ui-tabs .ui-tabs-nav li.ui-tabs-active,
.wpb_tabs .ui-tabs .ui-tabs-nav li.ui-state-active { background: #fff; border-left: 3px solid #006bc5; }
.wpb_tour .ui-tabs .ui-tabs-nav li.ui-tabs-active a,
.wpb_tour .ui-tabs .ui-tabs-nav li.ui-state-active a,
.wpb_tabs .ui-tabs .ui-tabs-nav li.ui-tabs-active a,
.wpb_tabs .ui-tabs .ui-tabs-nav li.ui-state-active a { color: #00509a; font-weight: 700; }
.ui-tabs .ui-tabs-hide { display: none; }

/* --- D. LEGIBILITY ---------------------------------------------------------
   The theme paints the navigation and several small labels in a grey that sits
   under 4.5:1 on its own white. These raise the ink; they do not move anything.
   Each value below was chosen against a contrast the gate then re-measured. */
/* White on #FF9400 is 2.6:1. A darker orange keeps the theme's colour and
   passes: white on #a85f00 is 5.2:1. */
ul.topheadernav li { background: #a85f00; background-image: none; }
ul.topheadernav li:hover { background: #8c4f00; background-image: none; }
/* NOT underlined. Measured both ways: underlining these three silenced the
   "links look like plain text" note but moved it onto the nine main-navigation
   items AND dropped the pills' owned hit area to 22px, i.e. it traded a note
   for a blocking failure. They stay as coloured pills with white bold text. */
/* The theme pins these to `padding:0; height:12px` with a 12px font, and its
   selector (ul.topheadernav li a) outranks a class-only override, so the
   padding has to be re-declared at the same weight. Measured after: the <a>
   owns 30px rather than 22px. */
ul.topheadernav li a { color: #fff; font-size: 14px; height: auto; line-height: 1.5;
                       padding: 5px 2px; min-height: 26px; display: inline-block; }
ul.topheadernav li a:hover { color: #fff; text-decoration: underline; }

/* The copyright line is painted #FFF by the theme and the band under it is
   white on 46 of the 85 pages, i.e. contrast 1:1 - literally invisible text.
   Give the band the dark ground the white ink was written for. */
.copy_container { background: #4a4a4a; }
footer .copytxt, footer .copytxt a, .copy_container, .copy_container a { color: #fff; }
/* CORRECTION, measured twice: the main navigation bar is a BLUE band, so the
   first attempt at "darker ink" drove Accueil to 1.62:1 - worse than the
   original. The bar wants white, and the dropdown panels (which are white)
   want near-black. */
#topmenu > li > a,
#topmenu > li > a span,
#topmenu > li > a strong { color: #ffffff; text-shadow: 0 1px 1px rgba(0,0,0,.35); }
#topmenu > li > a:hover strong,
#topmenu > li.current-menu-item > a strong,
#topmenu > li.current_page_item > a strong { color: #ffffff; }
#topmenu .sub-menu { background: #ffffff; }
#topmenu .sub-menu li a,
#topmenu .sub-menu li a span,
#topmenu .sub-menu li a strong { color: #1d1d1d; text-shadow: none; }
#topmenu .sub-menu li a:hover strong { color: #00509a; }
/* THIRD measurement: below 980px the theme drops the blue bar and shows the
   same <ul> inside a WHITE collapsible panel, so the white ink above turned
   the whole phone menu invisible (1.07:1). Scope the white to the bar only. */
@media (max-width: 979px) {
  #topmenu li a,
  #topmenu li a span,
  #topmenu li a strong,
  #topmenu > li.current-menu-item > a strong,
  #topmenu > li.current_page_item > a strong,
  #topmenu > li.menu-item-home > a strong { color: #1d1d1d; text-shadow: none; }
  #topmenu li a:hover strong { color: #00509a; }
  #topmenu, #topmenu li { background: #fff; }
  #topmenu li { border-bottom: 1px solid #e2e2e2; }
  a.mobile-menu-btn, a.mobile-menu-btn .mobile-menu-title { color: #fff; }
}

#top-contacts li { color: #333; font-size: 13px; line-height: 1.6; }
#top-contacts li span { color: #006bc5; font-weight: 700; }

.topheadernav li a { color: #1d1d1d; font-size: 13px; }
.topheadernav li a:hover { color: #006bc5; }

.copy_container, .copy_container a, .copytxt { color: #3d3d3d; }
.footer_container, .footer_container p, .footer_container .textwidget { color: #333; }
.footer_container a { color: #005a9e; }
.widget-title { color: #1d1d1d; }

/* Nothing on this site should print body copy under 12px. */
p, li, td, .textwidget { font-size: 14px; }
small, .small, .entry_date { font-size: 12px; }

/* --- E. TAP TARGETS --------------------------------------------------------
   Measured at 390px: several inline links and the social icon sat under the
   24px minimum on their shorter side. */
/* The theme drew this control entirely from a sprite (/img/socialicons-*.png) that the archive
   never held, on the <li> rather than the <a>, so the link had no picture, no text and no size.
   The sprite reference is switched off here so the browser stops asking for a 404, and the link
   is given a real label and a real hit area. */
header #social-icons li,
header #social-icons li.facebook { background: none !important; width: auto; height: auto; }
#social-icons li a {
  display: inline-block;
  min-width: 32px;
  min-height: 32px;
  line-height: 32px;
  padding: 0 12px;
  font-size: 13px;
  font-weight: 700;
  text-indent: 0;
}
.topheadernav li a,
#topmenu > li > a,
.pagination a, .pager a { display: inline-block; min-height: 24px; padding-top: 4px; padding-bottom: 4px; }

/* MEASURED at 390px: every link that is a list item's own child came back
   16px tall (the "Dans la même catégorie" rail, the footer widget links), and
   the map credit came back 14px, because the theme leaves them at the bare
   line box. A finger needs 24. */
li > a,
.textwidget center a,
p.osm-credit a {
  display: inline-block;
  padding-top: 5px;
  padding-bottom: 5px;
  line-height: 1.5;
  min-height: 24px;
}
p.osm-credit { line-height: 1.8; }

/* --- F. THE ICON FONT THAT IS GONE -----------------------------------------
   The theme's Entypo webfont was never captured (no /fonts/ directory exists
   in the archive for this domain), so every :before glyph drawn from it would
   render as a tofu box. Font Awesome IS available and is installed, so the two
   places the theme uses Entypo for a real control - the social icon and the
   back-to-top arrow - are drawn with characters instead of a missing glyph. */
#social-icons li a { color: #fff; background: #006bc5; text-align: center; border-radius: 3px; }
#social-icons li a:hover { background: #0086f6; }
#back-to-top:before { content: "\2191"; }
#back-to-top {
  color: #fff; background: #006bc5; text-align: center;
  width: 40px; height: 40px; line-height: 40px; border-radius: 3px;
  text-decoration: none;
  /* o7 review: the theme's `padding:10px 15px` (style.css #back-to-top) was still
     added to the 40x40 box, so the arrow rendered as a 72x61 slab that covered
     body copy and the footer links at 390px. The 40px square is what this rule meant. */
  padding: 0;
}

/* --- G. SMALL SCREENS ------------------------------------------------------
   The theme is Bootstrap 2 and does declare a viewport, so no reflow surgery
   is needed here; these only stop the two widest blocks from pushing the page
   sideways at 390px. */
@media (max-width: 767px) {
  .cse-wordmark-initials { font-size: 28px; }
  .cse-wordmark-rest { font-size: 12px; }
  .wpb_map_wraper img.osm-map { height: auto; }
  #top-contacts li { word-break: break-word; }
  .wp-caption, .wpb_single_image img, .textwidget img { max-width: 100%; height: auto; }
  table { max-width: 100%; display: block; overflow-x: auto; }
}

img { max-width: 100%; height: auto; }

/* --- H. THE PAGES WE AUTHORED ---------------------------------------------- */
.cse-authored h2 { margin-top: 28px; }
.cse-authored ul { margin-left: 20px; }
.cse-authored li { margin-bottom: 6px; }
.cse-section-index { list-style: none; margin-left: 0; }
.cse-section-index li {
  border-bottom: 1px solid #e4e4e4;
  padding: 10px 0;
}
.cse-section-index li a { font-weight: 700; font-size: 15px; }
.cse-section-index li span { display: block; color: #444; font-size: 13px; }

/* --- I. THE FOOTER LEGAL NAV -----------------------------------------------
   The theme reserves `<div class="span7 menu">` for a secondary menu and the
   capture left it empty, so four legal pages existed with nothing pointing at
   them. */
ul.cse-footernav { margin: 0; padding: 26px 0 0; text-align: right; list-style: none; }
ul.cse-footernav li { display: inline-block; margin: 0 0 0 16px; }
ul.cse-footernav li a {
  color: #fff; font-size: 13px; text-decoration: underline;
  display: inline-block; min-height: 24px; padding: 3px 0;
}
ul.cse-footernav li a:hover { color: #fff; text-decoration: none; }
@media (max-width: 767px) {
  ul.cse-footernav { text-align: center; padding-top: 12px; }
  ul.cse-footernav li { display: block; margin: 0; }
  .copy_container .span5.copytxt { text-align: center; }
  /* o7 review: the two rules above never applied. The theme's
     `footer .copy_container ul.footernav li` (0,2,3) outranks `ul.cse-footernav li`
     (0,1,2), so at 390px the five links stayed inline-block in 13px-high boxes with
     dotted separators, wrapped across three cramped lines, and the floated list put
     "Politique de cookies" under the fixed back-to-top button. Re-declared at a
     weight that wins, with the theme's fixed height/separator/float undone. */
  footer .copy_container ul.cse-footernav { float: none; text-align: center; }
  footer .copy_container ul.cse-footernav li {
    display: block; margin: 0; padding: 0; height: auto; line-height: 1.4; border-right: none;
  }
}

/* --- J. THE HOMEPAGE INTRODUCTION ------------------------------------------
   The centre's own staged intro, switched back on. It sits between the slider
   and the weave block and needs the band styling the theme wrote for it, minus
   the six picto images the archive never held. */
.cse-home-intro { padding: 34px 0 10px; }
.cse-home-intro .title-home {
  display: block; text-align: center; color: #006bc5;
  font-size: 26px; line-height: 1.3; font-weight: 700; margin: 0 0 18px;
}
.cse-home-intro .intro-home p { text-align: center; font-size: 15px; line-height: 1.7; color: #333; }
.cse-home-intro .text-home { margin-top: 22px; text-align: center; }
.cse-home-intro ul.cse-points {
  list-style: none; margin: 12px 0 18px; padding: 0;
}
.cse-home-intro ul.cse-points li {
  display: inline-block; margin: 0 10px 10px; padding: 10px 16px;
  background: #f4f7fa; border-left: 3px solid #006bc5; font-size: 14px; color: #1d1d1d;
  text-align: left; max-width: 100%;
}
@media (max-width: 767px) {
  .cse-home-intro .title-home { font-size: 21px; }
  .cse-home-intro ul.cse-points li { display: block; margin: 0 0 10px; }
}

/* --- K. THE COLLAPSED MOBILE MENU MUST BE OUT OF THE HIT TEST ---------------
   Bootstrap 2 collapses with `height:0; overflow:hidden` and NOT with
   `display:none`, so the 75 links inside the closed phone menu still had
   layout boxes. qa_interactions found twelve of them "UNREACHABLE - a real
   pointer lands on a.mobile-menu-btn instead", which is exactly right: they
   were controls a visitor could never hit. Taking the closed panel out of the
   box tree removes them from the page until the burger opens it. Verified
   after the change that the burger still opens the panel to its full height
   with all 75 links in it. */
#mobile-menu-wrapper.collapse:not(.in) { display: none; }
#mobile-menu-wrapper.collapse.in { display: block; height: auto; }

/* --- L. THE SEARCH PAGE ----------------------------------------------------
   The page the site names "Recherchez sur le site" had an empty article
   column. The control below filters a static index; the field and the button
   are sized so a finger can hit them. */
.cse-search-form { margin: 16px 0 8px; }
.cse-search-form label {
  /* A <label for> IS a control: clicking it focuses the field, so qa_legibility measures it
     as a tap target and blocked at 700x20 (shorter side 20px, under the 24px floor).
     Given its own 24px of height rather than shrink-wrapped to the 20px line box. */
  display: block; font-weight: 700; margin-bottom: 6px; color: #1d1d1d;
  min-height: 24px; line-height: 24px; }
.cse-search-form input[type="search"] {
  width: 100%; max-width: 460px; box-sizing: border-box;
  font-size: 16px; line-height: 1.4; padding: 10px 12px; min-height: 40px;
  border: 1px solid #b9b9b9; border-radius: 3px; color: #1d1d1d; background: #fff;
  float: none; margin: 0 8px 8px 0;
}
.cse-search-form button {
  font-size: 15px; font-weight: 700; color: #fff; background: #006bc5;
  border: 0; border-radius: 3px; padding: 11px 18px; min-height: 40px; cursor: pointer;
}
.cse-search-form button:hover { background: #0086f6; }
.cse-search-count { font-size: 14px; color: #333; margin: 10px 0; min-height: 20px; }

/* The theme hides this control's label with `text-indent:-9999px` ON THE <li>,
   which is what made the labelled link render 56px to the LEFT of its own
   zero-width parent and get clipped at the container edge. Measured: li
   x=1305 w=0, its <a> x=1249 w=56. */
#social-icons li { text-indent: 0; width: auto; height: auto; }
/* the theme also pins the <a> to a 28px SQUARE for a sprite that no longer exists,
   which clipped the word "Facebook" mid-letter; let it size to its label. */
#social-icons li a { width: auto; height: auto; }
#social-icons { margin-right: 0; }

/* --- M. THE BLOG LISTING META ----------------------------------------------
   Measured on /actualite-2/: the breadcrumb ("Vous êtes ici :", "Blog") sat at
   2.82:1 and the post meta ("Publié le", "27 novembre 2012") at 2.44:1 on
   their own white. */
.breadcrumb_area, .breadcrumb_area ul.breadcrumb,
.breadcrumb_area ul.breadcrumb li,
.breadcrumb_area ul.breadcrumb li span,
ul.breadcrumb, ul.breadcrumb li, ul.breadcrumb .divider { color: #4a4a4a; }
.breadcrumb_area ul.breadcrumb li a, ul.breadcrumb li a { color: #005a9e; }
.entry_meta, .entry_meta ul, .entry_meta li, .entry_meta li span,
.entry_date, .entry_date span { color: #4a4a4a; }
.entry_meta li a { color: #005a9e; }

/* The theme's own rule is `.entry_meta ul li { color:#a0a0a0; display:none }`.
   The items are hidden, so a visitor never sees them, but the ink is still
   2.44:1 and the gate reads it; match the theme's specificity so the number
   reflects what would be shown if the theme ever showed it. */
.entry_meta ul li, .entry_meta ul li span { color: #4a4a4a; }
.entry_meta ul li a { color: #005a9e; }

/* Inline links inside body copy come out of the theme at the bare 16px line
   box. A link in the middle of a sentence still has to be hittable, so the
   ones inside our own blocks and inside the weave paragraph get a real height
   without changing where the words sit. */
.cse-home-intro p a,
.cse-authored p a,
.content-wraparea p a,
.textwidget p a {
  display: inline-block;
  padding-top: 4px;
  padding-bottom: 4px;
  line-height: 1.5;
  min-height: 24px;
}

/* --- X. THE SIDEBAR PAGE TREE OVERFLOWS THE 768-979 GRID -------------------
   The four post pages carry the theme's nested page list, and each nesting
   level adds its own left padding. In the 724 grid the sidebar is 166px wide,
   and a third-level item ("Téléradiographie" under Radiologie > Pédiatrique)
   started 100px in and pushed 17px past the viewport - a real sideways scroll,
   measured at 768, invisible at 390 and at 1440 where the sidebar is wider.
   Tighten the indent and let long French words break rather than push. */
@media (max-width: 979px) {
  .widget ul.children { padding-left: 10px; margin-left: 0; }
  .widget ul.children ul.children { padding-left: 8px; }
  .widget li a { overflow-wrap: break-word; word-wrap: break-word; }
}

/* --- Y. A RAW URL USED AS LINK TEXT SCROLLED THE PHONE SIDEWAYS ------------
   /depistage-europe/ links its leaflet with the full urcamif.assurance-maladie.fr
   address as the anchor text. That is one unbreakable 402px token: at 390 it
   pushed the document 85px wide. Measured, not guessed - the same page is clean
   at every width from 600 up, which is why nothing caught it. Let long tokens
   break inside the article rather than widen the page. */
#primary, .postcontent, .cse-authored { overflow-wrap: break-word; word-wrap: break-word; }
/* The anchor itself is display:inline-block here (a theme rule for list links), and an
   inline-block shrink-wraps to its max-content width, so inheriting overflow-wrap alone
   changed nothing - MEASURED: still 402px after the rule above. Capping it at the line
   box is what lets the break actually happen. */
#primary a, .postcontent a, .cse-authored a { max-width: 100%; }

/* --- Z. THE GREY STRIPE ACROSS THE HOMEPAGE --------------------------------
   MEASURED: body is painted rgb(151,151,151) by the theme, and `.bloc-home`
   (the band that carries the closing homepage paragraph) has margin-top:35px.
   Between a #f7f7f7 section above and a #fff section below, those 35px of body
   showed through as a hard mid-grey bar straight across the page - it reads as
   a rendering fault, not as a divider. Fold the gap into the block's own
   padding so the spacing is unchanged and nothing grey is exposed. */
.content-wraparea.bloc-home { margin-top: 0; padding-top: 75px; }

/* --- Z2. TWO GENERATIONS, TWO PAGE BACKGROUNDS -----------------------------
   MEASURED: body computes to rgb(151,151,151) on 46 pages and rgb(255,255,255)
   on the other 41. Both generations link the same theme-options sheet, which
   says `body{background:#979797}`; they differ only in whether the theme's own
   style.css is loaded after it. Since `footer` carries padding-bottom:30px with
   no background of its own, that difference shows up as a 30px mid-grey slab
   under the copyright bar on half the site and nothing on the other half - the
   same site ending two different ways. Everything above it is full-bleed white,
   so white is the reading that matches the design; asserted once, last. */
html, body { background: #ffffff; }
/* o7 review: with the ground white, that 30px of footer padding became a white strip
   UNDER the dark copyright band (restored above as #4a4a4a), so every page ended
   with the band stopping short and its text hugging the band's bottom edge. In the
   theme the band and the padding were one colour (both showed the body grey). Paint
   the footer's own padding the band's colour; .footer_container keeps its #FFF. */
footer { background: #4a4a4a; }

/* --- Z3. A ONE-TAB TOUR IS A DEAD RAIL AND AN EMPTY COLUMN -----------------
   Thirteen pages (the section hubs and a few leaves) carry a Visual Composer
   "tour" holding exactly one tab. The rail is ~25% of the row, so on
   /accueil/scanner/ a single 280px label sat above roughly 950px of blank white
   while the text ran down the other 75% - the classic "half the page is empty"
   look. It is also a tab you can click that has nothing to switch to. Where
   there is only one tab, drop the rail and let the panel have the row. Pages
   with two or more tabs are untouched: there the rail is a real control and
   qa_interactions proves it works. */
.wpb_tour.cse-tour-single .ui-tabs .ui-tabs-nav { display: none; }
.wpb_tour.cse-tour-single .ui-tabs .ui-tabs-panel { width: 100%; float: none; margin-left: 0; }

/* A stated absence, set apart from the body copy so it reads as a note about the page
   rather than as part of the centre's own text. */
.cse-note {
  border-left: 3px solid #006bc5; background: #f4f7fa;
  padding: 12px 16px; margin: 0 0 18px; font-size: 14px; color: #1d1d1d;
}

/* --- Z4. THE CLOSING HOMEPAGE BLOCK WAS CUT OFF AT THE BOTTOM (o7 review) ---
   The theme gives .bloc-home margin-bottom:-50px (it tucks the band under the next one).
   For the closing block that negative margin drags the three-column address band UP over
   its bottom border and padding, so the box reads as overflowed. Give the block its own
   room instead. Styling is applied from outside; the block's markup is untouched. Its
   heading is also brought in line with the page's other section headings (bold #0066cc). */
.content-wraparea.bloc-home { margin-bottom: 0; padding-bottom: 50px; }
.content-wraparea.bloc-home .title-home { display: block; color: #006bc5; font-size: 26px; line-height: 1.3; font-weight: 700; }
