In case of missing signal, or the server not responding to the client anymore, users should be aware that their save may or may not have gone through. Different ues cases are:
- The network dropping (or changing) mid request
- The api never responding at all
- The api responding in a way we don't understand (a malformed response)
In all of these cases, we cannot tellwe follow the users what the current state is.general error handling pattern, Sobut we want to encourage the user to do !!what?!!
!!TODO!!give a meaningful error message
 After !!TODO!! seconds of not hearing back from the server, show an error message !!TODO including it may or may not have been saved!, and that we will not be able to tell them!! in an overlay to the user as shown in the mock
 Initially the popup appears on top of the content page (between grey bar and content, if possible, but if not possible, then above the grey bar)
 Users can scroll content "behind" the popup
 The error message does not disappear until the error is resolved (successful save, cancel button or leaving the page)
 As long as the save is not confirmed, input fields are disabled !!or are they not?!!
Can it happen that we receive a server response after the client has already given up hope, and what would be the result?