The fix committed handles the situation, when the app is started without network connection, quite well. Losing the connection when the app is open, and after a request was already made, can still lead to the desribed behaviour. But trying then a second time without connection should open the notification, though.
Unfortunately XMLHttpRequest.onTimeout isn't supported by QtQuick, will further investigate a possible solution.
The fix committed handles the situation, when the app is started without network connection, quite well. Losing the connection when the app is open, and after a request was already made, can still lead to the desribed behaviour. But trying then a second time without connection should open the notification, though.
Unfortunately XMLHttpRequest. onTimeout isn't supported by QtQuick, will further investigate a possible solution.
Thanks for the report!