I'm trying to find out if I need to include the -o-animation vendor prefix in my CSS, but I can't seem to find any resources which indicates it exists, and if it does, what versions of Opera it applies to.
Can anyone offer some suggestions?
The -o-animation vendor prefix is no longer required for Opera, unless you need to support old Opera v12.** versions.
Instead, use the -webkit-animation vendor prefix to support newer Opera.
According to Opera 12.10 release notes, you didn't need the -o- vendor prefix from that version on. Adding -o- was therefore just needed to support Opera 12.0x versions.
Related
I am following an tutorial that is typing -webkit-box-sizing: border-box; in the style.css nothing seems to happen when I write it... I am on windows and using atom. is it something you need to download? I understand an engine and something to do with animation in chrome/safari.
No need to download anythig. webkit is one of the prefixes used to make experimental css properties work for other browsers, they are temporary and you should remove them from your code once a property is fully supported by all browsers.
This is a list of prefixes used:
-webkit- (Chrome, Safari, iOS Safari / iOS WebView, Android)
-moz- (Firefox)
-ms- (Edge, Internet Explorer)
-o- (Opera, Opera Mini)
to determine if a property need vendor prefixes or not, use Can I Use they mention on the notes if the property searched is experimental.
once you found that you need to use prefixes, here is an easy tool to auto-prefix
AutoPrefixes
the following are some articles for more in depth reading:
https://flaviocopes.com/css-vendor-prefixes/
https://www.lifewire.com/css-vendor-prefixes-3466867
https://bitsofco.de/css-vendor-prefixes/
There are a lot of vendor prefixes that try to make cross browsers compatibility between the old and new versions ...
my question is it temporary until all old browsers disappear or updated and then no need for it ?
Or we can depend on it when a new level of css shipping to cover maybe the gab between supported and unsupported browsers again?
Thanks
There's a long answer here, i'll try the short one first.
The vendor tags are a tryhard to avoid glitches or the no-rendering of some properties/attributes. If you need to support an old browser that is obsolete and unsupported you may need those vendor tags. If you are working on browsers with support, when they are updated, this vendor tags will not be necessary anymore.
Are there any update timeline to know when and when not a vendor tag is needed? No
Can we check if some vendor tag is needed on some property? Yes, here, if you want to support a browser that is not capable to run some property, try adding vendor tag.
Remember that vendor tag is not a magician, and it can't render things, the capability of the render engine dealing with vendor tags is different on all versions of the same browser, so i recommend you to check if it really works.
Looking to a realistic future, vendor tags will keep working as they worked till nowadays, giving mostly cross-browser compatibility between older and newer versions.
Historically, vendors have also used prefixes for experimental APIs. If an entire interface is experimental, then the interface's name is prefixed (but not the properties or methods within). If an experimental property or method is added to a standardized interface, then the individual method or property is prefixed.
Interface prefixes
Prefixes for interface names are upper-cased:
WebKit (Chrome, Safari, newer versions of Opera, almost all iOS browsers (including Firefox for iOS); basically, any WebKit based browser)
Moz (Firefox)
O (Older, pre-WebKit, versions of Opera)
MS (Internet Explorer and Microsoft Edge)
Property and method prefixes
The prefixes for properties and methods are lower-case:
webkit (Chrome, Safari, newer versions of Opera, almost all iOS browsers (including Firefox for iOS); basically, any WebKit based browser)
moz (Firefox)
o (Old, pre-WebKit, versions of Opera)
ms (Internet Explorer and Microsoft Edge)
Remember that saying "experimental" is subjective, for example, background-size was experimental on I.E. 8, Chrome 3 and FF 3 but it had native support on versions 9, 4 and 4 respectivelly.
Now, to answer your questions with the info:
Vendor prefixes are made to be temporary (till browsers support the feature you're prefixing), but you'll need to add vendor prefixes to new "experimental" features if you want to use it, so yes, you'll need vendor prefixes in a future, but to add cross browser compatibility on different properties etc.
Can we stop to add -o- prefix in css for opera browser or not. I ask this question because opera browser move to web-kit engine.
Thanks in advance.
Opera supports certain -webkit- prefixes and will use these when applying styles as described here.
But if you want to support older versions is better to use.
Windows Internet Explorer 8. The -ms-accelerator attribute is an extension to CSS, and can be used as a synonym for accelerator in IE8 Standards mode.
This text is from the MSDN reference.
I'm not sure, should I use -ms vendor in this case or not.
Can be used as a synonym - they mean I can ommit a vendor prefix, or it should be used for ie8?
This question isn't specific for accelerator only.
-ms- is simply Trident's prefix. Like -webkit- is for webkit, -moz- for gecko, and so on and so forth. It's simply used to trial experimental features.
I have bits and pieces of CSS that use the -webkit- vendor prefix. For compatibility with "older" versions of Safari, I have the same rule with the -khtml- vendor prefix. I am actively uninterested in compatibility with Konqueror and other true KHTML browsers.
For example, I may have the following rules:
.menuItem {
-khtml-user-select: none;
-webkit-user-select: none;
}
I understand that modern WebKit browsers internally rewrite all -khtml- and -apple- rules to be -webkit- rules instead. However, that leaves me with the following question:
In what version of Safari did -webkit- become available? That is, what is the version before which Safari would completely ignore my rules?
I plan to use this information to find out whether my individual rules (such as -khtml-user-select) are actually supported by this early version of Safari.
The -webkit- prefix has been around since Safari 3. The -khtml- references in Safari 2 were replaced from that point on.
References
Webkit 63854 Changelog
Chromium Changelog
Webkit Bug 42990
Unforking of KHTML and WebKit
Interview with Lars Knoll, creator of KHTML
Companies and Organizations that have contributed to WebKit
konqueror/kcmcss.cpp at master ยท KDE/konqueror
The only browser that uses the -khtml- prefix now is a Konqueror, since it have a very little market share (less than 1%), you can drop it safely.
Basically very less people uses Konqueror, So it is not necessary to use -khtml- prefix
But if required you, can only use this with the -khtml- prefix