Browser/Spec bug: Failing test for capturing css shorthand with confounding variable#1322
Browser/Spec bug: Failing test for capturing css shorthand with confounding variable#1322eoghanmurray wants to merge 1 commit intorrweb-io:masterfrom
Conversation
|
|
I think this is the relevant spec issue: |
…n: var(--my-anim);`
4e5af20 to
2d21d1e
Compare
|
Similarly the following would exhibit the problem: |
|
There is a possibility to fix this when we have access to the raw
If they are the same, that means we can trust the For external stylesheets ( This will all be possible in an async manner after #1475 Hat-tip: CSSStylesheet idea was from https://github.com/rrweb-io/rrweb/pull/1357/files#diff-c61c2c2a3a84e2ee30a603d8363a994acce4caef8827931eb5b7317f08b53cb1R588 |
|
This also happens to Edit: Looks like part of this is fixed, the rest is related to w3c/csswg-drafts#2515 as mentioned above. |
This PR contains a new test which shows the failing behaviour;
I can't currently see a way around this, so this is a bug report and maybe a place to link to any bugs in browser version trackers.
#1268 PR (as reported in #1246) is very similar however this version occurs while serializing the static stylesheet, rather than as part of a mutation (where we can work around it)
Problem:
in a stylesheet gets serialized as
I presume a similar thing might happen for e.g.
background: var(--mycolor); background-image: url('x.png');