Re: [AngularJS] AngularJS Chart for StockExchange

On Sunday, April 17, 2016 at 12:49:48 AM UTC+1, samy chihi wrote: > > here you go :) > > On Sunday, April 17, 2016 at 12:22:04 AM UTC+1, Tito wrote: >> >> habibi. in chrome right click on white page and select inspect element to >> see the console. and what errors do u see. > > -- You

Re: [AngularJS] AngularJS Chart for StockExchange

here you go :) On Sunday, April 17, 2016 at 12:22:04 AM UTC+1, Tito wrote: > > habibi. in chrome right click on white page and select inspect element to > see the console. and what errors do u see. -- You received this message because you are subscribed to the Google Groups "AngularJS" group.

Re: [AngularJS] AngularJS Chart for StockExchange

i forget to mention i tested this with google chrome, firefox and Safari under macbook then i re-tested under windows server 2012 with internet explorer and firefox, always i'm getting the white page as in screenshot 1.png Thanks, Samy On Sunday, April 17, 2016 at 12:00:58 AM UTC+1, samy chihi

[AngularJS] Re: [angular2] Differents behavior between Chrome and FireFox

There are known issues with input elements that behave differently between browsers (broken in FF) There is no need to add directives : [ FORM_DIRECTIVES, NgForm, NgIf, NgFor ] they are available globally by default since a while On Friday, April 15, 2016 at

[AngularJS] Re: custom html component using the formbuilder in angular 2

You need to create your own ControlValueAccessor or implement it in your component to make `ngModel` work with it. There should be several examples on SO already. On Friday, April 15, 2016 at 11:12:01 PM UTC+2,

[AngularJS] Re: Angular2 - Unhandled Promise rejection: No provider for ElementRef

I don't see anything wrong. You can shorten the constructor to constructor(private elementRef: ElementRef){} (or `public` instead of `private`) Your problem is outside of the code your provided. Does your component not have a `template` or is this just because you shortened the code

[AngularJS] Re: [angular 2] Is it necessary to dispose of Observable subscriptions in ngOnDestroy()?

When the components class isn't referenced anywher anymore it will be garbage collected and your subscription with it (when no other class holds a reference to it) On Friday, April 15, 2016 at 6:07:41 PM UTC+2, Brian Kotek wrote: > > One thing that I'm not clear on is whether I'm required to

[AngularJS] Re: Angular JS binding when back from diffrent page

I think you refer to regular web, not a single page app. The answer on how to share state between controllers on completely different pages, or on the same page after a page reload (or navigate and cone back later) is still the same -service. You need a service that can preserve state. Whether