/* Plaza Hollywood — design tokens sampled from PH Screens 19082026,
   being reconciled against Figma (view access, 2026-08-25). */

/* Body face: Inter (designer-supplied, OFL — see assets/fonts/Inter-OFL.txt).
   Variable font covers 100–900. CJK falls back to Noto Sans TC/SC. */
@font-face {
	font-family: 'Inter';
	src: url('../fonts/Inter-Variable.woff2') format('woff2-variations');
	font-weight: 100 900;
	font-style: normal;
	font-display: swap;
}

/* Display face: Bou College (designer-supplied, confirmed vs Figma spec).
   ⚠ License file not provided — confirmation owed by designer/client. */
@font-face {
	font-family: 'Bou College';
	src: url('../fonts/BouCollege.woff2') format('woff2');
	font-weight: 400;
	font-style: normal;
	font-display: swap;
}

/* ==========================================================================
   COLOUR-SPACE CORRECTION — 27 Aug 2026
   ==========================================================================
 * WHY: every saturated token below was eyedropped from a Display-P3 render of
 * the spec PDFs, so each one carried a P3 number in an sRGB stylesheet — the
 * frames' own vector fill operators (`scn`, tagged sRGB2014) hold the true
 * values. This is a colour-space bug, not a taste change. Neutrals are
 * unaffected: P3 and sRGB share a white point, so greys map to themselves.
 *
 *   token            old (P3 eyedrop)   new (sRGB)   how
 *   --ph-teal            #53b6c4         #02b9c6     ICC P3->sRGB
 *   --ph-teal-mid        #48a1b2         #02a3b5     PDF vector (ICC gave #00a3b5)
 *   --ph-teal-deep       #29626d         #00636e     PDF vector (ICC gave #00646f)
 *   --ph-heading         #367c8a         #007e8c     ICC P3->sRGB
 *   --ph-gold            #f1b143         #fcae18     PDF vector (ICC gave #fdae19)
 *   --ph-muted           #766e5c         #786e5a     PDF vector (ICC agreed exactly)
 *   --ph-bg / --ph-text / --ph-card      unchanged   neutral, and already vector
 *
 * METHOD: ICC transform built with PIL ImageCms — the Display P3 profile
 * extracted from a `sips`-rendered PNG of a spec frame, to sRGB, relative
 * colorimetric. Where a converted value landed within 2/255 of a measured
 * vector value, the vector value was used verbatim. #02a3b5 is also the brand
 * teal Jestyn Khoo stated independently.
 *
 * READING THE COMMENTS BELOW: hex values quoted in the measurement notes
 * throughout this file ("samples #48a1b2", "the darkest pixel is #766e5c") are
 * the ORIGINAL P3-render eyedrops and are kept as the measurement record —
 * they remain true statements about the render. The LIVE values are the
 * converted ones here. Do not "fix" a token back to a number in a comment.
 * ========================================================================== */
:root {
	/* Sampled from the 1440px spec frames, then P3->sRGB corrected (see above). */
	--ph-teal: #02b9c6;
	--ph-teal-mid: #02a3b5;
	--ph-teal-deep: #00636e;
	--ph-heading: #007e8c;
	--ph-gold: #fcae18;
	--ph-bg: #f8f8f8;
	--ph-card: #ffffff;
	--ph-text: #333333;
	--ph-muted: #786e5a; /* warm taupe — UI-muted only: idle chips/tabs, unit numbers, search value. Body copy is --ph-text per the designer's ruling. */
	--ph-radius: 14px;
	/* Designer ruling (Jestyn Khoo, 25 Aug 2026): 1312px is the MAIN BANNER
	   width; every other element sits on 1090px. The shell (header, footer,
	   app strip) aligns to the banner edge, so it shares --ph-maxw. */
	--ph-maxw: 1352px;      /* 1312 + 2x20 padding — banner + shell only */
	--ph-content-maxw: 1130px; /* 1090 + 2x20 padding — all content */
	/* Display face per Figma = "Bou College" — awaiting font files from designer; Oswald stands in. */
	/* CJK fallbacks after Noto are the system faces, in the order a device is
	   likely to have them: PingFang (Apple), Microsoft JhengHei/YaHei
	   (Windows TC/SC), Hiragino, then Noto's own local name. They matter
	   because fonts.googleapis.com is blocked in mainland China and the SC
	   edition is aimed at exactly those readers — without this the TC/SC
	   pages would fall through to a generic sans and, on some Windows
	   installs, to missing glyphs. */
	--ph-cjk: 'Noto Sans TC', 'Noto Sans SC', 'PingFang TC', 'PingFang SC', 'Microsoft JhengHei', 'Microsoft YaHei', 'Hiragino Sans GB', 'Heiti TC', 'Heiti SC', sans-serif;
	--ph-font-display: 'Bou College', 'Oswald', var(--ph-cjk);
	--ph-font-body: 'Inter', var(--ph-cjk);
}

* { box-sizing: border-box; }
/*
 * Form controls do NOT inherit type from the page — every browser gives
 * button/input/select/textarea its own UA font, which on this stack is 13.333px
 * Arial. The theme never overrode it, so a large part of the interactive chrome
 * was rendering in a face the design never chose: the listing filter chips, the
 * listing search placeholder, the Location accordion bars, the Parking and
 * spotlight carousel arrows, the floorplan steppers and the header search box
 * all computed Arial while the copy beside them computed Inter. It reads as a
 * subtle mismatch rather than an obvious bug, which is why it survived this long.
 *
 * `font: inherit` (the shorthand, not just font-family) so size and weight come
 * from the cascade too; every component that wants its own size already sets one
 * on a class, which outranks these type selectors.
 */
button, input, select, textarea { font: inherit; }
/*
 * The `hidden` attribute only sets `display: none` at user-agent weight, so any
 * rule giving an element an explicit display beats it. Several components are
 * grids (.ph-promo-card, .ph-spotlight-inner) and were hidden by attribute from
 * JS, which meant the Parking offers carousel rendered all six cards stacked
 * and its prev/next arrows looked dead — the state was changing correctly, it
 * just had no visual effect.
 */
[hidden] { display: none !important; }
body {
	margin: 0;
	background: var(--ph-bg);
	color: var(--ph-text);
	font-family: var(--ph-font-body);
	font-size: 16px;
	line-height: 1.6;
	/* sticky footer: short pages never leave white space below the footer */
	min-height: 100vh;
	display: flex;
	flex-direction: column;
}
.site-main { flex: 1; }
img { max-width: 100%; height: auto; display: block; }
a { color: var(--ph-teal-mid); text-decoration: none; }
a:hover { color: var(--ph-teal-deep); }

.ph-container { max-width: var(--ph-content-maxw); margin: 0 auto; padding: 0 20px; }
/* Shell rows run to the banner width. */
.ph-header-inner, .ph-app-strip .ph-container, .site-footer .ph-container { max-width: var(--ph-maxw); }
/*
 * Card grids sit on 1090 like everything else.
 *
 * They used to take the wide measure: Jestyn's frames DO measure card grids at
 * 1312 (shop cards 424px on a 1312 container, same for What's On), so "1090 for
 * other elements" was read as meaning content blocks rather than grids.
 * Asked directly, he ruled the other way — "we can stick with 1090" — so the
 * ruling wins over the measurement, and only the main banner is 1312 now.
 *
 * Kept as an explicit rule rather than deleted, because the frames and the
 * build disagree on purpose and a future reader measuring the PDF will
 * otherwise "fix" this back. Confirmation is flagged in the Jestyn draft.
 */
.ph-section--grid > .ph-container { max-width: var(--ph-content-maxw); }

/* Display face (Bou College) is reserved for BIG moments — section titles,
   page banners, hero numerals — per the Figma spec. Everything else is Inter. */
h1, h2, h3 { color: var(--ph-heading); line-height: 1.2; }
.ph-display, .ph-section-title, .ph-promo-card .num,
.ph-hero-vic h3, .ph-logo, .ph-sdf span {
	font-family: var(--ph-font-display);
	text-transform: uppercase;
	letter-spacing: 0.04em;
}
/* Spec: section titles are LEFT-aligned by default ("Promotion & Exciting
   Deals", "Follow Us on Social Media"); only "Discover"/"Explore" are centred.
   Several are two-tone — second half in the lighter teal. */
/* No tracking. The 0.02em was inherited from the .ph-display group above (which
   does letterspace, 0.04em) and never measured: "Promotion & Exciting Deals" is
   519px of ink in the 1440 Home frame, which is Bou College at 40px with the
   tracking at ZERO — 0.02em adds 0.8px per glyph and pushes the line past it. */
.ph-section-title { text-align: left; font-size: 40px; margin: 0 0 10px; letter-spacing: 0; }
.ph-section-title--center { text-align: center; }
.ph-banner-page-title { margin: clamp(24px, 3vw, 40px) auto 0; padding-inline: 16px; overflow-wrap: anywhere; }
.ph-banner-page-title + :is(.ph-section, .ph-section--grid):not([data-ph-listing]) { padding-top: 24px; }
.ph-section-title .alt { color: var(--ph-teal); }
/*
 * 14px / #766e5c, measured — not 15px / #333.
 *
 * Colour is sampled, not inferred: the darkest pixel in the sub-line is exactly
 * (118,110,92) = #766e5c on BOTH the Home frame and the Floorplan frame, which
 * is the value --ph-muted already holds.
 *
 * The size is two independent measurements agreeing on the same number. Home's
 * "Discover exclusive promotions…" is 565px of ink and 14 rows tall; Inter 400
 * at 14px is 565.2 and 13.69. Floorplan's "Explore the different levels…" is
 * 572 and 14; Inter at 14px is 572.7 and 13.58. At 16px those strings would be
 * 639 and 648 — 74px and 75px too wide, so the size is not a close call.
 */
.ph-section-sub { text-align: left; color: var(--ph-muted); margin: 0 0 36px; font-size: 14px; }
.ph-section-title--center + .ph-section-sub { text-align: center; }

/* ---------- Header ---------- */
/* Spec: 99px tall, sits on the page background, no shadow. */
.site-header {
	background: var(--ph-bg);
	position: sticky; top: 0; z-index: 50;
	box-shadow: none;
}
.ph-header-inner {
	max-width: var(--ph-maxw); margin: 0 auto; padding: 29px 20px; min-height: 99px;
	display: flex; align-items: center; gap: 28px;
}
.ph-logo { display: block; flex: none; }
/*
 * 35px, not 37 — measured as INK against Desktop/Home.pdf, where the header
 * lockup is 136px wide (x66-x202). logo-plazahollywood.png is 312x80 with no
 * transparent margin, so its ink IS its box and its width is locked to 3.9x the
 * height: at 37 the mark rendered 144.3 wide, ~6% over the frame. 35 lands it on
 * 136.5 — the frame's own width to half a pixel. (The frame's ink HEIGHT reads
 * 37, i.e. the artwork in the frame is a slightly squarer lockup than the PNG
 * the client supplied; width is the dimension the eye reads against the nav
 * beside it, so width is the one matched.) Mobile is measured separately at 34
 * and is already correct — see the 900px block.
 */
.ph-logo img { height: 35px; width: auto; }
.ph-footer-logo { height: 46px; width: auto; }
/*
 * margin-left 16, not 8: the nav's first link starts at x244 in EVERY 1440
 * frame, and that position is measured from the logo's right edge. Shrinking the
 * logo by 7.8px (above) would otherwise have dragged the whole row 7.8px left
 * and quietly broken the one header number that was already correct.
 */
.ph-nav { display: flex; gap: 26px; margin-left: 16px; }
/*
 * 14px, and this supersedes an earlier round that read the same gap as a
 * TYPEFACE mismatch and left the size alone.
 *
 * The evidence is cross-frame ink WIDTHS, which pin the size in a way a
 * cap-height read cannot: "Movies" is 47px of ink and "VIC" 23px on all four
 * 1440 frames sampled (Home, Shopping, Exhibition, Movies), and Inter 500 fits
 * both at 14px — at 16px they would be 54 and 27. The row is the check that
 * makes it unarguable: six links plus five 26px gaps ends at x673 in the frames
 * and ended at x714 here, a 41px overrun that no letterform difference explains.
 */
.ph-nav a { color: var(--ph-teal-mid); font-size: 14px; font-weight: 500; padding: 6px 0; border-bottom: 2px solid transparent; }
.ph-nav a:hover, .ph-nav a.active { color: var(--ph-teal-mid); border-bottom-color: var(--ph-teal-mid); border-bottom-width: 3px; }
.ph-header-search { display: none; background: #fff; border-top: 1px solid #eee; padding: 14px 20px; }
.ph-header-search.open { display: block; }
.ph-header-search .ph-searchbar { margin: 0 auto; }
.ph-header-search .ph-searchbar input { min-width: 0; }
/* ---------- Site search results (search.php) ----------
 *
 * No frame exists for this screen, so every value below is borrowed from a
 * component the design DOES specify rather than invented: the count line is the
 * section sub-line (14px / --ph-muted), the rows are the shop card's surface
 * (white, --ph-radius, the same 0 2px 10px shadow and the same hover lift), the
 * result title is the event card's title colour and the "kind" badge is the
 * chip's type at the chip's ink. The page used to render a UA-default bulleted
 * list, which was the only browser-styled block on the site.
 */
.ph-search-results { padding-block: 40px 80px; }
.ph-search-count { margin: 0 0 22px; font-size: 14px; color: var(--ph-muted); }
.ph-result-list { list-style: none; margin: 0; padding: 0; }
.ph-result { margin: 0 0 12px; }
.ph-result > a {
	display: block; background: var(--ph-card); border-radius: var(--ph-radius);
	box-shadow: 0 2px 10px rgba(0,0,0,.05); padding: 20px 24px; color: var(--ph-text);
	transition: box-shadow .18s ease, transform .18s ease;
}
.ph-result > a:hover, .ph-result > a:focus-visible { box-shadow: 0 8px 22px rgba(0,0,0,.10); transform: translateY(-2px); color: var(--ph-text); }
/* The badge names the kind of thing found — a mixed result set is unreadable
   without it, since a shop, a film and a page all present as a bare title. */
.ph-result .kind { display: block; font-size: 12px; color: var(--ph-muted); margin-bottom: 4px; }
.ph-result .title { display: block; font-size: 20px; line-height: 28px; color: var(--ph-teal-mid); font-weight: 600; }
.ph-result .meta { display: block; margin-top: 6px; font-size: 14px; line-height: 20px; color: var(--ph-muted); }
/* Pagination: core's own markup, given the theme's chip shape. Only shown when
   the 50-row page cap is actually hit. */
.ph-search-results .navigation.pagination { margin-top: 32px; }
.ph-search-results .nav-links { display: flex; flex-wrap: wrap; gap: 8px; justify-content: center; }
.ph-search-results .page-numbers {
	display: inline-flex; align-items: center; justify-content: center;
	min-width: 40px; height: 40px; padding: 0 12px; border-radius: 999px;
	border: 1px solid #d3dfe1; color: var(--ph-teal-mid); font-size: 14px;
}
.ph-search-results .page-numbers.current { background: var(--ph-teal-mid); border-color: var(--ph-teal-mid); color: #fff; }
.ph-search-results .page-numbers.dots { border-color: transparent; }
/* Core prints a "Search results navigation" <h2> for screen readers; it is not
   part of the visual design but must stay in the accessibility tree. */
.ph-search-results .screen-reader-text {
	position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0 0 0 0); white-space: nowrap;
}
@media (max-width: 640px) {
	.ph-result > a { padding: 16px; }
	.ph-result .title { font-size: 17px; line-height: 24px; }
}
/*
 * gap 20, measured between INK edges in the 1440 header: the 繁｜简 pair ends at
 * x1311, the pin runs x1331-1341 and the magnifier x1362-1374 — so 20px and 21px
 * of air. With the icon buttons now sized to their ink (no padding, see
 * .ph-icon-btn below) the flex gap IS that air, where before it was 16px of gap
 * plus 4px of button padding on each side.
 */
.ph-header-tools { margin-left: auto; display: flex; align-items: center; gap: 20px; }
/* Teal, not #333 — the 繁｜简 pair in the 1440 header frame samples #48a1b2,
   which is --ph-teal-mid. The switcher only ever renders the languages you can
   switch TO (ph_language_switcher drops the current one), so every link here is
   an available action and they all take the action colour. */
.ph-langs a { color: var(--ph-teal-mid); padding: 0 2px; }
.ph-langs .active { color: var(--ph-teal-mid); font-weight: 700; }
/*
 * The box IS the glyph. These used to be emoji in an 18px font with 4px of
 * padding, which made their size a property of the platform's colour-emoji face;
 * they are now ph_icon()'s ui-* SVGs, whose viewBox equals their measured ink
 * box, so a width/height here lands the ink at exactly that size. No padding,
 * because the frames put the air BETWEEN the icons (the 20px flex gap above),
 * not around them — the magnifier's ink ends 2px inside the 1376 shell edge.
 *
 * currentColor, and the colour is the action teal the frame samples for the
 * whole tools cluster (the 繁｜简 links beside them already take it), not the
 * --ph-text the emoji rule nominally set and the emoji ignored.
 */
.ph-icon-btn {
	background: none; border: 0; padding: 0; cursor: pointer; line-height: 0;
	color: var(--ph-teal-mid);
	display: inline-flex; align-items: center; justify-content: center;
}
.ph-icon-btn svg { display: block; }
/* Measured ink: pin 10x14, magnifier 12x12 (Desktop/Home.pdf at 1:1). */
.ph-icon-btn--pin svg { width: 10px; height: 14px; }
.ph-icon-btn--search svg { width: 12px; height: 12px; }
.ph-burger svg { width: 16px; height: 12px; }
.ph-icon-btn:hover, .ph-icon-btn:focus-visible { color: var(--ph-teal-deep); }
.ph-burger { display: none; }

/* ---------- Footer ---------- */
.ph-app-strip { background: var(--ph-teal-mid); color: #fff; }
/* Spec: strip is exactly 101px tall; badges 57px with a 17px gap. */
.ph-app-strip .ph-container { display: flex; align-items: center; gap: 17px; padding: 0 20px; height: 101px; flex-wrap: nowrap; position: relative; }
.ph-app-strip .msg { margin-left: auto; font-size: 18px; }
/*
 * `align-self: flex-start` is what makes the -45px mean 45px.
 *
 * The tile is meant to hang 45px above the strip — measured in the Home frame,
 * where the strip starts at y5199 and the tile's first ink row is y5154, and
 * the tile's bottom then sits 19px ABOVE the strip's bottom, so it is
 * deliberately not centred in the band. With `align-items: center` inherited
 * from the row, though, a negative margin does not translate 1:1: flexbox folds
 * margins into the free space it centres, so -45px produced an overhang of
 * ((101 - 127 + 45) / 2) + 45 = 35.5px. The number in the file and the number
 * on screen were 9.5px apart, which is why an earlier audit recorded this as
 * "already correct".
 *
 * Opting out of the cross-axis centring makes the margin absolute again: the
 * tile's top edge is exactly 45px above the strip's, and the value in the file
 * is the value you can measure. The mobile block re-centres it (see below),
 * because there the row is a column and cross-axis means horizontal.
 */
.ph-app-icon { height: 127px; width: auto; align-self: flex-start; border-radius: 22px; margin-top: -45px; box-shadow: 0 4px 14px rgba(0,0,0,.18); }
.ph-app-strip .ph-stores { display: flex; gap: 17px; }
.ph-store-badge { height: 57px; width: 153px; object-fit: contain; }
.site-footer { background: var(--ph-teal-deep); color: #dbeff2; padding: 56px 0 40px; min-height: 277px; }
/* Spec footer is 5 columns: brand + socials, two nav columns, a third nav
   column, then the "Member of Wharf Group" marks. */
/*
 * Column starts measured off the 1440 Home frame: x64, 508, 730, 952, 1174 —
 * i.e. the brand column is wide and the four that follow are EQUAL, on a
 * ~222px pitch. The old 1.6/1/1/1.1/1.2 ramp landed them at 64, 418, 648, 878,
 * 1129: every column after the first drifted left, the last by 45px.
 * 2.1fr + four 1fr on the 1312 measure with 24px gutters puts them at 64, 507,
 * 730, 953, 1177 — inside 3px of the frame all the way across.
 */
.ph-footer-cols { display: grid; grid-template-columns: 2.1fr 1fr 1fr 1fr 1fr; gap: 24px; }
/* Measured: 32px circles on a 56px pitch, so a 24px gutter. The row's top sits
   132px below the footer's own top edge in the frame (56px padding + the 46px
   logo box + 30). It was 18, which put the row at 120. */
.ph-footer-socials { display: flex; align-items: center; gap: 24px; margin-top: 30px; }
/*
 * Scoped under .site-footer so it beats `.site-footer a`, which otherwise wins
 * on specificity and paints the glyph #dfeef1 — a near-white mark on a
 * near-white circle, i.e. invisible. Same reason padding/display are restated.
 */
.site-footer .ph-social {
	width: 32px; height: 32px; border-radius: 50%; border: 0; padding: 0; cursor: pointer;
	background: rgba(255,255,255,.85); color: var(--ph-teal-deep);
	display: flex; align-items: center; justify-content: center; flex: none;
}
.site-footer .ph-social svg { width: 18px; height: 18px; }
.site-footer .ph-social:hover,
.site-footer .ph-social:focus-visible { background: #fff; color: var(--ph-teal-mid); }
/*
 * The client's own marks (22 Sep 2026): each PNG is already a filled teal
 * circle with the glyph reversed out, so the disc above would show as a white
 * halo around it — `:has()` drops the disc only when the circle holds an image,
 * leaving the white-disc-plus-SVG treatment intact for any key that falls back.
 * Hover/focus lift the whole mark a step instead of recolouring a glyph that is
 * no longer `currentColor`; the focus ring is what keyboard users see.
 */
.site-footer .ph-social:has(> img) { background: transparent; }
.site-footer .ph-social:has(> img):hover,
.site-footer .ph-social:has(> img):focus-visible { background: transparent; filter: brightness(1.12); }
.site-footer .ph-social:focus-visible { outline: 2px solid #fff; outline-offset: 2px; }
.site-footer .ph-social img { width: 32px; height: 32px; display: block; border-radius: 50%; }
/*
 * WeChat ID card (QA 6.0). Sits beside its circle on desktop, exactly as the
 * old site's .wechatbox did (white card, 6px radius, warm-grey text) — and
 * drops UNDER the circle below 560px, where 129px of card to the right of the
 * fourth circle would run off the viewport. The old site hit the same wall and
 * solved it the same way (custom.css @media 460px).
 *
 * position:absolute on a relatively-positioned wrapper so opening the card
 * never reflows the circle row; z-index because the footer meta row paints
 * after it in source order.
 */
.ph-social-disclosure { position: relative; display: flex; flex: none; }
.ph-social-card {
	position: absolute; left: calc(100% + 11px); top: -4px; z-index: 3;
	display: flex; align-items: baseline; gap: 6px; white-space: nowrap;
	background: #fff; color: #786e5a; border-radius: 6px; padding: 6px 30px 6px 10px;
	font-size: 14px; line-height: 1.3;
	box-shadow: 0 4px 14px rgba(0,0,0,.22);
}
.ph-social-card__label { font-weight: 600; }
.ph-social-card__id { font-weight: 400; }
/* Not `.site-footer a` — this is a button, so it needs its own reset. */
.ph-social-card__close {
	position: absolute; top: 2px; right: 4px;
	border: 0; background: none; padding: 0 4px; cursor: pointer;
	color: #a2977f; font-size: 16px; line-height: 1.4;
}
.ph-social-card__close:hover,
.ph-social-card__close:focus-visible { color: #786e5a; }
.ph-footer-group { font-size: 13px; color: #dbeff2; }
.ph-footer-group strong { display: block; font-weight: 600; margin-bottom: 10px; }
/*
 * Both sister-mall marks, divided by the hairline the design and the old site
 * both draw. The two are NOT set to a common height — measured off
 * ui-specs/Desktop/Home.pdf the Harbour City mark is 36px tall and Times Square
 * 25px, because one is a two-line lockup and the other a single row of glyphs;
 * matching their box heights would leave Harbour City looking undersized. The
 * rule between them is taller than either (35px), so it is its own element
 * rather than a border on a mark, which could only ever be as tall as the mark
 * it hangs off.
 *
 * Measured x-gaps in the frame are 14px before the rule and 16px after; 15/15
 * splits the difference and keeps the pair centred under the label.
 */
.ph-wharf-marks { display: flex; align-items: center; gap: 15px; }
.ph-wharf-mark { display: block; padding: 0; }
.ph-wharf-mark img { display: block; width: auto; }
.ph-wharf-mark--hc img { height: 36px; }
.ph-wharf-mark--ts img { height: 25px; }
.ph-wharf-rule { flex: none; width: 1px; height: 35px; background: rgba(255,255,255,.15); }
.site-footer a { color: #dbeff2; display: block; padding: 3px 0; font-size: 14px; }
.site-footer a:hover { color: var(--ph-gold); }
.ph-footer-meta { margin-top: 28px; font-size: 12px; color: #a1c9cf; display: flex; justify-content: space-between; flex-wrap: wrap; gap: 8px; }

/* ---------- Buttons / chips ---------- */
/*
 * 202x48 is the SYSTEM pill, not a per-page size.
 *
 * Movies' "View All Showing" and the Home hero's VIC button were the only two
 * built to it, each via its own rule; Home's "View All" came out 114x46 and the
 * spotlight's "Learn More" 140x46, because with no min-width a pill is only as
 * wide as its label. Measured in Desktop/Home.pdf the "View All" pill is
 * x619-x821 by 48 tall — 202x48 exactly — so the size belongs to the component.
 *
 * min-width rather than width: "Join Now" in the VIC panel is a full-width
 * 265px button (.ph-hero-vic .ph-btn), and a floor leaves that alone while
 * still catching every short label. Long labels grow past 202 rather than
 * clipping, which matters for TC/SC.
 *
 * font-size 14 is measured too ("View All" is 14px in the frame, as is Movies'
 * "View All Showing" and the VIC "Join Now"), and it is now load-bearing rather
 * than cosmetic: the `font: inherit` reset at the top of this file means a
 * <button class="ph-btn"> would otherwise have jumped from the UA's 13.3px to
 * the body's 16px.
 *
 * inline-flex + centring replaces `inline-block` + symmetric padding: a fixed
 * height and vertical padding cannot both be right once a label wraps, and the
 * flex centring is what the height needs to stay honest.
 */
.ph-btn {
	display: inline-flex; align-items: center; justify-content: center;
	background: var(--ph-gold); color: #fff;
	border: 0; border-radius: 8px; padding: 0 26px; font-size: 14px; font-weight: 600; cursor: pointer;
	min-width: 202px; height: 48px; text-align: center;
}
.ph-btn:hover { filter: brightness(.95); color: #fff; }
.ph-btn--ghost { background: var(--ph-teal-mid); }
.ph-chip {
	display: inline-block; padding: 5px 14px; border-radius: 999px;
	background: none; border: 0; color: var(--ph-text); cursor: pointer; font-size: 14px;
}
.ph-chip:hover, .ph-chip.active { color: var(--ph-teal-mid); }

/* ---------- Hero / banner ---------- */
/* Spec: hero is inset 64px each side (1312 wide), 701 tall, radius 20 all round. */
.ph-hero { position: relative; border-radius: 20px; overflow: hidden; background: var(--ph-teal); min-height: 701px; max-width: 1312px; margin: 0 auto; }
.ph-hero video, .ph-hero > img { width: 100%; height: 100%; object-fit: cover; position: absolute; inset: 0; }
/* Keep the clock, weather and VIC card in the flow below the video. */
.ph-hero-wrap { max-width: 1312px; margin: 0 auto; }
.ph-hero-info { display: flex; flex-wrap: wrap; justify-content: space-between; gap: 8px 16px; padding: 12px 16px 0; color: var(--ph-heading); font-size: 14px; }
.ph-hero-temp { display: flex; align-items: center; gap: 10px; }
.ph-hero-temp svg { width: 16px; height: 11px; display: block; flex: none; }
.ph-hero-vic {
	background: linear-gradient(150deg, rgba(25,122,134,.95), rgba(0,99,110,.95));
	color: #fff; border-radius: 10px; padding: 23px; width: min(600px, calc(100% - 32px));
	margin: 16px auto 0; text-align: center;
}
.ph-hero-vic h3 { color: #fff; margin: 0 0 16px; font-size: 24px; line-height: 1.15; }
/*
 * flex, not block, and no line-height of its own. The button is full-width here
 * (265px in the 1440 frame, 302 at 390) and its own width therefore has to beat
 * .ph-btn's 202px floor — `width: 100%` does that. Centring now comes from
 * .ph-btn's align/justify rather than from `line-height: 28px` inside a 48px
 * box, which only centred the label because the base rule happened to carry
 * 10px of vertical padding; that padding is gone.
 */
.ph-hero-vic .ph-btn { display: flex; width: 100%; max-width: 302px; margin-inline: auto; height: 48px; border-radius: 6px; }
/* Interior banner artwork uses the existing 1312 × 400 frame. */
.ph-page-banner {
	position: relative; border-radius: var(--ph-radius); overflow: hidden; min-height: 400px;
	background: var(--ph-teal); margin: 0 auto; max-width: 1312px;
}
.ph-page-banner img { width: 100%; height: 100%; object-fit: cover; position: absolute; inset: 0; }
/* The shop search sits between the filters and the grid. */
.ph-listing-search { width: min(100%, 866px); margin: 16px auto 0; }
/*
 * A rounded rectangle, not a lozenge. Measured off the corner arc in
 * Shopping - Category.pdf: the pill spans x287–1152 (866 wide, as recorded) and
 * y313–374, and its top row is inset 14px while full width is reached 14 rows
 * down — which is the radius. A true pill on a 62px box would be r=31 and would
 * not square off until y344.
 */
.ph-listing-search .ph-searchbar { border: 1px solid var(--ph-teal-mid); border-radius: 14px; box-shadow: none; height: 64px; max-width: none; margin: 0; }
.ph-listing-search .ph-searchbar input {
	min-width: 0; align-self: stretch; padding: 0 16px; text-align: center; font-size: 15px; border-radius: 14px; color: var(--ph-muted); background: transparent;
}
.ph-listing-search .ph-searchbar input::placeholder { color: var(--ph-muted); opacity: 1; }
.ph-listing-search .ph-searchbar:focus-within { outline: 2px solid var(--ph-teal-deep); outline-offset: 3px; }

/* ---------- Sections ---------- */
.ph-section { padding: 56px 0; }
.ph-section--tint { background: #e7f2f3; }

/* Promotion cards (numbered rows) */
.ph-promo-card {
	background: var(--ph-card); border-radius: var(--ph-radius); box-shadow: 0 2px 10px rgba(0,0,0,.05);
	display: grid; grid-template-columns: 478px 1fr; gap: 62px; padding: 16px; margin-bottom: 14px; align-items: center;
}
.ph-promo-card:nth-child(even) { grid-template-columns: 1fr 478px; }
.ph-promo-card:nth-child(even) .media { order: 2; }
/* --ph-heading, not a hardcoded #3e8b9b. The two differ by 8/15/17 per channel —
   invisible on its own, but it made the numerals the one heading-coloured thing
   on the site that a token change would not reach. */
.ph-promo-card .num { font-family: var(--ph-font-display); color: var(--ph-heading); font-size: 41px; margin: 0 0 6px; }
.ph-promo-card h3 { margin: 0 0 10px; font-size: 26px; color: var(--ph-teal-mid); text-transform: none; }
.ph-promo-card p { font-size: 14px; line-height: 20px; }
.ph-promo-card .media { border-radius: 10px; overflow: hidden; background: #eee; aspect-ratio: 16/9; }
.ph-promo-card .media img { width: 100%; height: 100%; object-fit: cover; }

/* SHOP / DINE / FUN tiles */
.ph-sdf { display: grid; grid-template-columns: repeat(3, 1fr); gap: 0; }
.ph-sdf a { position: relative; aspect-ratio: 363/680; overflow: hidden; }
.ph-sdf img { width: 100%; height: 100%; object-fit: cover; transition: transform .3s; }
.ph-sdf a:hover img { transform: scale(1.04); }
/*
 * The label sits just above the tile's mid-line, not near its foot.
 *
 * Measured in Desktop/Home.pdf: the tiles run y2225-2905 (680 tall, the
 * 363x680 the grid above already encodes) and the SHOP/DINE/FUN ink sits at
 * y2539-2567 — an ink centre 328px down, i.e. 48.2% of the tile. It was pinned
 * 40px off the bottom, which put it at 91%.
 *
 * 48.2% + translateY(-50%) centres the LINE BOX, and the line box's centre is
 * not quite the ink's, so the small correction below the percentage is
 * deliberate: with Bou College's metrics on this 1.6 line-height the ink centre
 * lands ~1px above the box centre, which is inside the measurement's own
 * tolerance. Keeping it proportional (rather than a pixel offset) is what makes
 * it survive the mobile tiles, which are the same ratio at a different size.
 */
.ph-sdf span {
	position: absolute; left: 0; right: 0; top: 48.2%; transform: translateY(-50%);
	text-align: center; color: #fff;
	font-family: var(--ph-font-display); font-size: 28px; letter-spacing: .1em; text-shadow: 0 2px 8px rgba(0,0,0,.4);
}
/*
 * The white rule under the label is the HOVER state, not permanent furniture.
 *
 * The Home frame draws it under SHOP only — and SHOP is the tile the designer
 * put a mouse cursor on. FUN and DINE, on the same row of the same frame, have
 * nothing under their labels (checked as white ink: SHOP's band is y2576-2584,
 * FUN's column has no second band at all). So a rule painted on all three would
 * be reproducing the pointer, not the design.
 *
 * Measured off that one tile: 150px wide, 8px tall, centred, its top 9px below
 * the label's ink bottom. Width is fixed rather than tied to the label — 150 on
 * a 90px-wide "SHOP" is plainly not a text underline.
 *
 * Paired with the existing image scale-up, so a tile has one hover state made of
 * two parts rather than two competing ones; both are suppressed together under
 * prefers-reduced-motion only for the movement, since the rule itself does not
 * move.
 */
/*
 * `100% - 4px`, and the minus is not a typo. The frame puts the rule's top 9px
 * below the label's INK; `100%` is the bottom of the LINE BOX, which on an
 * all-caps label sits ~13px lower than the ink does (that space is the
 * descender room Bou College reserves and this label never uses). 9px below the
 * ink is therefore 4px above the box.
 */
.ph-sdf span::after {
	content: ""; position: absolute; left: 50%; top: calc(100% - 4px);
	width: 150px; height: 8px; margin-left: -75px; background: #fff;
	opacity: 0; transition: opacity .2s ease;
}
.ph-sdf a:hover span::after, .ph-sdf a:focus-visible span::after { opacity: 1; }
@media (prefers-reduced-motion: reduce) {
	.ph-sdf span::after { transition: none; }
}

/* Explore tiles */
.ph-explore-grid { display: grid; grid-template-columns: 1fr 1fr .84fr; grid-template-rows: 239px 239px; gap: 18px; }
.ph-explore-grid a { position: relative; border-radius: var(--ph-radius); overflow: hidden; background: #ddd; }
.ph-explore-grid a.tall { grid-row: span 2; }
.ph-explore-grid a.wide { grid-column: span 2; }
.ph-explore-grid img { width: 100%; height: 100%; object-fit: cover; }
.ph-explore-grid span { position: absolute; left: 18px; bottom: 14px; color: #fff; font-weight: 700; text-shadow: 0 1px 6px rgba(0,0,0,.5); }
.ph-searchbar { display: flex; margin: 0 auto 34px; max-width: 620px; background: #fff; border: 2px solid var(--ph-teal); border-radius: 999px; overflow: hidden; }
.ph-searchbar input { flex: 1; border: 0; padding: 12px 22px; font-size: 15px; outline: none; }
.ph-searchbar button { border: 0; background: none; padding: 0 18px; cursor: pointer; color: var(--ph-teal-mid); font-size: 17px; display: flex; align-items: center; }
/*
 * The submit glyph MUST be sized here.
 *
 * An inline <svg> with a viewBox but no width/height defaults to 100% x 100%,
 * and this button's content box is 0px wide (36px button, 18px padding each
 * side) — so the magnifier resolved to 0x0 and the button rendered empty. It
 * only looked fine while the glyph was an emoji, which sized off font-size.
 *
 * 16px rather than the header toggle's measured 12: there is no frame for the
 * expanded search bar, and 16 is the ink the 17px emoji occupied, so swapping
 * the glyph does not also change the bar's visual weight.
 */
.ph-searchbar button svg { width: 16px; height: 16px; display: block; flex: none; }

/* ---------- Listing (Shopping / Dining) ---------- */
.ph-filterbar { display: flex; align-items: center; gap: 30px; padding: 26px 0 0; flex-wrap: wrap; }
/* 24px, measured as ink: "Category" is 106x23 in the Shopping - Category frame,
   and the frame's own text layer confirms it (the three tabs are set at 24 while
   the chips under them are 14). At 26 the word came out 112 wide. */
.ph-filter-tab { background: none; border: 0; cursor: pointer; font-size: 24px; padding: 4px 2px 10px; color: var(--ph-muted); border-bottom: 4px solid transparent; font-family: var(--ph-font-body); }
.ph-filter-tab.active { color: var(--ph-teal-mid); border-bottom-color: var(--ph-teal-mid); }
.ph-floorplan-link { margin-left: auto; font-weight: 600; display: flex; align-items: center; gap: 10px; font-size: 16px; }
.ph-floorplan-link::before {
	content: ""; width: 32px; height: 32px; flex: none;
	background: url('../img/icon-floorplan.svg') center/contain no-repeat;
}
/* Page-banner decoration removed by the October UAT requirements. */
/* Design: chips are plain text separated by small teal dots (not pills). */
.ph-subfilters { padding: 22px 0 6px; display: flex; flex-wrap: wrap; align-items: center; gap: 10px 0; }
/* 14px — the frame's text layer sets every category/A-Z/floor chip at 14, and
   the ink agrees ("Newspaper / Gift / Stationery" is 194px there, 193.8 at Inter
   14). Until the `font: inherit` reset at the top of this file these were also
   rendering in Arial, so the 15 was never the size anyone was looking at. */
.ph-subfilters .ph-chip { padding: 2px 21px; font-size: 14px; position: relative; }
.ph-subfilter-options { display: contents; }
.ph-subfilters :is(.ph-chip + .ph-chip, .ph-subfilter-options > .ph-chip)::before {
	content: ""; position: absolute; left: -4px; top: 50%; transform: translateY(-50%);
	width: 8px; height: 8px; border-radius: 50%; background: #00bccb;
}
.ph-subfilters .ph-chip.active { color: #00bccb; font-weight: 400; }
@media (min-width: 901px) {
	.ph-listing-page [data-ph-subfilters]:has(> .ph-subfilter-options) {
		display: grid; grid-template-columns: max-content minmax(0, 1fr); align-items: start;
	}
	.ph-listing-page [data-ph-subfilters]:has(> .ph-subfilter-options) > .ph-chip { padding-inline-end: 12px; }
	.ph-subfilter-options { display: flex; flex-wrap: wrap; gap: 10px 0; }
	.ph-subfilters .ph-subfilter-options > .ph-chip { padding-inline: 24px 16px; }
	.ph-subfilters .ph-subfilter-options > .ph-chip::before { left: 0; }
	.ph-listing-page .ph-listing-search { width: 100%; }
}
.ph-shop-grid { display: grid; grid-template-columns: repeat(3, 1fr); gap: 16px 20px; padding: 26px 0 10px; }
.ph-shop-card {
	background: var(--ph-card); border-radius: var(--ph-radius); box-shadow: 0 2px 10px rgba(0,0,0,.05);
	padding: 30px 20px 22px; min-height: 300px; display: flex; flex-direction: column; justify-content: center; text-align: center; color: var(--ph-text);
}
.ph-shop-card:hover { box-shadow: 0 4px 18px rgba(0,0,0,.1); color: var(--ph-text); }
.ph-shop-card .logo { height: 120px; display: flex; align-items: center; justify-content: center; margin-bottom: 18px; }
.ph-shop-card .logo img { max-height: 120px; width: auto; }
/*
 * 14px in the muted taupe, not 16px in --ph-text.
 *
 * The shop names in Shopping - Category.pdf and Dining - Category.pdf are set at
 * 14 in the frame's own text layer, and the darkest pixel in a card name samples
 * #766e5c — the same plateau as the unit number directly under it, the facts on
 * the shop detail page and every section sub-line. The card was rendering its
 * name a size larger and two shades darker than its own unit line, which is why
 * the cards read heavier than the frame.
 */
.ph-shop-card .name { display: block; font-size: 14px; font-weight: 600; color: var(--ph-muted); }
.ph-shop-card .unit { display: block; color: var(--ph-muted); font-size: 14px; margin-top: 4px; }
.ph-movie-grid .poster, .ph-movie-grid .title { display: block; }
/* Spec: magnifier, then two grey lines, the first quoting the query. */
.ph-noresult { text-align: center; padding: 50px 0 120px; color: #b5b5b5; }
.ph-noresult-icon { display: block; width: 72px; height: 72px; margin: 0 auto 22px; background: url('../img/icon-search-grey.svg') center/contain no-repeat; }
.ph-noresult p { margin: 0; font-size: 16px; line-height: 20px; }
.ph-noresult .line1 { overflow-wrap: anywhere; }
/* One of the two copy variants at a time — .has-query is set by main.js when
   the empty result came from the search box rather than a filter chip. */
.ph-noresult .for-query { display: none; }
.ph-noresult .for-filter { display: block; }
.ph-noresult.has-query .for-query { display: block; }
.ph-noresult.has-query .for-filter { display: none; }

/* ---------- 404 ---------- */
/*
 * Two classes, so this does not depend on sitting after .ph-noresult in the
 * file. The 404 borrows the empty-state block for its layout but not its ink:
 * .ph-noresult paints #b5b5b5, which on the #f8f8f8 page is 1.9:1 — under half
 * the 4.5:1 WCAG 1.4.3 needs for body text, and unreadable in daylight on a
 * phone. --ph-muted measures 4.73:1 on the same ground — over the 4.5:1 line —
 * and is already the theme's muted-text colour, so this is the system value
 * rather than a new one invented for this page. (4.73, not the 4.76 recorded
 * here before: the P3->sRGB correction of 27 Aug moved the token from #766e5c
 * to #786e5a, which costs 0.03 and stays clear of AA. See the :root note.)
 *
 * NOTE: the listing empty state (.ph-noresult on Shopping/Dining) still carries
 * #b5b5b5 and fails the same check. Left alone deliberately — the spec draws
 * those two lines grey on purpose and changing them is a design call, not a
 * mechanical fix. Flagged rather than fixed.
 */
.ph-noresult.ph-404 { padding: 110px 20px; color: var(--ph-muted); }
/*
 * Was two inline styles on the template. Inline `font-size: 64px` also could
 * not respond to width: at 390 a 64px numeral is fine, but it left no room to
 * tune, so it scales with the viewport and floors at 48.
 */
.ph-404-num { font-size: clamp(48px, 12vw, 64px); margin: 0 0 10px; }

/* ---------- Shop detail (ui-specs: Shopping - Shop Details) ---------- */
.ph-shop-detail { background: #e3f1f3; padding: 30px 0 60px; }
/* Label is the warm taupe, not #333 — sampled straight off the spec frame
   (Shopping - Shop Details.pdf), where the darkest pixel in the back-link row
   is exactly #766e5c. Same ink as the facts, the description and the section
   sub-lines: one muted-text colour across the whole system. */
.ph-back { display: inline-flex; align-items: center; gap: 18px; color: var(--ph-muted); font-size: 14px; font-weight: 600; margin-bottom: 28px; }
.ph-back .chev {
	width: 48px; height: 48px; border-radius: 10px; background: #786e5a; color: #fff;
	display: flex; align-items: center; justify-content: center; font-size: 26px; line-height: 1;
}
.ph-shop-detail .ph-detail { grid-template-columns: 1fr 1fr; gap: 56px; padding: 0; }
.ph-shop-detail .shot { border-radius: 10px; overflow: hidden; background: #dde9ea; }
.ph-shop-detail .shot img { width: 100%; height: auto; }
.ph-shop-detail .cat { color: var(--ph-muted); margin: 0 0 6px; }
/*
 * `.ph-shop-detail .ph-detail h1`, not `.ph-shop-detail h1`.
 *
 * The shop name is an <h1> inside `.ph-detail`, and `.ph-detail h1` (30px, in
 * the "Detail pages" block below) has IDENTICAL specificity to a bare
 * `.ph-shop-detail h1` — so the winner was decided purely by source order, and
 * the generic rule happens to be written later. The shop name silently
 * rendered at 30px with a 6px margin against the spec's 44px/26px, and any
 * future re-ordering of this file would have flipped it back again.
 *
 * Naming the wrapper too takes it to two classes, which beats the generic rule
 * on specificity and therefore no longer depends on where either rule sits.
 * `.ph-detail h1` itself is left alone, but it no longer has a user: What's On
 * was its last one and that page moved off the `.ph-detail` grid entirely on
 * 27 Aug 2026 (see "What's On detail" at the foot of this file — the frame puts
 * its title at 24px, not 30). Movies has its own `.ph-movie-detail h1` at 44px.
 * Kept because the generic pair is still what a NEW detail page would inherit,
 * and because deleting it is the kind of change that quietly re-opens the
 * specificity trap this whole comment is about.
 *
 * 44px measured: "123 By ELLA" is 234px of ink in the spec frame, which is
 * Inter 400 at 43.0px — 44 within the render's antialias tolerance.
 */
.ph-shop-detail .ph-detail h1 { font-family: var(--ph-font-body); font-weight: 400; font-size: 44px; color: var(--ph-teal); margin: 0 0 26px; text-transform: none; letter-spacing: 0; }
.ph-shop-detail .facts { list-style: none; margin: 0 0 22px; padding: 0; }
/*
 * Facts rows, measured off Shopping - Shop Details.pdf at 1:1:
 *   - ink is #766e5c, not #333 (darkest pixel in every row is exactly that);
 *   - row tops sit at y299 / 336 / 377 / 419 — a ~40px pitch, which 15px text
 *     on the 1.6 body line-height (24px) plus 8px of padding lands on;
 *   - the icon column is ~19px wide (x843–862), not 22;
 *   - the text column starts 32px right of the row's left edge (icons at x841,
 *     text at x873) — and the 390 frame agrees exactly, icons at x16, text at
 *     x48. So one padding serves both breakpoints.
 *
 * 14px, not 15 or 16, and the four rows agree to under a pixel: "Shop No.: 260"
 * is 94px of ink (Inter 400 @14 = 93.5), "Telephone: 2601 1083" 145 (143.3),
 * "Visit website" 84 (82.6) and the long hours row 305 (305.0). 15px would put
 * that hours row at 325px, which is wider than the 326px text column left at
 * 390 — so the size is load-bearing on mobile, not only cosmetic: at 15px the
 * spec's single line becomes two.
 */
.ph-shop-detail .facts li { position: relative; padding: 9px 0 9px 32px; font-size: 14px; color: var(--ph-muted); }
.ph-shop-detail .facts li::before {
	content: ""; position: absolute; left: 0; top: 11px; width: 19px; height: 19px;
	background: center/contain no-repeat;
}
.ph-shop-detail .facts li.shop::before  { background-image: url('../img/icon-shop.svg'); }
.ph-shop-detail .facts li.phone::before { background-image: url('../img/icon-phone.svg'); }
.ph-shop-detail .facts li.time::before  { background-image: url('../img/icon-clock.svg'); }
.ph-shop-detail .facts li.web::before   { background-image: url('../img/icon-web.svg'); }
/* The rule above the description is 2px of #9cd5dd in the spec frame — rows
   y462 and y463 both sample (156,213,221) exactly. It was built as a 1px
   #b9d7dc hairline, which at this tint is close to invisible. Same weight and
   colour the Movies detail page already uses for its own divider. Body ink is
   the shared muted taupe, matching the facts above it. */
.ph-shop-detail .desc { border-top: 2px solid #8bd7df; padding-top: 22px; color: var(--ph-muted); font-size: 14px; line-height: 20px; }
/* Shop detail map: the pale teal band the design puts behind the floor plan,
   with the level rail on the left and "View Full Floorplan" on the right.
 *
 * The band is the ELEMENT now, with a plain background, and the measure is
 * restored by a .ph-container nested inside it (see single-ph_shop.php).
 *
 * It used to be a `left: calc(50% - 50vw); width: 100vw` pseudo-element on the
 * container itself. `100vw` is the viewport INCLUDING the classic scrollbar,
 * so on a page tall enough to scroll — which this one always is — the band came
 * out 1440 wide inside a 1425 client box and hung 7.5px past each edge. The
 * right-hand overhang is real content, so the document gained 8px of horizontal
 * scroll and the whole page could be dragged sideways.
 *
 * A block-level element resolves its width against its CONTAINING BLOCK, which
 * already excludes the scrollbar, so this cannot overflow by construction —
 * whatever the scrollbar's width, whether it is overlaid or classic, and at any
 * zoom. (`overflow-x: hidden` on body would only have hidden the symptom, and
 * with it every future horizontal overflow anywhere on the site.) */
.ph-shop-map { padding: 40px 0 30px; background: #e3f2f4; }
.ph-shop-map .ph-floorplan-link { justify-content: flex-end; margin-bottom: 14px; }
/* The rail's ghost label reads L2 rather than GF here, so keep it legible on
   the tint rather than against the page background it was designed over. */
.ph-shop-map .ph-floor-level { color: #c9dee1; }

/* ---------- Detail pages ---------- */
.ph-detail { display: grid; grid-template-columns: 1fr 1.2fr; gap: 34px; padding: 40px 0; align-items: start; }
.ph-detail .visual { background: #fff; border-radius: var(--ph-radius); padding: 30px; box-shadow: 0 2px 10px rgba(0,0,0,.05); }
.ph-detail h1 { font-size: 30px; margin: 0 0 6px; text-transform: none; }
.ph-detail .meta { color: var(--ph-muted); margin-bottom: 18px; }
.ph-detail dl { display: grid; grid-template-columns: auto 1fr; gap: 6px 18px; }
.ph-detail dt { color: var(--ph-muted); }
.ph-detail dd { margin: 0; }
.ph-map-embed { border-radius: var(--ph-radius); overflow: hidden; min-height: 320px; background: #e7f2f3; display: flex; align-items: center; justify-content: center; color: var(--ph-muted); }
/*
 * ...but NOT once a map is mounted in it. The flex centring above exists for
 * the placeholder text; Mapbox's canvas container has no intrinsic size (its
 * canvas is absolutely positioned), so as a flex item it collapsed to 0x0 and
 * was centred in the box.
 *
 * Mapbox measures every pointer position from that container's rect, so it was
 * measuring from the map's CENTRE rather than its top-left. Hit tests landed
 * hundreds of pixels from the cursor: hovering one shop opened another's card,
 * and the apparent error changed as you zoomed because the offset is fixed
 * while the content underneath moves. Mapbox adds .mapboxgl-map to whatever it
 * mounts into, so this switches back to block exactly when a map is live.
 */
.ph-map-embed.mapboxgl-map { display: block; }

/* Movies */
.ph-movie-grid { display: grid; grid-template-columns: repeat(6, 1fr); gap: 3px; padding: 58px 0 66px; }
.ph-movie-grid a { display: block; }
.ph-movie-grid .poster { aspect-ratio: 220/302; border-radius: 0; overflow: hidden; background: #ddd; }
.ph-movie-grid .poster img { width: 100%; height: 100%; object-fit: cover; }
.ph-movie-grid .title { position: absolute; width: 1px; height: 1px; overflow: hidden; clip: rect(0 0 0 0); }
/* Spec: a 202x48 teal pill centred under the poster wall. The 202x48 is the
   shared .ph-btn size now (see "Buttons / chips"); only the teal is local. */
.ph-movie-more { text-align: center; margin: 0 0 24px; }
.ph-movie-more .ph-btn { background: var(--ph-teal-mid); }
.ph-sessions { width: 100%; border-collapse: collapse; margin-top: 18px; }
.ph-sessions th, .ph-sessions td { padding: 10px 14px; border-bottom: 1px solid #e2e8e9; text-align: left; }

/* Events listing */
/* Campaign cards show complete artwork, title and start date only. */
.page-template-page-whats-on .ph-section:not(.ph-section--grid) { padding-bottom: 0; }
.page-template-page-whats-on .ph-section-sub { margin-bottom: 0; }
.page-template-page-whats-on .ph-section--grid { padding-top: 0; }
.ph-event-grid { display: grid; grid-template-columns: repeat(3, 1fr); gap: 24px; padding: 30px 0; }
.ph-event-card { background: #fff; border-radius: var(--ph-radius); overflow: hidden; box-shadow: 0 2px 10px rgba(0,0,0,.05); color: var(--ph-text); display: block; }
.ph-event-card .media { display: block; aspect-ratio: 16/9; background: #ddd; overflow: hidden; }
.ph-event-card .media img { width: 100%; height: 100%; object-fit: contain; }
.ph-event-card .body { display: block; padding: 18px 16px 27px; }
.ph-event-card .dates { display: block; font-size: 16px; font-weight: 600; color: var(--ph-text); }
.ph-event-card :is(h2, h3) { display: -webkit-box; -webkit-line-clamp: 2; -webkit-box-orient: vertical; overflow: hidden; margin: 0 0 12px; font-size: 24px; line-height: 34px; text-transform: none; color: var(--ph-teal-mid); }

/* "In The Spotlight" — spec: 307px text column, 757px 16:9 image, 429px tall. */
.ph-spotlight-inner { display: grid; grid-template-columns: 307px 757px; gap: 29px; align-items: center; min-height: 429px; }
.ph-spotlight .eyebrow { color: var(--ph-text); font-size: 14px; margin: 0 0 6px; }
.ph-spotlight h2 { font-family: var(--ph-font-display); text-transform: uppercase; font-size: 34px; line-height: 1.12; margin: 0 0 14px; }
.ph-spotlight .body { font-size: 14px; line-height: 20px; margin: 0 0 22px; }
.ph-spotlight .media { display: block; border-radius: var(--ph-radius); overflow: hidden; aspect-ratio: 16/9; background: #dbe7e9; }
.ph-spotlight .media img { width: 100%; height: 100%; object-fit: cover; }
.ph-spotlight-arrows { display: flex; gap: 10px; margin-bottom: 24px; }
.ph-arrow { width: 48px; height: 48px; border: 0; border-radius: 10px; background: var(--ph-gold); color: #fff; font-size: 22px; line-height: 1; cursor: pointer; }

/*
 * 901–1135: the same composition, proportionally smaller.
 *
 * The row above is the spec's absolutes — 307 + 29 + 757 = 1093px, fixed
 * tracks that shrink nowhere — while `.ph-container` gives it
 * min(1090px, 100vw - 40px). Measured on Home AND What's On (one shared part,
 * so identical numbers) in all three languages, in Chromium and WebKit, before
 * this block existed: the PAGE scrolled sideways by 212px at 901, 153 at 960,
 * 89 at 1024, 53 at 1060 and 13 at 1100. At 1024 that is the right edge of the
 * 16:9 artwork, 89px past the glass, on every one of the four slides.
 *
 * The band ends at 1135 because 1136 is the first width — swept a pixel at a
 * time, not assumed — where the row sits at its authored 1093 AND keeps the
 * whole 20px gutter. Page overflow alone stops at 1113, but 1113–1135 is the
 * state the /location/ band already refused: no overflow and no gutter either,
 * the artwork running into the glass. 20 of the 23px between those two widths
 * is simply the gutter; the other 3 are the spec's own arithmetic, because
 * 307 + 29 + 757 is 1093 on a 1090 measure — 3px wider than the measure it was
 * drawn for — and that overshoot is only absorbed once .ph-container stops
 * growing at 1130 and starts centring. 1136 and up resolve exactly
 * as they did before: nothing in here applies there, so 1280, 1440 and 1920
 * are unchanged BY CONSTRUCTION rather than by re-tuning.
 *
 * The seam at 1135/1136 is that same 3px: inside the band the row resolves to
 * the 1090 it has (306.2 + 28.9 + 754.9, measured at 1135) and above it goes
 * back to the spec's 1093, a 0.27% step in track width.
 */
@media (min-width: 901px) and (max-width: 1135px) {
	/*
	 * The two columns as the RATIO they are, and `fr` rather than a calc per
	 * track is the point: flexible tracks divide the measure the grid ACTUALLY
	 * has, so the row cannot overflow however the scrollbar, the gutter or the
	 * zoom level land. The measure below therefore only ever feeds lengths that
	 * are free to be a pixel out — never the total.
	 *
	 * min-height scales because 429 is the height of a 757-wide 16:9 plate plus
	 * 3px of rounding. Left at 429 while the plate shrinks to 335 at 901, it
	 * stops being the row's height and becomes 94px of dead air around a
	 * centred image — the one composition in the spec that is tight turned
	 * loose. It stays a FLOOR either way: a long title still grows the row
	 * rather than spilling out of it.
	 */
	.ph-spotlight-inner {
		--ph-spot-measure: min(1090px, 100vw - 40px);
		grid-template-columns: 307fr 757fr;
		column-gap: calc(var(--ph-spot-measure) * 29 / 1093);
		min-height: calc(var(--ph-spot-measure) * 429 / 1093);
	}
	/*
	 * A grid item's automatic minimum size is its own min-content, and the one
	 * item here whose min-content is not ours to bound is the text column: the
	 * h2 is a D365 event title set in uppercase display type, and one long
	 * unbreakable word holds the track open past its `fr` share. Measured at
	 * 901 with the title replaced by a 24-character single word — 241.83 with
	 * this rule, 437.48 without it in Chromium and 460.16 in WebKit, each
	 * taking the difference out of the artwork beside it. Today's four events
	 * do not trigger it; the client's next one might.
	 *
	 * The media column is deliberately NOT in this selector. Its min-content
	 * would be the event photo's intrinsic width, but `img { max-width: 100% }`
	 * in the reset already bounds it — measured in both engines at every width
	 * in the band, the media track never pushed — and a rule that restates a
	 * cap the base stylesheet already applies is indistinguishable from one
	 * that exists to override it.
	 */
	.ph-spotlight .text { min-width: 0; }
}

/* Instagram feed: 4 tiles overhanging a full-bleed teal band (spec). */
.ph-social-band { position: relative; }
.ph-social-band > .ph-container { position: relative; z-index: 1; }
.ph-social-band::before { content: ""; position: absolute; left: 0; right: 0; top: 50%; transform: translateY(-50%); height: 244px; background: var(--ph-teal-mid); }
.ph-ig-grid { display: grid; grid-template-columns: repeat(4, 1fr); gap: 22px; position: relative; z-index: 1; }
.ph-ig-tile { display: block; aspect-ratio: 255/316; border-radius: 8px; overflow: hidden; background: #dbe7e9; }
.ph-ig-tile img { width: 100%; height: 100%; object-fit: cover; }

/* Downloads (Exhibition) + floor switch */
/* ---------- Exhibition venues (ui-specs: Exhibition Venues) ---------- */
.ph-venue-intro { display: grid; grid-template-columns: 1fr; gap: 40px; align-items: start; }
.ph-venue-intro p { font-size: 14px; line-height: 20px; margin: 0; }
/* Card is the 1090 measure; photo 478x270 inset 16, floorplan sits to the right. */
/*
 * Floorplan column 192, not 250 — the width the TITLE needs, taken from the one
 * column that can spare it.
 *
 * At the corrected 40px (see h3 below) the longest venue title, "L2 SQUARE
 * ATRIUM", is 331px of ink; the detail column was 278 (1090 measure - 32 padding
 * - 478 photo - 250 floorplan - 2x26 gap), so rows 2 and 3 wrapped to two lines
 * even at the old 34px. With the floorplan at 192 the 1fr resolves to 336, which
 * clears 331 with a little air.
 *
 * The frame itself cannot be copied literally here: it gives the title 302px
 * AND the floorplan ~319, which is 41px more than the 1090 measure holds — it
 * works there because the floorplan artwork is a diagonal with an empty
 * top-left corner that the title's tail simply crosses. Two grid cells cannot
 * overlap, so the choice is which element absorbs the deficit, and a one-line
 * title beats 58px of orientation graphic.
 */
.ph-venue-row {
	display: grid; grid-template-columns: 478px 1fr 192px; align-items: center; gap: 26px;
	background: #fff; border-radius: var(--ph-radius); padding: 16px; margin-top: 25px;
	box-shadow: 0 2px 10px rgba(0,0,0,.05); min-height: 293px;
}
.ph-venue-row .photo { display: block; height: 270px; border-radius: 12px; overflow: hidden; background: #dbe7e9; }
.ph-venue-row .photo img { width: 100%; height: 100%; object-fit: cover; }
.ph-venue-row .floorplan img { width: 100%; height: auto; display: block; }
/*
 * 40px, fitted rather than guessed, and 47 was the number to beat.
 *
 * The frame's text layer sets these titles at 40, and the theme's own Bou
 * College agrees to within a pixel at that size: "L1 STARS ATRIUM" measures 300
 * of ink in Exhibition Venues.pdf and 299.2 here at 40px; "L2 SQUARE ATRIUM"
 * measures 331 both places. (An earlier pass fitted 47px off a render that was
 * ~16% oversampled — at 47 this title would be 352 wide and would re-open the
 * wrap the column widening above exists to close.)
 *
 * line-height 48 rather than 42: a 40px face on a 42px line clips Bou College's
 * ascenders in Safari.
 */
.ph-venue-row h3 { font-family: var(--ph-font-display); text-transform: uppercase; font-size: 40px; line-height: 48px; color: var(--ph-teal-mid); margin: 0 0 18px; }
.ph-venue-row ul { list-style: none; margin: 0; padding: 0; }
.ph-venue-row li { display: flex; align-items: center; gap: 10px; font-size: 14px; line-height: 20px; margin-bottom: 14px; }
.ph-venue-row li .icon { display: inline-flex; color: var(--ph-teal-mid); }
.ph-venue-row li .icon svg { width: 18px; height: 18px; }
/* Spec alternates the photo to the right on every second venue. */
/* Reversed rows re-order the CHILDREN (detail, floorplan, photo — see below),
   so the wide detail track is the FIRST one here, not the middle: 1fr resolves
   to the same 336 the un-reversed row gives it. */
.ph-venue-row.is-reversed { grid-template-columns: 1fr 192px 478px; }
.ph-venue-row.is-reversed .photo { order: 3; }
.ph-venue-row.is-reversed .detail { order: 1; }
.ph-venue-row.is-reversed .floorplan { order: 2; }

/*
 * Download row — measured off Exhibition Venues.pdf, which is a 1440 frame at
 * 1:1, so every number below is the frame's own pixel value:
 *   cards      313x166, x = 231 / 564 / 897  -> 20px gutters, 979 total, and
 *              (1440-979)/2 = 230.5, i.e. the row is CENTRED, not stretched to
 *              the 1090 measure the venue cards above it use.
 *   radius     16 (231 -> 247 on the corner arc), not the 14 of --ph-radius.
 *   icon disc  40x40 at +24,+24 inside the card; glyph 18-22px, white.
 *   title      30px, cap top +87 from the card top.
 *   hint       14px, 39px below the title's cap top.
 *   spacing    47px above the row from the last venue card, 93px below it to
 *              the app strip.
 */
.ph-download-grid { display: grid; grid-template-columns: repeat(3, 313px); gap: 20px; justify-content: center; margin-top: 47px; }
/* The section's own 56px is 37px short of the frame's 93px below the row. */
.ph-section--exhibition-end { padding-bottom: 93px; }
/* Spec: left-aligned card, teal disc icon, teal title, small teal caption. */
.ph-download-card { background: #fff; border-radius: 16px; padding: 24px; min-height: 166px; text-align: left; box-shadow: 0 2px 10px rgba(0,0,0,.05); color: var(--ph-text); transition: box-shadow .18s ease, transform .18s ease; }
/*
 * 12px, not the 23px that separates the disc from the title's INK in the frame.
 * The frame measures ink; CSS lays out line BOXES, and this title's box carries
 * 11.2px of leading and ascender above its cap (30px Inter on a 38px line). So
 * margin-bottom:23px puts the cap at 98 where the frame has it at 87. The 12
 * below is 23 minus that 11.2, measured in the browser rather than derived, and
 * it lands the cap on 87.2 — the frame's own value. Same reason the title's
 * bottom margin is 6 and not the 11.2 the frame shows between the two inks.
 */
.ph-download-card .icon { width: 40px; height: 40px; border-radius: 50%; background: var(--ph-teal-mid); color: #fff; display: flex; align-items: center; justify-content: center; margin-bottom: 12px; }
/* The glyph is drawn on a 24-grid scaled from the 40px disc, so it fills it. */
.ph-download-card .icon svg { width: 100%; height: 100%; }
.ph-download-card .name { display: block; font-size: 30px; line-height: 38px; font-weight: 700; color: var(--ph-teal-mid); margin: 0 0 6px; }
.ph-download-card .hint { display: block; font-size: 14px; line-height: 20px; color: var(--ph-teal-mid); }
/*
 * Hover matches the other card surfaces on the site (.ph-venue-row and the
 * shop/event cards): the shadow deepens and the card lifts 2px. No colour
 * change — the whole card is already teal-on-white, so recolouring it is the
 * one move that would make it read as a different component on hover.
 */
.ph-download-card:hover, .ph-download-card:focus-visible { box-shadow: 0 8px 22px rgba(0,0,0,.10); transform: translateY(-2px); color: var(--ph-text); }
@media (prefers-reduced-motion: reduce) {
	.ph-download-card { transition: none; }
	.ph-download-card:hover, .ph-download-card:focus-visible { transform: none; }
}
/*
 * Mobile — Exhibition Venues - Default.pdf, a 390 frame at 1:1: the three cards
 * stack full-measure, 16px above the row and 16px between, and everything
 * inside a card (166 min-height, 24 padding, 40 disc, 30/14 type) is unchanged
 * from desktop. The 93px below the row to the app strip is unchanged too, so
 * .ph-section--exhibition-end needs no override. Three older rules elsewhere in
 * this file already drop the grid to one column at the same breakpoint; this
 * one carries the spacing they never had.
 */
@media (max-width: 900px) {
	.ph-download-grid { grid-template-columns: 1fr; gap: 16px; margin-top: 16px; }
}
.ph-floor-switch { display: flex; gap: 6px; justify-content: center; margin-bottom: 20px; }
.ph-floor-switch .ph-chip { border: 1px solid #d3dfe1; }
.ph-floor-switch .ph-chip.active { background: var(--ph-teal-mid); color: #fff; border-color: var(--ph-teal-mid); }
/* Measured: 311 + 311 + 422 with 23px gutters is exactly the 1090 measure. */
.ph-rate-cards { display: grid; grid-template-columns: 311px 311px 422px; gap: 23px; max-width: 1090px; margin: 0 auto; }
.ph-rate-cards > * { background: #fff; border-radius: var(--ph-radius); padding: 24px; min-height: 245px; box-shadow: 0 2px 10px rgba(0,0,0,.05); margin: 0; }
.ph-rate-cards h3 { font-size: 30px; line-height: 38px; font-weight: 700; color: var(--ph-teal-mid); margin: 0 0 5px; text-transform: none; }
.ph-rate-cards p { color: var(--ph-teal-mid); font-size: 14px; line-height: 20px; margin: 0; }
.ph-rate-card .icon { width: 40px; height: 40px; border-radius: 50%; background: var(--ph-teal-mid); color: #fff; display: flex; align-items: center; justify-content: center; margin-bottom: 14px; }
.ph-rate-card .icon svg { width: 22px; height: 22px; }

/*
 * 901–1129: the same three cards, proportionally narrower.
 *
 * 311 + 23 + 311 + 23 + 422 is the 1090 measure exactly — and it is 1090 of
 * FIXED track, so below 1130 the row keeps its width while `.ph-container`
 * loses its own. Measured on /parking/ in all three languages, Chromium and
 * WebKit, before this block: the page scrolled sideways by 209px at 901, 150
 * at 960, 86 at 1024, 50 at 1060 and 10 at 1100. The offender is always the
 * same element — `.ph-rate-card--wide`, the "Parking Info" card, which at 1024
 * ran 86px off-screen with its paragraphs cut mid-sentence.
 *
 * The band ends at 1129 because 1130 is where .ph-container stops shrinking
 * (1090 + 2x20) and the row is therefore back at its authored 1090 with the
 * whole 20px gutter. Page overflow alone stops earlier, at 1110, and those 20
 * px are exactly the gutter — this row is drawn ON the measure, so unlike the
 * spotlight above there is no third number to explain. 1130 and up are
 * untouched.
 */
@media (min-width: 901px) and (max-width: 1129px) {
	/*
	 * The three tracks as the ratio they are. `fr` divides the measure the grid
	 * actually has, so 311/311/422 cannot add up to more than the row holds;
	 * the gap is the only length taken from the variable, and a pixel of error
	 * there is absorbed by the tracks rather than pushed off the page.
	 *
	 * `calc(100vw - 40px)` needs no min() clamp here the way the spotlight's
	 * measure does: the band stops at 1129, one pixel below the width at which
	 * .ph-container caps at 1130, so inside the band the container content box
	 * IS the window less its two 20px gutters.
	 *
	 * Nothing inside a card is touched. The 24px padding, the 40px icon disc
	 * (shared with .ph-download-card, and the same disc at a different size on
	 * one page would read as a different component) and the 30/14 type all hold
	 * their spec values, exactly as they do when these cards go full-width
	 * below 900.
	 *
	 * What that costs is height, in EN, at the bottom of the band only. The wide
	 * card's copy is the one thing on this page already sized to the pixel —
	 * five lines in a 374px measure filling the 245px card to 197 + 2x24 with
	 * nothing to spare — so in the 285px measure it has at 901 it takes a sixth
	 * line and the row stands 265 tall instead of 245. Measured in both
	 * engines: 265 at 901 and 960, back to the spec's 245 from 1024 up. TC and
	 * SC hold 245 at every width measured; their copy is shorter.
	 *
	 * Scaling the padding was measured rather than assumed, and it does not buy
	 * the line back: at 901 the sixth line survives a 19px inset (row 255) and
	 * a 16px one (row 249), and only 12px — half the spec's inset, a bigger
	 * change to the card than the 20px of height it saves — returns five lines.
	 * So the padding stays, and the card grows. That is the trade this file
	 * makes everywhere (see .ph-event-card): a card grows rather than clipping
	 * the client's copy, and min-height stays a floor, not a cap.
	 *
	 * minmax(0, …) IS THE SAME GUARD .ph-spotlight .text GETS, spelled on the
	 * track instead of the item. A bare `Nfr` track is minmax(AUTO, Nfr), and
	 * that auto floor is the item's min-content — so one unbreakable word in a
	 * rate-card h3 holds its track open and the two flexible tracks beside it
	 * are scaled up to keep the ratio, which multiplies the damage instead of
	 * containing it. Measured on /parking/ with every h3 replaced by a single
	 * 41-character word, page overflow at 901: 3058px with a bare `fr`, 923
	 * with minmax(0, …) — against 1064 on the pre-band CSS at the same width
	 * and 835 at 1130, where this block does not apply. So the long word
	 * overflows this page at EVERY width, in band and out, with or without this
	 * block and on HEAD's stylesheet too; what the bare `fr` added was roughly
	 * 2000px of it, and that part is this block's to own.
	 *
	 * It is bounded here and NOT otherwise mitigated, because real content is
	 * nowhere near it. The longest unbreakable run in any rate-card heading is
	 * "Private" at 98.5px inside a 198px content box at 901 — 101% slack, the
	 * tightest of the nine headings across EN/TC/SC in both the database and
	 * inc/content-defaults.php, and the Chinese headings cannot form a long run
	 * at all because CJK breaks between characters. `overflow-wrap: anywhere`
	 * on the heading was measured too and removes the in-band overflow
	 * completely, but it changes where the CLIENT's copy is allowed to break,
	 * it would only apply inside this band, and the overflow it removes is
	 * pre-existing at every other width — so it is not this block's call to
	 * make. If a heading ever does arrive long enough to matter, that is the
	 * rule to reach for, and it belongs on the base .ph-rate-cards h3.
	 *
	 * Verified free: against real content, minmax(0, …) changes no measured
	 * rect anywhere — row, card, content box, page overflow — in Chromium,
	 * WebKit and Firefox, in all three languages, at every width in the band
	 * and at both seams.
	 */
	.ph-rate-cards {
		--ph-rate-measure: calc(100vw - 40px);
		grid-template-columns: minmax(0, 311fr) minmax(0, 311fr) minmax(0, 422fr);
		column-gap: calc(var(--ph-rate-measure) * 23 / 1090);
	}
}

/* ---------- Responsive ---------- */
@media (max-width: 900px) {
	.ph-nav { display: none; position: absolute; top: 100%; left: 0; right: 0; margin-left: 0; background: #fff; flex-direction: column; gap: 0; padding: 10px 24px 18px; box-shadow: 0 10px 16px rgba(0,0,0,.08); }
	.ph-nav.open { display: flex; }
	/* inline-flex, not block: this rule only exists to reveal the button, and
	   `block` would silently drop the centring .ph-icon-btn sets for its glyph. */
	.ph-burger { display: inline-flex; }

	/* Keep search beside the language switcher on mobile. */
	.ph-header-tools .ph-icon-btn--pin { display: none; }
	.ph-header-tools { gap: 6px; }
	.ph-header-tools .ph-icon-btn { width: 44px; height: 44px; flex: none; }
	.ph-icon-btn--search svg { width: 18px; height: 18px; }
	.ph-header-inner { padding: 12px 16px; gap: 12px; }
	.ph-logo img { height: 34px; }
	.ph-langs { white-space: nowrap; }

	/* Banner keeps its inset + rounded corners at small widths (spec). */
	.ph-page-banner { margin-left: 16px; margin-right: 16px; min-height: 210px; }
	/*
	 * VIC only. Its banner (explore-vic-banner.jpg, 18 Sep 2026) keeps a phone
	 * in the right-hand third so the centred title has clear ground on desktop.
	 * A 358x210 banner shows only the middle ~75% of a 1440x640 picture, which
	 * drags that phone in under the title; biasing the crop to the left lets it
	 * slide back to the edge. Keyed on the page template because the banner is
	 * a Featured Image and has no class of its own — if the client replaces the
	 * picture, this costs them nothing worse than a slightly off-centre crop.
	 */
	.page-template-page-vic .ph-page-banner img { object-position: 22% center; }
	.ph-listing-search .ph-searchbar { height: 52px; border: 1px solid var(--ph-teal); }

	/* Spec order on mobile: floorplan link centred on its own row, then tabs. */
	.ph-filterbar { justify-content: center; gap: 22px; }
	.ph-floorplan-link { order: -1; width: 100%; justify-content: center; margin: 0 0 6px; }
	.ph-subfilters { justify-content: flex-start; }
	.ph-shop-grid, .ph-event-grid { grid-template-columns: repeat(2, 1fr); }
	.ph-movie-grid { grid-template-columns: repeat(2, 1fr); }
	.ph-promo-card, .ph-promo-card:nth-child(even) { grid-template-columns: 1fr; }
	.ph-promo-card:nth-child(even) .media { order: 0; }
	.ph-sdf { display: flex; gap: 12px; overflow-x: auto; scroll-snap-type: x mandatory; overscroll-behavior-x: contain; padding-bottom: 10px; }
	.ph-sdf a { flex: 0 0 84%; aspect-ratio: 4/3; scroll-snap-align: start; }
	.ph-explore-grid { grid-template-columns: 1fr 1fr; grid-template-rows: auto; }
	.ph-detail { grid-template-columns: 1fr; }
	/*
	 * The shop page needs its OWN rule here. `.ph-detail` above is one class;
	 * `.ph-shop-detail .ph-detail` (which sets the two equal columns) is two,
	 * and a media query adds no specificity — so the shop page kept its desktop
	 * two-up at every width while every other detail page collapsed. Mobile —
	 * Shopping - Details.pdf is a single column: the photo runs the full 358px
	 * measure at x16 with the info block beneath it, ~21px below.
	 *
	 * The photo is already first in the DOM (single-ph_shop.php), so source
	 * order alone puts it on top — no `order` needed.
	 */
	.ph-shop-detail .ph-detail { grid-template-columns: 1fr; gap: 24px; }
	/*
	 * 40, not the desktop 44: Mobile — Shopping - Details.pdf sets the shop
	 * name at 40pt, and the location page's own h1 already is. It never had a
	 * mobile override. It matters more since the description moved directly
	 * under the name (client QA 38): the longest title on the books runs six
	 * lines at 390 and pushes the description most of a screen down. Same two
	 * classes as the desktop rule and later in the file, so it wins on order.
	 */
	.ph-shop-detail .ph-detail h1 { font-size: 40px; }
	/*
	 * Client QA 38 — on a phone the description belongs directly under the shop
	 * name, not below four icon rows. The DOM order is category / name / facts /
	 * description because that is the DESKTOP spec (Shopping - Shop Details.pdf)
	 * and it is also the order a screen reader and the SEO snapshot want, so the
	 * re-order is presentational only: `.info` becomes a flex column and the two
	 * blocks swap with `order`. Nothing about the markup changes.
	 *
	 * Every selector names `.info` as well as `.ph-shop-detail` — three classes,
	 * not two. `.ph-shop-detail .desc` (the desktop rule at the top of this
	 * file) is two classes and a media query adds NO specificity, so a
	 * two-class rule here would tie with it and be decided by source order
	 * alone. That is the same trap the comment above documents, and the
	 * border-swap below is exactly the kind of override it would silently eat.
	 */
	.ph-shop-detail .info { display: flex; flex-direction: column; }
	.ph-shop-detail .info .cat { order: 1; }
	.ph-shop-detail .info h1 { order: 2; }
	.ph-shop-detail .info .desc { order: 3; }
	.ph-shop-detail .info .facts { order: 4; }
	/*
	 * The teal rule moves with the description. On desktop it is the
	 * description's border-TOP, dividing the facts above from the copy below;
	 * once the two swap, the same divider has to sit BELOW the description so
	 * the rhythm stays name -> description -> rule -> facts. Same 2px #8bd7df,
	 * same 22px of air — just on the other edge.
	 *
	 * `.desc` is a flex item here, so it establishes a BFC and the first
	 * paragraph's top margin can no longer collapse out of it the way it does
	 * on desktop (where the border-top blocks the collapse anyway). Zeroing the
	 * first and last child's outer margins keeps the 26px under the h1 and the
	 * 22px above the rule as the only gaps, instead of stacking a paragraph
	 * margin on top of each.
	 *
	 * The facts lose their own 22px bottom margin because they are now last in
	 * the block: kept, it is dead space between the final row and the floorplan
	 * band, with nothing under it to separate.
	 */
	.ph-shop-detail .info .desc { border-top: 0; padding-top: 0; border-bottom: 2px solid #8bd7df; padding-bottom: 22px; margin: 0 0 12px; }
	.ph-shop-detail .info .desc > :first-child { margin-top: 0; }
	.ph-shop-detail .info .desc > :last-child { margin-bottom: 0; }
	/*
	 * A tenant with no description. The template prints the .desc box whether
	 * or not D365 sent anything, and up here an empty box is not nothing — it
	 * is a 2px rule with 22px under it, floating in blank space directly below
	 * the shop's name. No shop is in that state today (shortest description on
	 * the books is two characters), but Description is a free CRM field and one
	 * sync can empty it. Mobile only: on desktop the same empty box lands after
	 * the facts, where it reads as a closing rule, and that view is not ours to
	 * change here.
	 */
	.ph-shop-detail .info .desc:empty { display: none; }
	.ph-shop-detail .info .facts { margin-bottom: 0; }
	/*
	 * Client QA 39 — each store-information row becomes two lines, label over
	 * value. The spans come from ph_fact_row() (inc/helpers.php); the separator
	 * that the msgid owns ("Shop No.: " / "舖號：") is meaningful only while the
	 * two halves share a line, so it is hidden rather than removed — the <li>'s
	 * text content stays byte-identical for the gate and the crawler.
	 *
	 * Type does the work of distinguishing the lines: the label drops to 13px
	 * and the value takes the darker body ink, so the value reads as the answer
	 * and the label as its caption. No new colours — --ph-muted is already the
	 * facts' ink and --ph-text is the body's.
	 *
	 * `line-height: 1.5` on the label is 19.5px, which is what the icon is sized
	 * and positioned against below.
	 */
	.ph-shop-detail .info .facts .k { display: block; font-size: 13px; line-height: 1.5; color: var(--ph-muted); }
	.ph-shop-detail .info .facts .v { display: block; color: var(--ph-text); }
	.ph-shop-detail .info .facts .sep { display: none; }
	/*
	 * The icon aligns to the LABEL line, not to the middle of the row.
	 *
	 * `top: 11px` was measured against a one-line row: 9px of padding plus half
	 * the 14px/1.6 line box, minus half the 19px icon. The row is now ~48px
	 * tall, so the same value leaves the icon floating between the two lines
	 * with neither to anchor it. Against the 13px/1.5 label line the arithmetic
	 * is 9 + (19.5 - 19) / 2 = 9.25, i.e. the icon is the same height as its
	 * line and simply sits on it.
	 *
	 * `.info` is in the selector for specificity, not for reach: the desktop
	 * `.ph-shop-detail .facts li::before` is the same weight as a two-class
	 * override here, and a media query adds none, so the two would tie and be
	 * settled by source order alone. The Movies venue rows are a separate
	 * container (.ph-movies-venue on page-movies.php), one line each, and out of
	 * scope for this QA item — nothing here can reach them.
	 */
	.ph-shop-detail .info .facts li::before { top: 9px; }
	/*
	 * "Visit website" has no label/value pair — it is a single link — so it
	 * stays one line. Its 9px padding was tuned for a row of the same height as
	 * its neighbours; beside two-line rows it reads as cramped, hence the
	 * matching top offset only.
	 */
	.ph-shop-detail .info .facts li.web { padding-top: 12px; }
	.ph-shop-detail .info .facts li.web::before { top: 12px; }
	.ph-footer-cols { grid-template-columns: 1fr 1fr; }
	.ph-download-grid, .ph-rate-cards { grid-template-columns: 1fr; }
}
@media (max-width: 560px) {
	/*
	 * Only EVENT cards go single-column on mobile. The 390 frames keep shops
	 * and movies two-up — shop cards 170x157 with a 17px gutter, movie posters
	 * edge to edge — and collapsing all three to one column made shop cards
	 * 358x300 and stacked 250 of them into a 63,000px page.
	 */
	.ph-event-grid { grid-template-columns: 1fr; }
	.ph-shop-grid { grid-template-columns: repeat(2, 1fr); gap: 17px; padding: 20px 0 10px; }
	/* 170x157 in the frame — the desktop card's 120px logo alone overshot it. */
	.ph-shop-card { min-height: 157px; padding: 16px 12px; }
	.ph-shop-card .logo { height: 70px; margin-bottom: 10px; }
	.ph-shop-card .logo img { max-height: 70px; }
	.ph-shop-card .name { font-size: 14px; }
	.ph-shop-card .unit { font-size: 12px; }
	.ph-movie-grid { grid-template-columns: repeat(2, 1fr); }

	.ph-page-banner { min-height: 224px; }

	/*
	 * Mobile gutter is 16px, not 20 — every 390px frame puts content at x16
	 * spanning 358 (Home, Shopping, VIC, Parking all measure identically).
	 * At 20 the whole site sat 4px narrow and 4px in on both edges.
	 */
	.ph-container { padding-inline: 16px; }
	/* Spec insets the VIC card's contents 28px, giving a 302px Join button. */
	.ph-hero-vic { padding: 28px; }
}

/* ---------- Movies detail (ui-specs: Movies - Details) ---------- */
/*
 * Every number below is measured off Movies - Details.pdf at its native 1440pt
 * page. The load-bearing one is the MEASURE: content runs x64 -> x1376, i.e.
 * the 1312 wide shell (--ph-maxw), not the 1090 the rest of the site uses. The
 * page was built on the default .ph-container and every column inside it was
 * therefore ~180px narrower than drawn, which is most of what "layout not
 * matching the design" was. Columns: poster 424 (x64-x488), gutter 64,
 * right column 824 (x551-x1375).
 */
.ph-container--wide { max-width: var(--ph-maxw); }
.ph-movie-detail { background: linear-gradient(#e3f2f4 0 78%, var(--ph-bg) 100%); padding: 32px 0 60px; }
.ph-movie-detail .ph-detail { grid-template-columns: 424px 1fr; gap: 64px; padding: 0; }
/*
 * The poster is flush in its column — no card. `.ph-detail .visual` gives it a
 * white background, 30px of padding and a shadow (that treatment belongs to the
 * What's On detail page), which shrank the artwork to 364px inside a frame the
 * spec does not draw: in the frame the poster's own left edge IS the container
 * edge at x64, and its top-left pixel is artwork.
 */
.ph-movie-detail .visual { background: none; padding: 0; box-shadow: none; border-radius: 10px; overflow: hidden; }
.ph-movie-detail .visual img { display: block; width: 100%; height: auto; }
.ph-movie-detail h1 { font-family: var(--ph-font-body); font-weight: 400; font-size: 44px; color: var(--ph-teal); text-transform: none; letter-spacing: 0; margin: 0 0 22px; }
/* Eyebrow ink is the muted taupe, matching the shop page's category line —
   the frame's "Alternatives" samples #766e5c, not the body colour. */
.ph-movie-detail .eyebrow { color: var(--ph-muted); font-size: 16px; margin: 0 0 6px; }

/* Facts: two columns, 40px apart, ~40px row pitch — rows sit at y297/337/380
   in the frame. 19px icons in a 32px column, the same geometry the shop detail
   page uses, so the two pages line up when viewed back to back. */
.ph-movie-facts { display: grid; grid-template-columns: 1fr 1fr; row-gap: 18px; column-gap: 40px; margin: 0 0 22px; padding: 0; list-style: none; }
.ph-movie-facts li { display: grid; grid-template-columns: 32px 1fr; align-items: start; font-size: 14px; color: var(--ph-muted); line-height: 20px; }
.ph-movie-facts .ico { width: 19px; height: 19px; color: #249fae; }
.ph-movie-facts .ico svg { width: 100%; height: 100%; display: block; }
.ph-movie-detail hr { border: 0; border-top: 2px solid #8bd7df; margin: 22px 0; }

/* Block headings ("Film Synopsis", "Schedules") are icon + label at body size,
   not display type — 15px in the frame, same taupe as the facts. */
.ph-movie-block h2 {
	display: grid; grid-template-columns: 32px 1fr; align-items: center;
	font-family: var(--ph-font-body); font-size: 15px; font-weight: 400; letter-spacing: 0;
	text-transform: none; color: var(--ph-muted); margin: 0 0 14px;
}
.ph-movie-block h2 .ico { width: 19px; height: 19px; color: #249fae; }
.ph-movie-block h2 .ico svg { width: 100%; height: 100%; display: block; }
.ph-movie-block .desc { color: var(--ph-muted); font-size: 14px; line-height: 20px; }
.ph-movie-block .desc p { margin: 0 0 10px; }
.ph-movie-block .desc p:last-child { margin-bottom: 0; }

/* Date tabs: a dot-separated row, active one teal with a 2px underline. The
   separator is a pseudo-element so it never lands before the first tab or
   after a wrap. */
.ph-showtime-tabs { display: flex; flex-wrap: wrap; align-items: center; gap: 0; margin: 0 0 18px; }
.ph-showtime-tabs button {
	appearance: none; background: none; border: 0; cursor: pointer; position: relative;
	font: inherit; font-size: 14px; color: var(--ph-muted);
	padding: 0 0 6px; margin: 0 20px 6px 0; border-bottom: 2px solid transparent;
}
.ph-showtime-tabs button + button { margin-left: 20px; }
/* The dot hangs in the button's own left margin — absolute against the button
   (hence position:relative above), so it sits OUTSIDE the border-bottom that
   marks the active tab and cannot pick up its underline. */
.ph-showtime-tabs button + button::before {
	content: ""; position: absolute; left: -23px; top: 7px;
	width: 5px; height: 5px; border-radius: 50%; background: #8bd7df;
}
.ph-showtime-tabs button.is-active { color: var(--ph-teal); border-bottom-color: var(--ph-teal); }
.ph-showtime-tabs button:hover { color: var(--ph-teal-deep); }

/*
 * Showtimes are cards, not table rows: 131x56 white, 17px apart, five to a row
 * inside the 824 column. Time top-left, seat-availability dot top-right, price
 * bottom-left, house bottom-right — a 2x2 grid rather than a stack, which is
 * what the first build made of it.
 */
.ph-showtimes { display: grid; grid-template-columns: repeat(auto-fill, 131px); gap: 17px; }
.ph-showtime {
	display: grid; grid-template-columns: 1fr auto; align-content: center; gap: 4px 8px;
	height: 56px; background: #fff; border-radius: 10px; padding: 9px 12px;
	color: var(--ph-text); text-decoration: none;
}
a.ph-showtime:hover { box-shadow: 0 2px 10px rgba(0,0,0,.12); color: var(--ph-text); }
a.ph-showtime:focus-visible { outline: 2px solid var(--ph-teal); outline-offset: 2px; }
.ph-showtime .time { font-size: 17px; line-height: 1; }
.ph-showtime .dot { width: 11px; height: 11px; border-radius: 50%; justify-self: end; align-self: center; }
.ph-showtime .price,
.ph-showtime .house { font-size: 12px; line-height: 1; color: var(--ph-muted); }
.ph-showtime .house { justify-self: end; }
/* JS shows one day at a time; with JS off every panel stays visible and keeps
   its own heading, so the tabs degrade to labels rather than hiding content. */
.ph-showtime-day { font-size: 14px; font-weight: 600; color: var(--ph-muted); margin: 0 0 10px; text-transform: none; letter-spacing: 0; }
.ph-showtime-panel + .ph-showtime-panel { margin-top: 22px; }
.js .ph-showtime-day { display: none; }
.js .ph-showtime-panel + .ph-showtime-panel { margin-top: 0; }
.js .ph-showtime-panel[hidden] { display: none; }
.ph-showtimes-empty { color: var(--ph-muted); font-size: 14px; margin: 0; }

@media (max-width: 900px) {
	/* 390 frame: one column, poster above the text, cards left to fill the
	   row rather than pinned to a 131px track that would strand a gap. */
	.ph-movie-detail .ph-detail { grid-template-columns: 1fr; gap: 24px; }
	.ph-movie-detail h1 { font-size: 30px; }
	.ph-movie-facts { grid-template-columns: 1fr; row-gap: 12px; }
	/* Two cards to a row, as the 390 frame draws them (~170 wide inside the
	   343 measure) — not the three a 131px track would squeeze in. */
	.ph-showtimes { grid-template-columns: repeat(auto-fill, minmax(150px, 1fr)); }
}

/* ---------- VIC (ui-specs: VIC - Default) ---------- */
/*
 * The full 1090 measure, not 1088. The designer sized these cards so the
 * longest title ("Exclusive Privileges", 226px at 24px) exactly fills the
 * inner width — two pixels short and it wraps, taking the card 23px over
 * spec height. The gutter is measured at ~20px; 18px buys the row back those
 * pixels while keeping the card pitch within 1px of the spec.
 */
.ph-vic-benefits { display: grid; grid-template-columns: repeat(4, 1fr); gap: 18px; max-width: 1090px; margin: 0 auto; }
.ph-vic-card { min-height: 193px; padding: 16px; border-radius: var(--ph-radius); background: #fff; text-align: left; box-shadow: 0 2px 10px rgba(0,0,0,.05); }
.ph-vic-card .icon { width: 60px; height: 60px; border-radius: 12px; background: var(--ph-teal-mid); color: #fff; display: flex; align-items: center; justify-content: center; margin-bottom: 16px; }
.ph-vic-card .icon svg { width: 28px; height: 28px; }
/*
 * 24px, not 26px: "Exclusive Privileges" measures exactly 226px in the spec,
 * which is the card's inner width — at 26px it is 243px and wraps to a second
 * line, which is what pushed these cards to 238px against a 193px spec.
 */
.ph-vic-card h3 { font-size: 24px; line-height: 30px; color: var(--ph-teal-mid); margin: 0 0 8px; text-transform: none; }
.ph-vic-card p { font-size: 14px; line-height: 20px; color: var(--ph-text); margin: 0; }
.ph-vic-privileges { display: grid; grid-template-columns: 1fr 1fr; max-width: 1090px; margin: 40px auto 0; min-height: 352px; border-radius: var(--ph-radius); overflow: hidden; background: #fff; }
.ph-vic-privileges .media { background: #dbe7e9; }
.ph-vic-privileges .media img { width: 100%; height: 100%; object-fit: cover; }
.ph-vic-privileges .panel { padding: 58px; }
.ph-vic-privileges h2 { font-family: var(--ph-font-display); font-size: 40px; line-height: 46px; text-align: left; color: #0090a0; margin: 0 0 14px; }

/* Parking rates band: full-bleed teal with the map card overhanging it. */
.ph-parking-map { position: relative; padding: 48px 0 47px; }
/*
 * Inset-based, not `left: calc(50% - 50vw); width: 100vw`. .ph-parking-map is
 * already a full-width block (it is a direct child of .ph-section, outside any
 * .ph-container), so `left/right: 0` reaches both page edges exactly. 100vw
 * measured the viewport INCLUDING the scrollbar, which made the band 1440 wide
 * inside a 1425 client box: 7.5px of real content past the right edge, and 8px
 * of horizontal scroll on the whole document. Insets resolve against the
 * containing block, which already excludes the scrollbar, so this cannot
 * overflow whatever the scrollbar's width or the zoom level.
 */
.ph-parking-map::before { content: ""; position: absolute; left: 0; right: 0; top: 48px; height: 352px; background: var(--ph-teal-mid); z-index: 0; }
.ph-parking-map .ph-map-embed { position: relative; z-index: 1; max-width: 1090px; margin: 0 auto; min-height: 447px; }
.ph-carousel-nav { display: flex; gap: 24px; justify-content: center; margin-top: 25px; }
.ph-carousel-nav button { width: 48px; height: 48px; border: 0; border-radius: 8px; background: var(--ph-gold); color: #fff; font-size: 20px; cursor: pointer; }

/* ---------- Nearby Attractions (ui-specs: Nearby Attractions - Default) ---------- */
/*
 * `.ph-attractions .ph-section-sub { color: var(--ph-text) }` used to sit here.
 * It was a no-op the day it was written — it restated the base rule's own
 * colour — but the moment the base moved to --ph-muted it would have become a
 * live exception, pinning this one page's sub-line to #333 while every other
 * page's went taupe. Removed rather than updated: there is no ruling that
 * Attractions differs, and a rule that only exists to repeat the default is
 * indistinguishable from one that exists to override it.
 */
/* Image-fill tiles that overhang the panel below them by 126px. */
.ph-attraction-grid { display: grid; grid-template-columns: repeat(4, 248px); gap: 16px; justify-content: center; position: relative; z-index: 2; margin-bottom: -126px; }
.ph-attraction-card { position: relative; height: 200px; border-radius: 10px; overflow: hidden; display: block; }
.ph-attraction-card img { width: 100%; height: 100%; object-fit: cover; }
.ph-attraction-card::after { content: ""; position: absolute; inset: auto 0 0 0; height: 60%; background: linear-gradient(transparent, rgba(0,0,0,.55)); }
.ph-attraction-card .label { position: absolute; left: 18px; bottom: 18px; z-index: 2; color: #fff; font-weight: 700; font-size: 20px; line-height: 28px; }
.ph-attraction-panel { background: #fff; border-radius: 20px; padding: 146px 26px 26px; display: grid; grid-template-columns: 1fr 1fr; max-width: 1090px; margin: 0 auto; }
.ph-attraction-panel h3 { font-size: 26px; color: var(--ph-teal-mid); text-transform: none; margin: 0 0 12px; }
.ph-attraction-panel > div + div { border-left: 2px solid #9adee4; padding-left: 44px; }
/* Tiles are buttons now — strip the UA chrome so they read as images. */
.ph-attraction-card { padding: 0; border: 0; background: none; cursor: pointer; text-align: left; width: 100%; }
.ph-attraction-body p { font-size: 14px; line-height: 20px; margin: 0 0 16px; }
/* Getting There: Walking • Driving, the active one underlined in teal. */
.ph-mode-switch { display: flex; align-items: center; gap: 14px; margin-bottom: 26px; }
.ph-mode { display: inline-flex; align-items: center; gap: 7px; padding: 0 0 7px; border: 0; border-bottom: 2px solid transparent; background: none; color: var(--ph-text); font-size: 14px; cursor: pointer; }
.ph-mode svg { width: 17px; height: 17px; }
.ph-mode.is-active { color: var(--ph-teal-mid); border-bottom-color: var(--ph-teal-mid); font-weight: 600; }

/*
 * The selected attraction tile needs to LOOK selected. main.js has always
 * toggled .is-active here, and the class had no rule anywhere — so clicking a
 * tile swapped the copy and the travel figures correctly while all four tiles
 * stayed identical. With the panel below the fold on a laptop, the click
 * produced no visible feedback at all. The mode switch beside it does get an
 * underline, which made the omission read as a bug rather than a choice.
 */
.ph-attraction-card { border: 2px solid transparent; transition: border-color .18s ease, box-shadow .18s ease; }
.ph-attraction-card.is-active { border-color: var(--ph-teal); box-shadow: 0 4px 16px rgba(0, 99, 110, .18); }
/*
 * The label stays WHITE when selected. The first version of the is-active fix
 * also recoloured it teal, which over a photograph + the bottom gradient was
 * barely legible (QA, Eddie, 27 Aug — Chi Lin Nunnery). The border and shadow
 * are the selected state; the label never changes.
 */
.ph-mode-switch .dot { width: 8px; height: 8px; border-radius: 50%; background: #00bccb; }
.ph-travel { list-style: none; margin: 0; padding: 0; }
.ph-travel li { display: flex; align-items: center; gap: 10px; font-size: 14px; line-height: 20px; margin-bottom: 18px; }
.ph-travel .icon { display: inline-flex; color: var(--ph-teal-mid); }
.ph-travel .icon svg { width: 18px; height: 18px; }
/* Spec map is full-bleed, square corners. */
.ph-attractions-map { margin-top: 26px; }
.ph-attractions-map .ph-map-embed { border-radius: 0; min-height: 815px; max-width: none; }

/*
 * 901–1079: the same four tiles and the same overhang, proportionally smaller.
 *
 * 4 x 248 + 3 x 16 is 1040 of fixed track, centred in a measure that stops
 * being 1040 wide at 1080. Measured on /nearby-attractions/ in all three
 * languages, Chromium and WebKit, before this block: the page scrolled
 * sideways by 70px at 901, 40 at 960 and 8 at 1024 — half of the shortfall at
 * each edge, because `justify-content: center` splits it. It is the smallest
 * of the three overflows on the site and the first to disappear, and like the
 * other two it was invisible to the browser gate: 375, 768, 1280 and 1440 all
 * sit outside this band.
 *
 * The band ends at 1079, and here the two criteria really do differ: overflow
 * stops at 1040, where the row exactly fills the measure and the outer tiles
 * touch the glass, while 1080 (1040 + 2x20) is the first width that also has
 * the whole gutter. Swept a pixel at a time. 1080 and up are untouched, so
 * 1280, 1440 and 1920 are unchanged by construction.
 */
@media (min-width: 901px) and (max-width: 1079px) {
	/*
	 * `minmax(0, 248px)` — fluid below the tile the spec draws, never wider
	 * than it. Free space is distributed equally up to each growth limit, so
	 * the four tracks stay identical to one another at every width and snap
	 * back to exactly 248 at the seam.
	 *
	 * The overhang is scaled, not kept. -126 against the spec's 200px tile hides
	 * 63% of it behind the panel and leaves 74 standing above it; against the
	 * 165.6px tile this band has at 901 the same 126 would hide 76% and leave
	 * 40 — a different picture, not a smaller one. Scaled, the tile gives up
	 * 104.3 at 901 and the proportion holds at every width in the band.
	 * The panel's 146 top padding is the same number seen from
	 * the other side — it is what clears the overhang by 20px — so it scales
	 * with it or the clearance goes negative and the copy lands under the
	 * tiles. Both are declared on the measure rather than as percentages
	 * because the panel is 1090 wide where the tiles are 1040, and a percentage
	 * would resolve each against a different base.
	 */
	.ph-attractions { --ph-attr-measure: calc(100vw - 40px); }
	.ph-attraction-grid {
		grid-template-columns: repeat(4, minmax(0, 248px));
		column-gap: calc(var(--ph-attr-measure) * 16 / 1040);
		margin-bottom: calc(var(--ph-attr-measure) * -126 / 1040);
	}
	/* 248 x 200 restated as the ratio it is, so the tiles keep their proportion
	   instead of turning into letterboxes as the tracks narrow. The 2px border
	   and the shadow of .is-active are deliberately NOT scaled — the border is
	   a brand line, and with box-sizing: border-box it costs the tile no width. */
	.ph-attraction-card { height: auto; aspect-ratio: 248 / 200; }
	/*
	 * The label is the one thing here that shrinking breaks, and 19.5 rather
	 * than 20 is the reason this rule is eight lines instead of none.
	 *
	 * It is absolutely positioned at left:18 with no right, so its shrink-to-
	 * fit width is the tile's PADDING box (248 less the 2px border each side)
	 * less that 18 — 226px — and the longest name in the set, "Kai Tak Cruise
	 * Terminal", already sets 224.8 of it at the spec size. 1.2px from wrapping
	 * at the width it was drawn for.
	 *
	 * Scaled straight at a 20 share that 1.2px does not survive, because glyph
	 * advances are not quite linear in the size: swept a pixel at a time, the
	 * name wrapped to two lines at 115 of the band's 179 widths (901 through
	 * 1015), which lifts it off the gradient it is set on and breaks the row.
	 * At 19.5 it clears everywhere in the band — measured, in every tile, in
	 * all three languages (TC and SC names are 80–120px and were never close).
	 * The seam pays 2.5% of label size at 1080, which is the smallest step that
	 * makes the sweep come back clean.
	 *
	 * THE REFERENCE IS THE TILE, NOT THE ROW, and that is the whole point of
	 * the cqw pair below. The measure is `100vw - 40px`, which is the container
	 * only while `100vw` equals the layout width — true on macOS and iOS, where
	 * scrollbars are overlays, and false on every Windows and Linux box, where
	 * `100vw` includes the 15–17px classic scrollbar and the container does
	 * not. The tracks absorb that (they are minmax(0, 248px), so the row cannot
	 * overflow) but the label's TYPE does not: it comes out ~2% large against a
	 * tile that did not grow, and 2% is more than the 1.2px this name has.
	 * Measured with a real 17px classic scrollbar, "Kai Tak Cruise Terminal"
	 * WRAPPED to two lines at layout widths 901 and 940 — the exact failure the
	 * 19.5 above was chosen to prevent, reappearing on the platforms the sweep
	 * could not see. Sizing from the tile removes the scrollbar from the
	 * arithmetic entirely: the container query resolves against the card's own
	 * content box, which is the box the label has to fit inside, so the ratio
	 * of available width to type size is now CONSTANT across the band instead
	 * of drifting with something the tile does not share.
	 *
	 * 244, not 248: container query units resolve against the query container's
	 * CONTENT box, and the card carries the 2px .is-active border on all four
	 * sides at every state (transparent when inactive), so 100cqw is 248 - 4 at
	 * the spec tile. Dividing by 244 therefore reproduces 19.5/28/18/18 exactly
	 * at 1080 and tracks the measure-based values it replaces to within 0.35%
	 * everywhere in the band — the seam and the sweep above both still stand.
	 * Dividing by 248 would quietly shrink the label 1.6% and double the seam
	 * step to 4.2%.
	 *
	 * The measure-based declarations are kept AHEAD of the cqw ones on purpose.
	 * This repo states no browser floor, and container query units are the
	 * newest thing in this file by some years (Safari 16 / Chrome 105 / Firefox
	 * 110, against Safari 15 for the aspect-ratio two rules up). Anything older
	 * drops the four it cannot parse and keeps the four above them, which is
	 * the behaviour this band shipped with — imperfect on a classic scrollbar,
	 * but the imperfection it already had, never nothing.
	 */
	.ph-attraction-card { container-type: inline-size; }
	.ph-attraction-card .label {
		font-size: calc(var(--ph-attr-measure) * 19.5 / 1040);
		line-height: calc(var(--ph-attr-measure) * 28 / 1040);
		left: calc(var(--ph-attr-measure) * 18 / 1040);
		bottom: calc(var(--ph-attr-measure) * 18 / 1040);
		font-size: calc(100cqw * 19.5 / 244);
		line-height: calc(100cqw * 28 / 244);
		left: calc(100cqw * 18 / 244);
		bottom: calc(100cqw * 18 / 244);
	}
	.ph-attraction-panel { padding-top: calc(var(--ph-attr-measure) * 146 / 1040); }
}

/* ---------- Location (ui-specs: Location - Default — no banner on this page) ----------
 *
 * Re-measured end to end off the 1440 frame after QA read the band as "off in
 * sizing, colour, assets and spacing". It was all four, and the numbers below
 * are the frame's, not estimates:
 *
 *   band          99 → 993 (894 tall), solid #e6f2f4 to 85.5% then fading out
 *   grid top      251 — so 152 of padding under the 99px header, 236 below
 *   bento tile    237 x 165 with 23 across and 16 down, radius 8 (NOT 14)
 *   middle column lifted 91 (was 94)
 *   stat card     centred, and its LABEL is #48a1b2 — it was --ph-text, which
 *                 is the single most visible colour error on the page
 *   action tile   133.33 x 137 in the 426 column with 13 gutters (was 136/10)
 *   feature card  the same 165 as every other tile — it was 178
 */
/*
 * The tint belongs to the PAGE, not to the hero section.
 *
 * In the frame the band runs 894px from under the header (99 → 993) and holds
 * #e6f2f4 solid to 863 before fading out — and "CONTACT US" sits at 872, i.e.
 * INSIDE the fade. Painting the gradient on .ph-location-hero made the band
 * stop where the hero stops, which pushed Contact Us (and with it the whole
 * transportation section) ~180px down the page and lost the one place the
 * design puts a heading on tinted ground.
 */
.ph-location { background: linear-gradient(#e3f2f4 0 764px, var(--ph-bg) 894px) no-repeat top / 100% 894px; }
/* min-height, because the hero's 708 is a COMPOSITION and the body copy is the
   client's: the frame's placeholder lorem runs six lines and the seeded copy is
   currently empty. Padding-top still pins the grid at 251, so short copy adds
   its slack at the bottom, which is where the design has slack. */
.ph-location-hero { position: relative; padding: 152px 0 48px; min-height: 708px; }
/* Content is flush with the 1312 measure — the extra 20px padding pushed the
   left column and the bento in from the edges the spec aligns them to. */
.ph-loc-hero-inner { display: grid; grid-template-columns: 426px 1fr; gap: 130px; width: 100%; max-width: 1312px; margin: 0 auto; padding: 0; }
.ph-location-hero .eyebrow { font-size: 14px; color: var(--ph-text); margin: 0 0 13px; }
/*
 * letter-spacing: 0, and that — not the size — was the "SINCE 1997 is too wide"
 * half of the QA note. .ph-display letterspaces 0.04em; .ph-section-title
 * already opts out with an explanation, and this h1 carries .ph-display and
 * never did. Measured as INK against the frame: "SINCE 1997" is 188px there,
 * and Bou College at 40px is 187.5 untracked and 201.9 tracked. The same
 * arithmetic on "TRANSPORTATION" (308 in the frame, 307.6 untracked) says the
 * size was never wrong.
 */
.ph-location-hero h1 { font-size: 40px; letter-spacing: 0; color: var(--ph-heading); margin: 0 0 18px; }
.ph-location-hero .body { font-size: 14px; line-height: 20px; }
/* Spec: three gradient tiles filling the hero's 426 left column — not pills by
   the map. A 3-track grid rather than flex+fixed-width, so the tile width is
   derived from the column (426 - 2x13) / 3 = 133.33 instead of guessed. */
.ph-loc-actions { display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 13px; margin-top: 52px; }
.ph-loc-action {
	height: 137px; border-radius: 16px;
	background: linear-gradient(#49b0be, #40848f); color: #fff;
	display: flex; flex-direction: column; align-items: center; justify-content: center; gap: 20px;
	font-size: 14px; font-weight: 700; text-align: center;
	box-shadow: 0 4px 12px rgba(0,0,0,.10);
}
.ph-loc-action:hover { color: #fff; filter: brightness(1.05); }
.ph-loc-action .ico { display: inline-flex; }
.ph-loc-action .ico svg { width: 24px; height: 24px; }
/* Scroll cue: three 20x17 white chevrons, 32 apart, inset 38 from the column
   edge. Decorative only — no link, no text, aria-hidden in the template. */
.ph-loc-scroll { display: flex; flex-direction: column; gap: 15px; margin: 24px 0 0 38px; }
.ph-loc-scroll span { width: 20px; height: 17px; background: #fff; clip-path: polygon(0 0, 100% 0, 50% 100%); }
/* Measured: three 237px columns with 23px gutters, the middle one lifted. */
.ph-loc-bento { display: grid; grid-template-columns: repeat(3, 237px); gap: 23px 23px; align-items: start; justify-content: end; }
.ph-loc-bento .col { display: grid; gap: 16px; }
/* The middle column sits 91px higher — the staggered rhythm in the spec. */
.ph-loc-bento .col--lifted { margin-top: -91px; }
/* Every cell in the bento is the same 237x165 box, photos included. */
.ph-bento-photo { display: block; height: 165px; border-radius: 8px; overflow: hidden; background: #dbe7e9; }
.ph-bento-photo img { width: 100%; height: 100%; object-fit: cover; }
.ph-stat-card {
	background: transparent; border: 2px solid var(--ph-teal-mid); border-radius: 8px;
	height: 165px; padding: 20px;
	display: flex; flex-direction: column; align-items: center; justify-content: center; text-align: center;
}
/* The one filled card in the bento — teal, with the brand mark top-right. Its
   copy is bottom-left, which is why it opts out of the centring above. */
.ph-stat-card--feature { background: var(--ph-teal-mid); border-color: var(--ph-teal-mid); color: #fff; align-items: flex-start; justify-content: flex-end; text-align: left; padding: 22px 26px 18px; position: relative; }
.ph-stat-card--feature p { font-size: 24px; line-height: 32px; margin: 0; }
/* 16/21, not 22/23: absolute offsets resolve against the PADDING box, and this
   card keeps its 2px border (transparent, but still 2px). The frame measures
   22/23 from the border box. */
.ph-stat-card--feature .mark { position: absolute; top: 16px; right: 21px; display: inline-flex; }
.ph-stat-card--feature .mark svg { width: 44px; height: 25px; }
.ph-stat-card strong { font-family: var(--ph-font-display); font-size: 47px; color: var(--ph-teal-mid); line-height: 1.1; }
/* Teal, not --ph-text: sampled at (72,161,178) in the frame, same as the numeral. */
.ph-stat-card span { font-size: 14px; color: var(--ph-teal-mid); margin-top: 4px; }
/* Brand mark at the BAND's bottom-right (194 up from its edge, on the 1312
   measure), not the grid's — the grid's height moves with the client's copy
   and the mark's does not. */
.ph-loc-mark { position: absolute; right: max(20px, calc((100% - 1312px) / 2)); bottom: 8px; display: block; width: 94px; height: 53px; color: var(--ph-teal-mid); }
.ph-loc-mark svg { width: 100%; height: 100%; }
.ph-loc-hours { text-align: center; margin: 40px 0 12px; font-weight: 600; }
.ph-loc-contact { text-align: center; }
.ph-loc-contact p { margin: 4px 0; }
.ph-accordion-bar {
	width: 100%; height: 64px; background: var(--ph-teal-mid); border: 0; border-radius: 10px;
	color: #fff; display: flex; align-items: center; justify-content: space-between;
	padding: 0 24px; margin-bottom: 16px; font-size: 14px; cursor: pointer;
}

/*
 * 901–1343: the same composition, scaled to the measure it actually has.
 *
 * Everything above this block is the 1440 frame's absolutes — a 426 + 130 + 757
 * row whose min-content is 1313px and which shrinks nowhere. Measured on
 * /location/ in all three languages before this block existed, the PAGE scrolled
 * sideways by 412px at 901, 353 at 960, 289 at 1024, 213 at 1100, 133 at 1180,
 * 33 at 1280 and 1 at 1312. And from 1313 to ~1343 there was no overflow but no
 * gutter either: `.ph-loc-hero-inner` carries `padding: 0` on purpose, so once
 * the window was narrower than the 1312 measure the text and the first tile ran
 * flush to the glass.
 *
 * One band, closed at both ends. It starts where the ≤900 stack stops and ends
 * at 1343, because 1344 is the first width at which the frame's own row fits
 * the window as authored (1313 inside 1344, centred by the 1312 max-width) —
 * i.e. exactly where the untouched layout stops overflowing. 1344 and above
 * resolve as they did before: nothing in here applies there, so 1440 and 1920
 * are unchanged BY CONSTRUCTION rather than by re-tuning.
 *
 * Inside the band every length of the composition is restated as its share of
 * --ph-loc-measure, and the 1312 max-width is dropped so the row takes the
 * window with a real gutter instead of centring a measure wider than the
 * window. The seam at 1343/1344 is then a 0.8% step in tile size (235.2 → 237)
 * and 4px of horizontal shift — the difference between this band's 20px gutter
 * and the 15.5px the centred measure happens to leave at 1344.
 */
@media (min-width: 901px) and (max-width: 1343px) {
	/* The frame's row is 1313 wide (426 + 130 + 757). This is what the band has
	   instead: the window less the 20px gutter `.ph-container` and the header
	   take at every width above 900 — measured on the running site at each of
	   the widths listed above, not assumed. */
	.ph-location-hero { --ph-loc-measure: calc(100vw - 40px); }
	/* The two columns as the RATIO they are, so they cannot fail to fit however
	   the measure lands, plus that gutter. `max-width: none` because the 1312
	   measure is the thing that does not fit here: below 1352 it stops centring
	   and just runs the row into the glass. Two classes to outrank the
	   one-class rule above, in the house style of the ≤900 block below. */
	.ph-location-hero .ph-loc-hero-inner {
		grid-template-columns: 426fr 757fr;
		gap: calc(var(--ph-loc-measure) * 130 / 1313);
		max-width: none;
		padding-left: 20px; padding-right: 20px;
	}
	/* Fluid below the frame's tile, never wider than it. `min-width: 0` because
	   a grid item's automatic minimum size is its own content and the stat
	   numerals are the widest content on the page — without it the wrappers
	   push the tracks back out past 237 and the overflow returns.
	   `grid-template-columns: minmax(0, 1fr)` for the same reason one level
	   down, and it is not belt-and-braces: each .col is itself a grid, its
	   single column was implicit and therefore `auto`, and an auto track sizes
	   to its content's minimum no matter how narrow the wrapper is. Measured at
	   901 without it — EN's first tile 160.1 in a 155.4 track, TC's last 174.5,
	   each hanging out of its own column and landing inside the 20px gutter by
	   luck rather than by rule. */
	.ph-loc-bento { grid-template-columns: repeat(3, minmax(0, 237px)); column-gap: calc(var(--ph-loc-measure) * 23 / 1313); }
	.ph-loc-bento .col { min-width: 0; grid-template-columns: minmax(0, 1fr); gap: calc(var(--ph-loc-measure) * 16 / 1313); }
	/* The stagger is a proportion of the tile, not 91 absolute px: a percentage
	   margin on a grid item resolves against its grid area, i.e. the tile
	   width, so 91/237 keeps the lift the frame's lift at every width. */
	.ph-loc-bento .col--lifted { margin-top: -38.4%; }
	/* 237 × 165 stated as the ratio it is. Height goes back to auto so a card
	   whose label wraps grows instead of spilling; the row is align-items:start
	   and stays aligned either way. */
	.ph-bento-photo, .ph-stat-card { height: auto; aspect-ratio: 237 / 165; }
	/*
	 * The stat card and its numeral are the two places this band cannot simply
	 * scale, and they are one problem: the numerals fit the FRAME exactly.
	 * "10K SQFT" sets 191.2 and 1萬平方呎 / 1万平方呎 set 193.0 inside an inner
	 * box of 193. Two things then refuse to shrink with everything else — the
	 * card's 2px border, which is a brand line and stays 2px — and the glyphs
	 * themselves, whose advances are not quite linear in the font size (the
	 * five-character Chinese numeral measures ~3% wider per point at 29px than
	 * at 47px). Scaled straight, the Chinese numeral wraps to two lines below
	 * ~1310, which breaks the tile's 237:165 and drops its column out of the
	 * stagger.
	 *
	 * So the inset is cut to a 12 share and the numeral is set at 45 rather
	 * than 47. The inset costs nothing visible — the card centres its content,
	 * so the padding only ever acts as a floor — and the pair leaves the widest
	 * numeral 5.7px of clearance at 901 and 11.1px at 1343 (TC/SC; EN has 15.3
	 * and 25.6), measured, in every card. At 47 with the same inset the Chinese
	 * numeral lands on 135.3 in a 135.3 box at 901, i.e. back to wrapping.
	 *
	 * The 14px label below is deliberately left alone and allowed to wrap: 9px
	 * type is the alternative, and the card's height is auto here so a wrapped
	 * label grows the card instead of spilling out of it.
	 */
	.ph-stat-card { padding: calc(var(--ph-loc-measure) * 12 / 1313); }
	/* Restated because the rule above it is one class too and now comes later:
	   the feature card's own padding, and the mark it hangs in its corner. */
	.ph-stat-card--feature { padding: calc(var(--ph-loc-measure) * 22 / 1313) calc(var(--ph-loc-measure) * 26 / 1313) calc(var(--ph-loc-measure) * 18 / 1313); }
	.ph-stat-card--feature p { font-size: calc(var(--ph-loc-measure) * 24 / 1313); line-height: calc(var(--ph-loc-measure) * 32 / 1313); }
	.ph-stat-card--feature .mark { top: calc(var(--ph-loc-measure) * 16 / 1313); right: calc(var(--ph-loc-measure) * 21 / 1313); }
	.ph-stat-card--feature .mark svg { width: calc(var(--ph-loc-measure) * 44 / 1313); height: calc(var(--ph-loc-measure) * 25 / 1313); }
	/* 45, not the frame's 47 — the other half of the note on .ph-stat-card
	   above. It lands 2.3px under the frame's size at the top of the band. */
	.ph-stat-card strong { font-size: calc(var(--ph-loc-measure) * 45 / 1313); }
	/* The action tiles are part of the same composition — the 3-track grid
	   already narrows them with the column, so the height and the inner gap
	   follow, or they turn into slabs. */
	.ph-loc-action { height: calc(var(--ph-loc-measure) * 137 / 1313); gap: calc(var(--ph-loc-measure) * 20 / 1313); }
}

@media (max-width: 900px) {
	/* The desktop band is 894px of deliberate whitespace around a 1312 grid;
	   none of that survives one column, so the padding goes back to normal and
	   the tint stops being a fixed-height slab. */
	.ph-location { background: linear-gradient(#e3f2f4 0 60%, var(--ph-bg) 100%) no-repeat top / 100% 520px; }
	.ph-location-hero { padding: 40px 0 60px; min-height: 0; }
	/*
	 * The 16px gutter. Mobile — Location - Default.pdf puts the eyebrow, the
	 * h1, the body copy and the first action tile all at x16 on the 390 frame,
	 * and the last tile's right edge at 374. `.ph-loc-hero-inner` is not a
	 * .ph-container — its `padding: 0` is right for the desktop band, where the
	 * 1312 measure centres itself — so once the band is narrower than that
	 * measure the whole block ran edge to edge: text touching the glass, and
	 * the first stat card's left border cut off by the screen. Two classes, so
	 * it outranks the one-class desktop rule wherever this block ends up.
	 */
	.ph-location-hero .ph-loc-hero-inner { grid-template-columns: 1fr; gap: 34px; padding-left: 16px; padding-right: 16px; }
	.ph-loc-bento { grid-template-columns: repeat(2, minmax(0, 1fr)); justify-content: stretch; }
	/* The stagger is a 1312-wide composition; stacked it just knocks the second
	   column out of alignment with the first. */
	.ph-loc-bento .col--lifted { margin-top: 0; }
	.ph-loc-mark { display: none; }
	.ph-loc-scroll { display: none; }
	.ph-attraction-grid { grid-template-columns: repeat(2, 1fr); margin-bottom: 24px; }
	.ph-attraction-panel { grid-template-columns: 1fr; padding: 26px; }
	.ph-attraction-panel > div + div { border-left: 0; padding-left: 0; margin-top: 24px; }
	.ph-attractions-map .ph-map-embed { min-height: 420px; }
}

/*
 * Phone only (QA 40): the bento becomes ONE horizontally scrolling row.
 *
 * Two-up, the seven tiles run the About Us band 896px tall on a 390 screen —
 * most of a viewport of stats standing between the heading and everything
 * below it. A row puts the whole set one thumb-swipe away and gives the band
 * back its 165px.
 *
 * 561–900 is untouched on purpose: the 2-column grid above is the tablet
 * answer and the client signed it off. This block is additive and starts below
 * it, so nothing desktop or tablet resolves differently than it did.
 */
@media (max-width: 560px) {
	/*
	 * `display: contents` on the three .col wrappers instead of a markup
	 * change. The columns are a 1312-wide composition — a stagger — and mean
	 * nothing in a row; flattening them lets the seven tiles BE the flex line,
	 * in the order the template authors them, with the DOM and the reading
	 * order untouched. The visual order that falls out is therefore:
	 * stat / photo / feature / photo / stat / stat / photo.
	 *
	 * justify-content is restated because the desktop rule sets `end`, and an
	 * overflowing flex row packed to the end starts at negative scroll space
	 * the user cannot reach.
	 */
	.ph-loc-bento {
		display: flex;
		flex-wrap: nowrap;
		justify-content: flex-start;
		align-items: flex-start;
		overflow-x: auto;
		overflow-y: hidden;
		scroll-snap-type: x mandatory;
		overscroll-behavior-x: contain;
		-webkit-overflow-scrolling: touch;
	}
	.ph-loc-bento .col { display: contents; }
	/*
	 * The tiles keep their designed 237x165 rather than shrinking to fit, which
	 * is the whole trick: 237 + the 23 gutter is 260, so a 390 screen shows one
	 * whole tile and a 130px slice of the next (100px at 360). That peek IS the
	 * affordance — full-width tiles would read as one static card and nobody
	 * would swipe. Hence no scrollbar cosmetics either: the cut-off tile says
	 * "more", and the page's other scroller (.ph-mtr-diagram) leaves the
	 * scrollbar alone too.
	 */
	.ph-loc-bento > .col > * { flex: 0 0 237px; scroll-snap-align: start; }
	/*
	 * Full bleed over the 16px gutter the ≤900 block gives the band. The row is
	 * pulled back out to the screen edges and the gutter is put back INSIDE it,
	 * so tiles slide under the glass instead of being clipped 16px short of it,
	 * the first tile still starts on the text measure (x16, with the h1), and
	 * the last one comes to rest at 374 — the same inset on the right. The
	 * scroll-padding is what keeps snap points on that measure rather than on
	 * the box edge. The overflow stays inside this box: the PAGE gains no
	 * horizontal scroll.
	 */
	.ph-location-hero .ph-loc-bento {
		margin-left: -16px; margin-right: -16px;
		padding-left: 16px; padding-right: 16px;
		scroll-padding-left: 16px; scroll-padding-right: 16px;
	}
	/*
	 * Keyboard reach, and why the template gets no tabindex.
	 *
	 * Nothing inside the bento is focusable — three plain stat cards, one
	 * statement card, three decorative photos with empty alt — so a scrolling
	 * row would normally be unreachable. Chrome makes a scroll container
	 * keyboard-focusable by itself (measured: focusable at 390, NOT at 1440,
	 * so it costs desktop nothing) and Firefox does the same; this is the
	 * focus ring for that, in the house style of a.ph-showtime.
	 *
	 * A tabindex="0" would have covered Safari too, which still does not do
	 * this — but it applies at EVERY width, so it buys Safari a scroll at the
	 * price of a dead tab stop, and a UA focus ring, on the desktop layout
	 * this ticket is not allowed to touch. It is not worth it here because no
	 * FIGURE in the row is unique to the row: the paragraphs immediately above
	 * it state 290 shops, 500 car park spaces and 10,000 sq ft in all three
	 * languages. The statement card ("One of the largest mall…") does appear
	 * nowhere else, but it is not lost either — every engine reads all seven
	 * tiles' text out of the a11y tree whatever the scroll position
	 * (display:contents on a semantically empty div takes nothing with it),
	 * and a screen reader scrolls to what it focuses. Revisit if a tile ever
	 * gains a link.
	 *
	 * The ring is drawn INSIDE the box: the row is full bleed, so an outset
	 * ring would sit off-screen on both sides.
	 */
	.ph-loc-bento:focus-visible { outline: 2px solid var(--ph-teal); outline-offset: -2px; }
}

/* ---------- Floorplan (ui-specs: Floorplan - Default) ---------- */
.ph-floorplan .ph-container { position: relative; }
.ph-map-stage { position: relative; padding: 0 60px; }
.ph-floorplan .ph-map-embed { background: transparent; border-radius: 0; min-height: 528px; }
/* Spec: a vertical rail at the shell's left edge — gold steppers around a
   large ghosted level label, not a row of chips. */
/* 24px gutters, not 37. Measured in Floorplan - Default.pdf: the two gold
   steppers are 48x48 at x63, tops y810 and y1000 — centres exactly 190px apart
   over a 238px rail. 48 + 24 + the 94px ghost label + 24 + 48 is 238 on the
   nose; at 37 the rail ran 264 and pushed the centres to 216. */
.ph-floor-rail { position: absolute; left: 0; top: 50%; transform: translateY(-50%); display: flex; flex-direction: column; align-items: center; gap: 24px; z-index: 2; }
.ph-floor-step { width: 48px; height: 48px; border: 0; border-radius: 8px; background: var(--ph-gold); color: #fff; font-size: 20px; line-height: 1; cursor: pointer; }
.ph-floor-level { font-family: var(--ph-font-display); font-size: 94px; line-height: 1; color: #dbd6cd; }
.ph-map-tools { position: absolute; right: 0; bottom: 24px; display: flex; flex-direction: column; gap: 8px; z-index: 2; }
.ph-map-tools button { width: 42px; height: 42px; border: 0; border-radius: 50%; background: var(--ph-teal-deep); color: #fff; font-size: 16px; cursor: pointer; }
/* The SDK mounts Mapbox's own zoom/compass control, which sat top-right as a
   second, differently-styled set of the buttons the design already specifies
   on the right edge. Ours are wired to the same map. */
.ph-map-stage .mapboxgl-ctrl-top-right,
.ph-map-stage .mapboxgl-ctrl-bottom-right { display: none; }

/* ---------- Transportation (ui-specs: Location - Default + Location - Expanded) ----------
 *
 * The white card carries the title, the MTR exit line and the transit diagram
 * — there is NO sub-line under "TRANSPORTATION" in the frame; the exit line
 * says the same thing and says it with the station's own mark. The card is
 * 1090 x 600 with a 16px radius, and the bus banner and both accordion bars
 * follow it at 16px intervals.
 */
.ph-transport-card { background: #fff; border-radius: 16px; padding: 48px 0 0; margin-bottom: 16px; overflow: hidden; }
.ph-mtr-exit {
	display: flex; align-items: center; justify-content: center; gap: 17px;
	/* 46, not the 36 the gap measures: this margin COLLAPSES with the section
	   title's own 10px margin-bottom, so the two together are max(10, 46). */
	/* #000, sampled — this one line really is black, not --ph-text. */
	margin: 46px 0 0; font-size: 14px; font-weight: 700; color: #000;
}
.ph-mtr-exit .mark { width: 52px; height: 42px; flex: none; }
/* The diagram is drawn at 1090 wide and scales with the card. */
.ph-mtr-diagram { margin-top: 21px; }
.ph-mtr-diagram svg { display: block; width: 100%; height: auto; }
.ph-mtr-diagram text { font-family: var(--ph-font-body); }
/* Frame: 1090 x 276 — a 3.95 crop of a much squarer source, so it is cropped
   rather than squashed, and the ratio (not a pixel height) survives mobile. */
.ph-transport-photo { border-radius: 8px; overflow: hidden; margin: 0 0 16px; }
/* 39%, not centre: the strip keeps only ~38% of a 3:2 source's height, and the
   fallback's bus rides above the centre line (roof 24%, wheels 63%) — centred,
   it loses its roof. A CMS photo with a centred subject moves by a few px. */
.ph-transport-photo img { width: 100%; aspect-ratio: 395 / 100; object-fit: cover; object-position: center 39%; }
/* The bar is a button inside a heading, so the heading contributes nothing. */
.ph-accordion-head { margin: 0; }
.ph-accordion-bar { font-weight: 700; padding-left: 25px; padding-right: 24px; }
.ph-accordion-bar[aria-expanded="true"] { border-radius: 10px 10px 0 0; margin-bottom: 0; }
.ph-accordion-bar .chev { display: inline-flex; width: 24px; height: 24px; color: #fff; }
.ph-accordion-bar .chev svg { width: 100%; height: 100%; transition: transform .18s ease; }
/* One glyph, flipped — an expanded panel points its chevron back at its bar. */
.ph-accordion-bar[aria-expanded="true"] .chev svg { transform: rotate(180deg); }
.ph-accordion-panel { background: #fff; border-radius: 0 0 10px 10px; padding: 15px 24px 12px; margin-bottom: 16px; }
/*
 * table-layout: fixed with measured column shares.
 *
 * Auto layout sizes columns off the longest cell, which means EN, TC and SC
 * each land on different column positions and the two halves of the split
 * panel stop lining up with each other. The frame's shares are 14/46/40 for a
 * half-width table and 16/26/58 for a full-width one — the GMB panel's names
 * are short, so its columns sit much closer together.
 */
/*
 * 14px, and it is not a downgrade from 16 — 16 was never measured.
 *
 * Sizes here were read as INK WIDTHS off Location - Expanded.pdf and matched
 * against Inter's own metrics, which is the only way to tell 14 from 16 on an
 * antialiased render (a cap-height read is ±2px and 2px is the whole
 * difference): "MTR Diamond Hill - Exit C1 & C2" is 215px in the frame and
 * 213.0 at 14px / 242.1 at 16px; "Reach Plaza Hollywood by Bus" is 206 and
 * 207.3 at 14px. At 16px two Arrival cells also wrapped, which is what put
 * 38px rows in a table the frame draws at a flat 36.
 */
.ph-bus-table { width: 100%; border-collapse: collapse; table-layout: fixed; }
.ph-bus-table th { color: var(--ph-teal-mid); font-weight: 700; font-size: 14px; text-align: left; border-bottom: 2px solid #9bdde5; padding-bottom: 12px; }
.ph-bus-table td { font-size: 14px; color: var(--ph-text); height: 36px; }
.ph-bus-table th:nth-child(1) { width: 16%; }
.ph-bus-table th:nth-child(2) { width: 26%; }
.ph-bus-table--half th:nth-child(1) { width: 14%; }
.ph-bus-table--half th:nth-child(2) { width: 46%; }
/* Spec: the first panel splits into two tables with a hairline between. */
.ph-bus-split { display: grid; grid-template-columns: 1fr 2px 1fr; column-gap: 23px; }
.ph-bus-split .divider { background: #9bdde5; }
/* Bento: the middle column leads with a solid teal statement card. */
.ph-stat-card--feature { background: var(--ph-teal-mid); border-color: transparent; color: #fff; }
.ph-stat-card--feature strong, .ph-stat-card--feature span { color: #fff; }

@media (max-width: 900px) {
	.ph-transport-card { padding: 32px 0 0; }
	.ph-mtr-exit { gap: 12px; font-size: 15px; }
	/*
	 * The diagram scrolls rather than scaling.
	 *
	 * At 390 the full 1090 width puts the station labels at 5px — legible to
	 * nobody. Scrolling inside its own box keeps them at 14px and keeps the
	 * PAGE from scrolling sideways, which is the failure this replaces.
	 */
	.ph-mtr-diagram { overflow-x: auto; }
	.ph-mtr-diagram svg { min-width: 760px; }
	/* One column of routes; the hairline has nothing left to separate. */
	.ph-bus-split { grid-template-columns: 1fr; }
	.ph-bus-split .divider { display: none; }
	.ph-accordion-bar { height: auto; min-height: 64px; padding: 14px 16px 14px 18px; text-align: left; gap: 14px; }
	.ph-accordion-panel { padding: 15px 16px 12px; }
}

/* ---------- Mobile, measured from ui-specs/Mobile (390px frames) ---------- */
@media (max-width: 900px) {
	.ph-hero { margin: 0 16px; min-height: 190px; border-radius: var(--ph-radius); }
	.ph-hero-vic { padding: 24px 16px; border-radius: var(--ph-radius); }
	.ph-hero-vic h3 { font-size: 26px; }

	/*
	 * Mobile keeps the desktop alignment — it does NOT centre everything.
	 * Home's "Promotion & Exciting Deals" sits at x15 in the 390 frame, and
	 * What's On's "In The Spotlight" at x16; centring them was this rule's
	 * doing. Pages whose titles are centred on desktop already carry
	 * .ph-section-title--center and stay centred here.
	 */
	.ph-section-title { font-size: 34px; }

	/*
	 * App strip stacks on mobile: a 122px tile above two 153x57 badges side by
	 * side, then the message — 272px tall in the 390 frame. The desktop row
	 * squeezed the badges to 34px wide once flex had no room for them.
	 */
	.ph-app-strip .ph-container {
		flex-direction: column; flex-wrap: wrap; height: auto; min-height: 272px;
		justify-content: center; gap: 14px; padding: 0 16px;
	}
	/* The strip is a COLUMN here, so the cross axis is horizontal: the
	   desktop's `align-self: flex-start` (which exists only to make the -45px
	   overhang absolute) would jam the tile against the left gutter. Nothing
	   overhangs on mobile — the spec stacks the tile inside the band. */
	.ph-app-icon { height: 122px; align-self: center; margin-top: 0; }
	.ph-app-strip .ph-stores { display: flex; gap: 17px; }
	.ph-store-badge { flex: none; }
	.ph-app-strip .msg { margin-left: 0; text-align: center; font-size: 16px; }

	/* Spotlight stacks image-first, with the carousel arrows beneath it. */
	.ph-spotlight-inner { grid-template-columns: 1fr; gap: 18px; min-height: 0; }
	.ph-spotlight .media { order: 1; }
	.ph-spotlight .text { order: 2; display: flex; flex-direction: column; }
	.ph-spotlight-arrows { order: -1; margin: 0 0 18px; }
	.ph-spotlight h2 { font-size: 30px; }

	/* One event card per row (357px at 390 = full width less 16px margins). */
	.ph-event-grid { grid-template-columns: 1fr; gap: 16px; }

	/* Promo cards stack: media above the copy. */
	.ph-promo-card, .ph-promo-card:nth-child(even) { grid-template-columns: 1fr; gap: 18px; }
	.ph-promo-card .media, .ph-promo-card:nth-child(even) .media { order: -1; }

	/* Movies: the six-up desktop grid is far too tight at this width. */
	/* Spec: posters run edge to edge, two up, with a hairline gap. */
	.ph-movie-grid { grid-template-columns: repeat(2, 1fr); gap: 4px; padding: 24px 0; }
	.ph-movie-grid, .ph-movies .ph-container { padding-left: 0; padding-right: 0; }

	/* Floorplan rail sits inline above the map rather than beside it. */
	.ph-map-stage { padding: 0; }
	.ph-floor-rail { position: static; transform: none; flex-direction: row; justify-content: center; gap: 18px; margin-bottom: 12px; }
	.ph-floor-level { font-size: 48px; }
	.ph-map-tools { right: 12px; bottom: 12px; }

	/* VIC + location blocks fall to a single column. */
	.ph-vic-benefits { grid-template-columns: 1fr 1fr; }
	.ph-vic-privileges { grid-template-columns: 1fr; min-height: 0; }
	.ph-vic-privileges .panel { padding: 26px; }
	.ph-rate-cards { grid-template-columns: 1fr; }
	.ph-download-grid { grid-template-columns: 1fr; }
	.ph-ig-grid { grid-template-columns: 1fr 1fr; }
	.ph-social-band::before { display: none; }
}

@media (max-width: 560px) {
	.ph-vic-benefits { grid-template-columns: 1fr; }
	.ph-movie-grid { grid-template-columns: 1fr 1fr; }
	/*
	 * The card cannot sit to the RIGHT of the fourth circle on a phone — it
	 * would run off a 375 viewport — so it drops under the row, anchored by its
	 * right edge so it grows leftwards into the space that exists.
	 *
	 * One line does not fit either: laid out in a row the card measures 241px
	 * and still hangs 25px off the left edge, where nothing scrolls it back into
	 * view. So label and ID stack, which is exactly what the old site did at its
	 * own narrow breakpoints (custom.css @media 460px / 380px).
	 */
	.ph-social-card {
		left: auto; right: 0; top: calc(100% + 8px);
		flex-direction: column; align-items: flex-start; gap: 0;
	}
}

/* Floorplan: centred sub-line, and stepper glyphs sized to the spec. */
.ph-section-sub--center { text-align: center; }
.ph-floor-step { display: flex; align-items: center; justify-content: center; }
.ph-floor-step svg { width: 22px; height: 22px; }
.ph-floor-step[disabled] { opacity: .35; cursor: default; }
/* Same treatment for the tool cluster, so an unconfigured map does not present
   three live-looking controls beside a "not configured" message. */
.ph-map-tools button[disabled] { opacity: .35; cursor: default; }
/* A shop page shows one unit, so it carries no level rail — reclaim the inset. */
.ph-map-stage--plain { padding: 0; }

@media (max-width: 900px) {
	.ph-venue-intro { grid-template-columns: 1fr; gap: 18px; }
	.ph-venue-row, .ph-venue-row.is-reversed { grid-template-columns: 1fr; }
	.ph-venue-row.is-reversed .photo { order: 1; }
	.ph-venue-row.is-reversed .detail { order: 2; }
	.ph-venue-row.is-reversed .floorplan { order: 3; }
	.ph-venue-row .photo { height: 220px; }
	.ph-download-grid { grid-template-columns: 1fr; }
}

/* Floorplan POI popup — the map's only route into the rest of the site.
   Typography follows the client-approved card (Eddie's ruling, 26 Aug 2026):
   white rounded card, shop name in teal, the shop number in muted grey, and
   "View Details" as black UNDERLINED text — the underline is what marks it as
   the link, since it is no longer carrying the teal that used to do that job. */
.ph-poi h3 { margin: 0 0 6px; font-size: 17px; line-height: 22px; color: var(--ph-teal-mid); text-transform: none; }
.ph-poi p { margin: 0 0 3px; font-size: 13px; line-height: 18px; color: var(--ph-muted); }
.ph-poi .ph-poi-link { display: inline-block; margin-top: 8px; font-size: 13px; font-weight: 600; color: var(--ph-text); text-decoration: underline; text-underline-offset: 2px; }
/* Scoped to the map stage to OUT-SPECIFY mapbox-gl.css, which is linked from
   parts/floorplan-map.php in the body and therefore lands after this file: a
   bare `.mapboxgl-popup-content` here ties on specificity and loses on order,
   so the card had silently kept the vendor's 3px radius and 10px/15px padding
   the whole time. Measured live, 26 Aug 2026. The approved card is a rounded
   white panel, so the radius is the part that has to win. */
.ph-map-stage .mapboxgl-popup-content { border-radius: 12px; padding: 14px 16px; background: var(--ph-card); box-shadow: 0 4px 18px rgba(0,0,0,.14); }

/* ---------- About Us fact list ---------- */
/*
 * The About Us copy was recovered from the legacy site's database dump, where
 * the contact block was a run of <p class="mb-35"> with an icon class on a
 * leading <span>. Rebuilt here as a definition-style list so the label/value
 * pairs line up and stay readable when a value wraps — which the Chinese
 * labels do at narrow widths, being longer than their English equivalents.
 */
.ph-about-facts { list-style: none; margin: 32px 0 0; padding: 0; }
.ph-about-facts .ph-fact {
	display: grid;
	grid-template-columns: minmax(140px, max-content) 1fr;
	gap: 4px 18px;
	padding: 12px 0;
	border-bottom: 1px solid rgba(2, 185, 198, .22); /* --ph-teal, P3->sRGB corrected */
}
.ph-about-facts .ph-fact:last-child { border-bottom: 0; }
.ph-about-facts .k { font-weight: 600; color: var(--ph-heading); }
.ph-about-facts .v { color: var(--ph-text); }
.ph-about-facts .v a { color: var(--ph-teal-mid); word-break: break-word; }
.ph-about-facts .v a:hover { color: var(--ph-teal-deep); text-decoration: underline; }

@media (max-width: 640px) {
	/* Label above value — two columns cannot hold a long CJK label plus an
	   email address on a phone without one of them overflowing. */
	.ph-about-facts .ph-fact { grid-template-columns: 1fr; gap: 2px; }
}

/* ==========================================================================
   Skip link (WCAG 2.4.1 "Bypass Blocks")
   ========================================================================== */

/*
 * Off screen until focused, NOT display:none / visibility:hidden — either of
 * those removes the anchor from the tab order, so the one user it exists for
 * can never reach it. Moving it with `left` (rather than clipping it to a 1px
 * box) keeps it a real, measurable element, which is what lets it simply slide
 * back into place on :focus.
 *
 * z-index sits above the sticky header: the link paints where the header
 * already is, and losing that stacking fight would make a "visible on focus"
 * control invisible on focus — the failure mode this rule exists to prevent.
 *
 * The visible state is styled to be legible on its own rather than to blend in:
 * it appears for a fraction of a second and has to be readable in that time.
 */
.ph-skip-link {
	/* fixed, not absolute: the header is sticky, so a visitor can be scrolled
	   well down the page when they first press Tab. Absolute would place the
	   link at the top of the DOCUMENT — off screen, focused, and unreachable. */
	position: fixed;
	top: 8px;
	left: -9999px;
	z-index: 1000;
	padding: 12px 20px;
	border-radius: 6px;
	background: var(--ph-teal-deep, #00636e);
	color: #fff;
	font-size: 16px;
	font-weight: 600;
	line-height: 1.2;
	text-decoration: none;
	white-space: nowrap;
}

.ph-skip-link:focus {
	left: 8px;
	/* Its own ring — the link lands on a dark fill, and the UA default outline
	   is the same kind of dark on most platforms. */
	outline: 3px solid var(--ph-gold, #fcae18);
	outline-offset: 2px;
	color: #fff;
}

/* The jump target must not land under the sticky header, or "skip to content"
   scrolls to content the visitor cannot see. 110px clears .ph-header-inner's
   99px min-height with a little air. */
#main-content { scroll-margin-top: 110px; }

/* ---------- Instagram section: Smash Balloon restyle (26 Aug 2026) ----------
 * The plugin ships its own grid markup (#sbi_images > .sbi_item). Scoped under
 * .ph-ig-grid--sbi, these rules make it render as the approved 4-tile row —
 * same geometry as our native .ph-ig-tile — instead of the plugin's default
 * look. If the plugin is absent or unconnected the template renders our own
 * tiles and none of this applies. */
/* The plugin owns its inner grid; its root must span the whole section. */
.ph-ig-grid--sbi { display: block; }
.ph-ig-grid--sbi #sb_instagram { padding: 0 !important; width: 100% !important; }
.ph-ig-grid--sbi #sb_instagram #sbi_images {
	display: grid !important; grid-template-columns: repeat(4, 1fr);
	gap: 20px; padding: 0 !important; float: none;
}
.ph-ig-grid--sbi #sb_instagram .sbi_item {
	float: none !important; width: auto !important; padding: 0 !important; margin: 0 !important;
}
.ph-ig-grid--sbi #sb_instagram .sbi_photo_wrap,
.ph-ig-grid--sbi #sb_instagram .sbi_photo {
	display: block; border-radius: var(--ph-radius); overflow: hidden;
}
.ph-ig-grid--sbi #sb_instagram .sbi_photo { width: 100% !important; height: auto !important; aspect-ratio: 1 / 1; }
.ph-ig-grid--sbi #sb_instagram .sbi_photo img { width: 100%; height: 100%; object-fit: cover; }
@media (max-width: 767px) {
	.ph-ig-grid--sbi #sb_instagram #sbi_images { grid-template-columns: repeat(2, 1fr); gap: 16px; }
	.ph-ig-grid--sbi #sb_instagram .sbi_header_text h3 { color: #226c7a !important; }
}

/* ---------- What's On detail (ui-specs: What_s On - Details, desktop + mobile)
 *
 * Measured 1:1 off the 1440px frame. Everything sits on ONE column between
 * x64 and x1376:
 *
 *   back link      y99–146   48x48 tile, #766e5c, 18px gap, label 14px/600
 *                            — that is `.ph-back` already, reused verbatim
 *   image          y169–900  x64–1376, ~14px corner radius
 *   title          ink y928–945 / 957–974   Inter 24px, 29px line, #48a1b2
 *   date range     ink y927–939, right edge x1376   Inter 14px bold, #333
 *   body copy      lines at y1025/1045/…    Inter 15px, 20px line, #333
 *
 * Sizes were fitted rather than guessed: "Event Name Title Line 1" is 264px of
 * ink in the frame, and Inter renders it at 265px at 24px — 30px (the old
 * `.ph-detail h1`) would have been 330px. "DD/MM/YYYY - DD/MM/YYYY" is 202px of
 * ink against Inter's 205px at 14px. Body x-height measures 8px, which is 15px
 * Inter. Every ink colour sampled off the frame is already a token: #48a1b2 is
 * --ph-teal-mid, #333 is --ph-text, #766e5c is --ph-muted.
 *
 * NOT the shared `.ph-detail` grid — that is the two-column layout this page
 * was built on and is exactly what the QA note replaces.
 * ---------------------------------------------------------------------------- */

/* 1312px, the BANNER measure, not the 1090px content measure. The detail frame
   really does run its copy to the banner edge — body text ends at x1369/1374
   against the image's x1375 — so title, dates and description align with the
   artwork rather than insetting from it. Same override the shell uses. */
.ph-event-detail .ph-container { max-width: var(--ph-maxw); }
.ph-event-detail { padding: 30px 0 90px; }

/* The poster at its own aspect ratio: width fills the measure, height follows.
   No aspect-ratio box and no object-fit — both would crop, and not cropping is
   the entire point of the change. A short landscape banner (the fallback when a
   record has no ph_poster_id) is just as un-cropped here as a 2:3 poster. */
.ph-event-detail .poster { margin: 0; border-radius: var(--ph-radius); overflow: hidden; background: #dbe7e9; }
.ph-event-detail .poster img { display: block; width: 100%; height: auto; }

.ph-event-detail-head {
	display: flex; flex-wrap: wrap; align-items: baseline; justify-content: space-between;
	gap: 8px 32px; margin: 24px 0 0;
}
.ph-event-detail h1 {
	font-family: var(--ph-font-body); font-weight: 700; font-size: 24px; line-height: 29px;
	color: var(--ph-teal-mid); text-transform: none; letter-spacing: 0; margin: 0;
	/* Wraps to the frame's two lines and lets the date keep its own edge. */
	flex: 1 1 320px; min-width: 0;
}
/* `white-space: nowrap` because the range is one atomic fact — "13/07/2026 -"
   above "13/09/2026" reads as two dates. It is 202px wide at most, so it costs
   the title nothing until the row wraps entirely, which is the mobile case. */
.ph-event-detail .dates { margin: 0; font-size: 14px; font-weight: 700; color: var(--ph-text); white-space: nowrap; }

.ph-event-venue { display: flex; align-items: center; gap: 8px; margin: 12px 0 0; font-size: 14px; color: var(--ph-muted); }
.ph-event-venue svg { width: 18px; height: 18px; flex: none; }

.ph-event-body { margin-top: 40px; font-size: 15px; line-height: 20px; color: var(--ph-text); }
/* 20px between paragraphs — in the frame the second block starts 40px below the
   last line of the first, which is exactly two 20px line slots. */
.ph-event-body > :first-child { margin-top: 0; }
.ph-event-body p { margin: 0 0 20px; }
.ph-event-body > :last-child { margin-bottom: 0; }
.ph-event-body img { max-width: 100%; height: auto; }
/* D365 descriptions arrive as pasted HTML and have shipped bare <table> markup
   before now; contain it rather than letting it widen the page. */
.ph-event-body table { max-width: 100%; display: block; overflow-x: auto; }
.ph-event-cta { margin: 32px 0 0; }

/* Mobile — What_s On - Details.pdf: same type sizes throughout (title ink is
   the same 265px at 24px, date the same 202px at 14px), single column, and the
   date drops onto its own line under the title, left-aligned. The flex row
   above wraps into exactly that, so this only sets the gap the frame shows
   (title baseline y373 to date ink top y391) and stops the date being pushed
   to the right edge by space-between on a wrapped row. */
@media (max-width: 640px) {
	.ph-event-detail { padding: 20px 0 56px; }
	.ph-event-detail-head { display: block; margin-top: 18px; }
	.ph-event-detail .dates { margin-top: 14px; }
	.ph-event-body { margin-top: 28px; }
}

/* ==========================================================================
   APPENDED BLOCK — Explore grid + Movies venue block + Movies "New Release"
   row. Written as a self-contained region so it can be reviewed (and reverted)
   independently of the chrome/typography work happening elsewhere in this file.
   Every number is measured off the spec PDFs at their native page size.
   ========================================================================== */

/* ---------- Home "Explore Plaza Hollywood" (Desktop/Home.pdf) ---------- */
/*
 * ⚠ CLIENT-OWED ASSET — the sky plate.
 *
 * The frame runs a photographic cloud band the full 1440 behind this whole
 * section. We do not hold it, and a stand-in sky would be an invented asset in
 * an approved design, so the slot is declared and left empty: set
 * --ph-explore-sky to url('../img/<file>') and the plate is in. `none` is a
 * legal <image> value here, so the shorthand stays valid and paints nothing.
 */
.ph-explore--sky {
	--ph-explore-sky: none;
	background: var(--ph-explore-sky) center / cover no-repeat;
}
/*
 * The pill: 866x64 in the frame (border box x287–1153, y172–235, centred on the
 * page axis at x720), against the 620x45 it was built at. Height, border weight
 * and the centred 15px placeholder are the listing pill's — the two are the
 * same control — but the radius stays the base 999px, because THIS one is drawn
 * as a true pill where the listing frame squares off at r14.
 *
 * The submit button is taken out of flow so the placeholder sits on the pill's
 * own centre line, as drawn, rather than on the centre of the space left over
 * beside the button. (The frame shows no magnifier at all; the control is kept
 * because removing the only visible submit affordance is a usability
 * regression, not a design fix.)
 */
.ph-explore .ph-searchbar {
	position: relative;
	max-width: 866px;
	height: 64px;
	border: 1px solid var(--ph-teal-mid);
	box-shadow: none;
	margin: 0 auto 73px; /* frame: pill bottom y235 -> grid top y308 */
}
.ph-explore .ph-searchbar input {
	height: 62px; padding: 0 56px; text-align: center;
	font-size: 15px; color: var(--ph-muted); background: transparent;
}
.ph-explore .ph-searchbar input::placeholder { color: #aaced3; }
.ph-explore .ph-searchbar button { position: absolute; right: 0; top: 0; height: 100%; }

/*
 * Grid geometry, measured off Home.pdf at 1:1:
 *   columns  x178–548 / x565–936 / x955–1267  ->  370 | 371 | 313, 18px gutters
 *   rows     y308–535 / y556–779              ->  227 | 224, 21px gutter
 *   block    1090 x 472 on the standard content measure
 * 370+371+313 = 1054 = 1090 - 2x18, so `fr` units reproduce the drawn widths
 * exactly at full measure and degrade proportionally below it.
 *
 * (The scan brief quoted "Getting Here ~769 wide". Measured, the tile is 758 —
 * which is what spanning the two left columns produces. Built to the columns,
 * because a 769 tile would not line up with the Nearby tile above it.)
 */
.ph-explore-grid {
	grid-template-columns: 370fr 371fr 313fr;
	grid-template-rows: 227px 224px;
	column-gap: 18px;
	row-gap: 21px;
}
/*
 * teal-deep, not #ddd. It is what the frame paints the Directory card, and for
 * the three photo tiles it is the colour that shows if an image fails — white
 * labels on #ddd was the illegibility this section was flagged for.
 */
.ph-explore-grid a { display: block; background: var(--ph-teal-deep); }
.ph-explore-grid img { display: block; }
/*
 * Legibility scrim. The labels are white and the photographs are client-
 * replaceable, so the contrast cannot depend on which photo is in the slot —
 * the gradient guarantees it for any of them. That now includes Directory
 * (`.tall` — the four destinations are frozen IA, [B-PH-16]): it used to be
 * exempt because the frame paints that card flat teal and a gradient over a
 * flat card reads as a printing fault, but since 18 Sep it carries a
 * photograph like its siblings — a bright, pale-floored one, which is exactly
 * the case the scrim is for.
 */
.ph-explore-grid a::after {
	content: ""; position: absolute; inset: 0; z-index: 1;
	background: linear-gradient(to top, rgba(0,0,0,.68) 0, rgba(0,0,0,.34) 38%, rgba(0,0,0,0) 68%);
}
/*
 * The scrim is tuned for a 224px tile; on the 472px Directory card the same
 * percentages would darken 320px of photograph to protect 96px of type. Pin
 * the ramp to the label's own height instead. Only where the card IS tall:
 * between 561 and 900 it is a 224px cell like the rest and takes their ramp.
 */
@media (min-width: 901px), (max-width: 560px) {
	.ph-explore-grid a.tall::after {
		background: linear-gradient(to top, rgba(0,0,0,.72) 0, rgba(0,0,0,.4) 110px, rgba(0,0,0,0) 230px);
	}
}
/*
 * Crop anchors, per photograph. All four sources are 3:2 landscape and every
 * cell is a different shape, so `cover` alone decides badly for two of them:
 *
 *  - Getting Here is 758x224 (3.4:1) — only ~44% of the source's height
 *    survives, and the bus sits ABOVE the centre line (roof at 24%, wheels at
 *    63%). Dead centre cuts the roof off; 40% frames the whole vehicle.
 *  - Directory is 313x472 (2:3) — only ~44% of the source's WIDTH survives.
 *    Centre is right: it is where the two escalators cross, which is the
 *    picture. Stated rather than defaulted so that nobody "fixes" it.
 */
.ph-explore-grid a.wide img { object-position: center 40%; }
.ph-explore-grid a.tall img { object-position: center center; }
/*
 * The old rule absolutely positioned EVERY span in the grid, which was fine
 * when a tile held exactly one. Reset it, then place the label/CTA stack once.
 */
.ph-explore-grid span { position: static; left: auto; bottom: auto; text-shadow: none; font-weight: 400; }
.ph-explore-grid .body {
	position: absolute; z-index: 2; left: 26px; right: 26px; bottom: 26px;
	display: flex; flex-direction: column; align-items: flex-start; gap: 14px; color: #fff;
}
/*
 * 24px: "Getting Here" is 144px of ink in the frame (x204–347), which is Inter
 * 700 at 24. The max-width reproduces the frame's line breaks — "VIC" over
 * "Membership", "Nearby" over "Attractions" — while leaving the one-line
 * labels ("Getting Here" 144, "Directory" 107) on one line. A longer label in
 * any language simply wraps, which is the behaviour the frame is showing.
 */
.ph-explore-grid .label { font-size: 24px; font-weight: 700; line-height: 1.25; max-width: 150px; }
.ph-explore-grid .cta { font-size: 14px; font-weight: 700; display: inline-flex; align-items: center; }
/* Frame: "Find out" ends x257, the arrow starts x269 — a 12px gap. */
.ph-explore-grid .arrow { margin-left: 12px; font-size: 17px; line-height: 1; }

/* Mobile — Home.pdf, 390 frame: one column of 358-wide tiles at 220 tall, the
   Directory card keeping its full 473 height, 12px gutters, and Directory
   moving to the END of the run (the desktop DOM order puts it third so that
   auto-placement lands it in the right-hand column up there). */
@media (max-width: 900px) {
	/* No tablet frame exists. Two equal columns, no spans — which is what the
	   rule this replaces was reaching for, without the row/column holes that
	   keeping the spans at two columns would leave. */
	.ph-explore-grid { grid-template-columns: 1fr 1fr; grid-template-rows: none; grid-auto-rows: 224px; }
	.ph-explore-grid a.tall { grid-row: auto; }
	.ph-explore-grid a.wide { grid-column: auto; }
}
@media (max-width: 560px) {
	.ph-explore .ph-searchbar { max-width: none; margin: 0 auto 30px; }
	.ph-explore-grid { grid-template-columns: 1fr; grid-template-rows: none; grid-auto-rows: auto; column-gap: 0; row-gap: 12px; }
	.ph-explore-grid a { height: 220px; }
	.ph-explore-grid a.wide { grid-column: auto; }
	.ph-explore-grid a.tall { grid-row: auto; height: 473px; order: 4; }
	.ph-explore-grid .body { left: 22px; right: 22px; bottom: 22px; }
}

/* ---------- Movies main: CineArt venue block (Desktop/Movies - Main.pdf) ---------- */
/*
 * Structurally this IS the shop detail block — photo left, category / name /
 * icon rows / rule / description right, on the pale teal band, with the
 * floorplan under it. The rules below MIRROR the `.ph-shop-detail` ones rather
 * than widening those selectors to include this page: that region of the file
 * is being worked on concurrently, and a shared selector list is the thing two
 * lanes collide over. Every measured value is copied deliberately, and the
 * comments there remain the reference for why each number is what it is.
 *
 * Columns, measured off Movies - Main.pdf: photo x64–780 (717), info x842–1376
 * (535), gutter 61. Reproduced as `fr` so the drawn proportion survives on the
 * 1090 content measure this is built to — the frame draws the block at 1312,
 * but the designer's ruling (see the `.ph-section--grid` note above) puts
 * everything except the main banner on 1090, and the ruling wins over the
 * measurement.
 */
.ph-movies-venue { padding: 90px 0 40px; }
.ph-movies-venue .ph-detail { grid-template-columns: 717fr 535fr; gap: 61px; padding: 0; align-items: start; }
.ph-movies-venue .shot { border-radius: 10px; overflow: hidden; background: #dde9ea; }
.ph-movies-venue .shot img { display: block; width: 100%; height: auto; }
.ph-movies-venue .cat { color: var(--ph-muted); margin: 0 0 6px; }
/* Same 44px Inter 400 teal as the shop name — "CineArt Hollywood" is 348px of
   ink in the frame, which is Inter 400 at 44. An <h2> here (the page's <h1> is
   the banner), so it needs the size stated rather than inherited. */
.ph-movies-venue .ph-detail h2 {
	font-family: var(--ph-font-body); font-weight: 400; font-size: 44px;
	color: var(--ph-teal); margin: 0 0 26px; text-transform: none; letter-spacing: 0; line-height: 1.2;
}
.ph-movies-venue .facts { list-style: none; margin: 0 0 22px; padding: 0; }
.ph-movies-venue .facts li { position: relative; padding: 9px 0 9px 32px; font-size: 14px; color: var(--ph-muted); }
.ph-movies-venue .facts li::before {
	content: ""; position: absolute; left: 0; top: 11px; width: 19px; height: 19px;
	background: center/contain no-repeat;
}
.ph-movies-venue .facts li.shop::before  { background-image: url('../img/icon-shop.svg'); }
.ph-movies-venue .facts li.phone::before { background-image: url('../img/icon-phone.svg'); }
.ph-movies-venue .facts li.time::before  { background-image: url('../img/icon-clock.svg'); }
.ph-movies-venue .facts li a { color: inherit; text-decoration: underline; }
.ph-movies-venue .desc { border-top: 2px solid #8bd7df; padding-top: 22px; color: var(--ph-muted); font-size: 14px; line-height: 20px; }
.ph-movies-venue .desc p { margin: 0; }
/* The frame leaves a clear run between the description and the floorplan link. */
.ph-movies-venue .ph-floorplan-link { margin-top: 64px; }
@media (max-width: 900px) {
	/* Two classes, to beat the desktop pair above — a media query adds no
	   specificity, the same trap `.ph-shop-detail .ph-detail` documents. */
	.ph-movies-venue .ph-detail { grid-template-columns: 1fr; gap: 24px; }
	.ph-movies-venue { padding: 40px 0 30px; }
	.ph-movies-venue .ph-detail h2 { font-size: 30px; }
	.ph-movies-venue .ph-floorplan-link { margin-top: 32px; }
}

/* ---------- Movie detail: "New Release" wall (Desktop/Movies - Details.pdf) ---------- */
/*
 * The tint wash moves from <main> to the detail wrapper. Its stops are a
 * percentage of the painted element, and appending the poster wall inside
 * <main> made that element roughly half again as tall — which would have
 * dragged the teal down over a wall the frame draws on the plain page
 * background (sampled down the frame's left margin: tint to y880, fully faded
 * by y1000, wall at y891+). Same gradient, same padding, one level lower.
 */
.ph-movie-detail { background: none; padding: 0; }
.ph-movie-detail-body { background: linear-gradient(#e3f2f4 0 78%, var(--ph-bg) 100%); padding: 32px 0 60px; }
/* Frame: detail block ends ~y880, "NEW RELEASE" ink at y891, then the shared
   .ph-movie-grid padding (58px) carries down to the posters at y976. */
.ph-movie-newrelease { padding: 24px 0 60px; }

/* ---------- Floorplan: shop-by-floor directory (audit item M7) ----------
 *
 * The crawlable list under the map (parts/shop-by-floor.php). There is no
 * frame for this block — it is not in the ui-specs, it exists because the map
 * is a <canvas> and carried no text — so every value below is taken from
 * something the design already settled rather than invented: the section rhythm
 * and container of .ph-section, the 40px display face of .ph-section-title, the
 * white --ph-radius card with the 0 2px 10px shadow the shop cards and search
 * results share, --ph-muted for the unit numbers exactly as .ph-shop-card .unit
 * uses it, and --ph-gold for the floor badge, which is the rail's colour for
 * the same idea one block above.
 *
 * The one deliberate departure from the listing pages: no logos, no cards, no
 * grid of tiles. This is a directory, and 250 tiles under a map reads as an SEO
 * footer. Multi-column text at a fixed ~220px measure is what a printed mall
 * directory does, and it is also what keeps 250 links to one screenful per
 * floor.
 */
.ph-floor-directory { padding-top: 8px; }
.ph-floor-directory__eyebrow {
	margin: 0 0 6px; font-size: 12px; font-weight: 700; letter-spacing: .12em;
	text-transform: uppercase; color: var(--ph-teal-mid);
}
/* CJK has no uppercase and letter-spacing on it just loosens a word into
   unrelated characters, so the eyebrow sets plain in TC/SC. :lang() and not a
   body class: <html lang> is already correct on every page. */
:lang(zh) .ph-floor-directory__eyebrow { text-transform: none; letter-spacing: .02em; }
.ph-floor-directory__lead { margin: 0 0 20px; font-size: 14px; color: var(--ph-muted); }

.ph-floor-directory__floor {
	background: var(--ph-card); border: 1px solid #d3dfe1; border-radius: var(--ph-radius);
	box-shadow: 0 2px 10px rgba(0,0,0,.05); margin-bottom: 10px; scroll-margin-top: 110px;
}
.ph-floor-directory__floor[open] { border-color: var(--ph-teal-mid); }
.ph-floor-directory__summary {
	display: block; list-style: none; min-height: 48px; padding: 14px 22px;
	border-radius: calc(var(--ph-radius) - 1px); cursor: pointer;
}
.ph-floor-directory__summary::-webkit-details-marker { display: none; }
.ph-floor-directory__summary:hover, .ph-floor-directory__floor[open] > .ph-floor-directory__summary { background: #eef7f7; }
.ph-floor-directory__floor[open] > .ph-floor-directory__summary { border-bottom-left-radius: 0; border-bottom-right-radius: 0; }
.ph-floor-directory__summary:focus-visible { outline: 2px solid var(--ph-teal-deep); outline-offset: -3px; }
.ph-floor-directory__summary h2 {
	display: grid; grid-template-columns: 2.25em minmax(0,1fr) auto 10px; align-items: center; gap: 12px;
	font-family: var(--ph-font-display); font-size: 24px; margin: 0; line-height: 1.2; color: var(--ph-teal-deep);
}
.ph-floor-directory__code { color: var(--ph-gold); letter-spacing: .04em; }
.ph-floor-directory__name { overflow-wrap: anywhere; }
.ph-floor-directory__count { font: 500 13px/1.25 var(--ph-font-body); color: var(--ph-muted); white-space: nowrap; }
.ph-floor-directory__chevron {
	width: 8px; height: 8px; justify-self: center;
	border: solid var(--ph-teal-deep); border-width: 0 2px 2px 0; transform: rotate(45deg);
}
.ph-floor-directory__floor[open] .ph-floor-directory__chevron { transform: rotate(225deg); }
.ph-floor-directory__body { padding: 0 22px 18px; }
.ph-floor-directory__body > .ph-floor-directory__group:first-child { border-top: 0; margin-top: 0; }
.ph-floor-directory__group {
	margin: 22px 0 10px; font-size: 13px; font-weight: 700; letter-spacing: .08em;
	text-transform: uppercase; color: var(--ph-muted);
	border-top: 1px solid #e7e3db; padding-top: 14px;
}
:lang(zh) .ph-floor-directory__group { text-transform: none; letter-spacing: .02em; font-size: 14px; }

/*
 * columns, not grid: a grid of 250 cells orders left-to-right, so the alphabet
 * runs across the page and back. Columns run DOWN, which is how a directory
 * board is read. `column-width` rather than `column-count` is what makes this
 * responsive with no breakpoints — the browser fits as many ~220px columns as
 * the container holds, four at 1440 and one at 375.
 */
.ph-floor-directory__list {
	list-style: none; margin: 0; padding: 0;
	columns: 220px; column-gap: 28px;
}
.ph-floor-directory__list li {
	/* A row split across a column break reads as two different shops. */
	break-inside: avoid; -webkit-column-break-inside: avoid;
	margin: 0 0 2px;
}
.ph-floor-directory__list a {
	display: flex; align-items: baseline; gap: 10px;
	padding: 5px 0; font-size: 14px; line-height: 20px; color: var(--ph-text);
}
.ph-floor-directory__list a:hover .name,
.ph-floor-directory__list a:focus-visible .name { color: var(--ph-teal-deep); text-decoration: underline; }
/* min-width:0 and the wrap are the overflow gate's business: a long tenant
   name — and TC/SC set wider than EN at the same size — would otherwise push
   its column past the container at 375. */
.ph-floor-directory__list .name { min-width: 0; overflow-wrap: anywhere; color: var(--ph-teal-mid); font-weight: 500; }
/* The unit number is the second thing you read, never the first: same
   treatment as .ph-shop-card .unit, pushed to the column's right edge so the
   numbers form a readable column of their own. */
.ph-floor-directory__list .unit { margin-left: auto; flex: none; font-size: 13px; color: var(--ph-muted); font-variant-numeric: tabular-nums; }

@media (max-width: 560px) {
	.ph-floor-directory__summary { padding: 12px; }
	.ph-floor-directory__summary h2 { font-size: 18px; gap: 8px; }
	.ph-floor-directory__count { font-size: 12px; }
	.ph-floor-directory__body { padding: 0 12px 12px; }
	.ph-floor-directory__list { columns: auto; column-count: 1; }
	.ph-floor-directory__list a { min-height: 44px; align-items: center; }
}

/* ---------- Screen-reader-only text ---------- */
/*
 * The clip-rect utility, global. It existed only scoped to
 * `.ph-search-results .screen-reader-text` (core's pagination heading), so the
 * class was here as a fix for one block rather than as the tool it is — and the
 * homepage's <h1> needed it next (front-page.php, 11 Sep 2026: the page had no
 * h1 in any language and the hero has nowhere visible to put one).
 *
 * `clip` with `clip-path`, both, and NOT `display:none` or `visibility:hidden`:
 * those two take the element out of the accessibility tree as well as off the
 * canvas, which would hide the heading from exactly the readers it is for.
 * The scoped rule above is left where it is — it is the same declaration, so
 * either winning is the same result.
 */
.screen-reader-text {
	position: absolute;
	width: 1px; height: 1px;
	margin: -1px; padding: 0; border: 0;
	overflow: hidden;
	clip: rect(0 0 0 0);
	clip-path: inset(50%);
	white-space: nowrap;
}

/* ---------- Home hero: the VIC card's line ---------- */
/*
 * Was `.ph-hero-vic h3`. The element became a <p> so that the homepage's first
 * heading is its new <h1> rather than a level-3 heading about VIC membership
 * (front-page.php carries the reasoning). Appearance is unchanged, which is what
 * these declarations are for: the display-face group from the top of this file,
 * the card's own colour/size/measure, AND `font-weight: 700`, which the <h3>
 * used to get free from the browser's own stylesheet and a <p> does not.
 */
.ph-hero-vic .ph-hero-vic-title {
	font-family: var(--ph-font-display);
	text-transform: uppercase;
	letter-spacing: 0.04em;
	font-weight: 700;
	color: #fff;
	margin: 0 0 16px;
	font-size: 24px;
	line-height: 1.15;
}
@media (max-width: 900px) {
	/* Pairs with the `.ph-hero-vic h3` step-up in the 900 breakpoint above. */
	.ph-hero-vic .ph-hero-vic-title { font-size: 26px; }
}

/* UAT navigation and drive-only attraction details. */
.ph-search-home { padding-top: 24px; }
.ph-driving-label { display: flex; align-items: center; gap: 7px; margin: 0 0 26px; font-weight: 600; }
.ph-driving-label svg { width: 17px; height: 17px; flex: none; }
@media (max-width: 380px) {
	.ph-header-inner { gap: 4px; padding-left: 10px; padding-right: 10px; }
	.ph-logo img { height: 27px; }
	.ph-header-tools { gap: 2px; }
}

.ph-header-search .ph-searchbar:focus-within { outline: 2px solid var(--ph-teal-deep); outline-offset: 3px; }
.ph-icon-btn:focus-visible, .ph-search-home a:focus-visible { outline: 2px solid var(--ph-teal-deep); outline-offset: 2px; }
.ph-sdf a:focus-visible { outline: 3px solid var(--ph-teal-deep); outline-offset: -3px; }
@media (max-width: 360px) {
	.ph-footer-cols { grid-template-columns: minmax(0, 1fr); }
}

/* Keep the artwork, directory controls and first results close on phones. */
@media (max-width: 600px) {
	.ph-page-banner { min-height: clamp(144px, 43vw, 190px); }
	.ph-banner-page-title {
		margin-top: 20px;
		font-size: clamp(26px, 7vw, 34px);
		line-height: 1.15;
	}
	.ph-attractions-title-break { display: none; }
	.ph-search-results { padding-top: 24px; }
	.ph-listing-page .ph-filterbar { gap: 18px; padding-top: 14px; }
	.ph-listing-page .ph-filter-tab { min-height: 44px; font-size: 18px; }
	.ph-listing-page .ph-subfilters {
		flex-wrap: nowrap; gap: 6px; overflow-x: auto; overscroll-behavior-x: contain;
		padding: 10px 2px 6px;
	}
	.ph-listing-page .ph-subfilters .ph-chip {
		flex: none; min-width: 44px; min-height: 44px; padding: 0 12px;
		border: 1px solid #d3dfe1; background: #fff; white-space: nowrap;
	}
	.ph-listing-page .ph-subfilters :is(.ph-chip + .ph-chip, .ph-subfilter-options > .ph-chip)::before { content: none; }
	.ph-listing-page .ph-subfilters .ph-chip.active {
		background: var(--ph-teal-deep); border-color: var(--ph-teal-deep); color: #fff;
	}
	.ph-listing-page .ph-subfilters .ph-chip:focus-visible { outline: 2px solid var(--ph-teal-deep); outline-offset: -3px; }
	.ph-listing-page .ph-subfilters .ph-chip.active:focus-visible { outline-color: #fff; }
	.ph-listing-search { margin-top: 10px; }
	.ph-listing-search .ph-searchbar input { font-size: 16px; }
	.ph-listing-page .ph-shop-grid { padding-top: 14px; }
}

/* The approved lifestyle heading keeps the two Home sections separate. */
.ph-lifestyle > h2 { max-width: 1090px; margin-left: auto; margin-right: auto; padding-inline: 16px; box-sizing: border-box; text-wrap: balance; }
@media (max-width: 767px) {
 .ph-lifestyle > h2 { font-size: clamp(24px, 7vw, 28px); line-height: 1.25; }
}
