Safari Technology Preview supports `safe` and `unsafe` in Flex layout about browser-compat-data HOT 2 OPEN

Also, looking at the tables on Can I Use — the footnotes are assigned to odd places.

For example, for Chrome the note is "Before version 115, this value is recognized, but has no effect." This footnote should not be on Chrome 115+. It should be on the versions where this was true, presumably version 114, 113, 112... back to whenever the parsing was first implemented. The boxes representing Chrome 114, 113 and prior should be red (as they are) with the footnote. And then, for Chrome 115, the box should be green without any footnote.

Once this change is made, there's only one footnote needed (rather than one for each Chromium browser). The new note can simply say: "This value is recognized, but has no effect." Or perhaps we should add more that explains feature queries will not work properly. Something like: "Testing with a feature query will show support, but only parsing was implemented, not the feature's functionality" or something. That one footnote can be applied to all the versions where it is the case — instead of all the versions where it is not the case.

from browser-compat-data.

It's likely that these "value is recognized, but has no effect" browser versions deserve partial support — with a footnote that says something like:

[1] Supports unsafe, and returns true for Feature Query tests of safe, but does not support safe.

This is because for Flexbox unsafe is the same behavior as no keyword being present, so therefore once it parses, it's correct & supported. But this still means "partial", since the table cell is about both safe and unsafe.

from browser-compat-data.