librewolf/website
14
55
Fork
You've already forked website
39

Mention system add-on updates under outgoing connections #145

Merged
alyx161 merged 2 commits from sysaddons into master 2026年06月03日 01:03:53 +02:00

In case librewolf/settings#135 gets merged.

In case https://codeberg.org/librewolf/settings/pulls/135 gets merged.

Maybe worth instead of making this about "built-in features" which, to be fair, could be everything or nothing to anyone who reads this, instead make a section about addon updates in general?

Addon Updates: To check for and install updates of your installed addons [...]

Something like this

Maybe worth instead of making this about "built-in features" which, to be fair, could be everything or nothing to anyone who reads this, instead make a section about addon updates in general? > Addon Updates: To check for and install updates of your installed addons [...] Something like this
Author
Owner
Copy link

Or something like this?

Add-on updates: to receive updates for your add-ons and some built-in features, see about:debugging#/runtime/this-firefox.

Allows users to see the full list of what is meant.

Or something like this? >Add-on updates: to receive updates for your add-ons and some [built-in features](https://firefox-source-docs.mozilla.org/toolkit/mozapps/extensions/addon-manager/SystemAddons.html), see `about:debugging#/runtime/this-firefox`. Allows users to see the full list of what is meant.

I honestly would scrap the built-in features part completely 🤔
Its.. very ambiguous? And the link to https://firefox-source-docs.mozilla.org/toolkit/mozapps/extensions/addon-manager/SystemAddons.html is.. well.. not really helpful?

Like, when I made this list the main focus was on providing a reason to why a connection is important in a very compact and especially simple to understand way (eg. also for non tech focused people).

Getting into built-in features probably causes more questions than it gives answers in this context, and since they are basically add-ons it probably makes sense to group them into add-ons.

So my suggestion would be:

Add-on Updates: To get updates for (internal) add-ons and installed extensions, ensuring they receive the latest security updates and bug fixes

I honestly would scrap the built-in features part completely 🤔 Its.. very ambiguous? And the link to https://firefox-source-docs.mozilla.org/toolkit/mozapps/extensions/addon-manager/SystemAddons.html is.. well.. not really helpful? Like, when I made this list the main focus was on providing a reason to why a connection is important in a very compact and especially simple to understand way (eg. also for non tech focused people). Getting into built-in features probably causes more questions than it gives answers in this context, and since they are basically add-ons it probably makes sense to group them into add-ons. So my suggestion would be: Add-on Updates: To get updates for (internal) add-ons and installed extensions, ensuring they receive the latest security updates and bug fixes
Simplify and include all add-ons
All checks were successful
/ deploy (push) Successful in 1m17s
0c4c19dc8e
Author
Owner
Copy link

@alyx161 wrote in #145 (comment):

I honestly would scrap the built-in features part completely 🤔 Its.. very ambiguous? And the link to https://firefox-source-docs.mozilla.org/toolkit/mozapps/extensions/addon-manager/SystemAddons.html is.. well.. not really helpful?

Not sure how ambiguous things can be if they're literally listed under about:debugging#/runtime/this-firefox and the link further explains that these extensions are otherwise hidden from the about:addons UI (already in the 2nd sentence), but I agree that mentioning regular add-ons should be done, so I've included the suggested changes.

@alyx161 wrote in https://codeberg.org/librewolf/website/pulls/145#issuecomment-16412129: > I honestly would scrap the built-in features part completely :thinking: Its.. very ambiguous? And the link to https://firefox-source-docs.mozilla.org/toolkit/mozapps/extensions/addon-manager/SystemAddons.html is.. well.. not really helpful? Not sure how ambiguous things can be if they're literally listed under `about:debugging#/runtime/this-firefox` and the link further explains that these extensions are otherwise hidden from the `about:addons` UI (already in the 2nd sentence), but I agree that mentioning regular add-ons should be done, so I've included the suggested changes.
alyx161 deleted branch sysaddons 2026年06月03日 01:03:55 +02:00
Sign in to join this conversation.
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
librewolf/website!145
Reference in a new issue
librewolf/website
No description provided.
Delete branch "sysaddons"

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?