question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue with "env()": compatibility description of "env()" on safari is ambiguous

See original GitHub issue

MDN URL: https://developer.mozilla.org/en-US/docs/Web/CSS/env()

What information was incorrect, unhelpful, or incomplete?

Description of “env()” compatibility table on safari image

Specific section or headline?

Browser compatibility

What did you expect to see?

The description in caniuse is like this, safari 11 and safari on IOS 11.2 supported as constant() instead of env(). and the newer version supports env().

But the description of the MDN page is, safari removed in version 11.1 and later(Alternate name: constant), safari on IOS removed in version 11.3 and later(Alternate name: constant). It misled me to think that env() has been removed in 11.1+ and 11.3+.

Did you test this? If so, how?

MDN Content page report details

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
queengooborgcommented, Jul 27, 2021

It wouldn’t really make much sense to add a note to BCD, since the data’s structure covers the story, and other than an alternative name, it isn’t something like non-spec behavior. (Plus, if we added a note ourselves, then we should add one to all features with an alt. name, which just doesn’t seem right when we already have the machine-readable version.)

I haven’t given much thought to what we could do to update the wording, but one thought I have is perhaps we should swap the position of alt. name + prefix data and the support status? (In other words, the row would read like “Alternative name: constant; Removed in 11.3 and later”)

1reaction
queengooborgcommented, May 30, 2022

@schalkneethling This issue was affected by the idle-autoclose problem, can we reopen?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Yarn2 compatibility · Issue #5135 · vuejs/vue-cli - GitHub
What is expected? Create the project and run yarn serve successfully. What is actually happening? The shell output some errors: ➤ YN0050: The ......
Read more >
env() - CSS: Cascading Style Sheets - MDN Web Docs
The env() CSS function can be used to insert the value of a user-agent defined environment variable into your CSS, in a similar...
Read more >
Options - Babel
The current active environment used during configuration loading. This value is used as the key when resolving "env" configs, and is also available...
Read more >
NODE_ENV value of 'test ' did not match any deployment ...
In your package.json file by omitting the space before && . This will detect the environment(s) correctly without extra space after the name....
Read more >
Java SE 7 Advanced - Oracle
The security baseline for the Java Runtime Environment (JRE) at the time of ... closeEntry() method has been modified to close out the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found