html - CSS3 Scale property Blurs Result of animationin Google Chrome -


i doing simple animation using scale property facing following problem:

it works fine in mozilla firefox browser blurs result in google chrome when scaled large. why happening? use -webkit- prefix google chrome.

i have following code :

<!doctype html>  <html> <head> <meta charset="utf-8"> <title>free sorry ecard</title>  </script> <style> .background-effect{     height:600px;     width:800px;     width:800px;     position:absolute;     overflow:hidden;     display:block;     z-index:1; }  .b1-heart{     position: absolute;      width: 100px;     height: 90px;      top:250px;     left:350px;     opacity:0;     -moz-animation: heartbeat 4s linear 0s infinite;     -webkit-animation: heartbeat 4s linear 0s infinite; }  .b1-heart:before, .b1-heart:after{     position: absolute; content: ""; left: 50px; top: 0; width: 50px;   height: 80px;      background: #ff0066; -moz-border-radius: 50px 50px 0 0; border-radius: 50px 50px 0 0; -webkit-transform: rotate(-45deg); -moz-transform: rotate(-45deg);-ms-transform: rotate(-45deg); -o-transform: rotate(-45deg); transform: rotate(-45deg); -webkit-transform-origin: 0 100%; -moz-transform-origin: 0 100%; -ms-transform-origin: 0 100%; -o-transform-origin: 0 100%; transform-origin: 0 100%;  } .b1-heart:after { left: 0; -webkit-transform: rotate(45deg); -moz-transform: rotate(45deg); -ms-transform: rotate(45deg); -o-transform: rotate(45deg); transform: rotate(45deg); -webkit-transform-origin: 100% 100%; -moz-transform-origin: 100% 100%; -ms-transform-origin: 100% 100%; -o-transform-origin: 100% 100%; transform-origin :100% 100%;}    @-moz-keyframes heartbeat{     0%{-moz-transform:scale(1);opacity:0;}     50%{-moz-transform:scale(5);opacity:.5;}     100%{-moz-transform:scale(10);opacity:0;}  }@-webkit-keyframes heartbeat{     0%{-webkit-transform:scale(1);opacity:0;}     50%{-webkit-transform:scale(5);opacity:.5;}     100%{-webkit-transform:scale(10);opacity:0;}  }  .b3-heart{     position: absolute;      width: 100px;     height: 90px;      top:350px;     left:50px;     opacity:.2;     -moz-animation: heartbeat 1.5s linear 0s infinite;     -webkit-animation: heartbeat 1.5s linear 0s infinite; }  .b3-heart:before, .b3-heart:after{     position: absolute; content: ""; left: 50px; top: 0; width: 50px;   height: 80px;      background: #00ccff; -moz-border-radius: 50px 50px 0 0; border-radius: 50px 50px 0 0; -webkit-transform: rotate(-45deg); -moz-transform: rotate(-45deg);-ms-transform: rotate(-45deg); -o-transform: rotate(-45deg); transform: rotate(-45deg); -webkit-transform-origin: 0 100%; -moz-transform-origin: 0 100%; -ms-transform-origin: 0 100%; -o-transform-origin: 0 100%; transform-origin: 0 100%;  } .b3-heart:after { left: 0; -webkit-transform: rotate(45deg); -moz-transform: rotate(45deg); -ms-transform: rotate(45deg); -o-transform: rotate(45deg); transform: rotate(45deg); -webkit-transform-origin: 100% 100%; -moz-transform-origin: 100% 100%; -ms-transform-origin: 100% 100%; -o-transform-origin: 100% 100%; transform-origin :100% 100%;}   .b2-heart{     position: absolute;      width: 100px;     height: 90px;      top:350px;     right:50px;     opacity:.2;     -moz-animation: heartbeat 1.5s linear 0s infinite;     -webkit-animation: heartbeat 1.5s linear 0s infinite; }  .b2-heart:before, .b2-heart:after{     position: absolute; content: ""; left: 50px; top: 0; width: 50px;   height: 80px;      background: #00ccff; -moz-border-radius: 50px 50px 0 0; border-radius: 50px 50px 0 0; -webkit-transform: rotate(-45deg); -moz-transform: rotate(-45deg);-ms-transform: rotate(-45deg); -o-transform: rotate(-45deg); transform: rotate(-45deg); -webkit-transform-origin: 0 100%; -moz-transform-origin: 0 100%; -ms-transform-origin: 0 100%; -o-transform-origin: 0 100%; transform-origin: 0 100%;  } .b2-heart:after { left: 0; -webkit-transform: rotate(45deg); -moz-transform: rotate(45deg); -ms-transform: rotate(45deg); -o-transform: rotate(45deg); transform: rotate(45deg); -webkit-transform-origin: 100% 100%; -moz-transform-origin: 100% 100%; -ms-transform-origin: 100% 100%; -o-transform-origin: 100% 100%; transform-origin :100% 100%;}   .b4-heart{     position: absolute;      width: 100px;     height: 90px;      top:550px;     right:350px;     opacity:.2;     -moz-animation: heartbeat 2s linear 0s infinite;     -webkit-animation: heartbeat 2s linear 0s infinite; }  .b4-heart:before, .b4-heart:after{     position: absolute; content: ""; left: 50px; top: 0; width: 50px;   height: 80px;      background: #fff000; -moz-border-radius: 50px 50px 0 0; border-radius: 50px 50px 0 0; -webkit-transform: rotate(-45deg); -moz-transform: rotate(-45deg);-ms-transform: rotate(-45deg); -o-transform: rotate(-45deg); transform: rotate(-45deg); -webkit-transform-origin: 0 100%; -moz-transform-origin: 0 100%; -ms-transform-origin: 0 100%; -o-transform-origin: 0 100%; transform-origin: 0 100%;  } .b4-heart:after { left: 0; -webkit-transform: rotate(45deg); -moz-transform: rotate(45deg); -ms-transform: rotate(45deg); -o-transform: rotate(45deg); transform: rotate(45deg); -webkit-transform-origin: 100% 100%; -moz-transform-origin: 100% 100%; -ms-transform-origin: 100% 100%; -o-transform-origin: 100% 100%; transform-origin :100% 100%;}   </style>  </head> <body>   <div id="container1">      <div class="background-effect">        <div class='b1-hearts'></div>       <div class='b2-hearts'></div>       <div class='b3-hearts'></div>       <div class='b4-hearts'></div>      </div>  </div>  </body> </html>


-

Comments

Post a Comment

Popular posts from this blog

how to proxy from https to http with lighttpd -

i have internal site (192.168.2.1) accessible http on different server run public web-server using lighttpd. can make internal site accessible outside work follows $http["host"] == "internal.example.com" { ... proxy.server = ( "" => ( "internal" => ( "host" => "192.168.2.1", "port" => 8000 ) ) } this works, use https outside world. question is, how can proxy going https http ? i've tried this: $server["socket"] == ":443" { $http["host"] == "internal.example.com" { ... proxy.server = ( "" => ( "internal" => ( "host" => "http://192.168.2.1", "port" => 8000 ) ) } } but doesn't seem wor...
Read more

android - Automated my builds -

i have multiple app , android project want automated in build , release sequence. have ant script build , create apk of app. want have 1 script or ant file start build sequence app. maybe don't konw search, can't find easy documentation on ant. the point of use jenkins ant (or maven, i'm not sure of difference between them now) automated build sequence when people commit on project. any int appreciated maven dependencies (over ant) don't need pass around jars. recommend maven on ant day. syntax , overall process easier understand, @ end of both build tools. if able to, more recommend upgrading gradle. easy create different build types , create them ./gradlew assemble here project jake wharton can see power of gradle. there release , debug build, can make lot more if like. https://github.com/jakewharton/u2020 here android docs gradle http://tools.android.com/tech-docs/new-build-system/user-guide . if can't find looking here, check out main grad...
Read more

python - Flask migration error -

i've got application build on flask , wanted create new migration today. when run $python manage.py db upgrade i got message raise util.commanderror('only single head supported. ' alembic.util.commanderror: single head supported. script directory has multiple heads (due branching), must resolved manually editing revision files form linear sequence. run alembic branches see divergence(s). so run command $alembic branches no config file 'alembic.ini' found, or file has no '[alembic]' section any clue on about? the error messages coming alembic, use command form alembic <command> , integrating flask coming flask-migrate, need use form python manage.py db branches . to resolve multiple branches, make 1 of branches point down other branch upgrade graph straight line. see alembic's docs on branches: http://alembic.readthedocs.org/en/latest/branches.html
Read more