-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Always apply isolation when u:dir
is set
#942
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is an important and quite useful improvement.
@@ -102,6 +105,25 @@ | |||
{ "type": "bidiIsolation", "value": "\u2069" } | |||
] | |||
}, | |||
{ | |||
"src": ".local $world = {world :string u:dir=ltr u:id=foo} {{hello {$world}}}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is intended as the transitivity text, I think? Should we have one with mulitple .local
declarations? or .input
followed by .local
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eh, not sure if it's necessary. I think the important part is making sure that moving the option from the placeholder to a declaration works.
Co-authored-by: Addison Phillips <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
See #916 for some of the preceding discussion.
In addition to changing the directionality of a placeholder, we should treat an explicitly set
u:dir
option as a request to isolate the placeholder, even if the direction matches the message's direction.This requires a small change to our default bidi strategy.
The inheritance of the option is not specified when it's set on a value that's used as a function operand, so e.g. a message like
might or might not have the placeholder isolated (depending on the implementation), while it would always be isolated in messages like
and