Philip Jägenstedt

I'm interested in this issue because it's a large chunk of failures in https://wpt.fyi/compat2021?feature=css-flexbox and am trying to understand, with the help of @svillar. I'm wondering about these two comments:...

OK, so interpreting that, there's not interop currently, Firefox has one behavior and Chrome+Safari have a largely matching but different behavior. This matches the test results here: https://wpt.fyi/results/css/css-flexbox/abspos?run_id=5121058602483712&run_id=5638952738357248&run_id=5721849096830976 Since someone...

No worries, I'm just stalking this thread and don't really understand the background and context here. If use counters are being added, it seems like there's a clear next step...

Is the issue here the belief that 水 was picked by accident because someone conflated it with 永? @fantasai disconfirmed that in https://twitter.com/fantasai/status/1555385335663759360, and I wonder if the same issue...

In the case of flex gap specifically, is there *any* workaround for web developers to detect support for it? It's only recently shipped in Chrome and even more recently landed...

Thanks @Dan503! I guess what people then typically to do is set a class on the body element and use that instead of `@supports`?

I should say also that I'm not sure I understand the relationship between the properties named `font-variant-*` and the descriptors, and if support for one implies support for the other....

Thanks for looking into this so quickly, @pmeenan!

@ShijunS @jan-ivar @youennf, can you comment or find others for Edge/Gecko/WebKit who could?

Just changing the order of the events there should fix the problem, implementation-wise I guess it's simple enough?