Hi, First of all, the fix to close a popup first and then refresh objects really is a big win, better performance, less confusion for the end user because they no longer see a popup briefly change its contents before closing. However, Chrome does complain about some of the new features and suspects insecure behavior. Not sure whether those complaints were also in 6.7.x: Mixed Content: The page at 'https://url.mxapps.io/index.html' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://url.mxapps.io/reload/'. This request has been blocked; this endpoint must be available over WSS. Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://home.mendix.com') does not match the recipient window's origin ('https://url.mxapps.io'). Edit: this still happens in 6.9.0
asked
Marcel Groeneweg ITV
1 answers
2
The errors you're seeing are due to our hotreload feature: the javascript client tries to maintain a websocket to listen for updates. We unfortunately had the oversight of not switching between the ws and wss protocols, which results in the error you're describing. We'll fix this in 6.9.0