Why modified the behavior of KHR_texture_transform extension since CesiumJS 1.97?

Hi, in CesiumJS 1.97, I found that you refactored the code about loading model, and the behavior of glTF extension “KHR_texture_transfrom” has been modified.
In CesiumJS1.118.2([cesium/packages/engine/Source/Shaders/Model/MaterialStageFS.glsl at 1.118.2 · CesiumGS/cesium · GitHub]), texture coordinates has been not “fract”, but in version 1.96([cesium/Source/Scene/processPbrMaterials.js at 1.96 · CesiumGS/cesium · GitHub]), texture coordinates has been “fract” before texture transform.
Now, the effect in new CesiumJS version is simlilar to Babylon.js,and it’s seem to be consistent with the description in the KHR documentation([glTF/extensions/2.0/Khronos/KHR_texture_transform/README.md at main · KhronosGroup/glTF · GitHub]).
However, I’m not sure it was implemented incorrectly in old version(before 1.97), or it’s a new bug?