v2.4.3

2.4.3 - the Firefox background comes up, and the tag panel with it

The Firefox archive's background never started at all. Firefox's MV3 background is a page, not a
worker, and a page has no importScripts: the worker's first two lines called it, the call threw,
and the file died before it reached the runtime.onMessage listener that answers the card page. On
Firefox every request the page makes to the worker went unanswered — tags, the extra legalities,
EDHREC, the finish column — and nothing said so, because a background that throws on load looks
exactly like a background with nothing to do. The Firefox manifest names those two files ahead of
the worker now, and the worker calls importScripts only where it exists, so one file works in
both browsers.

And the shim's callback never ran. The shim gives runtime.sendMessage, permissions.request
and permissions.contains their callback form back on Firefox, and reports a failure by writing
runtime.lastError — which Firefox makes getter-only. The write threw inside the promise handler,
so the callback was never reached: a caller that was waiting for an answer waited for ever, and one
whose request nothing answered resolved into nothing instead of saying so. That is what left every
tag panel on a card page reading "Loading tags…". The shim puts an own, writable lastError in
front of Firefox's getter now, so the callback runs and the error reaches it, as it does on Chrome.

---

Built by CI from this tag. The SHA-256 is printed in the workflow run that
produced this file, so the bytes published here can be tied to the commit and
the runner that made them.

Verify against the run: Actions → Release → v2.4.3

Full Changelog: v2.4.2...v2.4.3

v2.4.2

Built by CI from this tag. The SHA-256 is printed in the workflow run
that produced this file, so the bytes published here can be tied to
the commit and the runner that made them.

Verify against the run: Actions → Release → v2.4.2

Full Changelog: v2.4.1...v2.4.2

v2.4.1

Built by CI from this tag. The SHA-256 is printed in the workflow run
that produced this file, so the bytes published here can be tied to
the commit and the runner that made them.

Verify against the run: Actions → Release → v2.4.1

Full Changelog: v2.4.0...v2.4.1

v2.4.0

Built by CI from this tag. The SHA-256 is printed in the workflow run
that produced this file, so the bytes published here can be tied to
the commit and the runner that made them.

Verify against the run: Actions → Release → v2.4.0

Full Changelog: v2.3.2...v2.4.0

v2.3.2

Built by CI from this tag. The SHA-256 is printed in the workflow run
that produced this file, so the bytes published here can be tied to
the commit and the runner that made them.

Verify against the run: Actions → Release → v2.3.2

Full Changelog: v2.3.1...v2.3.2

v2.3.1

Built by CI from this tag. The SHA-256 is printed in the workflow run
that produced this file, so the bytes published here can be tied to
the commit and the runner that made them.

Verify against the run: Actions → Release → v2.3.1

Full Changelog: v2.3.0...v2.3.1

v2.3.0

Built by CI from this tag. The SHA-256 is printed in the workflow run
that produced this file, so the bytes published here can be tied to
the commit and the runner that made them.

Verify against the run: Actions → Release → v2.3.0

Full Changelog: v2.0.0...v2.3.0

v2.0.0

Built by CI from this tag. The SHA-256 is printed in the workflow run
that produced this file, so the bytes published here can be tied to
the commit and the runner that made them.

Verify against the run: Actions → Release → v2.0.0

Full Changelog: v1.0.1...v2.0.0

v1.0.1

Built by CI from this tag. The SHA-256 is printed in the workflow run
that produced this file, so the bytes published here can be tied to
the commit and the runner that made them.

Verify against the run: Actions → Release → v1.0.1

Full Changelog: v1.0.0...v1.0.1

v1.0.0

Built by CI from this tag. The SHA-256 is printed in the workflow run
that produced this file, so the bytes published here can be tied to
the commit and the runner that made them.

Verify against the run: Actions → Release → v1.0.0

Full Changelog: v0.51.0...v1.0.0