hiro, do you know if there's a bug tracking this issue (about animations on compositor vs. non-compositor getting reset in out-of-sync ways. such that we draw a background-color into a shape of the wrong size)? I wonder if this is perhaps just an unfortunate side effect of having a single element that has animations running on+off the compositor simultaneously, whenever there's a bad outcome from "looping" the properties in a slightly out-of-sync way... I imagine the recommended way to avoid this would be to (in this case) run both animations on the compositor, i.e. to use `scale` instead of `width`/`height` for growing the "waves" in the Asus animation (using a small-but-nonzero starting width of course, so that we have something to scale). Though I don't know if we'd be able to get them to make that change in this case, and it might be worth mitigating this on our end if we have some way to do so...
Bug 1760795 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
hiro, do you know if there's a bug tracking this issue (about animations on compositor vs. non-compositor getting reset in out-of-sync ways, such that we e.g. draw a background-color into a shape of the wrong size)? I wonder if this is perhaps just an inevitable side effect of having a single element that has animations running on+off the compositor simultaneously, whenever there's a bad outcome from "looping" the properties in a slightly out-of-sync way... I imagine the recommended way to avoid this would be to (in this case) run both animations on the compositor, i.e. to use `scale` instead of `width`/`height` for growing the "waves" in the Asus animation (using a small-but-nonzero starting width of course, so that we have something to scale). Though I don't know if we'd be able to get them to make that change in this case, and it might be worth mitigating this on our end if we have some way to do so...
hiro, do you know if there's a bug tracking this issue (about animations on compositor vs. non-compositor getting reset in out-of-sync ways, such that we e.g. draw a background-color into a shape of the wrong size)? I wonder if this is perhaps just an inevitable side effect of having a single element that has animations running on+off the compositor simultaneously. I imagine the recommended way to avoid this would be to (in this case) run both animations on the compositor, i.e. to use `scale` instead of `width`/`height` for growing the "waves" in the Asus animation (using a small-but-nonzero starting width of course, so that we have something to scale). Though I don't know if we'd be able to get them to make that change in this case, and it might be worth mitigating this on our end if we have some way to do so...
hiro, do you know if there's a bug tracking this issue (about animations on compositor vs. non-compositor getting reset in out-of-sync ways, such that we e.g. draw a background-color into a shape of the wrong size)? I wonder if this is perhaps just an inevitable side effect of having a single element that has animations running on+off the compositor simultaneously. I imagine the recommended way to avoid this would be to (in this case) run both animations on the compositor, i.e. to use `transform:scale(...)` instead of `width`/`height` for growing the "waves" in the Asus animation (using a small-but-nonzero starting width of course, so that we have something to scale). Though I don't know if we'd be able to get them to make that change in this case, and it might be worth mitigating this on our end if we have some way to do so...