Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

[terra-paginator] Styling update to support anchor attribute gap in F… #3900

Closed
wants to merge 6 commits into from

Conversation

chenyixuan625
Copy link
Contributor

@chenyixuan625 chenyixuan625 commented Aug 31, 2023

…usion

Summary

What was changed:
A new optional boolean prop(false by default) is added to support the anchor style. When the new prop is set(true), the paginator will be rendered in a gray background color with a borderline at the top.

Why it was changed:
Currently the paginator renders without any borderline and the background color is white. However, MPage PagiantorFooter(utilizing Progressive Paginator) has an "anchor" style, which has a top borderline and the background color is gray. We will want to add a new optional boolean prop(false by default) to support the anchor style from the Terra perspective.

Testing

The default progressive paginator looks like(no top border line and no background color):
Screenshot 2023-08-31 at 3 41 57 PM

The progressive paginator with Fusion Anchor style(top border line and gray background color):
Screenshot 2023-08-31 at 3 41 12 PM

This PR does not contain Accessibility changes.

This change was tested using:

  • WDIO
  • Jest
  • Visual testing (please attach a screenshot or recording)
  • Other (please describe below)
  • No tests are needed

Reviews

In addition to engineering reviews, this PR needs:

  • UX review
  • Accessibility review
  • Functional review

Additional Details

This PR resolves:

UXPLATFORM-9527


Thank you for contributing to Terra.
@cerner/terra

Copy link

@RayGunY RayGunY left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@chenyixuan625
Copy link
Contributor Author

@eawww @sdadn @sycombs This PR is ready for review. Thanks!

Comment on lines 50 to 53
/**
* Apply Fusion anchor style or not.
*/
fusionAnchor: PropTypes.bool,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems odd to add a prop for a very specific use case. Especially since it's related to theming. I'm confused why this is needed to be an API change and not a theme update or any other alternative solution.

cc: @JessieRandle , @mjpalazzo , @sycombs

Copy link
Contributor Author

@chenyixuan625 chenyixuan625 Sep 13, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the Orion fusion theme, there are 2 different styles(anchor and canvas) and we need to support both. So applying this new optional prop is to distinguish each other in the same fusion theme(and we keep the current Orion fusion theme to render the canvas style).
Screenshot 2023-09-13 at 1 09 41 PM
Any suggestions?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it's styling we need to support then I would say that we should support it for all themes and not add a niche prop that is only useful for a specific theme.

cc: @eawww , @mjpalazzo , @JessieRandle

@scottwilmarth scottwilmarth added ⭐ UX Reviewed UX Reviewed and approved. and removed UX Review Required labels Sep 13, 2023
@github-actions github-actions bot temporarily deployed to preview-pr-3900 September 14, 2023 17:13 Destroyed
@chenyixuan625
Copy link
Contributor Author

Synced with Scott and Terra folks, we believe that the best practice would be that Fusion takes care of its own customized style. Adding a prop for a specific styling usage is very confusing for consumers. Closing this PR out. Will comment on the UXPLATFORM-9527 soon.

@chenyixuan625 chenyixuan625 deleted the UXPLATFORM-9527 branch September 20, 2023 13:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants