1777826 - Console Error during Import: Uncaught TypeError: startController is undefined

Status: NEW

(MailNews Core :: Import, defect, P2)

Description

[Thomas D. (:thomas8)]

This occured while testing for the latest bugs I filed. 102.0 (64-bit), win10
And why does aboutImport also have a step "toExport"??

about:addressbook : Unable to run script because scripts are blocked internally. (Typically occurs 30 times en block)

Uncaught TypeError: startController is undefined
restart chrome://messenger/content/aboutImport.js:1491
showTab chrome://messenger/content/aboutImport.js:1450
toImport chrome://messenger/content/mailCore.js:549
setTimeout handler*toImport chrome://messenger/content/mailCore.js:548
toExport chrome://messenger/content/mailCore.js:563
oncommand chrome://messenger/content/messenger.xhtml:1
aboutImport.js:1491:3

Comment 1

[Martin Giger [:freaktechnik]]

I believe the reason this happens is https://searchfox.org/comm-central/rev/4326871adc58e1f014f000fea10b265e5d9c48bb/mail/base/content/mailCore.js#546-547 - we have to try to make the about import tab show the correct thing twice when trying to open it.

Comment 2

[Thomas D. (:thomas8)]

Can someone enlighten me why this is now in Feed Reader component?

Comment 3

[Magnus Melin [:mkmelin]]

Can't reproduce.
Martin: maybe we should add { once: true} to https://searchfox.org/comm-central/rev/12d3830dea34b6289efb9dad17496dac8c093ab1/mailnews/import/content/aboutImport.js#1510?

Comment 4

[Martin Giger [:freaktechnik]]

The issue isn't that the listener runs more than once, the issue is that the code in mail core I linked above calls showTab in the import tab's context before the dom content loaded listener ran.

But sure, adding a once to that listener should be fine, it's a dom content loaded listener after all.