Bootstrap RTL the correct way

[brianteeman]

This PR is using bootstrap the way that bootstrap intended for it to be used since 5.0 for RTL.

removing any rtl specific code that can be automatically handled by rtlcss or by using rtlcss specific markup (just as bootstrap itself does)

All our current css is doing bootstrap the wrong way for rtl support.

The problem is NOT with our own scss as in general this is now correct with logical properties (The few instances of dir=rtl are now handled by rtlcss)

The problem is with the actual bootstrap code. We are using it without addressing any RTL issues with that. With the exception of a very incomplete set of bootstrap overrides in https://github.com/joomla/joomla-cms/blob/7cf5e1228db337881d7678ad1c71915d5c885150/build/media_source/templates/administrator/atum/scss/vendor/bootstrap/_bootstrap-rtl.scss

Technically this will change all left to right etc so we dont need to use logical properties in our own css however I still think its good practice that we continue to use logical properties where available.

Bootstrap 5 is designed to be post-processed using rtlcss - This takes the generated template.css and converts it to template-rtl.css

Benefits

• it is DRY
• we don't need to remember to check it works in rtl (we almost always forget)
• we dont need to waste time creating rtl overrides (in most cases)
• fixes numerous open issues
• replaces numerous open pull requests
• fixes several issues with input buttons not already on the tracker.

Testing

1. Apply the pr and then run npm i
   This will generate all the css and install rtlcss

Or

2.Use a prebuuilt package

3. test test test

Sample Tests

Global configuration in arabic

Before

After

Add Multi-Factor Authentication

Before

After

[dgrammatiko]

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 new -rtl.css this needs to be minified as well.

brianteeman#291

[brianteeman]

Thanks @dgrammatiko

[wilsonge]

AMAZING if this works. I looked when I plumbed in 5.x and it seemed really painful to migrate everything. Thought it was way more work than this. Really nice job!

[brianteeman]

Thought it was way more work than this.

Well it was 14hours solid so not a small amount - plus dont forget all the PR since you did the first work where I moved our own css to logical properties

[wilsonge]

Yeah that makes a lot of sense. Still really nice work though :)

[laoneo]

Thanks, merging stuff like this as early as possible brings us more time to iron out regressions, even when the chance is small that there will be one.

[brianteeman]

except it cant be tested right now :(

Thanks, merging stuff like this as early as possible brings us more time to iron out regressions, even when the chance is small that there will be one.

I hope this means that pull requests wont wait as RTC for weeks and months before merging any more

[laoneo]

Updated the branch, should be back to normal.

[brianteeman]

Thanks @laoneo

[laoneo]

I have tested this item ✅ successfully on 4609b33

Tested it with farsi. Did browse around and saw no issue. Installed DPCalendar and created events and so on. All did look ok with RTL.

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38412.}

[brianteeman]

thanks for testing. dpc was one of the components I developed this with ;)

[obuisard]

I have tested this item ✅ successfully on 95ba902

I did extensive browsing trying to catch issues.
As a non-rtl reader, I may have missed issues related to rtl that I may not be unaware of, but I honestly think this PR was a great work through.
It would be useful to get a tester using rtl daily.

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38412.}

[alikon]

made some tests, but i'm not a RTL user...
...so if we don't get any RTL tester... you can consider this as a valid one

[brianteeman]

fyi I use RTL a lot which is why I spent the time making the pr

[obuisard]

I would like to merge this PR into 4.3 early on. I will merge it tomorrow if there are not any issues by then.
Any objection @chmst @HLeithner ?

[brianteeman]

is it tomorrow yet?

[obuisard]

Was hoping to hear from reviewers...

[obuisard]

Thank you Brian @brianteeman for this needed fix and for keeping track.