Great to hear. This caused me troubles in the past because there were often two calls to xxxChanged at startup when run in JavaScript while in Dart there was only one such call.
> Recently we decided to also prevent transitions between undefined and null > from being reported as `*Changed`. It's true this is a lossy change, but it > prevents a lot of unwanted side-effects at construction time where various > properties tend to be in either state, but are almost always indicative of > an _uninitialized_ state. > > > 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/35dcda59-4204-4f8b-98e0-fb45f5f7a650%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
