MWPW-155694 Dispatch sticky close event for dynamic chat

[Brandon32]

• Dispatch sticky close event for dynamic chat
• Increase z-index to place above chat (Dynamic chat has 2 second loading delay)

Resolves: MWPW-155694

Test URLs:

• Before: https://main--milo--adobecom.hlx.page/drafts/bmarshal/sticky/aside?martech=off
• After: https://bmarshal-chat-promo--milo--adobecom.hlx.page/drafts/bmarshal/sticky/aside?martech=off
• Before: https://main--milo--adobecom.hlx.page/drafts/bmarshal/sticky/notification?martech=off
• After: https://bmarshal-chat-promo--milo--adobecom.hlx.page/drafts/bmarshal/sticky/notification?martech=off

Bacom URLs:

• Before: https://business.stage.adobe.com/resources/digital-economy-index.html?martech=on
• After: https://business.stage.adobe.com/resources/digital-economy-index.html?martech=on&milolibs=bmarshal-chat-promo

[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

• dccfc85 ✅ (latest)

[aem-code-sync]

	Page	Scores	Audits	Google
M	/drafts/bmarshal/sticky/aside?martech=off
D	/drafts/bmarshal/sticky/aside?martech=off
M	/drafts/bmarshal/sticky/notification?martech=off
D	/drafts/bmarshal/sticky/notification?martech=off

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.91%. Comparing base (d90dcc0) to head (dccfc85).
Report is 37 commits behind head on stage.

Additional details and impacted files

@@           Coverage Diff           @@
##            stage    #2788   +/-   ##
=======================================
  Coverage   95.90%   95.91%           
=======================================
  Files         173      173           
  Lines       45842    45848    +6     
=======================================
+ Hits        43967    43974    +7     
+ Misses       1875     1874    -1     

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

[JasonHowellSlavin]

I am guessing the other martech element has a high z-index like this as well?

[Brandon32]

Yes, the dynamic chat is at 10k.

[meganthecoder]

I think this is fine given what currently exists, but @ryanmparrish @elan-tbx we might want to rethink some of the sticky functionality. Didn't our tiger team say that any sticky section should be closable? It seems like maybe the close button/functionality should go with the section metadata code rather than the block code, if possible.

[elan-tbx]

@meganthecoder Looks like that's already a part of Asides, I can create a due-diligence ticket for this to be added to Notifications as well.

It's just tricky, because the actual DOM element of a close button would need to live within each block itself, so having the section inject a close button into the block feels wrong.

Would make sense to me if we dispatched the same event onClick across those blocks and let section-metadata handle the rest, though.

[meganthecoder]

@meganthecoder Looks like that's already a part of Asides, I can create a due-diligence ticket for this to be added to Notifications as well.

It's just tricky, because the actual DOM element of a close button would need to live within each block itself, so having the section inject a close button into the block feels wrong.

Would make sense to me if we dispatched the same event onClick across those blocks and let section-metadata handle the rest, though.

I don't think there's a need for another ticket. Brandon covered notifications as well as asides in this PR. I was more thinking about the fact that other blocks can use the sticky section metadata functionality, and we'd need to add this code to every one. However, if you think that the close button needs to be in the block code then that sounds good.

Thanks!

[github-actions]

Reminder to set the Ready for Stage label - to queue this to get merged to stage & production.