This typically results in the browser putting that element onto its own compositor layer, making animation updates more efficient. You could also add force3D:false to your tweens and that should remove the blurriness of the image.Īs of 1.15.0, force3D defaults to "auto" mode which means transforms are automatically optimized for speed by using matrix3d() instead of matrix(), or translate3d() instead of translate(). in 2 seconds, fade back in with visibility:visible This makes it simple to start things out on your page as invisible (set your css visibility:hidden) and then fade them in whenever you want. And for convenience, if the element's visibility is initially set to "hidden" and opacity is 1, it will assume opacity should also start at 0. It is not set to "visible" in order to honor inheritance (imagine the parent element is hidden - setting the child to visible explicitly would cause it to appear when that's probably not what was intended). When the value is anything other than 0, visibility will be set to "inherit". Identical to opacity except that when the value hits 0 the visibility property will be set to "hidden" in order to improve browser rendering performance and prevent clicks/interactivity on the target. You just want to add a slight rotation:0.01 to your tweens that use scale and that use x, y, or z to work around this sub-pixel snapping bug in Firefox, MS Edge and IE.Īlso instead of using opacity use autoAlpha for a slight performance goodness. See the Pen zNmeKq by jonathan ( on CodePen I forked your codepen and made some additions: Hello AntalNagy, and Welcome to the GreenSock Forum! Otherwise, why would there be several browsers if they all did the exactly same thing/behaved in the exactly same manner. While the browser wars is a good thing for innovation, it also generates a lot of differences as they all try to do their own thing and stand above the others. I'll try to get it as smooth as possible but there's only so far that I would go. I am tired, i am sad, i don't care anymore.īut, You can find various posts here in this forum like: It is their job to implement the standards perfectly. I feel that, this is not my job to make the animations perfect in every browser. The last known perfect chrome version was v41. I did it, multiple times, but the workarounds aren't working now. I don't have more patience to patch/hack the browsers. I am fighting with these issues since a year and I have to tell that at this point: I don't care if my animations are jerky or stuttering or whatewer weird insane bugs they have in different browsers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |