You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What do we mean by "safe" here? If we allow treating a bound string as markup, there's not much safety to be had. Off the top of my head the main safety to be had would be if we allowed binding to some constructed DOM hung off the model (sort of a model-as-template). Or is there something else we can do?
Abarth's original plan about this sort of mirrored the approach that ruby
takes which is to allow markup to be evaluated, but limited by a policy in
what constructs can be contained in the markup.
It's possible that this is an orthogonal, but related primitive that we
need to raise. In any case, it seems like it's a requirement that there by some mechanism for achieving this.
What do we mean by "safe" here? If we allow treating a bound string as
markup, there's not much safety to be had. Off the top of my head the main
safety to be had would be if we allowed binding to some constructed DOM
hung off the model (sort of a model-as-template). Or is there something
else we can do?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-8133366.
No description provided.
The text was updated successfully, but these errors were encountered: