If reporting a bug:

1. __When does this occur?__
<!-- Ex. Going to settings, every night at 3pm, when I go to search -->

2. __Can (and how do) we replicate the issue?__
<!-- Please be specific as possible. Use dashes (-) or numbers (1.) to create a list of steps -->

3. __Expected behavior (i.e. solution)__
<!-- What should have happened? -->

4. __Other comments__

If reporting a bug:

1. __When does this occur?__
<!-- Ex. Going to settings, every night at 3pm, when I go to search -->

2. __Can (and how do) we replicate the issue?__
<!-- Please be specific as possible. Use dashes (-) or numbers (1.) to create a list of steps -->

3. __Expected behavior (i.e. solution)__
<!-- What should have happened? -->

4. __Error stack (from extension crash page)__
<!-- Did the issue lead you to the crash page? -->

5. __Other comments__

Add Error stack to issue template for runtime errors
Add Error stack to issue template for runtime errors

- if the issue is from an in-extension crash, they'll arrive at the crash page with the error stack info available to copy and paste
