This discussion is spread across many separated issues (as it should) but I wanted to have a parent issue to discuss handling this problem once and for all.
We should really had RTL support in D7 long time ago, we had it in D6, and we don't have it anymore, this is a major regression, especially considering the fact that RTL support was one of the requirements for new core theme.
All these 7.0 and 8.0 rtl patches need to be committed once and for all, even if only 99% perfect, they are all interdependent and every time one of them gets outdated because another css patch got committed, all or many of them go back to needs work.
RTL support in D7 is becoming a real PITA to achieve.
Someone in the Israeli community already suggested maintaining a distro with rtl patches already applied, this seems weird but we are really this close to having RTL supported and yet, the current fresh install of D7 look really bad for RTL users.

this was started as a comment on #1040262: locale-rtl.css

Comments

aspilicious’s picture

Sub, trying to help you guys even if I don't need it :)

tsi’s picture

@aspilicious - thanks, you sure do, actually I was sure you were "one of us" :)

mightyiam’s picture

subscribe

aspilicious’s picture

I started working on the last remaining css rtl issues. I think we have to do better in the future. And make sure NO css gets committed if there is no rtl patch available! :)

catch’s picture

Is there any way to automate testing for missing RTL css?

catch’s picture

Title: RTL support in D7 [Regression] » RTL is no longer fully supported by core (regression)
Version: 7.x-dev » 8.x-dev
Issue tags: +Needs backport to D7
aspilicious’s picture

catch no but there are test sites set up :)

catch’s picture

Status: Active » Closed (duplicate)

#766458: Seven theme lacks rtl styling is still open, I'm not sure we need this meta issue since we have both the tag and individual bug reports in patches, so I'm marking this duplicate. If parts of core are completely missing RTL storing compared to D6 (either old features where it was lost, or completely new stuff where it was never included), those should probably be major bugs by themselves given it's a regression in both cases.

tsi’s picture

Status: Closed (duplicate) » Active

The idea behind creating this issue was to discuss how can we make sure the D7 rtl situation will not repeat itself.
just to make myself clear, when I'm saying "D7 rtl situation" I'm talking about the situation where out of the main 3 UX improvements in drupal 7 (Bartik, Seven & overlay) we have RTL support for *only* one - Bartik and that is mainly because of the "new core theme contest" that took place in the pre-release period that required each of the candidates to be in top shape before it was committed.
Now we are more then six months after D7 official release, 4 versions releases after, and still, nothing, truly nothing, out of all the work we were doing in #766458: Seven theme lacks rtl styling and in #766170: Overlay lacks rtl styling *nothing* was committed - that means we are still having the same display bugs we had during Beta even though the patches to fix them were available already then, really - these issues have working patches since april 2010 !
So why weren't they committed ? first and furthermost because of IE7 support, which was always ok but never perfect, still, those patches are a huge improvement for FF, chrome, IE 8-9, Safari, Opera, Konqueror (etc.) users, and frankly, if we are talking about admin tools (seven & overlay) - who the hell is using IE7 to administer drupal today ??
People are still (!) afraid of going into D7, and these kind of bugs with no visible improvement are exactly why.
I'm reopening this not because there is work to do here but to see if anyone has comments or ideas on the matter.

Bojhan’s picture

Priority: Major » Normal

We cannot have an [meta] issue with no actual tasks be major.

Jeff Burnz’s picture

I think if you want to drop support for IE7 in RTL then you will get my vote of support. If you can get consensus on it I'm all for it.

star-szr’s picture

Title: RTL is no longer fully supported by core (regression) » [Policy, no patch] Improve RTL support
Component: theme system » CSS

Hope I'm not hijacking this issue too much.

Can we make RTL support a core gate or have some other way of ensuring RTL support when reviewing and testing patches containing new or changed CSS?

RTL styles seems to be slipping through the cracks a bit too often. I've never used RTL in Drupal personally, but recently I've worked on a couple issues for updating RTL stylesheets:
#1799124: locale-rtl.css is out of sync with locale.admin.css, is never included due to incorrect filename
#1324058: forum-rtl.css does not overide #forum div.indent from margin-left to margin-right

RTL is mentioned in both the new CSS formatting guidelines and the older CSS standards draft which is great, but I don't think that's enough.

echoz’s picture

LewisNyman’s picture

Issue summary: View changes

This might be relevant to your interests #2313783: Contribute a csslint rule to detect LTR properties

LewisNyman’s picture

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

catch’s picture

Category: Bug report » Plan

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.