Extend / Modules page disabled red signal concerned usability participants

Red suggests an error or problem. A required or a disabled module is neither and error or a problem.

The red should be removed in both places.

I agree with Mitron, the red should be removed in both cases. We could use emphasis or bold but I would just keep it in plain text.
Especially because if you try to activate a module that requires another one drupal will ask you to auto activate it.

It appears there are possibly four relevant colors in the system.admin.css:

div.admin-requirements,
div.admin-required {
font-size: 0.9em;
color: #666;
}
span.admin-disabled {
color: #800;
}
span.admin-enabled {
color: #080;
}
span.admin-missing {
color: #f00;
}

Any color changes must consider all four.

Agreed, required, missing should be red.

@Bojhan: Did you mean should NOT be red?

Yes, only required + missing should be red.

Here is a proposed patch that changes just the color of the word "disabled" to gray (#666).

Screen shot for patch in #9.

Manually tested patch in #12. It looks like screen shot in #11 on OS-X in Chrome, Firefox, and Safari.

Do we need more reviews before this can be marked RTBC?

I rerolled the patch for the current version of D8.

I think this is in general a good idea but in D8, unlike D7, all the Required/Required by notation is hidden by default. In D7, all those red "disabled" gave the impression of lots of problems on the site. In D8, you don't see any Required/Required by unless you expand the module description, which has to be done one module at a time. Consequently, there is no overall impression of a problem if this patch isn't committed. So I don't think this is extremely important, just nice to have.

One thing I DO think is important is that the red "missing" designation should be a link to the project page where you can acquire the missing module. It makes no sense to me to highlight a problem like a "missing" module but provide no way to solve that problem. If others agree, I will provide a patch to add this feature. Or, maybe that should be the subject of a different issue.

Updated issue summary to remove incorrect related issue. still need to find the issue about the modules page in general.

@TR I love that idea, of providing a link to the missing module.

I tested this and it applies and addresses the issue.

Without patch:

With patch:

While I still think linking to a missing module page would be nice, that's a separate issue. I'd like to see this committed and backported to 7, since it easily fixes a usability issue. I just now was helping someone (on Drupal 7) who was confused that a module he was using was disabled (he interpreted the red text to mean error) when in fact it was dependent modules of the one he was using that simply weren't enabled.

I get that this is less of an issue on Drupal 8, but since this text (disabled) does not represent an error, there's no reason for it to be colored red.

I still think linking to a missing module page would be nice, that's a separate issue...

There you go ;)

Perfect!

Committed/pushed to 8.x, thanks!