1770696 - MV3 non-persistent background pages vs native messaging host

Status: RESOLVED FIXED

(WebExtensions :: General, defect, P2)

Description

[Ales Pospichal]

Steps to reproduce:

Converted existing extension (working correctly) with MV2 to MV3, manifest had this setting:
"background": {
"persistent": false,
"scripts": [ "background.js" ]
},

Extension is connecting to native messaging host from background script using chrome.runtime.connectNative()

Actual results:

MV2: Background script remained active as long as the connection with native host was live
MV3: Background page is disconnected every time after 30 seconds of inactivity and native host process is killed

Expected results:

Same behavior as with MV2

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Messaging System' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Luca Greco [:rpl] [:luca] [:lgreco]]

Attachment: Bug 1770696 - Reset the background script idle timer if the extension have native app ports still open. r?mixedpuppy!

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d9d595b22939
Reset the background script idle timer if the extension have native app ports still open. r=mixedpuppy

Comment 4

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/d9d595b22939