Allow insecure hosts

[stassinari]

I'm trying to use chromeless on my machine (macOS Sierra) to test my local webapp.

The issue is that the test gets stuck at the "Your connection is not private" Chrome page.

I know there is the Chrome flag --allow-running-insecure-content you can pass when executing the Chrome binary, but it would be great if I could keep the ability to open Chrome for my scripts instead of having to open it beforehand.

So I was wondering if there was a way of passing arbitrary Chrome flags to the Chromeless constructor?

Thank you

[adieuadieu]

Hi @stassinari — Thank you for sharing your use-case. I'm going to close this issue as a duplicate of #184 which is being addressed by PR #192. In other words—we should see this feature released in v1.3. 😄

Duplicate of #184