/* ==============================================================================================
   laboratoire-dentaire-sinard.com - restore-extras.css
   Authored during the order-5 finish pass (2026-08-19). Nothing here is archived material: the
   four original stylesheets (general/body/form/menus.css) are left byte-exact and this file is
   linked AFTER them, so every rule below is an override that can be deleted to get the 2014 site
   back unchanged.

   Three jobs, in the order they were found:
     A. legibility  - the 2009 design sets 9px, 10px and 11px type and 17px-tall nav links
     B. phone       - the original declares no viewport at all and has zero @media rules
     C. desktop     - keep the 980px payload the site actually was
   ============================================================================================== */


/* ----------------------------------------------------------------------------------------------
   SECTION A - LEGIBILITY

   qa_legibility.js at 1440 and 390 reported, before this file existed: 9px "[Derniere mise a jour]"
   stamp, 10px footer bar, nav anchors 109x17 (the CELL is 40px tall but the <a> inside it is not,
   so a finger has nothing to land on), and "Mentions legales" rendered in the footer's own colour
   with no underline - a link indistinguishable from the prose beside it.

   The type sizes are raised to the 12px floor rather than to a modern 16px: this is a 2009
   fixed-width design and the relationship between its sizes is part of what it looked like.
   -------------------------------------------------------------------------------------------- */

body            { font-size: 12px; }
/* .subtitre was rgb(150,150,150) on white: 2.93:1, under the 4.5:1 floor. rgb(105,105,105) is
   5.5:1 and still reads as a subtitle beside the black .titreSpan above it. */
.subtitre       { font-size: 12px; color: rgb(105, 105, 105); }
td.liteComment  { font-size: 12px; }
td.bottom       { font-size: 12px; }
/* nowrap because the footer bar is a single centred line of four short policy links separated by
   pipes: left to wrap, "Plan du site" broke after "Plan" on every page at 390 AND at 1440, leaving
   the word "site" alone and underlined on a line of its own, which reads as a fifth link. A link
   label is one thing; it should break as one thing. */
a.bottom        { font-size: 12px; text-decoration: underline; white-space: nowrap; }
/* Independent review defect 9, second half of the same bug: the label fix above stopped "Plan du
   site" splitting internally, but the " | " separator sat as loose text BETWEEN the anchors in the
   markup, so a line could still break right after a pipe - "Mentions legales | Confidentialite |
   Cookies" on one line, a bare "|" hanging at its end, "Plan du site" orphaned alone below it. Each
   separator now lives INSIDE the <a>'s wrapping span as "| Label" (o5_sinard_finish.py FOOTER_LINKS
   and the splash's .o5-sitefoot), so nowrap here binds the pipe to the link that follows it and a
   break can only fall on the plain space BETWEEN two "| Label" groups, never inside one. */
.o5-footsep     { white-space: nowrap; }
.SupportHead    { font-size: 12px; }
#TopBoxHeaderSupportClientele { font-size: 12px; }

/* The per-page "last updated" stamp. Its 9px is inline on the <td>, so it needs the class the
   finish pass adds rather than a bare element selector. */
td.majstamp { font-size: 12px !important; font-family: tahoma, verdana, sans-serif; }

/* A nav link has to BE the 40px cell, not sit in the middle of it. */
a.menuBox, a.menuBoxSelect { display: block; line-height: 40px; }

/* The splash page's two entries are images inside anchors; an inline anchor reports a 15px text
   box to any tap-target measurement instead of the 64px picture it actually contains. Scoped to
   the mosaic table so that the woven paragraph below it keeps normal inline link wrapping.

   THE WHOLE MOSAIC HAS TO GO BLOCK TOGETHER, and this is the trap. Making only the two linked
   slices display:block left their row-mates inline, sitting on a text baseline with the descender
   space under them - white seams straight across a picture that had none, visible at 1440 in the
   screenshot and in nothing any gate measures. So every slice is block and every cell has its
   line-height and font-size zeroed: a nine-piece sliced GIF is one picture, not nine pictures. */
#homePage #Tableau_01 td,
#homePage #Tableau_02 td { padding: 0; line-height: 0; font-size: 0; }
#homePage #Tableau_01 img,
#homePage #Tableau_02 img { display: block; }

/* AND THE ANCHOR HAS TO BE A BLOCK, NOT AN INLINE-BLOCK. This is the 2026-08-19 review finding and
   it is the second half of the same trap. An inline-block SHRINK-WRAPS: it takes its width from its
   content, so the `width:100%` the phone section gives the slice image resolved against the ANCHOR
   (still at the GIF's intrinsic 184px/172px) instead of against the cell, which table-layout:fixed
   had already stretched to 254px/238px. The two LINKED slices - "ENTREE HTML" and "ENTREE FLASH",
   the only two links on the page - therefore sat in blocks of bare page background from 723px to
   1000px, while 390 and 1440 stayed perfect because at those widths the cell happens to equal the
   intrinsic width. A block box fills its cell instead of shrink-wrapping, which fixes the band
   without giving anything back at either end; measured flush at 21 widths from 360 to 1600 by
   _scripts/_o5rw_sinard_band.js. Do not put this back to inline-block to "fix" a tap target - a
   block anchor is the full 184x64 picture and measures larger, not smaller. */
#homePage #Tableau_02 a  { display: block; line-height: 0; }

/* The splash page carries no footer bar of its own - the site's only legal link lived on the
   inner template - so the four policy pages are stated here in the footer bar's own type. */
.o5-sitefoot   { max-width: 721px; margin: 6px auto 18px; text-align: center;
                 font-family: verdana, arial, sans-serif; font-size: 12px; line-height: 2;
                 color: rgb(50, 50, 50); }
.o5-sitefoot a { font-family: verdana, arial, sans-serif; font-size: 12px;
                 color: rgb(50, 50, 50); text-decoration: underline; white-space: nowrap; }

/* The splash page's own text band: the business said in the site's own published words, and below
   it, kept in a wrapper of its own because the backlink check requires exactly one <a> inside
   .content-wraparea, the woven paragraph. Both copy the masthead's 721px axis and the page's own
   tahoma, so they read as part of the same document rather than as something bolted on. */
.o5-intro      { max-width: 721px; margin: 14px auto 0; text-align: left;
                 font-family: tahoma, verdana, sans-serif; font-size: 13px; line-height: 20px;
                 color: #333; }
.o5-intro p    { margin: 0 0 .7em; font-size: 13px; color: #333; }
.o5-intro a    { font-family: tahoma, verdana, sans-serif; font-size: 13px; }

/* The woven paragraph on the splash page. */
.content-wraparea            { max-width: 721px; margin: 12px auto 18px; text-align: left;
                               font-family: tahoma, verdana, sans-serif; font-size: 13px;
                               line-height: 20px; color: #333; border-top: 1px solid #ccc;
                               padding-top: 10px; }
.content-wraparea p          { margin: 0 0 .7em; font-size: 13px; color: #333; }
.content-wraparea p:last-child { margin-bottom: 0; }

/* Authored pages (404, cookies, privacy, plan du site, the retired Flash entry) share this
   container. A list item whose whole content is one link is a navigation control, not a link in
   prose, so a tap-target measurement counts its 15px text box; the padding gives it 27px without
   changing how the list reads. */
.o5-legal a    { text-decoration: underline; }
.o5-legal li   { margin-bottom: .5em; }
.o5-legal li a { display: inline-block; padding: 6px 0; }

/* The honest replacements the finish pass installs where a dead widget used to be: the Flash
   intro, and the two forms that posted to a script that no longer exists. */
.o5-note  { border: 1px dashed rgb(160, 180, 205); background: rgb(246, 250, 255);
            padding: 14px 18px; margin: 18px 0; text-align: left; font-family: arial, verdana;
            font-size: 13px; line-height: 1.55; color: rgb(80, 80, 80); }
.o5-note strong { color: rgb(44, 119, 183); }
.o5-contact { text-align: left; font-family: arial, verdana; font-size: 13px; line-height: 1.7;
              color: rgb(80, 80, 80); }
.o5-contact a { font-size: 13px; text-decoration: underline; }
.o5-cta   { display: inline-block; margin: 6px 0; padding: 10px 18px; min-height: 24px;
            background: rgb(44, 119, 183); color: #fff !important; font-family: verdana, arial;
            font-size: 13px; text-decoration: none !important; border-radius: 3px; }
.o5-cta:hover { background: rgb(28, 90, 145); color: #fff !important; }


/* ----------------------------------------------------------------------------------------------
   SECTION C - DESKTOP: THE 980px PAYLOAD IS WHAT THIS SITE WAS

   The layout width lives in an HTML width="980" attribute, nowhere in CSS, which is why
   qa_client_bar's captured_device_payload check read the site as a phone capture. Stating it in
   CSS is not a change to the design, it is writing down the width the design already had.
   -------------------------------------------------------------------------------------------- */

@media (min-width: 1001px) {
  table.main { width: 980px; }
}


/* ----------------------------------------------------------------------------------------------
   SECTION P - PHONE: A REAL REFLOW, NOT A SHRUNK DESKTOP

   WHAT WAS WRONG. All 11 pages declared no viewport, so a phone lays the page out at a notional
   ~980px and scales the whole thing down - the client's "hold a magnifying glass to the screen".
   The plan note's original instruction was to ship viewport width=980, but qa_client_bar now fails
   any fixed-width viewport for exactly that reason (the wenou.pt finding), so the meta says
   width=device-width and this section supplies the layout that makes device-width safe.

   WHY device-width ALONE WOULD BE WORSE. The shell is <table class="main" width="980"> with a
   224px menu cell beside a 756px content cell, and the FCKeditor bodies inside carry their own
   px-width tables (721px on the splash, 600px on the contact form) plus <td nowrap>. Left alone at
   390px the table would simply be 980px wide inside a 390px window: sideways scroll on every page.
   So the shell, its rows and its cells all become blocks, and every inner table and image is
   capped at the container width.

   WHY 1000px AND NOT 768px. The breakpoint is the design width, not a device class: below 1000px
   the 980px table no longer fits, whatever is holding the screen. A tablet in portrait gets the
   column layout for the same reason a phone does.

   WHAT IS DELIBERATELY NOT REFLOWED. The splash mosaic on / is one picture cut into nine GIF
   slices; stacking the slices would be nonsense, so it scales as a unit. The <colgroup> the finish
   pass adds carries each slice's exact share of the 721px and 635px rows (38/721, 635/721, 48/721
   and 79/635, 184/635, 155/635, 172/635, 45/635), and table-layout:fixed makes the browser honour
   them, so the mosaic stays seamless at any width.
   -------------------------------------------------------------------------------------------- */

@media (max-width: 1000px) {

  body { margin: 0 0 5px 0; }

  /* the 980px shell becomes a single column */
  table.main,
  table.main > tbody,
  table.main > tbody > tr,
  table.main > tbody > tr > td {
    display: block !important;
    width: auto !important;
    max-width: 100%;
    height: auto !important;
  }
  table.main { margin-top: 0; }

  /* td.haut is the empty decorative cap beside the logo; on one column it is a 30px blue bar with
     nothing in it, and dropping it removes a gap, not content. */
  table.main > tbody > tr > td.haut { display: none !important; }

  /* The menu column becomes a banner strip above the content.

     ITS CHROME IS THREE SPRITES CUT FOR A 224px COLUMN and none of them survives being widened.
     menu-1_03 is a 224px horizontal gradient (repeat-y), menu-1_02 a 224x508 panel with a darker
     1px right border, menu-1_01 the 224x109 logo tile with a border of its own. Stretched or
     tiled across 390px they produce seams the first phone screenshot showed as a light vertical
     bar beside the logo. So the band is painted in the flat colour sampled from the middle of the
     logo tile's own field - rgb(205,223,239) - and only the logo tile itself is kept, at its
     natural size, centred on it. */
  td.menu { background-image: none; background-color: rgb(205, 223, 239);
            padding-bottom: 14px; }
  td.menu > table,
  td.menu > table > tbody,
  td.menu > table > tbody > tr,
  td.menu > table > tbody > tr > td {
    display: block !important; width: auto !important; height: auto !important;
  }
  /* The logo lives in td.menuT1's BACKGROUND, so the cell has to keep its 109px or the mark
     disappears entirely on a phone. Written at the full child-chain specificity because the
     height:auto rule above it is also !important and more specific - a plain `td.menuT1` lost,
     silently, and the first phone screenshot came back with a nav band and no logo on it. */
  td.menu > table > tbody > tr > td.menuT1 {
    height: 109px !important; background-position: top center !important; }
  td.menu > table > tbody > tr > td.menuT2 { background-image: none !important; }
  table.menuBox { width: 100% !important; max-width: 340px; margin: 0 auto; }

  /* the content column */
  .corps { padding: 12px 14px 26px !important; }
  div.block { margin-left: 0 !important; }
  table.TopBox { padding: 8px 0 0 0; }

  /* every table and picture the FCKeditor bodies carry has a px or % width of its own */
  .corps table,
  .corps table[style] { width: 100% !important; max-width: 100% !important; height: auto !important; }
  .corps img { max-width: 100%; height: auto; }
  .corps td[nowrap], td[nowrap] { white-space: normal !important; }
  .corps td { word-break: break-word; }

  /* The 980px rule above the footer is a picture of the desktop layout - a blue band with the
     content cell's drop shadow burnt into it at the 224/756 split. That split does not exist in
     one column, so squashed to 390px it reads as a rendering fault rather than as trim, and it
     carries no information. It goes; the footer bar butts against the content instead.

     The footer bar's own background is a 980x6 strip that is footer-blue for 890px and page-blue
     for the last 90px - the desktop bar deliberately stops short of the right edge. Scaled to a
     phone that tail is a 35px stripe of a different blue, and because a background is sized to the
     PADDING box it also left the bar's own 10px padding uncovered. Flat rgb(141,172,195), the
     colour sampled from that strip, edge to edge. */
  table.main img[src*="home-001_04-"] { display: none; }
  td.bottom { height: auto !important; padding: 14px 12px; line-height: 1.9;
              background-image: none; background-color: rgb(141, 172, 195); }

  /* the splash page: scale the nine-slice mosaic as one picture */
  #homePage table.TopBox { padding: 0; }
  #homePage #Tableau_01,
  #homePage #Tableau_02 { width: 100% !important; height: auto !important; table-layout: fixed; }
  #homePage #Tableau_01 img,
  #homePage #Tableau_02 img { width: 100% !important; height: auto !important; display: block; }
  #homePage #Tableau_01 > colgroup > col.sl-38  { width: 5.2704%; }
  #homePage #Tableau_01 > colgroup > col.sl-635 { width: 88.0721%; }
  #homePage #Tableau_01 > colgroup > col.sl-48  { width: 6.6575%; }
  #homePage #Tableau_02 > colgroup > col.sl-79  { width: 12.4409%; }
  #homePage #Tableau_02 > colgroup > col.sl-184 { width: 28.9764%; }
  #homePage #Tableau_02 > colgroup > col.sl-155 { width: 24.4094%; }
  #homePage #Tableau_02 > colgroup > col.sl-172 { width: 27.0866%; }
  #homePage #Tableau_02 > colgroup > col.sl-45  { width:  7.0867%; }
  .o5-intro, .content-wraparea, .o5-sitefoot { padding-left: 14px; padding-right: 14px; }

  /* authored pages */
  .o5-legal { padding: 1.4em 0 2.4em !important; }
}


/* ----------------------------------------------------------------------------------------------
   SECTION R - o7 visual review, 2026-10-14 (phone column, max-width 1000px)

   1. The blue square that opens each page body (carrebleu, float:left, 21x25) relied on
      div.block's margin-left:30px to keep the heading off it. Section P zeroes that margin on
      one column, so a left-aligned heading beside the float - "MENTIONS LEGALES" - started on the
      square's right edge with no gap at all. The float gets its own gutter instead.
   2. The logo lives in td.menuT1's background: the 224x109 sprite menu-1_01, whose last ~9px
      columns are the start of the desktop column's drop shadow (rgb 172,189,208 at the bottom of
      x=223). Centred on the flat phone band that shading stood out as a dark vertical edge down
      the right side of the logo tile on every inner page. The cell is narrowed to the sprite's
      shadow-free 214px and centred, so the edge is simply not painted. Still a 214x109 target. */
@media (max-width: 1000px) {
  .corps img[src*="carrebleu"] { margin-right: 10px; }
  td.menu > table > tbody > tr > td.menuT1 {
    width: 214px !important; margin: 0 auto !important; background-position: top left !important; }
}
