Typography Audit Issue: Global search results left/right padding

[laflannery]

Description

From Phase 1 of the Typography audit, an issue was found with the padding on the Global search results that should be reviewed:

1. The left/right padding has slightly increased on the global search results. While this is on all breakpoints, the concern is on the 320 breakpoint where the H1 now goes to 2 lines. The concern from UX is that because it dropd to 2 lines, it's just adding to the scroll length before users can see search results.
   
   

Acceptance Criteria

• Heading for Search results does not drop to 2 lines on any breakpoint
• Requires design review

[jilladams]

@FranECross I've tagged this into Sprint 4, but please feel free to override if this doesn't feel like a priority for next sprint. @thejordanwood also happy to hear your opinion on priority here.

[randimays]

I tested this locally. Dropping my findings here. It feels to me like the typography scaling issues are something in DST's court but I could be wrong there.

Header line width issue

This seems either fixed or just not-reproducible on my end.

Typography scaling issues

It seems as though the default font size is 10px 🤔 Looking specifically at misalignment in the header and the tiny description text under each search result.

[laflannery]

I think this might be another instance of Local and RI showing different things - which again is slightly concerning because we were told either way of testing would be fine

[FranECross]

@jilladams @laflannery Circling back around on this one... I completely forgot @jilladams you'd tagged for Sprint 4, but to Randi's point, I think this might be a no op, or something the DST will fix/has a fix for? Should we wait and retest? cc @randimays

[FranECross]

DST has merged their fixes; need to validate on Prod @FranECross . If it's still an issue, then the PW team will need to take action.

[randimays]

@FranECross I validated in production; everything looks fine to me (padding, text size, etc.). I'll lean on @laflannery to confirm.

[laflannery]

I'm also not seeing the issues in prod that we reported in the previous screenshots, we should be good to close this!

[randimays]

Closing as a no-op per the above comments.