Update bug_report.md less is more #2323
Conversation
|
hi! @raszpl
this is a bit long:
those (fewer) people who know chrome://extensions, might also know how to see the version there already |
|
*...Concluding, you might be motivated, when everything is criticized , such as 2293 (if not both of you or protective Vivaldi fans), Isn't such motivation stressful though? (if not, i should i might start to publish frustrations about almost everything 😲)(More seriously, to "protect oneself from trolls", we can care equally for all issues or the thumbs for the release) |
"Steps to reproduce" is enough. Keep it simple. Settings dont really matter at the moment of bug submission. Can ask for settings later when unable to reproduce.
Its not F12 in all browsers\oses. I specifically left it brief as a filter - If someone doesn know what devtools/console is he wont be able to recognize what is a valid error message and what is not.
Its as long as the text you replaced it with, except: "(Written in the Extension header & your Browser's store)" version is not showing in extension header, you need to close search In fact in newest Chrome even chrome:extensions is not enough, its still hidden under Details :/ What I didnt like in the first place :
Whats the point of telling someone to be clear and concise? Its patronizing. Moving instructions to the right side of colon means people will just live whole line like this, cant expect people to edit the template.
trailing ')'. Now that I clicked New Issue again I realize template doesnt display formatted, so the whole code line will give most non technical people grief, should be in new line to avoid confusion
How many people know what a root element is? :) I wouldnt even know how would that be of any use to me while debugging. Its one of those things that can be asked later if its actually needed.
as above no idea how that would help me with debugging. |
Less text, more concise.