If the server is not responsive and user clicks again then multiple handlers are setup and when the server is back they will all fire (creating different requests and different QRs in succession)
Either the button should be disabled if a connection is being attempted, or at least when clicked again it should cancel the first request.
If the server is not responsive and user clicks again then multiple handlers are setup and when the server is back they will all fire (creating different requests and different QRs in succession)
Either the button should be disabled if a connection is being attempted, or at least when clicked again it should cancel the first request.