/* ==========================================================================
   CIRE child theme - listing detail
   MRT-OUTSTANDING C1: neutralise the h1 tag change
   ==========================================================================

   templates/template-property-details.php (child) promotes the listing
   address line from <div> to <h1> so that ~1,000 indexed listing URLs stop
   rendering with no first-level heading. Nick's condition on that promotion
   is that the page must look identical afterwards.

   It very nearly is already. `.property-detail-a-2col
   .cire-listing-summary__name` in the parent's cire-luxury.css is
   specificity 0,2,0 and already pins font-family, font-size, font-weight,
   line-height, colour, margin, max-width, text-wrap, text-transform and
   letter-spacing, all of which beat app.css's h1 rules on specificity
   regardless of enqueue order.

   Measured, not assumed. The div was replaced with an h1 carrying the
   identical class inside three live listing pages (Barbados, Sint Maarten,
   Bahamas) at 375 / 1024 / 1366 / 1440 / 1920 / 2560, viewport asserted from
   inside the document, and every computed property compared. Across all
   eighteen renders exactly ONE property differed:

     text-rendering:  auto  ->  optimizelegibility

   and getBoundingClientRect was identical to the hundredth of a pixel. One
   property inherited from a heading rule, one declaration to put it back.
   optimizeLegibility switches on optional ligatures and extra kerning, which
   can move ink inside an unchanged box - invisible on most strings and not
   on all of them, and "not visible on the three addresses I happened to
   test" is not a standard worth shipping on a thousand pages.

   Scoped to the detail template's own body class, so this rule cannot reach
   any other h1 on the site.
   -------------------------------------------------------------------- */

.property-detail-a-2col h1.cire-listing-summary__name {
  text-rendering: auto;
}