Some questions about what behavior is defined for data binding (and what's
undefined behavior and should be avoided) when using properties which
aren't actually defined.

https://jsfiddle.net/daLLdao2/

If I give a Polymer tag some-made-up-attribute="foo", nothing happens. But
if I give that made-up attribute a value via data binding
(some-made-up-attribute="[[myProperty]]"), the Polymer element gets a new
someMadeUpAttribute property set to the value and type of myProperty. Is
that okay, or should we not expect that to work?

It gets weirder: if I want to create a property and assign it to a literal,
I can do this:
    some-made-up-attribute="[[notARealProperty]]my string literal"
the attribute someMadeUpAttribute is again created on the child, and given
the string value "my string literal". Is that a fluke, or is data binding
defined to work that way?

Follow Polymer on Google+: plus.google.com/107187849809354688692
--- 
You received this message because you are subscribed to the Google Groups 
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/polymer-dev/CACi5S_1%2BiB7SpHQkhEANxpvhe-4Dgp%3DYNnL%2BU%2Be0obHySi-3pA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to