-
Improvement
-
Resolution: Fixed
-
Minor
-
4.3
-
MOODLE_403_STABLE
-
MOODLE_404_STABLE
-
MDL-78334-main -
-
HQ 2023 Sprint I4.1 Moppies
This has come up in the context of migrating to BS5.
At the moment we have a huge amount of CSS which has been carried through from older versions of Moodle. Unfortunately it is very difficult to detect unused CSS in Moodle, and also rather tricky to inform people that a style is deprecated.
There are a couple of pieces to solving this:
- policy
- finding a way to deprecate content (technical perspective)
- finding a way to detect uses of deprecated styles
Policy
I would suggest that we follow the same policies we have for the rest of Moodle
Technical deprecation
There are a couple of ways we can do this, the one that springs to mind is:
- move deprecated scss into a new deprecated.scss style
- apply a mixin to all deprecated styles which applies only in themedesigner mode to:
- applies a thick border
- applies a obvious background colour
- have another mixin applied which applies to behat to add text content such as:
&&::before {
content: "Deprecated style in use";
}
- Add to our existing check for exceptions to search for deprecated styles too
In some cases we may decide tht we just want to be ruthless about gutting some of the older styles and ignore the deprecation process. Some of these things have been useless for over a decade.
- has a non-specific relationship to
-
MDL-67687 Add Behat step to verify WCAG A and WCAG AA compliance
-
- Closed
-
- has been marked as being related by
-
MDL-66239 Document various deprecation processes
-
- Open
-
- has to be done before
-
MDL-68472 Remove obsolete css in block_activity_results
-
- Open
-
- is parent of
-
MDL-80154 Add "since" version to deprecated SCSS
-
- Closed
-