Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RTL field inputs are shown as LTR if the user's preferred language is LTR #20

Closed
angrybrad opened this issue Jan 29, 2017 · 3 comments
Closed

RTL field inputs are shown as LTR if the user's preferred language is LTR #20

angrybrad opened this issue Jan 29, 2017 · 3 comments
Labels
bug severity:minor Cosmetic issues or bugs with simple workarounds

Comments

@angrybrad
Copy link
Member

Environment:

  • Craft version: 3.x
  • PHP version: 7.x
  • Database driver & version: n/a
  • Plugins & versions:

Description:

If a user's preferred language is LTR-oriented, and they are editing a RTL-oriented locale (e.g. Arabic), the fields are still LTR-styled, when they should be RTL.
@angrybrad angrybrad added bug severity:minor Cosmetic issues or bugs with simple workarounds labels Jan 29, 2017
@johanneslamers johanneslamers mentioned this issue Feb 1, 2017
Closed
@brandonkelly
Copy link
Member

This has been fixed for v2 and v3 for a while.

@E2design E2design mentioned this issue Dec 8, 2017
Open
@ddbr ddbr mentioned this issue Jan 25, 2018
Closed
@Rainbowlemon Rainbowlemon mentioned this issue Feb 14, 2018
Closed
@jamielaughton jamielaughton mentioned this issue Jun 26, 2018
Closed
@AlisherN AlisherN mentioned this issue Jul 26, 2018
Open
@peteeveleigh peteeveleigh mentioned this issue Oct 10, 2018
Closed
@nickfreedom nickfreedom mentioned this issue Oct 19, 2018
Closed
@neokoenig neokoenig mentioned this issue Dec 15, 2018
Closed
@philbrookweb philbrookweb mentioned this issue Apr 2, 2019
Closed
@bryantwells bryantwells mentioned this issue Jun 24, 2019
Closed
@vasuhooda vasuhooda mentioned this issue Jan 16, 2020
Open
@laurabennett laurabennett mentioned this issue Jan 28, 2020
Closed
@phillmorgan28 phillmorgan28 mentioned this issue Mar 3, 2020
Closed
@justinholtweb justinholtweb mentioned this issue Mar 3, 2020
Closed
@lenvanessen lenvanessen mentioned this issue Mar 13, 2020
Closed
@nathancope nathancope mentioned this issue Mar 20, 2020
Closed
@Simon-00 Simon-00 mentioned this issue Apr 23, 2020
Closed
@rossthomson89 rossthomson89 mentioned this issue May 1, 2020
Closed
@kaspar-allenbach kaspar-allenbach mentioned this issue May 6, 2020
Closed
@karltriest karltriest mentioned this issue May 21, 2020
Closed
@stefangallas stefangallas mentioned this issue Jun 11, 2020
Closed
@chandamotiyani chandamotiyani mentioned this issue Jun 25, 2020
Closed
@weotch weotch mentioned this issue Jun 25, 2020
Closed
@samhibberd samhibberd mentioned this issue Jun 27, 2020
Closed
@hiake21c hiake21c mentioned this issue Jul 22, 2020
Closed
brandonkelly added a commit that referenced this issue Feb 5, 2021
@brandonkelly
Merge pull request #20 from sparkbox/craft-3rtm
7460a38 
Require Craft 3.0.1
@JordanMed JordanMed mentioned this issue Mar 4, 2021
Closed
@ujanko ujanko mentioned this issue May 3, 2021
Closed
@tyssen tyssen mentioned this issue Jun 8, 2021
Closed
@proimage
Copy link

@brandonkelly @angrybrad This appears to be an issue again in 3.6.x and 3.7.4. I've got a plain text field, in a Hebrew-language site (he-IL), but when my user is set to show things in English, the text field's (Hebrew) contents are shown LTR.

@brandonkelly
Copy link
Member

@proimage Can you please create a new issue, with steps to reproduce, expected behavior, and screenshots?

@proimage proimage mentioned this issue Jul 21, 2021
Closed
@brianjhanson brianjhanson mentioned this issue Jul 22, 2021
Closed
@humandevs humandevs mentioned this issue Sep 16, 2021
Closed
@humandevs humandevs mentioned this issue Oct 11, 2021
Closed
@Bilge Bilge mentioned this issue Dec 21, 2021
Closed
@khalwat khalwat mentioned this issue Apr 7, 2022
Closed
@alexr8 alexr8 mentioned this issue Jun 8, 2022
Closed
@FabioIaderosa FabioIaderosa mentioned this issue Jun 20, 2022
Closed
@mofman mofman mentioned this issue Jun 25, 2022
Closed
@j-stechmann j-stechmann mentioned this issue Jul 25, 2022
Closed
@proimage proimage mentioned this issue Sep 15, 2022
Closed
@swordinthestone swordinthestone mentioned this issue Oct 16, 2022
Closed
@alexanderloewe alexanderloewe mentioned this issue Dec 4, 2022
Closed
@bob-pixeldeluxe bob-pixeldeluxe mentioned this issue Dec 7, 2022
Closed
@joepagan joepagan mentioned this issue Jun 8, 2023
Closed
@robinbeatty robinbeatty mentioned this issue Oct 31, 2023
Closed
@DTesch-Level-R DTesch-Level-R mentioned this issue Jan 9, 2024
Closed
@chadcrowell chadcrowell mentioned this issue Aug 6, 2024
Closed
@funkysoul funkysoul mentioned this issue Aug 6, 2024
Closed
@pnpaes pnpaes mentioned this issue Aug 23, 2024
Closed
@stephenmatthews stephenmatthews mentioned this issue Oct 24, 2024
Open
@joshmcoffman joshmcoffman mentioned this issue Oct 31, 2024
Open
@fancy-pug fancy-pug mentioned this issue Nov 13, 2024
Closed
@tibbis tibbis mentioned this issue Nov 13, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug severity:minor Cosmetic issues or bugs with simple workarounds
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brandonkelly @angrybrad @proimage