w3c / w3c/afrlreq

Should bars in HTML progress and meter elements be read RTL?

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

i:bidi_text i:interaction l:ff l:nqo question s:adlm s:nkoo
Dominant language
HTML
Stars
11
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Background

This question was prompted by the HTML issue at https://github.com/whatwg/html/issues/8413

Currently, for RTL script text Blink, WebKit and Gecko engines all reverse the direction of the progress bar when progress, meter or input=range elements are used in HTML when the text direction is RTL.

This means that the direction of the controls is the same as the reading direction of the text. For example, the following is for N'Ko. Adlam would look the same.

Screenshot 2022-10-25 at 17 12 23

Test for meter

Test for progress

Test for range input control

Question

Is it preferable for the direction of the control to follow the direction of the surrounding text, or should it always progress from left to right?

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 by reviewing the linked WHATWG HTML issue and the three exploratory tests for meter, progress, and range controls. Compare behavior in RTL and LTR text, then determine whether the surrounding text direction should control these elements or whether they should always progress left to right. Done means the project has a documented, resolved recommendation.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
internationalization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.