Microsoft Edge 会使用 -webkit- 或 -ms- 之类的前缀吗？
Will Microsoft Edge use prefixes like -webkit- or -ms-?
Microsoft Edge 会使用 -webkit-、-ms- 之类的前缀，还是会为未来的功能使用自己的新前缀？可能是 -me- 之类的东西？
如果CSS标签是已经被所有浏览器接受的网络标准，则无需为其添加前缀。
否则，如果你想使用 CSS 标签来针对浏览器的实验性功能，那么你需要包含 -ms 供应商前缀以使该功能在 Microsoft Edge 上运行，类似于为该标签添加 -webkit 以在 Chrome.
tl;dr：是和否
非常受欢迎的现有前缀属性将一直保留，直到获得本机支持，但 Microsoft Edge 不会 为功能引入新的前缀系统。相反，他们将使用功能标志（如 Chrome 和 Firefox 在客户端而非开发人员端使用实验性功能）。
Some of the more notable removals are those where Microsoft Edge supports the latest standard API definition and removes support for MS prefixed versions of the APIs. Examples include CSS Transforms, Fullscreen API, and Pointer Events. This brings up an important topic: vendor prefixes. You’ll see a trend in the vendor prefixes in Microsoft Edge compared to IE:
Our support (or lack thereof) of prefixed APIs is data-driven with compatibility as the sole purpose for any that remain. As examples, -webkit-border-radius is still in use on over 60% of page loads and the MS-prefixed Encrypted Media Extensions APIs are still in use on top video streaming services. Because of the impact on interoperability across the Web, these are supported in Microsoft Edge for the time being.
The consensus across the industry is that vendor prefixes cause more harm than good and the necessity of browsers supporting other vendor’s prefixes is a good example of why. Going forward, we’re using feature flags (accessible by navigating to about:flags) to introduce experimental APIs and minting new vendor prefixed APIs sparingly, if ever. Today, you’ll find examples like early implementations of CSS Filters, Touch Events, and HTML5 date inputs in about:flags. We’re also working with other browser vendors on exploring new approaches to experimental APIs that enable easier and broader access to experimental APIs while minimizing the compatibility burden that prefixes incur. Check out this talk (starts around 31 min mark) for an initial proposal we’ve made, tentatively named “API Trials”.
（强调我的）
此处提供 Microsoft Edge 支持的 WebKit 属性的详细列表：https://msdn.microsoft.com/en-us/library/mt270097%28v=vs.85%29.aspx
Microsoft Edge 会使用 -webkit-、-ms- 之类的前缀，还是会为未来的功能使用自己的新前缀？可能是 -me- 之类的东西？
如果CSS标签是已经被所有浏览器接受的网络标准，则无需为其添加前缀。 否则，如果你想使用 CSS 标签来针对浏览器的实验性功能，那么你需要包含 -ms 供应商前缀以使该功能在 Microsoft Edge 上运行，类似于为该标签添加 -webkit 以在 Chrome.
tl;dr：是和否
非常受欢迎的现有前缀属性将一直保留，直到获得本机支持，但 Microsoft Edge 不会 为功能引入新的前缀系统。相反，他们将使用功能标志（如 Chrome 和 Firefox 在客户端而非开发人员端使用实验性功能）。
Some of the more notable removals are those where Microsoft Edge supports the latest standard API definition and removes support for MS prefixed versions of the APIs. Examples include CSS Transforms, Fullscreen API, and Pointer Events. This brings up an important topic: vendor prefixes. You’ll see a trend in the vendor prefixes in Microsoft Edge compared to IE:
Our support (or lack thereof) of prefixed APIs is data-driven with compatibility as the sole purpose for any that remain. As examples, -webkit-border-radius is still in use on over 60% of page loads and the MS-prefixed Encrypted Media Extensions APIs are still in use on top video streaming services. Because of the impact on interoperability across the Web, these are supported in Microsoft Edge for the time being.
The consensus across the industry is that vendor prefixes cause more harm than good and the necessity of browsers supporting other vendor’s prefixes is a good example of why. Going forward, we’re using feature flags (accessible by navigating to about:flags) to introduce experimental APIs and minting new vendor prefixed APIs sparingly, if ever. Today, you’ll find examples like early implementations of CSS Filters, Touch Events, and HTML5 date inputs in about:flags. We’re also working with other browser vendors on exploring new approaches to experimental APIs that enable easier and broader access to experimental APIs while minimizing the compatibility burden that prefixes incur. Check out this talk (starts around 31 min mark) for an initial proposal we’ve made, tentatively named “API Trials”.
（强调我的）
此处提供 Microsoft Edge 支持的 WebKit 属性的详细列表：https://msdn.microsoft.com/en-us/library/mt270097%28v=vs.85%29.aspx