INTL1207 - Add content-toggle block for A/B test campaign

[elindseth]

This PR adds new functionality to the content-toggle block that has previously been tested.

New functionality:

• Config-driven mounting of the toggle nav inside a marquee via Mount target/Mount marker
• Config-driven default option via Default toggle
• Config-driven sticky behavior (None / Sticky / Pinned)
• Config-driven scroll-on-toggle (None / Top / Matched anchor)

Resolves: OPT-42221

Test URLs:

• Before: http://main--da-cc--adobecom.aem.page/uk/products/premiere?martech=off
• After: https://main--da-cc--adobecom.aem.page/uk/products/premiere?mep=%2Fuk%2Fcc-shared%2Ffragments%2Froc%2Fmep%2Fproducts%2Fpremiere%2Froc-premiere.json--default---%2Fproducts%2Fpremiere.json--default---%2Fcc-shared%2Ffragments%2Fpromos%2F2026%2Fglobal%2Ffirefly-crosslinking-banner.json--default---%2Fcc-shared%2Ffragments%2Fpromos%2F2026%2Fglobal%2Ffooter-de-kr%2Fseparate-de.json--default---%2Fcc-shared%2Ffragments%2Fpromos%2F2026%2Fglobal%2Ffooter-de-kr%2Fseparate-kr.json--default---%2Fcc-shared%2Ffragments%2Ftests%2Femea-latam%2F2026%2Fq3%2Fintl1207%2Fintl1207.json--all&milolibs=intl1207-content-toggle

[aem-code-sync]

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

• Re-sync branch

Commits

• 82eda11 ✅ (latest)

[github-actions]

This pull request is not passing all required checks. Please see this discussion for information on how to get all checks passing. Inconsistent checks can be manually retried. If a test absolutely can not pass for a good reason, please add a comment with an explanation to the PR.

[jpratt2]

@elindseth Here is a code review from Claude:
No blockers.PR-6451-review.docx

[jpratt2]

@elindseth
When I use this URL in a mobile phone emulator in Chrome dev tools, I am noticing that the toggle defaults to "desktop" when I add the new intl1207.json manifest via the MEP button :



Is this OK / expected?

https://main--da-cc--adobecom.aem.page/uk/products/premiere?milolibs=intl1207-content-toggle&mep=%2Fuk%2Fcc-shared%2Ffragments%2Froc%2Fmep%2Fproducts%2Fpremiere%2Froc-premiere.json--default---%2Fproducts%2Fpremiere.json--phone---%2Fcc-shared%2Ffragments%2Fpromos%2F2026%2Fglobal%2Ffirefly-crosslinking-banner.json--default---%2Fcc-shared%2Ffragments%2Fpromos%2F2026%2Fglobal%2Ffooter-de-kr%2Fseparate-de.json--default---%2Fcc-shared%2Ffragments%2Fpromos%2F2026%2Fglobal%2Ffooter-de-kr%2Fseparate-kr.json--default
URL for intl1207 manifest: https://main--da-cc--adobecom.aem.page/cc-shared/fragments/tests/emea-latam/2026/q3/intl1207/intl1207.json

[jpratt2]

Note: I don't expect you to act on all of the suggestions from Claude. There are no blockers, so I consider all of the other suggestions optional.

[elindseth]

@elindseth When I use this URL in a mobile phone emulator in Chrome dev tools, I am noticing that the toggle defaults to "desktop" when I add the new intl1207.json manifest via the MEP button : Is this OK / expected?

@jpratt2 There is an expectation that it starts in desktop for this test campaign. That is how I've parsed the charter anyway. There is a config option to make it default to the second toggle option, but nothing that makes it detect the device. That might be the more logical behaviour, and a good enhancement if this test wins.

The block was initially written for Express vs CC so I didn't consider baking in any such mobile enhancements. Maybe I should have. :)