/* restore extras — generated by restore_04_polish.py */

/* Consent overlays: the restore ships no analytics or third-party tracking at all, so there
   is nothing to consent to. Their scripts are gone too, meaning the banner can never be
   dismissed and would cover the top of every page. Removing the markup is unreliable when a
   JS bundle re-renders it, so it is hidden here as well. */
.cookies-banner, .cookies-banner-content, .cookie-banner, .cookie-consent, .cookie-notice,
.cc-window, .cc-banner, #cookie-law-info-bar, #cookieChoiceInfo, .gdpr-banner,
#tarteaucitronRoot, .consent-overlay, .cookiebar {
  display: none !important;
}
body.cookie-banner-open, body.has-cookie-banner, html.cookies-open {
  overflow: auto !important;
}

/* Dead account/login modals left by the CMS (no backend on a static host) */
.modal-login, #loginModal, .login-modal { display: none !important; }

/* Carousel slots the platform's JS bundles would have filled at runtime: without a working
   bundle they stay as <img> elements with no src and render as broken-image icons. Nothing is
   lost by hiding them — they never had content in the restore. */
img:not([src]), img[src=""], img[src="#"] { display: none !important; }

/* The client's backlink block must read as the page's own copy. Where a theme only colours
   links inside specific containers, the anchor would otherwise look like plain text — inherit
   the surrounding colour but keep an underline so it is still visibly a link. */
.content-wraparea a { color: inherit; text-decoration: underline; }

/* A few px of horizontal overflow on phones (an absolutely-positioned login list, a wide footer
   logo) makes the whole page pannable sideways, which reads as broken.
   NB: use `clip`, never `hidden`, and never on html together with height:100%. `overflow:hidden`
   turns the element into a scroll container: on themes that set html{height:100%} it stops body's
   overflow propagating to the viewport, the window stops scrolling entirely and every
   scroll-driven behaviour (sticky nav, back-to-top, in-page anchors, PageDown/End) dies.
   `clip` suppresses the sideways pan without creating a scroll container. */
body { overflow-x: clip; }
/* ---- end generated block; anything below is preserved across re-runs ---- */

/* ============================================================================================
   A PHONE GETS A PHONE LAYOUT (o7 fixer, 2026-10-17)
   restore_03_seo.py INSERTED width=device-width into a fixed 650px design, so a 390px phone
   laid out 650px centred and cropped BOTH sides: the left menu (an absolutely positioned column
   pulled out to margin-left:-55px, i.e. outside the page box) fell off the left edge and the
   text (460px column with 100px/90px margins) ran off the right. A fixed viewport would shrink
   the copy to ~5px (order 4 tried it, the client rejected it), so device-width stays and the
   pixel-pinned boxes are released: .contenidos / .contenedor_textos / .textos become fluid, the
   menu leaves absolute positioning and becomes a wrapped row of the same pink buttons above the
   text, the banner photo scales inside its box, the form fields stack at full width.
   ============================================================================================ */
@media (max-width: 768px) {
  html, body { max-width: 100%; }
  #contenedor { min-height: 0; }
  .contenidos, .contenedor_textos {
    width: auto !important; max-width: 100%; float: none; margin-left: 0; margin-right: 0;
    box-sizing: border-box;
  }
  .contenidos { padding: 0 12px; margin-bottom: 30px; }
  #cabecera { height: auto; padding: 12px 0 0; overflow: visible; }
  #cabecera h1, h1[class^="fondo_"] {
    float: none; width: auto !important; height: 130px !important; padding: 0; margin: 0;
    background-size: contain; background-position: center top;
  }
  #cabecera h1 a { width: 100%; height: 100%; background: none; }
  .corte { padding-top: 120px; }

  #menu { position: static; width: auto; font-size: 0.95em; }
  #menu div.menu1 { margin: 8px 0; float: none; overflow: visible; }
  #menu ul { display: flex; flex-wrap: wrap; gap: 6px; }
  #menu ul li { display: block; padding: 0; flex: 1 1 auto; }
  #menu ul li a, #menu ul li a:hover, #menu ul li a.on {
    width: auto !important; padding: 9px 12px !important; text-align: center;
  }
  .espacio { padding: 0 0 8px; }

  .textos { float: none; width: auto !important; margin: 6px 0 0; padding: 0 0 30px; }
  .textos img, .contenidos img { max-width: 100%; height: auto; }
  .fotocontenidos { float: none; padding: 0 0 10px; }
  #submenu ul { float: none; width: auto; }
  .listado_fotos ul, #dhtmlgoodies_slideshow, #imagen, #thumbwrapper, #thumbarea {
    width: auto !important; max-width: 100%;
  }

  fieldset.contacto .campos { padding: 12px; }
  fieldset.contacto .campos label { float: none; display: block; width: auto; text-align: left; padding: 0 0 3px; }
  fieldset.contacto .campos input, fieldset.contacto .campos textarea,
  fieldset.contacto .campos select { width: 100%; box-sizing: border-box; }
  fieldset.contacto .campos input.boton { width: auto; padding: 6px 14px; }

  /* o7 round 2: the desktop #pie is pulled UP over the content by margin-top:-220px (the .corte
     spacer above it is sized to pay for that). With .corte shortened to 120px the footer's opaque
     background painted over the bottom ~70px of the white panel while the text stayed on top, so
     the last lines printed on blue. On a phone the footer simply follows the content. */
  .corte { padding-top: 0; }
  #pie { height: auto; min-height: 120px; margin-top: 0; clear: both; }
  #fondo_pie { height: 120px; background-size: cover; }
  .fijos { padding-top: 70px; }
}

/* ===== CONTRAST ROUND (2026-10-19, gate legibility) ======================================
   Main menu tabs: the site's own link text is #fde (very pale pink) on a #EA69A9 fill, which
   measures 2.37:1 (the gate's figure matches this calculation). The hover state of the same menu
   already pairs white text with a fill, so the fill is darkened within the same pink hue to
   #b31965 (6.47:1 against white) and the text becomes white. The hover and selected states keep
   their own colours (#37525B). No background photograph and no text content is touched. */
#menu ul li a { color: #fff; background-color: #b31965; }

/* ===== ORDER 7 ROUND 2026-10-20 (one agent looked, fixed and re-measured) ================= */

/* THE FOOTER'S ONE LINK. `.fijos` sets bold 10px Verdana, below the 12px floor on every page of
   the site; 12px is the smallest change that reads, and the link keeps its colour, weight, case
   and place on the toothbrush illustration. */
.fijos { font-size: 12px; }

/* THE APPOINTMENT FORM (/cita/). Its labels now point at real fields (the ids their for= always
   named), so each one is a control that focuses its field - and at 15px tall (18px on a phone)
   too short to hit. The box grows to 24px; on the desktop float the negative margin keeps the text
   exactly where it was beside its field. The submit is a <button> holding the site's own
   "enviar" picture, drawn with no chrome of its own so it looks as the image input did. */
fieldset.contacto .campos label { padding-top: 5px; padding-bottom: 4px; margin-top: -5px; }
fieldset.contacto .campos button.boton {
  display: inline-block; margin: 0; padding: 0; border: 0; background: none; cursor: pointer;
  line-height: 0; vertical-align: middle; }
fieldset.contacto .campos button.boton img { display: block; }
@media (max-width: 768px) {
  fieldset.contacto .campos label { padding: 5px 0 4px; margin-top: 0; }
}

/* ===== ORDER 7 ROUND 2026-10-20, EVENING (one agent looked, fixed and re-measured) ========= */

/* THE PHONE HEADER LOST THE CLINIC'S NAME AND TELEPHONE. The logo is the background of `h1 a`
   (img/logo: the "CLINICA DENTAL Adriana Gozalo" swoosh with the white "948 40 33 48" strip
   beneath it), and the phone block above set `#cabecera h1 a { background: none }`. On /cita/
   and /accesibilidad/ that left a cropped photo of a mouth; on the nine inner pages whose header
   photo is a 1x1 transparent gif it left a 130px band with nothing in it. The logo comes back at
   the left of the band, as on the desktop, and where the band has a photo it moves to the right:
   the photo's left edge is a transparent diagonal, which is what the desktop logo sits against.
   Only an h1 that holds the logo link is affected - the authored pages print their title as text. */
@media (max-width: 768px) {
  #cabecera h1 a { background: url("/img/logo-47d4d6f0.png") left center / auto 120px no-repeat; }
  #cabecera h1[class^="fondo_"]:has(> a) { background-position: right top; }
}

/* THE FOOTER LINK PRINTED ACROSS THE TOOTHBRUSHES. The forest drawing is 397x129 and fills its
   whole height; on the desktop `.fijos` sits 160px down, below it. The phone block shrank the band
   to 120px with background-size:cover and put the link 70px down - inside the drawing, its letters
   across a toothbrush handle. On a phone the drawing keeps its own size and the link goes back
   underneath it, as on the desktop. The list now also carries the three legal pages (nothing linked
   to them before - see footer_links in _recon/authored_*.json), so on a phone it may wrap: the band
   grows with it instead of clipping it (#fondo_pie is overflow:hidden), and each link gets a row
   a finger can hit. */
@media (max-width: 768px) {
  #pie { min-height: 160px; }
  #fondo_pie { float: none; height: auto; min-height: 160px; padding-bottom: 10px;
    background-size: auto; background-position: center 0; }
  .fijos { padding-top: 132px; }
  .fijos li a { display: inline-block; padding: 6px 0.5em; }
}

/* THE APPOINTMENT FORM'S FIELDS WERE 18px TALL ON A PHONE. They are a finger's target and the only
   way to ask for an appointment from this page; at 390 they now take a comfortable height. Desktop
   keeps the site's own slim fields. */
@media (max-width: 768px) {
  fieldset.contacto .campos input[type="text"], fieldset.contacto .campos select {
    min-height: 36px; padding: 4px 6px; font-size: 15px; }
  fieldset.contacto .campos textarea { font-size: 15px; padding: 4px 6px; }
}

/* The dhtmlgoodies slideshow on /quienes_somos/instalaciones/ lost its engine with the archive.
   #previewPane is a fixed 410px box with background #ea69a9, and the large photograph that used
   to fill it was inserted by image-slideshow.js, which also raised the thumbnails from the
   opacity:0.5 they are given in general.css. So the page rendered a 460x410 pink slab carrying
   nothing but one caption, over three faded thumbnails - the client's "empty block where an image
   belongs", first on his rejection list.
   Only three photographs of the premises survive in the capture and all three are 80x60: there is
   no large image to put back, and upscaling a thumbnail to half a screen would be a lie about what
   the site showed. So the dead pane and the dead arrows go, and the three real photographs are
   shown at full opacity as the plain strip they are. Nothing is invented and nothing is stretched.
   The ten .imageCaption divs stay hidden as general.css has them: they sit after the images rather
   than beside them, so showing three of ten would caption the wrong photograph. Each img carries
   its own correct alt. */
#previewPane { display: none !important; }
#arrow_left, #arrow_right { display: none !important; }
#galleryContainer { height: auto !important; overflow: visible !important; }
#theImages { position: static !important; left: 0 !important; width: auto !important;
             height: auto !important; overflow: hidden; }
#theImages img { opacity: 1 !important; filter: none !important; cursor: default;
                 margin: 0 6px 0 0; }
#dhtmlgoodies_slideshow { width: auto !important; }
