Crontab module: JS error when command contains > (client area only, admin area w

When creating a cron job that includes a > redirection (for example > /dev/null 2>&1), the crontab module throws a JavaScript error and the table fails to render.
Key detail: this only happens in the client area (user panel). When the exact same cron is created directly from the admin area, it works perfectly. The cron syntax is identical in both cases.
The console shows:

Code: [Select]

Uncaught TypeError: Cannot read properties of undefined (reading 'length')
    at cronTable (?module=crontab:3340:16)
    at Object.complete (?module=crontab:3022:11)
    ...
    at createCron (?module=crontab:3016)
The redirection (> /dev/null 2>&1) is the standard way to suppress output and avoid cron emails, and the commands work fine via crontab -e over SSH. So this looks like a parsing issue in the client area frontend (cronTable) when handling commands containing >, rather than a problem with the cron itself. It also used to work correctly in older versions, so something seems to have regressed.
Questions:

Has anyone else hit this in the client area and found a workaround?
Could the CWP team look into why cronTable in the client area fails on commands containing > / 2>&1, while the admin area handles them fine?