Sam Atkins 89b59cb5c3 LibWeb/CSS: Implement env() as an arbitrary substitution function ... Technically, env() should not be an ASF. (😱) This is why some tests still fail - env() as specced is expected to have its syntax checked fully at parse-time, whereas ASFs are not properly syntax-checked until later. However, I think this approach was worth doing for a few reasons: - env() behaves like an ASF otherwise. (It is replaced with a set of arbitrary component-values that are not known until computed-value time.) - env() was defined before the ASF concept existed, so I strongly suspect it will be updated in the future to match that definition, with a couple of adjustments. (eg, env() is allowed in some extra places compared to var() and attr().) - This was much quicker and easier to implement (under 3 hours in total) compared to the greater amount of work to implement a whole separate system just for env(). - Most of these tests are marked tentative, and the spec definition of env() is still somewhat in flux, so failing some is not a huge deal. If in the future I turn out to be wrong on this, we can convert it to its own special thing.		2025-08-07 16:38:29 +02:00
..
at-supports.tentative.txt
env-in-custom-properties.tentative.txt
env-parsing.txt
fallback-nested-var.tentative.txt
indexed-env.tentative.txt
seralization-round-tripping.tentative.txt
supports-script.tentative.txt
syntax.tentative.txt
unknown-env-names-override-previous.tentative.txt