-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MWPW-151517] - Remove condition for promobar hidden on mobile from gnav #2538
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## stage #2538 +/- ##
=======================================
Coverage 95.69% 95.70%
=======================================
Files 172 172
Lines 45359 45359
=======================================
+ Hits 43406 43409 +3
+ Misses 1953 1950 -3 ☔ View full report in Codecov by Sentry. |
|
@@ -4,7 +4,7 @@ | |||
--global-height-nav: 64px; | |||
--global-height-breadcrumbs: 33px; | |||
/* stylelint-disable-next-line custom-property-pattern */ | |||
--global-height-navPromo: 65px; | |||
--global-height-navPromo: 72px; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have there been any considerations regarding the two-line, 80px use-case utilizing a min-height here? To me it seems like that use-case would lead to CLS currently. (Suggested CLS Strategy within the design specs)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the design specifications, the goal is to ensure that the feds promobar displays as a single line on all viewports. This character count limit is also included in the authoring documentation, following the design specifications.
So, with that we can ignore the case of two-line copy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed it spawns on two lines between 1200 and 1270px
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@narcis-radu is right, the Promo spans two rows between 1200 and 1287px. Either the copy needs to be adapted or some styles.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Based on discussions with Joel Blytt the character count limit in design specs will be updated so that promobar displays on single line for this range also.
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. |
promoMeta.remove(); | ||
}); | ||
|
||
it('Exist on mobile', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could have more descriptive test names that tell the reader when the promobar should or should not exist on mobile, i.e. when we have content for mobile
Let's wait for the consonant/design sign-off on the ticket before merging this. From what I've seen, once you got a branch ready - you send that over on the Jira, have them sign off and then raise the PR. @ryanmparrish would that be the correct flow involving any (design) changes for blocks? |
Validated the promobar functionality in Devices and observed that after enabling the promobar for the device, the Gnav does not show up on both the iPhone and the iPad. For Gnav, the iPhone does not display the Hamberg symbol. Note: Android device is working as expected URL: iphone device: (both safari and chrome browser have same result) In iPad landscape orientation, the gnav displays as expected: A JIRA ticket has been created to track the details. Refer to https://jira.corp.adobe.com/browse/MWPW-154090 for further details. Validation would be done after the bug fix. |
@Deva309 there seems to be design feedback on the Ticket |
Error merging 2538: [MWPW-151517] - Remove condition for promobar hidden on mobile from gnav Base branch was modified. Review and try the merge again. |
Error merging 2538: [MWPW-151517] - Remove condition for promobar hidden on mobile from gnav 1 review requesting changes and 3 approving reviews by reviewers with write access. |
@@ -571,6 +570,11 @@ header.global-navigation { | |||
overflow: auto; | |||
} | |||
|
|||
.global-navigation.has-promo .feds-navItem--megaMenu .feds-popup { | |||
max-height: calc(100vh - 100% - var(--global-height-navPromo)); | |||
box-sizing: border-box; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of the elements in the global navigation are context-box
and this might generate some confusion when setting padding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@narcis-radu Yes, but this case involves the megamenu, where scrolling is necessary if its height and width exceed the screen dimensions. To address this, we calculate the height for the megamenu and add a scroll. However, due to content-box
, it only sets the scroll for the content area, but we need scrolling for both the content and the surrounding spacing. I've now moved it closer to overflow:auto
, which is only required for the scroll functionality.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We already have scrolling functionality on Production and the box-sizing is content-box
, don't we ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -4,7 +4,7 @@ | |||
--global-height-nav: 64px; | |||
--global-height-breadcrumbs: 33px; | |||
/* stylelint-disable-next-line custom-property-pattern */ | |||
--global-height-navPromo: 65px; | |||
--global-height-navPromo: 72px; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed it spawns on two lines between 1200 and 1270px
The promobar functionality is verified after the resizing and scrolling issue was fixed. https://mwpw-151517-promobar--milo--deva309.hlx.page/drafts/prativa/feds-promobar-one |
@narcis-radu |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The flex-wrap
declaration should be revisited, as it has the potential to affect a large number of production pages.
@@ -702,5 +706,6 @@ header.global-navigation { | |||
|
|||
.feds-navItem--megaMenu .feds-popup { | |||
align-items: center; | |||
flex-wrap: wrap; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this needed? Is it desirable to have columns span on multiple rows in certain scenarios? Doesn't this interfere with the feds-crossCloudMenu-wrapper
element, since it's also inside the popup? This is how this tweak affects the current Photoshop page:
Since this doesn't seem to be related to the promo, it might be good to remove this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
5 columns have never been supported in the dropdown. The initial Consonant guidelines (which I can't locate currently due to how many changes they had on their platform 😅 ) stated that a maximum of 4 columns should be added in a dropdown menu.
@@ -4,7 +4,7 @@ | |||
--global-height-nav: 64px; | |||
--global-height-breadcrumbs: 33px; | |||
/* stylelint-disable-next-line custom-property-pattern */ | |||
--global-height-navPromo: 65px; | |||
--global-height-navPromo: 72px; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@narcis-radu is right, the Promo spans two rows between 1200 and 1287px. Either the copy needs to be adapted or some styles.
@@ -569,6 +568,11 @@ header.global-navigation { | |||
padding: 40px 0 0; | |||
max-height: calc(100vh - 100%); | |||
overflow: auto; | |||
box-sizing: border-box; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see any box-size model properties adapted to justify this change. Why is it needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making the changes!
* stage: MWPW-150557 - Split Marquee CLS issues on consuming sites (adobecom#2636) Mwpw 147034: Custom border color + badge/border color decoupling [merch card] (adobecom#2613) [MWPW-151517] - Remove condition for promobar hidden on mobile from gnav (adobecom#2538) # Conflicts: # libs/deps/merch-card.js
* stage: [MWPW-153611] [Gray Box] environment aware links (adobecom#2622) MWPW-153580: Add Opt-In Feature for CaaS Badge Display (adobecom#2625) [MWPW-154335] [callout] Spacing issue encountered when the call-out section is added (adobecom#2628) MWPW-150557 - Split Marquee CLS issues on consuming sites (adobecom#2636) Mwpw 147034: Custom border color + badge/border color decoupling [merch card] (adobecom#2613) [MWPW-151517] - Remove condition for promobar hidden on mobile from gnav (adobecom#2538) MWPW-154998 [MEP][MILO] Manifests do not execute in the right order when there is a disabled manifest (adobecom#2632) mwpw-154965: Fetch federal stage content from hlx.page instead of stage.adobe.com (adobecom#2618) Correct error messages for duplicate files on the stage to main workflow (adobecom#2621) MWPW-153245 [merch][analytics] dispatch wcomp events, and let default lh (adobecom#2610) Revert "MWPW-146528[MILO][MEP][ANALYTICS] Add attribute to content changed by Target for analytics and MWPW-152274" (adobecom#2627) MWPW-128600 Locale Tool: Langstore points to langstore/en (adobecom#2615) Fix for errors in dynamically loaded scripts in test cases (adobecom#2619) MWPW-146528[MILO][MEP][ANALYTICS] Add attribute to content changed by Target for analytics and MWPW-152274 (adobecom#2593) Bootstrapper script for milo feds blocks (adobecom#2560) Revert "[MWPW-152968] mWeb - Passing ECID to Branch.io banner - Implementation" (adobecom#2612) # Conflicts: # libs/deps/merch-card.js
Description
Removed the condition that hides the gnav promobar on mobile. We now have the ability to set separate copies for each viewport. The acceptance criteria to on and off the promobar only for mobile comes with a CLS issue, so it is not part of this PR, as discussed with the PDMs.
For example:
To avoid CLS impact, we need to adhere to the character count limits specified in the design specs for the feds promo bar, also mentioned in the ticket. Additionally, this information has been included in the authoring documentation for the aside promo bar.
Resolves:
Test URLs: