/*
 Theme Name:   Bricks Child Theme
 Theme URI:    https://bricksbuilder.io/
 Description:  Use this child theme to extend Bricks.
 Author:       Bricks
 Author URI:   https://bricksbuilder.io/
 Template:     bricks
 Version:      1.2
 Text Domain:  bricks
*/

/*
 * INTENTIONALLY EMPTY since 2026-08-20.
 * All site CSS moved to Bricks global custom CSS, deployed from
 * treasurers_office/styles.css via bricks-deploy (deploy.py css).
 * Do not add styles here — they belong in that master file.
 * Pre-migration copy: style.css.bak-20260820-css-to-deploypy
 */

/* ──────────────────────────────────────────────────────────────────────────
   Exception to the "intentionally empty" rule above — read before removing.
   ──────────────────────────────────────────────────────────────────────────
   iOS Safari resolves `background-attachment: fixed` against the viewport
   instead of the element box, so a `cover` hero gets scaled and cropped to
   the wrong frame. Reported 2026-08-21 against Public Depositories and
   Distributions; the news post hero was fine in the same pass because it
   already carried this override.

   This lives here, and not only in the Bricks global CSS, because the Bricks
   inline stylesheet is emitted AFTER the child theme stylesheet: a `deploy.py
   css` push that does not carry this rule would re-pin every hero. The `html`
   prefix raises specificity to 0,1,1 so the override survives that push
   regardless of source order.

   Once the rule is merged into the treasurers_office/styles.css master, this
   block is redundant but harmless — it is identical to what the master emits.
*/
@media (max-width: 1024px) {
	html .brxe-section,
	html .brxe-container,
	html .brxe-block,
	html [class^="section-"],
	html [class*=" section-"],
	html [class^="block-"],
	html [class*=" block-"],
	html body.et_cover_background {
		background-attachment: scroll;
	}
}

/* ──────────────────────────────────────────────────────────────────────────
   Home hero on phones: show the landmark, and stop eating the whole screen.
   ──────────────────────────────────────────────────────────────────────────
   The background is a 1920x1080 shot of Devils Tower, and the tower sits in
   the right third of the frame. At `cover` on a 375px-wide viewport only the
   middle 26% of the source is visible, so the one recognisable thing in the
   photo fell outside the crop and phones got an anonymous stretch of pine and
   scrub — raised by the content team on 2026-08-21.

   Two changes, and they help each other. Shifting the focal point to 78%
   brings the tower back into frame on the right, clear of the headline on the
   left. Cutting the height from 691px to 520px (97% -> 62% of an iPhone
   screen) both reveals that content follows below the fold and widens the
   visible slice of the photo from 26% to about 41%, which makes the crop
   easier to compose in the first place.

   Desktop is untouched: there the full panorama is visible and centred.
*/
@media (max-width: 767px) {
	html .section-home-hero {
		min-height: 520px;
		padding-top: 96px;
		padding-bottom: 40px;
		background-position: 78% 50%;
	}

	html .block-home-hero {
		min-height: 384px;
		padding-top: 56px;
		padding-bottom: 48px;
	}
}


/* ──────────────────────────────────────────────────────────────────────────
   News grid: single column on phones.
   ──────────────────────────────────────────────────────────────────────────
   The intended `max-width: 980px -> 1fr` rule sits earlier in the file than
   the base `repeat(3, ...)`, so at equal specificity the base wins and phones
   showed three ~96px columns with cramped headings (reported 2026-08-21 at
   463px). The `html` prefix (0,1,1) wins the cascade regardless of order.
   Kept to <=600px so tablets keep the three-up layout. */
@media (max-width: 600px) {
	html .block-home-news__grid,
	html .block-office-news__grid {
		grid-template-columns: 1fr;
	}
}


/* ──────────────────────────────────────────────────────────────────────────
   Investment report links: no default underline.
   ──────────────────────────────────────────────────────────────────────────
   These sit inside a .brxe-text-basic block, so the global
   `#brx-content :where(.brxe-text-basic) a` rule underlines them with
   ID-level specificity (1,0,1) — the existing `.card-...__body a { none }`
   (0,1,1) loses. Matching the ID prefix wins it back (reported 2026-08-21). */
#brx-content .card-investment-report-group__body a:not(.bricks-button),
#brx-content .card-investment-report-group__body a:not(.bricks-button):visited,
#brx-content .block-investments-archive__body a:not(.bricks-button),
#brx-content .block-investments-archive__body a:not(.bricks-button):visited,
#brx-content .block-home-reports__links a:not(.bricks-button),
#brx-content .block-home-reports__links a:not(.bricks-button):visited {
	text-decoration: none;
}