1773493 - Eliminate IPDL-specific Class for Passing ComputedTimingFunction Around

Status: RESOLVED FIXED

(Core :: CSS Transitions and Animations, enhancement)

Description

[David Shin[:dshin]]

In Rust, we use a generic linear easing function struct for specified & computed values. However, with bug 1764126 implementing linear(...), easing functions no longer have 1:1 mapping between specified (i.e. form that accommodates for parsing and printing) & computed (i.e. form that can be queried for output) values. This causes conversions back and forth between the computed & specified values.
May need a separate implementation to avoid this.

Comment 1

[David Shin[:dshin]]

While what is said in comment #0 is true, we should avoid stuffing this non-1:1 mapping into specified/computed value, which have very specific definitions by the standard. Perhaps a wrapper object containing additional data for linear function can be defined as Rust/C++ timing function computations get merged in bug 1766041.

This ticket tracks another angle to reduce complexity of passing computed timing functions around by eliminating the IPDL definition of it and using Rust's definitions.

Comment 2

[David Shin[:dshin]]

Attachment: Bug 1773493 - Use Rust's `ComputedTimingFunction` for IPDL. r=emilio

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/3b21ee5c328c
Use Rust's `ComputedTimingFunction` for IPDL. r=emilio

Comment 4

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/3b21ee5c328c