Cornelius Schmale

I had the same issue and nailed it down to be a watchpack problem. https://github.com/webpack/webpack/issues/4341

I confirm: Manually entered (typed) dates in inputs with datepicker-popup, which are outside minDate/maxDate-restrictions, will not mark the input as invalid. (still `ng-valid` / `ng-valid-date` instead of `ng-invalid` / `ng-invalid-date`)....

Can confirm this error. Problem is incorrect path definition for loaded content in webview. It tries to load a) search-window from a path where it does not exist b) file:///C:/UsersusernameDocumentsgitfolderdistdefault-style.css...

In your method 'fixPathSlashes' you use 'process.platform' which is undefined on my machine. This leads to unloadable search-window.js.

It would be great if this could be merged.

Is there any workaround for this?

Thats true. `directConnect: false` results to `Error: browserName (phantomjs) is not supported with directConnect.`

+1