Closed Bug 1688887 Opened 4 years ago Closed 4 years ago

Add-on search field no longer works - Uncaught TypeError: aOpenParams is undefined

Categories

(Thunderbird :: General, defect)

Thunderbird 86
Unspecified
All
defect

Tracking

(thunderbird_esr78 unaffected, thunderbird86+ verified)

VERIFIED FIXED
87 Branch
Tracking Status
thunderbird_esr78 --- unaffected
thunderbird86 + verified

People

(Reporter: TbSync, Assigned: TbSync)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

The function switchToTabHavingURI() does not have a default value for the aOpenParams parameter, but Geoff removed this parameter to a call here which causes the search to fail:
https://searchfox.org/comm-central/source/mail/base/content/utilityOverlay.js#349

I propose to add a default parameter value for the aOpenParams parameter, same as for Firefox.

Keywords: regression

Set default value for aOpenParams parameter.

Attachment #9199261 - Flags: review?(mkmelin+mozilla)
See Also: → 1688428
Comment on attachment 9199261 [details] [diff] [review] bug1688887_set_default_value_for_aOpenParams.patch Review of attachment 9199261 [details] [diff] [review]: ----------------------------------------------------------------- Looks good, thx! r=mkmelin
Attachment #9199261 - Flags: review?(mkmelin+mozilla) → review+

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/f5391028d2fd
Set default value for aOpenParams parameter in switchToTabHavingURI(). r=mkmelin DONTBUILD

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 87 Branch

Thanks for fixing this. Danny Colin indicates this is now working on nightly. So ready for uplift to beta?

Beta shows
Uncaught TypeError: aOpenParams is undefined
switchToTabHavingURI chrome://messenger/content/mailWindow.js:987
openLinkIn chrome://communicator/content/utilityOverlay.js:349
searchAddons chrome://mozapps/content/extensions/aboutaddons.js:1239
handleEvent chrome://mozapps/content/extensions/aboutaddons.js:1203
_fireCommand chrome://global/content/elements/search-textbox.js:231
_enterSearch chrome://global/content/elements/search-textbox.js:249
on_keypress chrome://global/content/elements/search-textbox.js:212
handleEvent chrome://global/content/customElements.js:466
mailWindow.js:987:5

Status: RESOLVED → VERIFIED
Flags: needinfo?(john)
OS: Unspecified → All
Summary: Add-on search field no longer works → Add-on search field no longer works - Uncaught TypeError: aOpenParams is undefined
Version: unspecified → Thunderbird 86

Comment on attachment 9199261 [details] [diff] [review]
bug1688887_set_default_value_for_aOpenParams.patch

[Approval Request Comment]
Regression caused by (bug #):
User impact if declined:
Testing completed (on c-c, etc.):
Risk to taking this patch (and alternatives if risky):

Flags: needinfo?(john)
Attachment #9199261 - Flags: approval-comm-beta?

Comment on attachment 9199261 [details] [diff] [review]
bug1688887_set_default_value_for_aOpenParams.patch

[Triage Comment]
Approved for beta. looks like low risk ;)

Attachment #9199261 - Flags: approval-comm-beta? → approval-comm-beta+

Add-ons search working for me in my tests of 86.0b2 on Windows 10 and Fedora 33 Workstation.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: