-
Notifications
You must be signed in to change notification settings - Fork 3
Logical CSS keyword support needed #8
Copy link
Copy link
Open
Labels
doc:adlmdoc:nkoogapThe first comment in this issue is read by the gap-analysis document.The first comment in this issue is read by the gap-analysis document.i:bidi_textBidirectional textBidirectional textl:ffPular (Adlam)Pular (Adlam)l:nqoN'Ko script & languageN'Ko script & languagep:basicThe gap-analysis priority is Basic.The gap-analysis priority is Basic.s:adlms:nkoo
Description
Metadata
Metadata
Assignees
Labels
doc:adlmdoc:nkoogapThe first comment in this issue is read by the gap-analysis document.The first comment in this issue is read by the gap-analysis document.i:bidi_textBidirectional textBidirectional textl:ffPular (Adlam)Pular (Adlam)l:nqoN'Ko script & languageN'Ko script & languagep:basicThe gap-analysis priority is Basic.The gap-analysis priority is Basic.s:adlms:nkoo
Type
Fields
Give feedbackNo fields configured for issues without a type.
This issue is common to all RTL scripts.
Adoption of logical keywords such as
-startand-end, rather than-leftand-rightneeds to be completed.For margins, padding, block size, border colour, width & style, logical keywords such as
margin-inline-startormargin-block-endare widely supported by major browsers in their simplest forms (such as those just mentioned). However, logical properties are not well supported in shorthands such asmargin-blockormargin-inlineor themarginproperty. The lack of support for shorthands is significant, since they are expected to have high use.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.