Dimitris Grammatikogiannis

Loading **all** the fonts by default results to 3 fonts that need to be fetched with a size (at least) over 164kb +(59kb for the css file). The problem is...

> A modern browsers will load the font file only when it really used. True, but the css is still render-blocking so bye-bye meaningful performance. I mean the PR is...

Nice one. Not necessarily something for this PR but would be good to have support for these native inputs: - datetime-local: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/datetime-local - month: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/month - week: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/week Oh date...

@laoneo could you elaborate on your thumbs down? Shouldn't Joomla implement the full HTML5 specs, and if so why?

> You answered it here perfectly https://github.com/joomla/joomla-cms/issues/36346#issuecomment-997437474. The core can never use this field, because we want to support also none gregorian calendars. You're mixing different things here. My comment...

> but not in core. Here is were I strongly disagree. For me ALL the HTML5 input fields should be provided from Joomla core for 2 reasons: - Joomla's byproduct...

> With this PR we need to update the build tools. rtlcsss is a postcss plugin that runs on the generated template.css of atum and cassiopeia and after generating the...

This is a standing issue for the template manager obviously exaggerated when child templates are also in the mix. The root problem is that the overrides diffing, notification, etc is...

It cannot be finished with the current codebase without making a total mess, the template manager is already very ugly code wise. The best path is to rewrite it from...

> it is useless as it is right now. I'll repeat again that Child Templates were introduced in 4.0.0. What you're complaining about is the GUI, which obviously you can...