PG1204 opened a new pull request, #5895: URL: https://github.com/apache/texera/pull/5895
### What changes were proposed in this PR? Upgrades the ng-zorro-antd dependency in the frontend from 21.2.2 to 21.3.1 (frontend/package.json + frontend/yarn.lock). Motivation: 21.2.2 has a bug in nz-input-number where the mouse-wheel handler (onWheel) guards on the raw nzDisabled() input instead of the computed finalDisabled() state. When a form control is disabled via the form group, as the operator property panel does while a workflow is running, the field greys out and blocks typing, but scrolling the mouse wheel over it still changes the value, bypassing the disabled state. This was fixed upstream in [NG-ZORRO/ng-zorro-antd#9785](https://github.com/NG-ZORRO/ng-zorro-antd/pull/9785), which guards on finalDisabled() || nzReadOnly(). The fix first shipped in 21.3.0; 21.3.1 is the latest stable. This is a minor-version bump within the same major (21.x) with no breaking changes in the [21.3.0/21.3.1 changelogs](https://github.com/NG-ZORRO/ng-zorro-antd/releases). ### Any related issues, documentation, discussions? Closes #5879. Close #5848. Related bug: #5848. Upstream fix: NG-ZORRO/ng-zorro-antd#9785. ### How was this PR tested? Tested with existing test cases. Additionally verified manually: - yarn install succeeds; confirmed the installed nz-input-number onWheel handler now guards on finalDisabled() || nzReadOnly(). - Ran the app, started a workflow, and confirmed that greyed-out number fields in the operator property panel (e.g. Python UDF "Worker count") no longer change value on mouse-wheel scroll during execution. No new automated tests were added, as this is a dependency version bump with no source-code changes; the fix lives in the upstream library. ### Was this PR authored or co-authored using generative AI tooling? This PR was co-authored by Claude Opus 4.7, in compliance with ASF. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
