JabRef version
5.10 (latest release)
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Import something by id, and click "cancel". The dialog disappears, so it looks like it canceled the request. But if the request actually times out (or fails for some other reason) you still get the error dialog shown.
A proper fix would require to cancel/disconnect from the actual http request, and that might be a major refactoring. But at least the composite id fetcher should have a option to not ask the next id fetcher, and errors should be hidden from the users after cancel.
Appendix
...
Log File
Paste an excerpt of your log file here
JabRef version
5.10 (latest release)
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Import something by id, and click "cancel". The dialog disappears, so it looks like it canceled the request. But if the request actually times out (or fails for some other reason) you still get the error dialog shown.
A proper fix would require to cancel/disconnect from the actual http request, and that might be a major refactoring. But at least the composite id fetcher should have a option to not ask the next id fetcher, and errors should be hidden from the users after cancel.
Appendix
...
Log File