Closed nikkimk closed 1 week ago
When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
If the changes are expected, update the current_golden_images_cache
hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.
Category | Latest (report) | Main (report) | Branch (report) |
---|---|---|---|
Performance | 0.98 | 0.99 | 0.99 |
Accessibility | 1 | 1 | 1 |
Best Practices | 1 | 1 | 1 |
SEO | 1 | 0.92 | 0.92 |
PWA | 1 | 1 | 1 |
main
("Main"). Higher scores are better, but *note that the SEO scores on Netlify URLs are artifically constrained to 0.92.*
Category | Latest | Main | Branch |
---|---|---|---|
Total | 251.018 kB | 236.736 kB | 236.702 kB 🏆 |
Scripts | 60.952 kB | 54.188 kB 🏆 | 54.246 kB |
Stylesheet | 53.904 kB | 47.969 kB 🏆 | 48.005 kB |
Document | 6.225 kB | 5.474 kB | 5.46 kB 🏆 |
Font | 126.951 kB | 126.755 kB | 126.641 kB 🏆 |
Category | Latest | Main | Branch |
---|---|---|---|
Total | 52 | 52 | 52 |
Scripts | 41 | 41 | 41 |
Stylesheet | 5 | 5 | 5 |
Document | 1 | 1 | 1 |
Font | 2 | 2 | 2 |
Totals | |
---|---|
Change from base Build 11907852264: | 0.006% |
Covered Lines: | 32358 |
Relevant Lines: | 32778 |
@caseyisonit @Rajdeepc @rubencarvalho PTAL
@nikkimk Can you please make sure the tests are passing and surface up a new hash so that the VRTs are clean! Thanks
Description
<sp-button>
and<sp-action-button>
withhref
could not be activated by mouse-click or screenreader click.ButtonBase
to allow clicks when there is anhref
attribute set.<sp-button>
and<sp-action-button>
.<sp-action-button>
with anhref
attribute.Related issue(s)
4576
How has this been tested?
[ ]
<sp-button> mouse click
[ ]
<sp-button> screenreader click
[ ]
<sp-action-button> mouse click
[ ]
<sp-action-button> screenreader click
[x] Did it pass in Desktop?
[ ] Did it pass in Mobile?
[ ] Did it pass in iPad?
Screenshots (if appropriate)
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main
.