Skip to content

fix(rtl): use CSS logical properties for problem blocks and remove ha… - #38961

Open
andrey-canon wants to merge 1 commit into
openedx:masterfrom
eduNEXT:and/fix-problem-rtl
Open

fix(rtl): use CSS logical properties for problem blocks and remove ha…#38961
andrey-canon wants to merge 1 commit into
openedx:masterfrom
eduNEXT:and/fix-problem-rtl

Conversation

@andrey-canon

Copy link
Copy Markdown
Contributor

Description

This PR fixes styling and alignment issues when the platform is rendered in Right-to-Left (RTL) languages within the Problem Blocks (choice groups, radio buttons, and checkboxes) .

Previously, the layout relied on physical CSS properties that forced elements to the left side regardless of the language direction.

Changes Made

  • xmodule/static/css-builtin-blocks/ProblemBlockDisplay.css:
    • Modernized the layout by replacing physical directional properties with CSS logical properties.
    • Replaced margin-right with margin-inline-end.
    • Replaced padding-left with padding-inline-start.
    • Replaced left with inset-inline-start.

Impact

By delegating the alignment to the browser using logical properties, elements like radio buttons and checkboxes will now automatically mirror their position based on the dir="rtl" or dir="ltr" HTML attribute, fixing the UI without needing separate overriding stylesheets.

How to Test

  1. Checkout This branch

  2. Set the following setting to False: USE_EXTRACTED_PROBLEM_BLOCK = False

  3. Compile assets: npm run compile-sass -- --skip-themes

Before

EN

image

AR

image

After

EN

image

AR

image

…rdcoded LTR import (#81)

- Removed the explicit `@import 'vendor/bi-app/bi-app-ltr';` in `_builtin-block-variables.scss` that was overriding RTL configurations.
- Replaced physical CSS properties (`left`, `padding-left`, `margin-right`) with their logical equivalents (`inset-inline-start`, `padding-inline-start`, `margin-inline-end`) in `ProblemBlockDisplay.css` to natively support bidirectional layouts.
@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Aug 6, 2026
@openedx-webhooks

Copy link
Copy Markdown

Thanks for the pull request, @andrey-canon!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform-oncall.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@github-project-automation github-project-automation Bot moved this to Needs Triage in Contributions Aug 6, 2026
@mphilbrick211 mphilbrick211 moved this from Needs Triage to Waiting on Author in Contributions Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

open-source-contribution PR author is not from Axim or 2U

Projects

Status: Waiting on Author

Development

Successfully merging this pull request may close these issues.

3 participants