css3 - What is the right combination of prefixes for CSS transitions and transforms? -

-

what right way prefix css in order cover widest range of browsers , versions?

version 1: 

-webkit-transition: -webkit-transform .3s ease-in-out;    -moz-transition:    -moz-transform .3s ease-in-out;     -ms-transition:     -ms-transform .3s ease-in-out;      -o-transition:      -o-transform .3s ease-in-out;         transition:         transform .3s ease-in-out;   -webkit-transform: rotatex(-30deg);     -moz-transform: rotatex(-30deg);      -ms-transform: rotatex(-30deg);       -o-transform: rotatex(-30deg);          transform: rotatex(-30deg);

or version 2: 

-webkit-transition: transform .3s ease-in-out;    -moz-transition: transform .3s ease-in-out;     -ms-transition: transform .3s ease-in-out;      -o-transition: transform .3s ease-in-out;         transition  transform .3s ease-in-out;   -webkit-transform: rotatex(-30deg);     -moz-transform: rotatex(-30deg);      -ms-transform: rotatex(-30deg);       -o-transform: rotatex(-30deg);          transform: rotatex(-30deg);

it appears me when using vendor prefixes on transition property, should target vendor prefixed attribute want transition.

i can't find closure this.

as mentioned in very similar question...

this 1 of cases vendor prefixes standardized features become extremely problematic, because need account different prefixed and/or unprefixed implementations of different features in different versions of different browsers.

what mouthful. , have combine various permutations of these. handful.

in short, need figure out versions of each browser requires prefix each of individual properties, , unless don't mind bloat, need apply prefixes differently individual browsers.

the linked question refers animations rather transitions results in different notations, both features went through similar unprefixing processes afaik. being said, here compatibility tables caniuse.com 2d transforms , transitions.

in other words, because 1 feature prefixed in 1 version of 1 browser doesn't mean other feature prefixed in same version of same browser. example, chrome unprefixed transitions @ least ten major versions (26) before unprefixed transforms (36), , safari still requires prefixes transforms. result, you're going have have declaration:

transition: -webkit-transform .3s ease-in-out;

and if absolutely need to, have cover older versions following:

-webkit-transition: -webkit-transform .3s ease-in-out;

other browsers, miraculously, able unprefix both transitions , transforms (as animations) simultaneously, makes things easier:

  • -ms-transition used pre-release versions of ie10, have long since expired. no other version of ie uses prefixed transitions, should remove particular transition prefix.

    -ms-transform prefix used ie9; ie10 , later ship unprefixed transforms. purposes of graceful degradation may want keep -ms-transform: rotatex(-30deg); declaration — keep in mind cannot transitioned ie9 not support css transitions or animations.

  • -moz-transition , -moz-transform used firefox , including 15, unprefixed in 16.

  • -o-transition , -o-transform used opera , including 12.00, unprefixed in 12.10, re-prefixed -webkit- in later versions in move blink.

in summary, here prefixes need, based on information given caniuse.com (which trust current , accurate part):

-webkit-transition: -webkit-transform .3s ease-in-out; /* chrome < 26, safari < 7 */    -moz-transition:    -moz-transform .3s ease-in-out; /* firefox < 16 */      -o-transition:      -o-transform .3s ease-in-out; /* opera < 12.10 */         transition: -webkit-transform .3s ease-in-out; /* chrome 26-35, safari, opera 15-23 */         transition:         transform .3s ease-in-out; /* ie10+, firefox 16+, chrome 36+, opera 12.10 */   -webkit-transform: rotatex(-30deg);     -moz-transform: rotatex(-30deg);      -ms-transform: rotatex(-30deg); /* graceful degradation in ie9, cannot transitioned */       -o-transform: rotatex(-30deg);          transform: rotatex(-30deg);

the bare minimum need support latest version of each browser of writing is:

        transition: -webkit-transform .3s ease-in-out; /* chrome 26-35, safari, opera 15-23 */         transition:         transform .3s ease-in-out; /* ie10+, firefox 16+, chrome 36+, opera 12.10 */   -webkit-transform: rotatex(-30deg);          transform: rotatex(-30deg);

as mentioned in comments, can use tool autoprefixer automate based on level of browser support require. however, prefer write css manually, or wondering prefixes needed browsers, it.

on final note: notice 2 unprefixed transition declarations in above examples? now, you'd think it'd easy enough combine them single declaration this:

transition: -webkit-transform .3s ease-in-out, transform .3s ease-in-out;

but, unfortunately, chrome erroneously ignore declaration, while other browsers apply fine.


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more