vendor-prefix

问题 Will Microsoft Edge use prefixes like -webkit- , -ms- , or its own new prefix for future functions? Something like -me- , perhaps? 回答1: tl;dr: Yes and No Existing prefixed properties that are hugely popular will remain until they have native support, but Microsoft Edge will not be introducing a new prefix system for features. Instead, they'll use feature flags (like Chrome and Firefox for experimental features on the client side, rather than the developer side). Direct Source Some of the more

问题 As the title states I was wondering if this should be used. According to MS documentation simply using "animation" is now the default for IE10 (which is why i had a green squiggle) After looking this up and fixing it, I wondered, should I still include this line "-ms-animation" Can anyone say if it is needed for older browsers, or did removing the need for an "-ms" prefix apply retroactively? 回答1: The -ms- prefix was required for animations, transitions, gradients and font-feature-settings in

问题 If I were writing a JavaScript line to set a style attribute of an element it could look like this (this example: "width"): document.getElementById('myDiv').style.width="50px"; and if there is a dash in the CSS element it would look like this (this example: "margin-top"): document.getElementById('myDiv').style.marginTop="15px"; But how do I access the prefix -webkit- , if I want to give it a style like this example: {-webkit-transition: width 1s;} 回答1: You have two options: style["-webkit

问题 This question already has answers here : Why do browsers create vendor prefixes for CSS properties? (2 answers) Closed 5 months ago . I know that if we want to make sure some CSS3 features work everywhere we need to use the prefixed versions of the W3C recommended one like: transition: all 1s ease; -moz-transition: all 1s ease; -o-transition: all 1s ease; -webkit-transition: all 1s ease; I know that the prefixes are used for experimental features, but why are they necessary? Why don't they

问题 I was testing some CSS3 stuff and I discovered that some properties like border-radius don't need the vendor prefix anymore (at least on recent up to date browsers). My next website will only target recent browsers like IE9/Chrome 15+/FF8+, so I was wondering: Is there a list of the current CSS3 properties where I can see which of them I can safely drop vendor prefixes for? Note: I'm not interested in JS hacks that automatically insert prefixed properties. 回答1: When can I use... contains

问题 I think I've written something like the following a thousand times now: .foo { border-radius: 10px; /* W3C */ -moz-border-radius: 10px; /* Mozilla */ -webkit-border-radius: 10px; /* Webkit */ } But only now have I thought about whether the ordering of those is important? I know that between -moz-* and -webkit-* it doesn't matter, since at most 1 of those will be read, but is it better (in terms of future-proofing, etc) to do the W3C standard first or last? 回答1: The best practise is

问题 I'm styling placeholder text, and need to use several vendor-prefixed selectors so that it works in different browsers. When I put each of them as a separate code block, it works. However, if I use a comma-separated list of selectors instead of repeating the same CSS for each of them, it won't work. Can anyone explain? This works: input[type=text]::-webkit-input-placeholder { color: green; } input[type=text]::-moz-placeholder { color: green; } input[type=text]:-ms-input-placeholder { color:

问题 Since this code works with the -moz vendor prefix I thought it would work a well with -webkit or -ms for instance, but it doesn't seem to allow it: background-image: -moz-linear-gradient(center top , rgba(255, 255, 255, 0) 0%, rgba(255, 255, 255, 0) 75%, rgba(255, 255, 255, 0.95) 100%); I guess Mozilla is allowing something that shouldn't be used, but my research has been infructuous as of now... Any idea? 回答1: Remove the center . Then it should work. Also make sure you have it for all

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 5 years ago . As far as I know the only reason behind usage of vendor prefixes is that they were introduced by browser creators to release a new specification before its completely implemented according to W3C But why need a specific vendor prefix for every browser. If we look at the

问题 This question already has answers here : Why do browsers create vendor prefixes for CSS properties? (2 answers) Closed 4 years ago . I could understand using them for experimental things that aren't official (ie; not in the CSS3 spec) to prevent name collisions, but why the need for prefixes on shadowing and such? Shouldn't each vendor be implementing the effects the same, as per the CSS3 specs? EDIT: Will the prefixes go away once CSS3 is finalized? I just am curious about the history of why