4 ms·

So, the standard for constant() will have a different name/syntax but they put it without any prefix? Why?

• alwillis 9y ago
  The current consensus among browser implementors is that, on the whole, prefixed properties have hurt more than they’ve helped. So, WebKit’s new policy is to implement experimental features unprefixed, behind a runtime flag.: https://webkit.org/blog/6131/updating-our-prefixing-policy/ https://webkit.org/blog/6131/updating-our-prefixing-policy/ As the article states, prefixes have created a set of problems, which is why Apple, Google, Mozilla and Microsoft stopped using them for new features.
  • pietroalbini 9y ago
    But the things they added aren't behind a runtime flag, but enabled by default and without any prefix, yet not standardized.
    • alwillis 9y ago
      Because these specs are in progress at the W3C, so they don't need to be prefixed or hidden in some way: https://news.ycombinator.com/item?id=15314812 https://news.ycombinator.com/item?id=15314812 min() and max() Haven't been enabled in iOS 11 yet, as the article states.
    • gsnedders 9y ago
      https://www.w3.org/TR/css-2017/#future-proofing https://www.w3.org/TR/css-2017/#future-proofing is the current WG policy. I have no idea whether or not there's a WG resolution because the WG is terrible at tracking resolutions.