Travis: test with more platforms about angular HOT 7 CLOSED

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

from angular.

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 [email protected]
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

from angular.

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 [email protected]
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 <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');>
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).

from angular.

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.

from angular.

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

from angular.

@Mlaval is already working on this.

from angular.

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.}

from angular.