fix: Fix CSS rules captured in Safari#1253
Conversation
🦋 Changeset detectedLatest commit: d591538 The changes in this PR will be included in the next version bump. This PR includes changesets to release 8 packages
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 |
|
@mydea thanks for submitting this, could you add a Changeset then I can merge this issue? |
Added a changeset 👍 |
* fix: Fix CSS rules captured in Safari * Apply formatting changes * add changeset * fix --------- Co-authored-by: mydea <mydea@users.noreply.github.com>
* fix: Fix CSS rules captured in Safari * Apply formatting changes * add changeset * fix --------- Co-authored-by: mydea <mydea@users.noreply.github.com>
* fix: Fix CSS rules captured in Safari * Apply formatting changes * add changeset * fix --------- Co-authored-by: mydea <mydea@users.noreply.github.com>
* fix: Fix CSS rules captured in Safari * Apply formatting changes * add changeset * fix --------- Co-authored-by: mydea <mydea@users.noreply.github.com>
* fix: Fix CSS rules captured in Safari * Apply formatting changes * add changeset * fix --------- Co-authored-by: mydea <mydea@users.noreply.github.com>
|
In light of performance efforts in #1271 I wonder whether it's desirable to run a browser check before employing the I believe (correct me if I'm wrong) that the |
* fix: Fix CSS rules captured in Safari * Apply formatting changes * add changeset * fix --------- Co-authored-by: mydea <mydea@users.noreply.github.com>
Correct, + regexp.replace will always allocate a new string for you, so you are also performing an unnecessary copy |
Safari does not capture some css selectors correctly, so we need to fix them, or else playback fails for them.
Closes #1208
ref getsentry#86