postulo-firefox: the browser extension for Firefox and its forks #18
Labels
No labels
accessibility
authentication
breaking change
bug
documentation
enhancement
interface
internationalisation
observability
security
tier
1
tier
2
tier
3
tier/4
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
Reference
Postulo/postulo#18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Observation
Shape
Everything in #17 applies — same code, same options page, same capture flow, same privacy statement — and Firefox adds what follows. Firefox has supported Manifest V3 since version 109, with differences that are exactly the kind of thing that costs a day if nobody wrote them down:
background.scripts). Current Chromium tolerates a manifest that lists both keys, so one manifest can serve both if checked at build time; otherwiseweb-extbuilds one per target from a shared source.browser_specific_settings.gecko.idis required for a Manifest V3 extension to be signed and to keep its storage across updates.browser.*with promises. Chromium'schrome.*returns promises in Manifest V3 as well, soglobalThis.browser ?? chromecovers both without a polyfill.host_permissionsare not granted at install; the person grants them in the extension's permission panel or the extension requests them at run time. The instance-origin request at configuration time from #17 is therefore not optional here, and the extension must behave when it is refused — say what it needs and why, and do nothing else.Classification
Enhancement. A separate build (or repository); changes nothing in Postulo. Not breaking.
Depends on
#17 for the shared code. #12 for the read features, as there.
Open questions