Now the behaviour in the OP JSFiddle link is consistent in Canary (WP flag enabled) and Chrome stable (WP flag disabled) - changes made inside the Polymer Element are not propagated to the model.
Is this intentional? What's the workaround? On Thursday, January 23, 2014 5:57:32 PM UTC+1, Tomek W wrote: > > Hi, > > I'm a bit confused what is the right way to do so, especially that my > snippet behaves inconstantly between Canary and regular Chrome. > > Here http://jsfiddle.net/tomalec/F8j3F/ is an example. > > (I took from http://www.polymer-project.org/getting-started.html as a > merge of binding between elements and 'Publishing properties') > > In regular Chrome (32.0.1700.76 m) it behaves as I desire - it binds all > 4 {{name}} together. However, Canary (34.0.1799.0 canary) isolates > changes to (published) attribute made within custom element. > > Is it a bug in Canary? > If not, what is the correct way to notify outer binding about attribute's > change? > > Thanks, > 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/ca68447a-1609-4aab-8d23-54568f8707ad%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
