Can you please check in this repo where the admin template etc is being developed as I believe this has already been done https://github.com/joomla/40-backend-template/

@brianteeman I didn't included any change related to the backend template.

I have tested this item ✅ successfully on b8c7f7f

Code review

Resolved conflicts.

@rdeutz everything looks fine to me. May you review this PR, please?

@ciar4n and @wilsonge do you really want to tightly couple the front end to Bootstrap? There is always the option to extend to some random unique class which will work nicely with but especially without Bootstrap (you can even keep the old classes and extend them to badge).

Personally I wouldn't tightly couple the FRONTEND core output to Bootstrap, it brings more limitations than the promised easiness of doing things. Also it's a no go if someone needs to build a fairly performant site, whatever that means according to the current benchmarking tools out there (google is probably installed in every client pc, so lighthouse is just a click away). Food for thought...

The badge/label utility class isn't going to "tightly couple the FRONTEND core output to Bootstrap".

• https://semantic-ui.com/elements/label.html
• https://foundation.zurb.com/sites/docs/badge.html or https://foundation.zurb.com/sites/docs/label.html
• https://materializecss.com/badges.html
• http://getbootstrap.com/docs/4.1/components/badge/

Pick a standard, stick with it, or say "screw every existing standard" and write the Joomla CSS Framework already.

@htmgarcia it can't be merged until it passes all the tests

@brianteeman This PR is just about replacing "label" as classname in the HTML. Nothing fancy.
Sorry. I don't follow the 2 fails on the checks. Any idea what's the issue with these failed checks?

At this stage it is safe to say we are not going to be creating our own CSS framework. Prefixing one of the current standards (eg Bootstrap) is the only viable option IF we want to decouple the views from Bootstrap. To do that we either

1. Rewrite an existing framework manually, taking what we need and prefixing all the classes (#15225)
2. Automating the prefixing at a SCSS compiler level.

I've looked in to the second option (the ideal of the 2) however the automated prefixing modules I've tested to date do not play nice with SCSS @extends which pretty much rules out using Bootstrap. Most other frameworks avoid @extend (https://csswizardry.com/2016/02/mixins-better-for-performance/).

@brianteeman @wilsonge may we merge this one, pretty please?

@htmgarcia it can't be merged until it passes all the tests

it still has zero user tests

@brianteeman #20328 (comment)

tests are reset when the code changes which you did when you resolved the conflicts

Found some more. Please see screenshot.

There are 3 more in the screenshot that have to be replaced.

Sorry these should be the last ones.

COM_JOOMLAUPDATE_VIEW_DEFAULT_DESCRIPTION_BREAK="*Extensions marked with <span class='label label-important'>No</span> or <span class='label'>Missing Compatibility Tag</span> might break your website. Please consult with the developer before upgrading."
COM_JOOMLAUPDATE_VIEW_DEFAULT_DESCRIPTION_MISSING_TAG="*Extensions marked with <span class='label'>Missing Compatibility Tag</span> indicate the developer did not add a compatibility tag in the respective extension's XML."
COM_JOOMLAUPDATE_VIEW_DEFAULT_DESCRIPTION_UPDATE_REQUIRED="*Extensions marked with <span class='label label-warning'>Yes (X.X.X)</span> might require an update."

I have tested this item ✅ successfully on 59ed416

Nice work! Thanks :)