So I wanted to test the stacking context and grouping effects of offset-path, so I thought I'd look for a value of offset-path that: (a) was supported in Firefox and Chrome and (b) didn't cause the element to move at all.
(The goal was a row in dbaron.org/css/test/2018/sta… .)
1
3
It turned out interoperability of CSS Motion Path (drafts.fxtf.org/motion-1/) is not very good... and I couldn't actually find a value that did what I wanted without falling back to a degenerate path ("M 0 0").
1
Some of the things I tried are in the demo at dbaron.org/css/test/2021/off… . Interoperability is not good... and wpt.fyi/results/css/motion?l… doesn't have very many tests.
1
1
Based on my very limited understanding of the spec, it seems like both implementations are both quite incomplete (in different ways) and have a number of bugs. But the spec is quite complicated, and I'm really not sure.
Jun 10, 2021 · 5:50 PM UTC
1
