On Wed, 9 Sep 2026 20:50:47 GMT, Marius Hanl <[email protected]> wrote:
>> speaking of `steps()`, do we want to include all possible values (jump-*, >> start, end)? > > I think this is not related to a missing converter, but good catch > nonetheless. > Because in the CSS transition PR (I checked it before), only the > `InterpolatorConverter` and `TransitionDefinitionConverter` were added (and > `DurationConverter$SequenceConverter`). > > `cubic-bezier` is handled in `InterpolatorConverter`, so maybe something is > missing for the actual serialization. That's a good catch! It turns out that we didn't serialize CSS easing functions at all. Now, there's a way to fix this with and without a specification change: 1. We can serialize the numbers in an easing function as `Size` components with the existing BSS format. However, sizes have a unit (like `SizeUnits.PX`), but the numbers in an easing function are not sizes. We can just silently ignore the unit and go on with life, but it's fundamentally not correct to treat these numbers as sizes. 2. We can extend the BSS format to allow direct serialization of numbers. I've implemented the second approach. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/2303#discussion_r3974406848
