Travis: test with more platforms

[vicb]

What about testing with more browsers:

• IE,
• Safari,
• Firefox,
• Chrome

I had been working on testing angular.dart on those platforms with SauceLabs, ref dart-archive/angular.dart#1288

[caitp]

Would it not make sense to bring mobile browsers in early for the benchmarks? (no pressure)

[EisenbergEffect]

I would certainly vote for that. I think we've been emphasizing mobile to
the community. So, if we want to keep ourselves honest, we should probably
start testing that up front.

On Tue, Sep 30, 2014 at 9:34 AM, Caitlin Potter notifications@github.com
wrote:

Would it not make sense to bring mobile browsers in early for the
benchmarks? (no pressure)

—
Reply to this email directly or view it on GitHub
#35 (comment).

Rob Eisenberg,
President - Blue Spire
www.durandaljs.com

[tbosch]

Yes, we should add more browsers.
But probably not until AngularJS 1.3 and AngularDart 1.0 are out to not
cause more Travis digestion problems, as we only have a limited amount of
granted vms...

On Tuesday, September 30, 2014, Rob Eisenberg notifications@github.com
wrote:

I would certainly vote for that. I think we've been emphasizing mobile to
the community. So, if we want to keep ourselves honest, we should probably
start testing that up front.

On Tue, Sep 30, 2014 at 9:34 AM, Caitlin Potter <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');>
wrote:

Would it not make sense to bring mobile browsers in early for the
benchmarks? (no pressure)

—
Reply to this email directly or view it on GitHub
#35 (comment).

Rob Eisenberg,
President - Blue Spire
www.durandaljs.com

—
Reply to this email directly or view it on GitHub
#35 (comment).

[ericwj]

Even if you will test other browsers later, it'd be nice to get some issues out of the way perhaps - simple things such as vendor prefixes?

For example would you like me to patch elementMatches in browser_adapter.ts? It calls Element.matches(string) which is still prefixed as msMatchesSelector in IE and Edge and that breaks my template that uses <content select="[ding]"/> in those browsers and everything else comes down as a result as well.

[pkozlowski-opensource]

We've got a PR for this already: #2347

[mhevery]

@Mlaval is already working on this.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}