w3c / w3c/afrlreq

:dir lacks wide support – FIXED !

Open
#23 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

doc:adlm doc:nkoo gap i:bidi_text l:ff l:nqo p:ok s:nkoo x:adlm x:nkoo
Dominant language
HTML
Stars
11
Forks
4
PR merge metrics
No merged PRs in 30d

Description

This issue is applicable to all languages with RTL orthographies.

Style sheets need to add special rules for RTL styles if they are not supported by logical properties or values.

One approach is to create a second style sheet which, when pulled into an HTML page, overrides styles in the main style sheet with settings for RTL text. This approach is not ideal because it requires maintaining the styles in two separate locations, which can therefore get out of synch, and it requires explicit addition of a call to the second style sheet in every page that will support RTL text.

The :dir() pseudo-class avoids these issues by allowing the content author to include the RTL variations in the same style sheet as the others. However, it is not yet supported by all major browser engines.

For more details, see this GitHub issue, which is being used to track this gap. Please add any discussion there, and not to this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked w3c/alreq#256 issue, which the message identifies as the active place for discussion of the :dir() support gap. The work is considered done when that issue's status and any required RTL guidance reflect the browser-support situation; this issue asks that discussion stay there.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html
Domain
internationalization, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.