Skip to content

Conversation

timdorr
Copy link
Member

@timdorr timdorr commented Jan 7, 2016

Firefox and Chrome were really old and auto-update now.

Also, iOS 9 and 8 distribution is high, so they should be tested too. Also bumped up Safari and used Windows 10 where possible.

@taion
Copy link
Contributor

taion commented Jan 7, 2016

Chrome 39 is sorta special since it's what Travis uses. If we have something that's broken in Chrome 39, we're likely to cause pain to our users who use Travis for their CI.

@timdorr
Copy link
Member Author

timdorr commented Jan 7, 2016

What if we ran against the installed version of Chrome, rather than via BrowserStack? That way we stay in lockstep if Travis ever updates their build environment again (no idea what the holdup is. It's been 8 months...)

@taion
Copy link
Contributor

taion commented Jan 7, 2016

Sounds like a good idea to me. @mjackson, any thoughts?

Maybe we can configure this with .travis.yml ENV.

@timdorr
Copy link
Member Author

timdorr commented Jan 7, 2016

I'll just make the BS config not overwrite the non-BS config. Should work fine.

@timdorr timdorr force-pushed the upstack branch 3 times, most recently from 11f20d2 to 295b098 Compare January 7, 2016 22:01
timdorr added a commit that referenced this pull request Jan 7, 2016
Update our tested browsers
@timdorr timdorr merged commit 5e824a7 into master Jan 7, 2016
@timdorr timdorr deleted the upstack branch January 7, 2016 23:03
@taion
Copy link
Contributor

taion commented Jan 7, 2016

Might be worth updating rackt/history as well, then.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants