1846488 - [css-properties-values-api] motionone doesn't work on nightly (depends on interpolating registered properties, bug 1846516)

Status: RESOLVED DUPLICATE of bug 1846516

(Core :: CSS Parsing and Computation, defect, P3)

Description

[B.J. Herbison]

Reported in #nightly:mozilla.org.

Steps to reproduce:

1. Visit https://ix99x9.csb.app/ .

Expected:

1. The image rotates while changing color.

Actual:

1. No rotation.

The rotation occurs on release and Chrome.

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a31b524ec43ad1f7e5ad7ad6a1eae27160111a06&tochange=96efb14c1b2e225253f22aae7b217fdd48b4cb9f

[e-mail]
Tue Jun 27 11:13:52 2023 +0000 96efb14c1b2e225253f22aae7b217fdd48b4cb9f Emilio Cobos Álvarez — Bug 1840480 - [css-properties-values-api] Enable on nightly. r=zrhoffman,webidl,peterv

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:emilio, since you are the author of the regressor, bug 1840480, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Comment 2

[Emilio Cobos Álvarez (:emilio)]

Yeah so this library is using a different codepath for animations based on CSS.registerProperty presence, and we still haven't implemented interpolation of typed custom properties. Filed a bug for that.

Comment 3

[zvasylvv]

Hello everyone!

Could someone kindly assist in deciphering the severity and priority codes, namely "Severity: S3, Priority: P3," and provide an ETA, even if it's approximate, for actual appearance in users' browsers?

I need this for a small feature and would like to understand if I need to go with JS fallback or if this will be fixed earlier than we do a release.

Comment 5

[Calum Smith [:cpmsmith]]

FWIW, I can't reproduce this. In the linked CodeSandbox, the square does rotate. I see the same behaviour in Firefox 130.0, Firefox Nightly, Chrome stable, and Safari stable. Should this be closed?

The square's background-color doesn't smoothly transition, but it doesn't use a custom property, and this matches all tested browsers, so I'm not sure it's supposed to.

Comment 6

[Emilio Cobos Álvarez (:emilio)]

Yes, this was fixed by bug 1869185 afaict.