-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fix mapping of CSS URLs #33
Conversation
07977d7
to
f9c5b5b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. A future improvement here would be ensuring that assets which can be shared across captures/archives are deduped. However, no changes needed yet!
🚀 PR was released in |
Issue: CAP-1329
What Changed
When we need to rewrite an asset path, we're currently only updating the
src
attribute on DOM nodes. If an asset loaded from a CSS file orstyle
attribute was rewritten, it will fail to load because the CSS will reference the old path when the snapshot is rendered.This goes through the contents of
style
attributes andstyle
elements and replaces anyurl
references as needed.There's still one empty box in the E2E Storybook due to a missing asset, but that's due to CAP-1194. I believe getting rid of the rrweb fork, which can be a follow up to this, will resolve that.
How to test
Change Type
maintenance
documentation
patch
minor
major
📦 Published PR as canary version:
0.0.37--canary.33.f9c5b5b.0
✨ Test out this PR locally via:
npm install @chromaui/test-archiver@0.0.37--canary.33.f9c5b5b.0 # or yarn add @chromaui/test-archiver@0.0.37--canary.33.f9c5b5b.0