internet explorer - Will Microsoft Edge use prefixes like -webkit- or -ms-? -
will microsoft edge use prefixes -webkit-
, -ms-
, or own new prefix future functions? -me-
, perhaps?
tl;dr: yes , no
existing prefixed properties hugely popular remain until have native support, microsoft edge not introducing new prefix system features. instead, they'll use feature flags (like chrome , firefox experimental features on client side, rather developer side).
some of more notable removals microsoft edge supports latest standard api definition , removes support ms prefixed versions of apis. examples include css transforms, fullscreen api, , pointer events. brings important topic: vendor prefixes. you’ll see trend in vendor prefixes in microsoft edge compared ie:
our support (or lack thereof) of prefixed apis data-driven compatibility sole purpose remain. examples, -webkit-border-radius still in use on over 60% of page loads , ms-prefixed encrypted media extensions apis still in use on top video streaming services. because of impact on interoperability across web, these supported in microsoft edge time being.
the consensus across the industry vendor prefixes cause more harm , necessity of browsers supporting other vendor’s prefixes example of why. going forward, we’re using feature flags (accessible navigating about:flags) introduce experimental apis , minting new vendor prefixed apis sparingly, if ever. today, you’ll find examples implementations of css filters, touch events, , html5 date inputs in about:flags. we’re working other browser vendors on exploring new approaches experimental apis enable easier , broader access experimental apis while minimizing compatibility burden prefixes incur. check out this talk (starts around 31 min mark) initial proposal we’ve made, tentatively named “api trials”.
(emphasis mine)
Comments
Post a Comment