[UX] CustomCSS field for advance persistent styling #4282
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to fix 2 problems:
For example, this feature can be used to support this feature request #4242 (which was also requested in Discord) by applying this custom CSS
(or
display: none
to fully remove those icons)Then, any theme that's selected will still have this custom CSS style applied.
Since this can be dangerous (a user could
body { display: none }
and break everything), there's a warning with an indication on where to update the config files manually, and that's the reason why I put this in Advanced, it's not meant for inexperienced users.Use the following Checklist if you have changed something on the Backend or Frontend: