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

Ensure {{}} are removed after binding #304

Closed
sorvell opened this issue Oct 2, 2013 · 5 comments
Closed

Ensure {{}} are removed after binding #304

sorvell opened this issue Oct 2, 2013 · 5 comments
Assignees

Comments

@sorvell
Copy link
Contributor

sorvell commented Oct 2, 2013

No description provided.

@ghost ghost assigned sorvell Oct 2, 2013
@sorvell
Copy link
Contributor Author

sorvell commented Oct 8, 2013

Binding mustaches are potentially valuable serialization data. For example, the template binding library leaves if and repeat attributes as mustaches. It does this (presumably) so that the serialized html can be deserialized and bound again to produce the same result.

Currently, polymer leaves binding mustaches in the dom when values cannot be serialized because they are objects. This allows the same behavior as described above. If we remove or alter this data, we lose this ability.

@sorvell
Copy link
Contributor Author

sorvell commented Oct 8, 2013

The above point is not convincing since It's not possible in general to serialize/deserialize to a bound state. This is because attributes store binding mustaches and also express bound values.

@sorvell sorvell assigned sjmiles and unassigned sorvell Aug 14, 2014
@sorvell
Copy link
Contributor Author

sorvell commented Aug 14, 2014

I don't think we should bother to do this. For performance reasons, I don't want to touch any attributes the user hasn't specifically asked us to reflect.

@sjmiles wdyt?

@sjmiles
Copy link
Contributor

sjmiles commented Aug 15, 2014

There's no rationale given in the original post for why it would be a good thing to affect these attributes. Until and unless a strong argument emerges, I agree we should not take action.

@sorvell
Copy link
Contributor Author

sorvell commented Aug 15, 2014

Will reopen/refile if this becomes relevant.

@sorvell sorvell closed this as completed Aug 15, 2014
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