-
Notifications
You must be signed in to change notification settings - Fork 658
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
[css-writing-modes] unicode-bidi: plaintext
not affect ul/ol
#3491
Comments
unicode-bidi: plaintext
not affect ul/ol
As far as I can tell, it does what it is supposed to do, but that seems to be less than what you expect it to do:
I think this little demo should help clarify: https://jsbin.com/valaluf/edit?html,output |
@frivoal, Thanks. Is it possible to change this in the future of CSS and make |
@ali-hardan I'm not sure I would rule it out 100%, but it seems doutful:
|
@fantasai should know this better than me, and be able to tell if I'm missing something here. |
@frivoal's explanationis entirely correct with his explanation, but he misses one thing: the feature you're looking for exists in HTML. Use In general, we strongly strongly recommend that authors do not use I also want to warn you: the automatic determination of 'direction' is a very dumb heuristic. It only looks at the first letter. There is a lot of text content out there that is in an RTL language but begins with an LTR character, such as a number (2018) or an abbreviation (USA) or some other LTR text. This will give you bad results! So you should, if it's at all possible, try to use dir=ltr or dir=rtl explicitly based on the language of your content as you know it, or can guess it from some more sophisticated heuristic. (We use this simple heuristic for dir=auto because it works frequently if not quite reliably, it's straightforward and easy to understand, and it can be easily manipulated using the RLM and LRM characters.) |
Basically the advice is:
|
Thanks for your help. Yes I know it's better to use html Sometimes we are sure client are not disabled CSS, so we have no problem using it. When we sure clients enabled CSS and when we have used RLM and LRM characters to set direction, I think it is not good idea to repeat One good example is when we convert markdown to html using it's tools. Most of them not add
|
Sounds like the markdown processor should be updated to set dir correctly. |
This spec in w3.org: https://www.w3.org/TR/css-writing-modes-3/
When I set
unicode-bidi
toplaintext
, direction should be set automatically. But on ul and ol tags, It not works.The example is:
The text was updated successfully, but these errors were encountered: