[Webkit-unassigned] [Bug 281647] New: iOS 18 animations using "infinite"

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=281647

            Bug ID: 281647
           Summary: iOS 18 animations using "infinite"
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Animations
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: kirsten.frager at hotmail.com
                CC: graouts at apple.com

I have a page that has a pulsing div animation which uses the animation-iteration-count: infinite

With users running iOS 18 and up, this animation now break if any other animation (e.g. toggling a  or dropping of a modal takes place somewhere else in the application. 

For example, I have a tab structured application which means that if a user navigates to another tab, that previous page will not have been ngDestroy-ed. User encounters an animation somewhere else on the platform, then goes back to the original tab where the pulsing div is. This is now displaying with no animation anymore as if the "infinite" count has been removed. When inspecting the element, the css still shows all the correct tags. Destroying the page and navigating back to it, renders the animation correctly again with infinite iteration count until the user encounters another animation.

This is only happening on iOS 18 platforms.

For reference the code animation is as follows:


<div class="blip-pulse position-absolute top-0 bottom-0 end-0 start-0 rounded-circle"></div>


.blip-pulse {
  animation-name: marketBlipAnimation;
  animation-duration: 3s;
  animation-iteration-count: infinite;
}

@keyframes marketBlipAnimation {
  0% {
    -webkit-transform: scale(0.3);
    transform: scale(0.3);
    opacity: 0.9;
  }
  100% {
    -webkit-transform: scale(0.9);
    transform: scale(0.9);
    opacity: 0;
  }
}

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20241017/f66e8bef/attachment.htm>