Issue Bug Closed

#97776Disabled scheduler tasks are not dimmed out

Sebastian Michaelsen 06/15/22, 09:50 updated 06/08/24, 20:27

Description

The SchedulerModueController says // Row is shown dimmed if task is disabled, unless it is still running and a corresponding CSS class disabled is set on disabled tasks, but visually there is no difference.

Tested in TYPO3 v10, but I suppose this is also the case in higher versions.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 2

History 4

  1. Guido Schmechel commented and changed attached scheduler-v11.JPG 06/16/22, 08:06

    I just had a look at it, even in older versions. It is always set disabled, but nothing happens in the CSS.

    My visual suggestion: Work with Opacity 0.2 for “disabled” and use the Bootstrap classes for e.g. errors. Attached is a suggestion for v11

  2. Chris Müller commented 07/18/22, 16:49

    From an accessibility perspective I would suggest something else than just reduce the opacity – as it can’t be read any longer for some persons (like me). The “disabled” hint (then with better contrast ratio) is just fine.

  3. Riccardo De Contardi commented 06/08/24, 19:58

    As far as I can see inside /typo3/sysext/scheduler/Classes/Controller/SchedulerModuleController.php the comment

    // Check the disable status
    // Row is shown dimmed if task is disabled, unless it is still running

    Is no more present since version 12 (and the code below);

    Plus, from TYPO3 12 the “disabled” badge on the scheduled task list has a background color: #737373 and white text, which as far as I can see is sufficient to meet the constrast ratio for AA guidelines (but not AAA)

    Is this sufficient to consider this issue closed?

  4. Riccardo De Contardi commented and changed status New Closed 06/08/24, 20:27

    I tend to close this issue for now; the accessibility issue on the “disabled” badges has been addressed; further improvement could be discussed with new fresh issues that also take into account the need to maintain a coherent UI language.

    Thank you for your work