Request more specific information in bug report#13905
Conversation
|
|
||
| ### Actual behavior: | ||
|
|
||
| #### Actual NVDA speech/braille sample: |
There was a problem hiding this comment.
I'm not sure that this always applies to bug reports. For instance, no (unexpected) speech/Braille is present when apps crash or hang or for developer-facing changes (an API works in an unexpected way, etc.)
There was a problem hiding this comment.
It can be left blank in those cases.
It might be worth indicating optional fields (e.g. including the "other questions", which are generally less relevant than expected speech, NVDA logs, etc)
See test results for failed build of commit a3fd1d124a |
| ### Actual behavior: | ||
|
|
||
| #### Actual NVDA speech/braille sample: |
There was a problem hiding this comment.
What if this is an instruction under the heading instead?
| ### Actual behavior: | |
| #### Actual NVDA speech/braille sample: | |
| ### Actual behavior: | |
| <!-- | |
| Use "Speak command keys" (NVDA+4) and speech viewer to copy and paste here. | |
| Use braille viewer to copy and paste here. | |
| You may additionally include an explanation. | |
| --> |
There was a problem hiding this comment.
I would be reluctant to ask users to copy from Braille viewer, as that is not something which can be done using keyboard only.
There was a problem hiding this comment.
I think these instructions are more likely to be ignored than an explicit field, but this might be a better solution as copied speech/braille is not always relevant (as per #13905 (comment)).
Fixing braille viewer copy/paste sounds like an important thing to do as well.
Link to issue number:
None
Summary of the issue:
It would be helpful if bug reporters include exact speech/braille that is expected vs. occurring.
This is requested in
devDocs\githubIssueTemplateExplanationAndExamples.mdbut not in the issue template.It would also be good to add a section for logs and other attachments, as they are often required when reporting an issue.
This is also requested in
devDocs\githubIssueTemplateExplanationAndExamples.mdbut not in the issue template.Description of user facing changes
Bug reports are now prompted to include explicit speech/braille and NVDA logs.
Description of development approach
N/a
Testing strategy:
Community feedback/usage of new sections
Known issues with pull request:
None
Change log entries:
Code Review Checklist: