I guess this is known issue with traceur/ng2 that was recently fixed... https://github.com/angular/angular/issues/2163 Not sure if you are already aware, thought I'd share in case other Safari users come along.
I guess this is known issue with traceur/ng2 that was recently fixed... angular/angular#2163
Not sure if you are already aware, thought I'd share in case other Safari users come along.