Skip to content
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

design context-aware bindings #8

Open
rafaelw opened this issue Aug 24, 2012 · 1 comment
Open

design context-aware bindings #8

rafaelw opened this issue Aug 24, 2012 · 1 comment

Comments

@rafaelw
Copy link
Collaborator

rafaelw commented Aug 24, 2012

which property escape binding content based on the type of the attribute content

@ajklein
Copy link
Owner

ajklein commented Aug 29, 2012

Given our current binding model (text nodes and attribute values), are there any cases we need to worry about besides URLs?

Within an URL, we should probably validate schemes, if there's a placeholder at the start (no "javascript:", for example). But after that it's not obvious to me what we can do automatically, unless we restrict how placeholders work in URL attribute bindings. That is, in <img src="http://www{{ foo }}/bar/baz.jpg">, it's not clear what restrictions we would want to put on {{foo}}, if any. But perhaps we could do something smart with <a href="http://www.site.com/foo/bar?baz={{ foo }}">.

Okay, I think it's not really about putting "restrictions", it's just that we can only do special handling if we can parse the leading parts of the URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants