Bug 1931928 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I think I do not consider this a bug. The WebExtension gets a proper error (2 being the ID of the message that failed to be read).

`Error reading message 2`

The add-on should catch the error. We usually do not expose the URL of the failed message, as it exposes internal information about the users server. The extension tried to read message XY and got the error that reading message XY failed. I attach some screenshots to illustrate the error messages.
Revision 1 by
on 
I think I do not consider the act of throwing as a bug. The WebExtension gets a proper error (2 being the ID of the message that failed to be read).

`Error reading message 2`

The add-on should catch the error. We usually do not expose the URL of the failed message, as it exposes internal information about the users server. The extension tried to read message XY and got the error that reading message XY failed. I attach some screenshots to illustrate the error messages.
Revision 2 by
on 
I think I do not consider the act of throwing as a bug. The WebExtension gets a proper error (2 being the ID of the message that failed to be read).

`Error reading message 2`

The add-on should catch the error. We usually do not expose the URL of the failed message, as it exposes internal information about the users server. The extension tried to read message XY and got the error that reading message XY failed.

Back to Bug 1931928 Comment 4