Skip eager-loading hidden hero-marquee foreground at current breakpoint

[JasonHowellSlavin]

What

Guards the foreground fallback in getLCPImages so a hero-marquee foreground that is hidden at the active breakpoint (media-hidden-mobile / media-hidden-tablet) is never hinted as the LCP image.

Why

getLCPImages falls back to the foreground image when no breakpoint-specific background exists. If the foreground is hidden for the current viewport, that fallback could eager-load an image that is never rendered — wasting bandwidth and supplying a wrong fetchpriority hint.

How

const fgHidden = lcpSection.classList.contains('hero-marquee') && (
  (window.innerWidth < 600 && lcpSection.classList.contains('media-hidden-mobile'))
  || (window.innerWidth >= 600 && window.innerWidth < 1200 && lcpSection.classList.contains('media-hidden-tablet'))
);
const foregroundImg = fgHidden ? null : lcpSection.querySelector(':scope > div:last-child img');

Strictly narrowing — the existing breakpoint background paths are unchanged; only the hidden-foreground fallback now no-ops.

Context

Adopts the visibility-aware pattern from adobecom/cc#407, per discussion adobecom/milo-private#374. Breakpoint-aware background selection (cc#346) was already present; MEP marquee replacement (cc#345) does not apply to bacom (eager attributes are set before loadArea/MEP).

Test

• Full unit suite passes locally (335 passed, 0 failed).
• Validate on a hero-marquee page using media-hidden-mobile/media-hidden-tablet with no breakpoint background, across mobile/tablet/desktop.

🤖 Generated with Claude Code

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run all PSI checks
• Re-run failed PSI checks
• Re-sync branch

Commits

• 46b9224 ✅ (latest)