Skip to content

Unnecessarily persistent background in Firefox #167

@wheelercj

Description

@wheelercj

Neither Stardown's Chrome nor Firefox manifests specify whether the background should be persistent, which means the Firefox version (which uses manifest v2) is persistent while the Chrome version (manifest v3) is not persistent (source: background - Mozilla | MDN). Stardown seems to work well in Chrome, so the Firefox version should probably be changed to not be persistent.

Convert to non-persistent

This change may have a side benefit in the future. Stardown currently doesn't listen for the onUpdateAvailable event, but it might someday. The quote below is from the Chrome docs but has a decent chance of applying to Firefox too.

If your extension is using a persistent background page, the background page of course never gets unloaded, so unless you call chrome.runtime.reload() manually in response to [the onUpdateAvailable] event the update will not get installed until the next time Chrome itself restarts. If no handlers are listening for [the onUpdateAvailable] event, and your extension has a persistent background page, it behaves as if chrome.runtime.reload() is called in response to [the onUpdateAvailable] event.

chrome.runtime  |  API  |  Chrome for Developers

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions