For the application we need to test to work well, we need to start browser Chrome with a setup option: " --allow-running-insecure-content"
Right now, this scenario is not supported in LoadComplete, since you can only select caching mode:
Currently, there is not an option to set any chrome startup flags, so if you enable the option "Launch Web browser", Chrome is started (by LoadComplete), there is no way to control Chrome (or any other browser) setup behaviour.
