[MWPW-154795] Style Feds Global-footer region picker drop-up variant (without hash)

[sonawanesnehal3]

Add styling for region picker drop-up variant (without hash)

Resolves: MWPW-154795

Test URLs:

• Before: https://main--milo--adobecom.hlx.page/drafts/snehal/unav11
• After: https://dropup--milo--adobecom.hlx.page/drafts/snehal/unav11

Before styles applied :

After styles applied :

QA : Sample Page

[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 PSI checks
• Re-sync branch

Commits

• 01645e9 ✅ (latest)
• 3219438 ✅
• ff66bd6 ✅
• a450bd4 ✅

[aem-code-sync]

Page	Scores	Audits	Google
/drafts/snehal/unav11

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.86%. Comparing base (31c21e8) to head (01645e9).
Report is 10 commits behind head on stage.

Additional details and impacted files

@@            Coverage Diff             @@
##            stage    #2599      +/-   ##
==========================================
- Coverage   95.86%   95.86%   -0.01%     
==========================================
  Files         176      176              
  Lines       46211    46211              
==========================================
- Hits        44300    44298       -2     
- Misses       1911     1913       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[narcis-radu]

@sonawanesnehal3 - I remember @overmyheadandbody implemented support for this already, I am able to see it running with forcing the global-footer component on blog - https://main--blog--adobecom.hlx.page/?footerqa=global-footer. Can you check whether your enhancement is needed or this can be addressed from authoring? Thanks!
Also, if a PR is needed, please provide test URLs in the before/ after area to make sure we capture the changes in the reports.

[sonawanesnehal3]

Thanks @narcis-radu.
It was not added to Milo's styles. Blog is using custom styles.css to fix this issue.
Adding this fix to Milo, since all consumers who wants to use drop-up can leverage this .
Sure, I will provide test URLs in the before/ after area.

[spadmasa]

Hi @sonawanesnehal3 , can you please confirm on the region selection in locale page , when JP locale is updated in region doc, on change region selection is still seen as US.Can you please advise on this.
https://dropup--milo--adobecom.hlx.page/jp/drafts/snehal/unav11

[bandana147]

Hi @sonawanesnehal3 , can you please confirm on the region selection in locale page , when JP locale is updated in region doc, on change region selection is still seen as US.Can you please advise on this. https://dropup--milo--adobecom.hlx.page/jp/drafts/snehal/unav11

Please test the localisation flow in this PR as localisation flow is fixed in this PR.

[spadmasa]

Validation done on the below url :
https://dropup--milo--adobecom.hlx.page/drafts/Sou/universalnav/unav3

loc flow will be verified as part of #2560

[overmyheadandbody]

This may need to be reverted, as it affects current behavior:

Current look: https://main--milo--adobecom.hlx.page/drafts/ramuntea/footer-refactor-variant

Look after merging this PR: https://stage--milo--adobecom.hlx.page/drafts/ramuntea/footer-refactor-variant

I'm still not clear on what the intention for this PR was, as the logic and styles were working as expected.

CC: @bandana147, @sharmrj, @spadmasa, @narcis-radu

[overmyheadandbody]

Also tried looking at the links provided in this PR, but the logic is trying to load https://stage--milo--adobecom.hlx.page/federal/footer/fragments/regions1.plain.html, which doesn't exist