Eric Bidelman
Eric Bidelman
_From @chriswalz on December 31, 2015 5:3_ My work clunky work around by creating a second property 'a' ``` post: function() { this.a = this.store; // post code } ```
Can you add a test?
Seems like an oversight. Have you tried to reset the `.location` property? That should re-establish a firebase instance. https://github.com/GoogleWebComponents/firebase-element/blob/master/firebase-document.html#L94
I haven't taken a look a the code, but yea, it'll require a coordinated effort among the related components. The FirebaseQueryBehavior should remain unaware of auth.
Please provide full jsbin that repos the issue. On Fri, Feb 12, 2016, 4:36 PM Roberto Simonetti [email protected] wrote: > Hi, > > I am trying to use google-map element...
Not sure exactly what's going on here, but you described the underlying problem. The Google Maps API throws these warnings when the API is loaded more than once. I'm not...
That's correct. Because of how the Maps API loads, it's important to have all your properties known ahead of time, before creating ``. If you change them at runtime, google-map...
It doesn't: http://jsbin.com/tipemoseka/edit?html,output
It looks like Angular is doing something interesting under the hood. Does anyone know more about the internals of how component markup is parsed and setup in Angular2? Seems like...
I think we understand what's happening now. Angular's bootstrap reconstructs the DOM from the string template. This means the attributes are actually "removed" then added one by one: http://i.imgur.com/4b98YFd.png Hence,...