You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issue tracker for a bug report that matches the one I want to file, without success.
What package is this bug report for?
rrweb
Version
latest v2
Expected Behavior
that the grid-template-area is captured correctly
Actual Behavior
A customer site uses grid template areas in their CSS. When playing back we see the content is not aligned as expected. When viewing the working site things appear in the correct place.
On checking the captured CSS it does not match the source
ah, looking in safari and firefox. this is another Chrome is the IE8 of the new millenium since it seems correct in those other browsers 🤣
pauldambra
changed the title
[Bug]: grid template areas are not inlined correctly
[Bug]: grid template areas are not inlined correctly by Chrome
Jan 9, 2024
Resurfacing that this is still an issue. We were using the fix from @pauldambraPR that was closed, but ran into an issue with the regex that solution used. I have opened another PR that tweaks the original to address the issue.
Preflight Checklist
What package is this bug report for?
rrweb
Version
latest v2
Expected Behavior
that the grid-template-area is captured correctly
Actual Behavior
A customer site uses grid template areas in their CSS. When playing back we see the content is not aligned as expected. When viewing the working site things appear in the correct place.
On checking the captured CSS it does not match the source
The source has
but the captured CSS has:
you can see the CSS has been collapsed to a short-hand
grid-template
and lost detail from the originalSteps to Reproduce
You can see a working example of this here: https://jsfiddle.net/pauldambra/oLtcrjm4/10/ showing that the captured CSS has been mangled
Testcase Gist URL
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: