Skip to content
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

[Bug] Don't fill in the spinner circle svg path #2227

Merged
merged 5 commits into from
Aug 31, 2023
Merged

Conversation

jonrohan
Copy link
Member

@jonrohan jonrohan commented Aug 30, 2023

Authors: Please fill out this form carefully and completely.

Reviewers: By approving this Pull Request you are approving the code change, as well as its deployment and mitigation plans.
Please read this description carefully. If you feel there is anything unclear or missing, please ask for updates.

What are you trying to accomplish?

This change https://github.com/primer/view_components/pull/2215/files#diff-686a7fe5dfe914efd5dbef88bc0175b303cffbb1eaa8b3668b8ac12c2284eb99 resulted in a bug where the spinner gets filled in with the current color. This is because the spinner svg uses <circle instead of path.

Screenshots

spinners.mov

Integration

No

List the issues that this change affects.

Reported in slack

Risk Assessment

  • Low risk the change is small, highly observable, and easily rolled back.
  • Medium risk changes that are isolated, reduced in scope or could impact few users. The change will not impact library availability.
  • High risk changes are those that could impact customers and SLOs, low or no test coverage, low observability, or slow to rollback.

What approach did you choose and why?

I could revert the CSS change, but I assume this was done for the button support. So instead I added fill="none" to the spinner svg code.

Accessibility

  • Fixes axe scan violation - This change fixes an existing axe scan violation.
  • No new axe scan violation - This change does not introduce any new axe scan violations.
  • New axe violation - This change introduces a new axe scan violation. Please describe why the violation cannot be resolved below.

Merge checklist

  • Added/updated tests
  • Added/updated documentation
  • Added/updated previews (Lookbook)
  • Tested in Chrome
  • Tested in Firefox
  • Tested in Safari
  • Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

@jonrohan jonrohan requested review from a team and keithamus August 30, 2023 23:13
@changeset-bot
Copy link

changeset-bot bot commented Aug 30, 2023

🦋 Changeset detected

Latest commit: 0fdc860

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@primer/view-components Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@jonrohan jonrohan temporarily deployed to preview August 30, 2023 23:13 — with GitHub Actions Inactive
@github-actions github-actions bot added the ruby Pull requests that update Ruby code label Aug 30, 2023
@jonrohan jonrohan temporarily deployed to preview August 30, 2023 23:31 — with GitHub Actions Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Aug 30, 2023

⚠️ Visual differences found

Our visual comparison tests found UI differences. Please review the differences by viewing the files changed tab to ensure that the changes were intentional.

Review visual differences

@jonrohan jonrohan merged commit bb336bb into main Aug 31, 2023
@jonrohan jonrohan deleted the fill_none_spinner branch August 31, 2023 15:15
@jonrohan jonrohan temporarily deployed to preview August 31, 2023 15:15 — with GitHub Actions Inactive
@primer primer bot mentioned this pull request Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch release ruby Pull requests that update Ruby code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants