Closed oxala closed 8 years ago
Hey @oxala, just wanted to let you know that I was able to reproduce the problem. I am still investigating a fix. I'll update when I know more. Thanks for reporting the problem!
This problem was due to a bug in Marko: https://github.com/marko-js/marko/issues/303
A new version of marko
has been published with a fix. Test cases added to marko-widgets
. This should work now, but please let me know if you see any issues. Thanks!
All good, thank you very much!
Apparently marko3 (or marko-widgets6, not sure which module exactly) stopped understanding two (or more)
w-bind
s inside one template.Whenever such case happens, it only sees the last w-bind it found and applies it to all
w-bind
ed elements in the template.Imagine the
template.marko
file with content:The result of that inside
template.marko.js
would be something like this:It's not necessary to have
w-bind
nested. Having then one after another produce the same result of only the last one being recognised and added to all w-bind elements.