Marking as TGP candidate as such fixes can affect existing code in surprising ways that are hard to track down. I might even go as far as suggesting to sync this one on its own.

caretaker note: it is advised to sync this one on its own, assuming TGP ends up green

The deflaked TGP came back "green". I'm going to merge and sync this one separately on Monday.

This PR was merged into the repository by commit 387e1cb.

The changes were merged into the following branches: main, 18.0.x, 18.1.x

@JoostK @devversion
Thank you for your support.

I posted in #49068 but I believe this PR also fixed #49068.

Issue pertained to an animation declaration with two or more keyframe names where not all of the keyframe names were preceded by 1 or more whitespace (could be caused by a prod build stripping whitespace). In my testing, the issue is resolved once this PR makes its way to an NPM release. Maybe #49068 can be closed as well.

Issue CSS from #49068 :

@keyframes foo { ... }
@keyframes bar { ... }

#my-div {
    /* prettier-ignore */
    animation: bar 1s infinite,foo 1s infinite; /* THIS BUG: foo is not processed */
    animation: bar 1s infinite, foo 1s infinite; /* OK: foo is processed */
    animation: 1s infinite bar,1s infinite foo; /* OK: foo is processed */
}

I think this PR may have also fixed #49384

I posted on that issue but on 18.2.0-next.0 the 5 animation names are properly scoped in dev/prod builds.

In the screenshot provided in #49384 the animations in the list were not separated by one or more whitespace characters which this PR addressed (by supporting animations not separated by one or more whitespace characters).

Worth someone else taking a look and potentially closing as resolved.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}