Skip to content

Specify window size for the karma chrome launcher (Fixes #444) #445

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 20, 2016

Conversation

monfera
Copy link
Contributor

@monfera monfera commented Apr 19, 2016

Fixes #444 by specifying a certain window size for the Chrome launcher. The numbers are simply derived from observing the window size in the properly working case.

CI karma/jasmine testing isn't impacted because, while CI piggybacks on this baseline config file, it specifies a separate browser (currently, Firefox). @etpinard suggested we don't change CI starting options right now.

I haven't experienced any problems with the fact that the browser we use is named differently (we can't name it Chrome as it's wired to mean plain vanilla Chrome and is being referenced as the base.

@monfera monfera changed the title #444 specify window size for the karma chrome launcher Specify window size for the karma chrome launcher (Fixes #444) Apr 19, 2016
@etpinard
Copy link
Contributor

Nice solution.

This works like a charm on my machine.

@mdtusz @n-riesco @timelyportfolio could you try to pull this branch down and run:

 npm run test-jasmine -- tests/click_test.js

Thanks.

@n-riesco
Copy link
Contributor

n-riesco commented Apr 19, 2016

WFM (Executed 29 of 29 SUCCESS)

I've just looked into the PR; would this PR force us to use Chrome?

@mdtusz
Copy link
Contributor

mdtusz commented Apr 19, 2016

Works for me!

@etpinard
Copy link
Contributor

Ok. Let's give a shot.

@etpinard etpinard merged commit a66f3f4 into plotly:master Apr 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants