You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Websites need to detect whether an environment variable is support in order to have special rules applied on it. It seems there is currently no way to do that.
for the detection, but the only thing it checks is that env is supported. If you replace safe-area-inset-top with something else like x, all implementations nowadays would still happily accept it. This is problematic for future extensions.
I'm not sure whether #3285 would solve this (and breaks things like env(x) in @supports). If not, we probably need to either special-case the behavior of env in @supports, or introduce a function for it.
The text was updated successfully, but these errors were encountered:
Okay... I cannot think of any usecase. Authors may want to specify different style when certain env is available, but conceptually I think what they would actually want would be to make the page responsive to different value of the env, which should be done with media queries, and in that case, fallback should be enough.
Websites need to detect whether an environment variable is support in order to have special rules applied on it. It seems there is currently no way to do that.
Natively authors would just use something like
for the detection, but the only thing it checks is that
env
is supported. If you replacesafe-area-inset-top
with something else likex
, all implementations nowadays would still happily accept it. This is problematic for future extensions.I'm not sure whether #3285 would solve this (and breaks things like
env(x)
in@supports
). If not, we probably need to either special-case the behavior ofenv
in@supports
, or introduce a function for it.The text was updated successfully, but these errors were encountered: