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.

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

Logical CSS keyword support needed #217

Open
r12a opened this issue Feb 2, 2020 · 2 comments
Open

Logical CSS keyword support needed #217

r12a opened this issue Feb 2, 2020 · 2 comments
Labels
doc:arab_ks doc:arab_ug doc:arfa gap The first comment in this issue is read by the gap-analysis document. i:bidi_text Bidirectional text l:arb Arabic l:ks Kashmiri l:pes Persian l:ug Uighur l:ur Urdu p:basic The gap-analysis priority is Basic. s:arab Arabic script (Used for arb + pes) s:aran Arabic nastaliq script style x:adlm x:alreq x:arab-ks x:arab-ug x:blink x:css x:css-logical x:gecko x:hebr x:nkoo x:webkit

Comments

@r12a
Copy link
Contributor

r12a commented Feb 2, 2020

This issue is common to all RTL scripts, and vertically set scripts.

Adoption of logical keywords such as -start and -end, rather than -left and -right needs to be completed.

For margins, padding, block size, border colour, width & style, logical keywords such as margin-inline-start or margin-block-end are widely supported by major browsers in their simplest forms (such as those just mentioned). However, logical properties are not well supported in shorthands such as margin-block or margin-inline or the margin property. The lack of support for shorthands is significant, since they are expected to have high use.

Support for the margin shorthand is currently held up by a discussion about the appropriate syntax. See this CSS issue.

Other logical properties that are not widely supported include border radius, caption side, and float. Firefox does support border-radius and floats, but otherwise these are not supported.

See a set of test results.

These new values also need to be widely supported in editing applications.

@r12a r12a added gap The first comment in this issue is read by the gap-analysis document. doc:arfa i:bidi_text Bidirectional text p:basic The gap-analysis priority is Basic. labels Feb 2, 2020
@r12a
Copy link
Contributor Author

r12a commented Feb 2, 2020

The first comment in this issue contains text that will automatically appear in one or more gap-analysis documents as a subsection with the same title as this issue. Any edits made to that comment will be immediately available in the document. Proposals for changes or discussion of the content can be made in comments below this point.

Relevant gap analysis documents include:
Arabic & PersianAdlamHebrewKashmiriN'KoUighur

@xfq
Copy link
Member

xfq commented Sep 12, 2023

This issue is common to all RTL scripts.

I think this is not only useful for RTL scripts, but also for Chinese, Japanese, and Mongolian text in vertical writing mode.

@r12a r12a added l:arb Arabic l:pes Persian l:ug Uighur l:ur Urdu l:ks Kashmiri labels Jun 5, 2024
@r12a r12a moved this to Awaiting spec text in Gap-analysis pipeline Jun 20, 2024
@r12a r12a added s:arab Arabic script (Used for arb + pes) s:aran Arabic nastaliq script style labels Jun 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc:arab_ks doc:arab_ug doc:arfa gap The first comment in this issue is read by the gap-analysis document. i:bidi_text Bidirectional text l:arb Arabic l:ks Kashmiri l:pes Persian l:ug Uighur l:ur Urdu p:basic The gap-analysis priority is Basic. s:arab Arabic script (Used for arb + pes) s:aran Arabic nastaliq script style x:adlm x:alreq x:arab-ks x:arab-ug x:blink x:css x:css-logical x:gecko x:hebr x:nkoo x:webkit
Projects
Status: Awaiting spec text
Development

No branches or pull requests

2 participants