Should RTE Config Css loading in Frontend?

[Kanti]

With 206c94a We added the loading of the custom CSS files of the RTE Config in the Frontend.

This was added because of customized lib.parseFunc_RTE
eg: https://github.com/TYPO3/typo3/blob/329edc5b803742f1c4ab7597dfb01147312aced1/typo3/sysext/theme_camino/Configuration/Sets/camino/TypoScript/content.typoscript#L26-L47
Without the custom CSS from Camino the ul and li are not styled and can not be identified by the user.

But with added CSS from the RTE Config in the Frontend it is possible that custom li marker are duplicated:

A few concrete questions:
👉 Did you need the RTE config CSS in the frontend so editors could properly recognize elements like lists?
👉 Are you using a customized lib.parseFunc_RTE or custom RTE CSS?
👉 Did loading that CSS cause side effects for you, like duplicated list markers or other styling conflicts?
👉 Did you solve it by adding dedicated frontend CSS instead?
👉 What would be the more practical default for your project setup?

[garvinhicking]

I consider that a shortcoming of camino frontend CSS

[Kanti]

I have decided that this is in deed a Problem of Camino, and we should not load the CSS from the RTE Configuration at all.