New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make reload desktop notifications more concise #796
Comments
this is indeed a pretty good first bug! I hope someone will pick it up soon as an introduction to web-ext |
@saintsebastian If you want to grab it, then feel free :) I only added the label since it is a small change but I do think we should make this change sooner rather than later. |
@kumar303 Hi! If no one has taken this on yet, I'd love to take a stab at it. (with some guidance since this would be my first open source bug fix) |
@francesar Hey! I think I can point you to a couple of places to look into. Notifications utility function is here and they are created here. Let me know if I can help you with anything else and good luck! |
Hey, I am new to open source, and I think I fixed this issue (I'm not actually sure if I did it correctly) Is it okay if I open a pull request? |
Is this a bug or feature request?
feature
What is the current behavior?
web-ext run
You will see a desktop notification telling you that the extension could not be reloaded because of an error:
What is the expected or desired behavior?
It's hard to glance at this and know what just happened. Can we make it more concise? Here is a suggestion (but maybe there are other things we can do):
Change the body to "unknownError: error occurred while processing ...." In other words, remove "reload response error:" from the message because that's redundant. The title of the notification already tells you that an error occurred.
Version information (for bug reports)
v6.9.4
3.10.10
1.8.1
The text was updated successfully, but these errors were encountered: