Add bidirectional-override #1952
Conversation
github-actions
bot
added
the
feature definition
features/bidirectional-override.yml
Outdated
| @@ -0,0 +1,18 @@ | |||
| name: Bidirectional override | |||
There was a problem hiding this comment.
The title seems ambiguous, maybe should include some combo of Unicode or layout or direction or something like that, which would disambiguate from people thinking it's the bdo tag (separate but related feature).
There was a problem hiding this comment.
Good point, I renamed "Layout direction override"
features/bidirectional-override.yml
Outdated
| @@ -0,0 +1,18 @@ | |||
| name: Bidirectional override | |||
| description: The `unicode-bidi` and `direction` CSS properties override the Unicode layout algorithm in non-HTML documents. Authors should use the `dir` global HTML attribute instead. | |||
There was a problem hiding this comment.
"in non-HTML documents" doesn't seem right? Do they only apply in that case?
There was a problem hiding this comment.
They are applied in HTML documents, but use is discouraged. Stylesheets could be disabled, so text direction should be set in the HTML and not in CSS. I updated the description to clarify.
…idirectional-override
…idirectional-override
| @@ -0,0 +1,17 @@ | |||
| name: Layout direction override | |||
| description: The `unicode-bidi` and `direction` CSS properties override the Unicode layout algorithm. For HTML documents, authors should use the `dir` global HTML attribute and `<bdo>` HTML element instead. | |||
There was a problem hiding this comment.
As written, this sounds like an anti-feature. Is it possible you could link to some history about this feature? I'm wondering who it's for, if it's not deprecated.
There was a problem hiding this comment.
Good point- I'm not seeing historical posts about this, but both MDN and WebReference say it is explicitly for DTD designers, so I updated the description.
ddbeck
left a comment
ddbeck
left a comment
There was a problem hiding this comment.
Optional description suggestions for you. In any case, ready to go. Thank you!
Co-authored-by: Daniel D. Beck <daniel@ddbeck.com>
3 participants
No description provided.