The float ranges of Cubic Bézier curve arguments don't match the changelog

From changelog 25w45a:

An Easing Type may also be specified with a Cubic Bézier in the format: { "cubic_bezier": [ x1, y1, x2, y2 ] }

• x1: float between 0 and 1, x-coordinate of the first control point

• y1: float, y-coordinate of the first control point

• x2: float between 0 and 1, x-coordinate of the second control point

• y2: float, y-coordinate of the second control point

But the real float range is:

• x1: float between 0 and 1

• y1: float between 0 and 1

• x2: float

• y2: float

I make a example data pack attached below. I set minecraft:test use [0, 2, 0, 0] and minecraft:test2 use [0, 0, 2, 0]. The load result is “test” fail: Failed to parse either. First: Not a string: {"cubic_bezier":[0,2,0,0]}; Second: y1 must be in range [0; 1] missed input: {..., which means the float range is appling y1 instead of x2.

But from the application of the Cubic Bezier Curve, The correct float range should apply x1 and x2, not x1 and y1.