error details are not keyboard-navigable

Observed behavior

the error details are currently implemented using a <pre> tag instead of a <textarea>:

This means that you can’t get a cursor into the text area, or use ctrl-a to select all. Instead, it selects everything on the page:

Expected behavior

I expected to be able to put a cursor in there and then:

• use ctrl-a, ctrl-c, or
• or, move the cursor around and select subsets of the text using the keyboard

User-facing consequences

slightly different UX than typical for this kind of UI

Errors and logs

N/A

Steps to reproduce

Try to tab down to the field

Context

see #4051

[indirectlylit]

A <text-area> seems an odd decision, given that this isn’t supposed to be taking any input? I can understand some use cases for subset selection, but wouldn’t the “copy-to-clipboard” button be more ideal than doing the ctrl-a, ctrl-c procedure?

This is pretty standard behavior for a crash report. Some examples:

Adobe:

Mozilla:

OSX:

Purely subjective, but being able to tab into the error isn’t behavior I’d expect o.o

Not all users think like you 😃

[indirectlylit]

fixed in #4232