Closed
Bug 1736090
Opened 4 years ago
Closed 4 years ago
Multiple JS errors with Import dialog
Categories
(Thunderbird :: General, defect)
Thunderbird
General
Tracking
(thunderbird_esr91 unaffected, thunderbird94 wontfix)
RESOLVED
FIXED
95 Branch
| Tracking | Status | |
|---|---|---|
| thunderbird_esr91 | --- | unaffected |
| thunderbird94 | --- | wontfix |
People
(Reporter: aleca, Assigned: mkmelin)
Details
(Keywords: regression)
Attachments
(1 file)
When opening the Import dialog, these errors show up in the terminal:
JavaScript error: chrome://messenger-newsblog/content/feed-subscriptions.js, line 2117:
TypeError: can't access property "getAttribute", el is null
JavaScript error: chrome://messenger-newsblog/content/feed-subscriptions.js, line 775:
TypeError: can't access property "focus", FeedSubscriptions.mTree is null
When interacting with the dialog, every click produces this error:
JavaScript error: chrome://messenger-newsblog/content/feed-subscriptions.js, line 2150:
TypeError: can't access property "textContent", document.getElementById(...) is null
| Assignee | ||
Comment 1•4 years ago
|
||
Harmless, but yes we should fix it.
Assignee: nobody → mkmelin+mozilla
Keywords: regressionwindow-wanted
| Reporter | ||
Comment 2•4 years ago
|
||
I just discovered that the same "textContent" error prevents closing the dialog with the Escape key.
| Assignee | ||
Comment 3•4 years ago
|
||
That feed-subscriptions.js is "shared" is of course wrong. Things should be modularized, but since they are not...
Had regressed by https://hg.mozilla.org/comm-central/rev/fa72aeb98faaa70e429cf1ebc46d314866cd571b
I also notice the onClose() did apparently not exist at all.
Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/0a6c70474a48
move event handling back to feed-subscriptions.xhtml since feed-subscriptions.js is shared. r=aleca
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•4 years ago
|
status-thunderbird94:
--- → wontfix
Target Milestone: --- → 95 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•