Open TarunAdobe opened 1 month ago
Category | Latest (report) | Main (report) | Branch (report) |
---|---|---|---|
Performance | 0.99 | 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 | 222.263 kB | 210.764 kB 🏆 | 211.462 kB |
Scripts | 54.308 kB | 48.461 kB 🏆 | 48.631 kB |
Stylesheet | 34.963 kB | 30.389 kB 🏆 | 30.87 kB |
Document | 6.006 kB | 5.282 kB 🏆 | 5.292 kB |
Font | 126.986 kB | 126.632 kB 🏆 | 126.669 kB |
Category | Latest | Main | Branch |
---|---|---|---|
Total | 45 | 45 | 45 |
Scripts | 37 | 37 | 37 |
Stylesheet | 5 | 5 | 5 |
Document | 1 | 1 | 1 |
Font | 2 | 2 | 2 |
@castastrophe If you feel good about this PR, we would love to land this in our next SWC release! Let us know
LGTM!
Summary
This PR introduces changes to the Spectrum Web Components (SWC) project to facilitate the transition from Spectrum 1 (S1) to Spectrum 2 (S2) CSS. It includes the addition of a new index file
(component/{bridge,spectrum,express}/index.css)
in the@spectrum-css/tokens@14.1.0-alpha.3
package to assist in loading component-specific CSS. Additionally, it updates the SWC library to process the bridge file (referred to as legacy-overrides in SWC for now) and import it into the components.Changes Made
1.
@spectrum-css
added a new bridge file in the@spectrum-css/tokens@14.1.0-alpha.3
package to aid in loading component-specific CSS from the tokens module directly.generate-token
script to include component's system levels inglobal-vars.css
process-spectrum
script to create alegacy-override
css file from the@spectrum-css/tokens.../bridge.css
Note: Investigated and identified VRT failures due to changes in global CSS tokens in the new
sp-action-button
from the CSS side. For example,--mod-actionbutton-content-color-default
now points togray-25
instead ofgray-50
for the selected state, which might be a breaking change for S1.Next Steps
Ensure there are no breaks to the existing code before merging.
Motivation and context
This PR is important to bring in S1/Express core tokens with S2 overrides keeping in mind
How has this been tested?
main
branch should just work as it is !!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
.