Error notification dialog: "Error number" should be "Error code"

RESOLVED FIXED in 1.0b1

Status

Calendar
General
--
minor
RESOLVED FIXED
9 years ago
6 years ago

People

(Reporter: Robert Brand, Assigned: Fallen)

Tracking

unspecified
1.0b1

Details

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090220 Calendar/1.0pre

With the revised provider error notifications from Bug 392561 errors I see don't have numbers anymore, but are something like UTF8_DECODING_FAILED or MODIFICATION_FAILED. In such cases the string "Error number" in the error dialog looks strange.
I'd suggest to call it "Error code" as it is called in corresponding message in the error console.

Reproducible: Always

Steps to Reproduce:
1. Subscribe to a remote calendar (ICS) you don't have write access to.
2. Try to create a new event in this calendar.
3. Have a look at the error notification and into the error console.
(Assignee)

Comment 1

9 years ago
Created attachment 363605 [details] [diff] [review]
Fix - v1
Assignee: nobody → philipp
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attachment #363605 - Flags: review?(bugzilla)
Comment on attachment 363605 [details] [diff] [review]
Fix - v1

Stealing review.  ;) r=mschroeder
Attachment #363605 - Flags: review?(bugzilla) → review+
(Assignee)

Comment 3

9 years ago
Pushed to comm-central <http://hg.mozilla.org/comm-central/rev/3dd8f05f37cf>

-> FIXED
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
OS: Windows XP → All
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → 1.0
(Assignee)

Comment 4

6 years ago
These bugs are likely targeted at Lightning 1.0b1, not Lightning 1.0. If this change was done in error, please adjust the target milestone to its correct value. To filter on this bugspam, you can use "lightning-10-target-move".
Target Milestone: 1.0 → 1.0b1
You need to log in before you can comment on or make changes to this bug.