NEW ARTICLE: Thunderbird version of Firefox's: Why are some add-ons not allowed on sites restricted by Mozilla?

Open
#64 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start with the linked Firefox article on quarantined domains and use the issue’s screenshot and Thunderbird 128 context to plan the Thunderbird version. Create the corresponding Thunderbird Knowledge Base article so the Learn more URL at /thunderbird/128.0.1/Linux/en-US/quarantined-domains resolves to accurate Thunderbird guidance.

Written by the indexing model from the issue text.

Description

  • Firefox article: Why are some add-ons not allowed on sites restricted by Mozilla?
  • Assuming we're keeping the Learn more link in the add-ons manager in Thunderbird 128 (install an extension and then go to the add-ons manager and select that extension and you will see the Learn more link in the Details tab under on Run on sites with restrictions)
    Screenshot:
    image

More context from Martin's email:

So there's this new thing for extensions that m-c introduced which is called "sites with restrictions". As I understand it it's a blocklist that MoCo maintains of sites extensions can't just run on to fight abuse. I don't know if this system even works for us (or if we intend to use it), but fact is that we now have a "Learn more" link in the add-ons manager (in 128!) that wants to go to https://support.thunderbird.net/thunderbird/128.0.1/Linux/en-US/quarantined-domains (the link is constructed with your build's variables so YMMV). Sadly this page doesn't exist for us. The Firefox counterpart is https://support.mozilla.org/en-US/kb/quarantined-domains?as=u&utm_source=inproduct

Dominant language
No language data
Stars
7
Forks
1
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from thunderbird/knowledgebase-issues

All issues in thunderbird/knowledgebase-issues

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.