Problem/Motivation

I've formulated the title very matter-of-factly, but this is more of a question. What is the reason for the styling using the additional body:not(.path-admin) in the styling? For example, the front-end-minimal.css reads:

/*
 * This is the minimal styling that will be used also if the user selects to
 * use custom styling, so that the users sees what are the tooltip triggers.
 */

/* If there is no pin, but the selected text. */
body:not(.path-admin) .ckeditor-tooltip-text {
  text-decoration: underline;
  text-decoration-style: dotted;
}
body:not(.path-admin) .ckeditor-tooltip-text:hover {
  cursor: pointer;
}

I wanted to override this styling and I had to include the body:not(.path-admin) in my custom styling to be able to override this, whereas it doesn't seem too harmful to include this also on admin pages.

Steps to reproduce

Add custom styling
Notice you need to include body:not(.path-admin) in your style rule in order to override the default styling.

Proposed resolution

Could it be removed, maybe only from front-end-minimal.css? The regular frontend-css is more comprehensive, so I can imagine you'd want to restrict it more.

Remaining tasks

TBD

User interface changes

None.

API changes

Could default styling be considered an API? Developers won't need to add the extra specificity to get their styles to apply.

Data model changes

None.

Comments

eelkeblok created an issue.