Project

General

Profile

Actions

Bug #97776

closed

Disabled scheduler tasks are not dimmed out

Added by Sebastian Michaelsen over 2 years ago. Updated 6 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2022-06-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

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.


Files

Screenshot_2022-06-15_at_11_48_33.png (53.9 KB) Screenshot_2022-06-15_at_11_48_33.png Sebastian Michaelsen, 2022-06-15 09:49
scheduler-v11.JPG (54.9 KB) scheduler-v11.JPG Guido Schmechel, 2022-06-16 08:06
Actions #1

Updated by Guido Schmechel over 2 years ago

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

Actions #2

Updated by Chris Müller over 2 years ago

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.

Actions #3

Updated by Riccardo De Contardi 6 months ago

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?

Actions #4

Updated by Riccardo De Contardi 6 months ago

  • Status changed from New to Closed

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

Actions

Also available in: Atom PDF