Closed
Bug 1376123
Opened 7 years ago
Closed 7 years ago
Warning: "ReferenceError: assignment to undeclared variable ritem" {file: "file:///[...]/components/calStorageCalendar.js" line: 1893}
Categories
(Calendar :: Provider: Local Storage, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
5.8
People
(Reporter: mschroeder, Assigned: mschroeder)
Details
Attachments
(1 file)
1.28 KB,
patch
|
redDragon
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•7 years ago
|
||
Attachment #8881063 -
Flags: review?(philipp)
Comment 2•7 years ago
|
||
Comment on attachment 8881063 [details] [diff] [review] Patch v1 Review of attachment 8881063 [details] [diff] [review]: ----------------------------------------------------------------- LGTM
Attachment #8881063 -
Flags: review+
Assignee | ||
Updated•7 years ago
|
Attachment #8881063 -
Flags: review?(philipp)
Assignee | ||
Updated•7 years ago
|
Keywords: checkin-needed
Comment 3•7 years ago
|
||
Is this an actual error or just a strict warning? In the former case, what regressed it and what branches are affected, i.e. do we need to port it back to beta or release? Do you have a test case that could be used for unit test to prevent similar regression?
Flags: needinfo?(mschroeder)
Assignee | ||
Comment 4•7 years ago
|
||
It is just a JavaScript warning, so I do not intend to request a backport or write an unit test as this is a pure programming oversight.
Flags: needinfo?(mschroeder)
Updated•7 years ago
|
Summary: "ReferenceError: assignment to undeclared variable ritem" {file: "file:///[...]/components/calStorageCalendar.js" line: 1893} → Warning: "ReferenceError: assignment to undeclared variable ritem" {file: "file:///[...]/components/calStorageCalendar.js" line: 1893}
Version: Trunk → Lightning 5.8
Comment 5•7 years ago
|
||
https://hg.mozilla.org/comm-central/rev/5f8fb8c490aa4ecbf5236a84ab6f069b85235dd7
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → 5.8
You need to log in
before you can comment on or make changes to this bug.
Description
•