Prefill bug report form instead of clipboard usage

[Chriki]

I find it potentially problematic that JOSM automatically copies error reports to the clipboard. This can easily overwrite important user data which has been in the clipboard previously. I’d suggest to rather offer a button like “Copy Report to Clipboard” so that the user has the possibility to save her clipboard data before going and reporting the error here.

Thanks,
Chriki™

[stoecker]

Errors are seldom and in an error situation it must be easy for users to report or they don't do it.

[Chriki]

Replying to stoecker:

Errors are seldom and in an error situation it must be easy for users to report or they don't do it.

I agree, therefore I have suggested to add a “Copy Error Report to Clipboard” button.

I am reopening this ticket as there has been no comment, yet, on the actual (data) security problem I have mentioned: IMHO a program should not unexpectedly overwrite the contents of the system clipboard. The loss of data for the user is potentially much more severe than a not reported JOSM problem.

[stoecker]

You are right, that the clipboard loss is a drawback, but one has to choose between different possibilities. Getting the bug reports outweights the clipboard loss ATM and getting the full bug reports is an important issue.

As said these troubles are very seldom (most problems do not issue an exceptions anymore). Currently after the API 0.6 switch the number of these reports is a bit higher, but JOSM generally is very stable.

Adding another inbetween step (even a button) will reduce helpful reports.

I change that to an enhancement. When the bug-report call uses prefilled data we can drop the clipboard usage at all

[xeen]

Ideally JOSM would open a browser page with the bug report already filled in. How about writing a bug report.html in the temp directory and opening it automatically in the default browser? It even reduces the amount of steps to take.

I haven't checked, but I believe submitting to another domain from a local file is going make the browsers post a dozen warnings which isn't too good either.

[Hb---]

Works as expected now, probably fixed with #8571.