/* 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 ---- */

/* =============================================================================================
   order-7 fixer round (podocarthago.com). Every rule below answers a defect in
   _recon/visual_podocarthago.com.json; the page markup is untouched except where noted.
   ============================================================================================= */

/* P1. THE SLIDER BAND WAS EMPTY ON EVERY PAGE.
   The pages call $('#slider').nivoSlider(...) but the archive never kept jQuery 1.6.1 (a CDN
   script), so the plugin throws before it starts and the five photographs stay at the template's
   display:none: a 270px blank band under the menu. The photographs are all here and are the
   site's own (870x270, the exact size of the band). A real, honest replacement that needs no
   script: the same five images cross-faded one after another, 5s each, in the document order the
   slider used. The first image is the resting state (opacity 1), so a reader with animations
   switched off, or a capture taken at t=0, sees a photograph and not a blank. */
.banner { position: relative; max-width: 100%; }
#slider.nivoSlider {
  position: relative;
  width: 870px; max-width: 100%;
  height: auto; aspect-ratio: 870 / 270;
  margin: 0 auto;
  background: none;
  overflow: hidden;
}
#slider.nivoSlider img {
  display: block !important;
  position: absolute; top: 0; left: 0;
  width: 100%; height: 100%;
  object-fit: cover;
  opacity: 0;
  animation: podo-fade 25s linear infinite;
}
#slider.nivoSlider img:nth-child(1) { opacity: 1; animation-delay: 0s; }
#slider.nivoSlider img:nth-child(2) { animation-delay: 5s; }
#slider.nivoSlider img:nth-child(3) { animation-delay: 10s; }
#slider.nivoSlider img:nth-child(4) { animation-delay: 15s; }
#slider.nivoSlider img:nth-child(5) { animation-delay: 20s; }
@keyframes podo-fade {
  0%   { opacity: 1; }
  20%  { opacity: 1; }
  23%  { opacity: 0; }
  97%  { opacity: 0; }
  100% { opacity: 1; }
}
@media (prefers-reduced-motion: reduce) {
  #slider.nivoSlider img { animation: none; }
  #slider.nivoSlider img:not(:first-child) { opacity: 0; }
}

/* P2. THE MENU WAS WHITE ON PALE GREY. The template wrote the four menu words in #ffffff and
   meant them to sit on a coloured pill (.circulos) whose background image is a 1x1 transparent
   placeholder in the archive. With no pill the words land on the page grey at under 1.5:1. The
   site's own dark grey (#575757, used for its hover) carries them at 5.6:1 on #e2e2e2; hover
   goes to a darker shade of the site's blue. */
a:link.boton, a:visited.boton, a:active.boton { color: #2b2b2b; }
a:hover.boton { color: #2f6f8f; }

/* P3. ONE PAGE (/patologias-de-la-una/) CARRIED ITS OWN, DARKER BODY COLOUR. Eight pages use
   #e2e2e2; the odd one out made the whole site change shade for a click and back. */
body { background-color: #e2e2e2 !important; }

/* P4. THE SIDEBAR RULE. The thin blue line beside the service list is three parts: a fading cap
   at the top, a fading cap at the bottom and a middle cell (td.barra) whose repeating image is a
   1x1 transparent placeholder in the archive, so only the caps drew. The middle repeats the
   caps' own colour, #00A0DF, and their two-pixel width (columns 9-10 of the 20px cell), at the
   opacity where the caps meet it (161/255). */
td.barra {
  background-image: linear-gradient(to right, transparent 9px, rgba(0, 160, 223, 0.63) 9px,
                                    rgba(0, 160, 223, 0.63) 11px, transparent 11px);
  background-repeat: no-repeat;
  background-position: center top;
  background-size: 20px 100%;
}

/* P5. /contacto/ HAD AN EMPTY LEFT COLUMN. The page is a two-cell table whose first cell
   (width 55%, only a <br>) held an illustration in the original that the archive did not keep.
   Nothing is invented to fill it: the cell is dropped and the contact details, which are all
   the page has, are centred in the width. */
.dentro > table td[width="55%"] { display: none; }
.dentro > table td[width="45%"] { width: 100%; text-align: center; padding: 24px 0 40px; }

/* P6. PHONE. restore_03_seo.py put width=device-width on a fixed 870px template; at 390 the
   phone showed the left 390px and cropped the rest (menu, photographs, the whole /contacto/
   block). The meta stays (a fixed viewport scales the type to 5px and was rejected on order 4)
   and the template reflows below 768px. Unpinned: .arriba (870 wide, 205 tall), .logo and
   .circulos/.menu/.iconitos (positioned by top/left offsets), .banner, .dentro (800 wide), .pie
   (870 wide) and the layout tables inside .dentro and .pie (service pages put the sidebar and
   the text in two table cells; the footer puts four facts in four cells). */
@media (max-width: 768px) {
  .arriba { width: auto; height: auto; padding: 12px 12px 0; box-sizing: border-box; }
  .logo { position: static; width: auto; height: auto; text-align: center; margin: 0 0 8px; }
  .logo img { max-width: 100%; height: auto; }
  .circulos { position: static; width: auto; height: auto; }
  .menu { position: static; width: auto; left: auto; top: auto; }
  .menu table { width: 100%; }
  .menu table td { width: 25% !important; padding: 8px 2px; }
  .iconitos { position: static; width: auto; left: auto; top: auto; margin: 4px auto 10px; }
  .iconitos table { margin: 0 auto; }
  .banner { width: auto; height: auto; }

  .dentro { width: auto; padding: 14px 16px 0; box-sizing: border-box; text-align: left; font-size: 15px; line-height: 1.5; }
  .contenido { padding-left: 0; text-align: left; font-size: 15px; line-height: 1.5; }
  .dentro > table, .dentro > table > tbody, .dentro > table > tbody > tr,
  .dentro > table > tbody > tr > td { display: block; width: 100% !important; }
  .dentro > table > tbody > tr > td.submenu { padding-bottom: 12px; }
  /* the vertical rule and its caps only make sense beside a list */
  .dentro .submenu table, .dentro .submenu table tbody, .dentro .submenu table tr,
  .dentro .submenu table td { display: block; width: auto; height: auto !important; }
  .dentro .submenu td.barra, .dentro .submenu td[align="center"] { display: none; }
  .submenu a { display: inline-block; padding: 3px 0; }
  .dentro img, .contenido img { max-width: 100%; height: auto; }

  .pie { width: auto; padding: 0 16px 24px; box-sizing: border-box; font-size: 12px; line-height: 1.5; }
  .pieCopia, .pieCopia tbody, .pieCopia tr, .pieCopia td { display: block; width: 100% !important; }
  .pieCopia { font-size: 12px; line-height: 1.5; }
  .pieCopia td { padding: 0 0 14px; overflow: hidden; }
  .pieCopia td img { margin-right: 10px; }
}

/* CONTRAST (gate legibility, 2026-10-19). The service-page submenu links (Delaminacion, Una encarnada,
   Ortopodologia...) are the site's own blue #4188a8 on the beige submenu ground: 3.05:1 measured, below the
   4.5:1 body-text bar. Same hue, darkened in lightness only, so it clears 4.5:1 on both white and the beige
   ground (#2d5f76: about 5.4:1 on the measured grey ground, 6.98:1 on #fff). The hover grey #575757 is the site's own and is kept. */
.dentro .submenu a, .dentro .submenu a:visited, .dentro .submenu a:active { color: #2d5f76; }
.dentro .submenu a:hover { color: #575757; }

/* LEGIBILITY, THE TWO BLOCKING CLASSES (gate legibility, order-7 round of 2026-10-20). Every page of
   the site carried the same two, which is all its 114 was made of: 24 x the logo link, 90 x the
   footer type. Low contrast does not block and was not touched here.

   (L1) THE LOGO LINK MEASURED 296x17. <a href="/"> wraps the 296x95 logo, but it is an inline box,
   and an inline box is as tall as its line of text, not as the picture inside it. A finger on the
   picture always landed on the link (the image is its child), so the control was never actually
   unpressable - but its own box said 17px to every tool that asks it. inline-block makes the box
   the picture. An inline image already sat at the top of its line, so nothing moves on screen. */
.logo a { display: inline-block; vertical-align: top; }
.logo a img { display: block; }

/* (L2) THE FOOTER WAS 9px TYPE ON 10px LINES. That is what the clinic published (inline <style>,
   .pie and .pieCopia, every page) and it is the whole of its contact block: address, e-mail,
   telephone, "previa cita", and the practitioner's registration line. At 9px it needs a magnifying
   glass on a desktop. The phone rule above had already taken it to 12px; this does the same for
   the desktop, and does it by SCALING the original footer rather than redesigning it: 9->12px and
   10->13px lines is a factor of 4/3, and the 600px table becomes 800px (the width of the text column
   above it), whose four cells keep their published 165:139:173:123 proportions because their own
   width attributes are what the table distributes. Four lines of 13px are 52px; the pictograms are
   39px and are NOT upscaled (their files are 39px, a 4/3 stretch would blur them), they are centred
   on the four lines instead, so no line wraps under them. Words, line breaks, order, colour,
   alignment and pictograms are the original's. */
@media (min-width: 769px) {
  .pieCopia { width: 800px; font-size: 12px; line-height: 13px; }
  .pieCopia td img { margin-top: 6px; margin-bottom: 7px; }
  .pie p { font-size: 12px; line-height: 13px; }
}
/* (L3) PHONE: the fourth line of each footer fact wrapped UNDER its pictogram ("estamos a su
   disposicion." and "o el tel 868 09 18 12" started at the left edge, below the icon), because a
   39px float is shorter than four 18px lines. The pictogram is pinned beside the text instead, in a
   72px gutter (the widest pictogram is 60px), so each fact reads as one block. */
@media (max-width: 768px) {
  .pieCopia td { position: relative; padding-left: 72px; min-height: 53px; box-sizing: border-box; }
  .pieCopia td img { position: absolute; left: 0; top: 0; margin: 0; }
}

/* (L4) THE THREE PAGES WE WROTE (/404.html, /politica-de-cookies/, /politica-de-privacidad/) opened
   with a small black bold line (<p><strong>...</strong></p>) where every archived page opens with
   the site's own heading, p.titulo: Museo500, 20px, the site's blue #00A0DF. Same look, by CSS: the
   selector needs a FIRST paragraph of .contenido that is not .titulo and holds nothing but a
   <strong>, which only those three pages have (every archived page's first paragraph is .titulo).
   No words change. */
.contenido > p:first-child:not(.titulo):has(> strong:only-child) {
  font-family: 'Museo500', Arial, Helvetica, sans-serif; font-size: 20px; color: #00A0DF;
}
.contenido > p:first-child:not(.titulo):has(> strong:only-child) > strong { font-weight: normal; }

/* (L5) PHONE: a photograph floated beside the text took up to 284px of a ~358px column on
   /patologias-de-la-una/, leaving a 50px strip where the first sentence ran one word per line.
   Below 480px a floated content photograph keeps its float and its side but is capped at 55% of
   the column, so the text beside it always has a usable width. Desktop is untouched. */
@media (max-width: 480px) {
  .contenido img.img_derecha, .contenido img.img_izquierda,
  .contenido img[align="right"], .contenido img[align="left"] { max-width: 55%; height: auto; }
}

/* (L6) /instalaciones/ IS THE ONE PAGE WHOSE PHOTOGRAPHS FLOAT LOOSE IN .dentro (every other page
   holds its floats inside a table cell, measured over all 21 pages). Nothing cleared them, so the
   footer flowed up underneath: the second photograph's lower edge sat on the footer row, and once
   (L2) widened the footer to the text column's 800px, its fourth fact ("Las consultas son previa
   cita") printed ~6px under that photograph. The container now ends below its own floats; on the
   other twenty pages there is no float to clear and nothing moves. */
.dentro::after { content: ""; display: block; clear: both; }

/* (L7) PHONE: THE PAGE'S OWN TEXT BEFORE THE SERVICE LIST (o7 r6, 2026-10-20). Below 768px the
   two-cell row of every service page, the 404 and both legal pages (td.submenu, then td.contenido -
   18 pages, one such row each, measured) stacked in source order, so after the hero a phone showed
   the bare 14-link service list and the page's own heading only at y~800; on the 404 the message
   was the last line of the first screen. The phone layout is this restoration's (P6 above: the
   clinic published a fixed 870px desktop template), so its order is ours to choose: the text now
   comes first and the list after it, before the footer. Same cells, same words, same list; desktop,
   /, /contacto/ and /instalaciones/ (no submenu cell) are untouched. */
@media (max-width: 768px) {
  .dentro > table > tbody > tr:has(> td.submenu):has(> td.contenido) { display: flex; flex-direction: column; }
  .dentro > table > tbody > tr > td.contenido { order: -1; }
  .dentro > table > tbody > tr:has(> td.contenido) > td.submenu { padding-top: 18px; padding-bottom: 12px; }
}
