Document the (add-ons) soft-blocking capability for Desktop and Android [Desktop/Android V133]
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(Not tracked)
People
(Reporter: willdurand, Assigned: lsiebert)
References
Details
(Whiteboard: [addons-jira])
Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]
**Note: Learn more at https://mozilla-hub.atlassian.net/wiki/spaces/MSS/pages/21430745/Mozilla+Support+Content **
IMPORTANT NOTICE: FOR TIMELY PUBLICATION, CONTENT REQUESTS MUST BE SUBMITTED AT LEAST 14 DAYS BEFORE THE RELEASE DATE, ENABLING THE SUMO TEAM TO MAKE THEM LIVE WITHIN 48 HOURS POST-RELEASE. PLEASE ENSURE THAT ALL SUBMITTED INFORMATION, INCLUDING FEATURE DETAILS AND VISUAL ASSETS, IS FINAL. IN THE EVENT OF ANY UNFORESEEN CHANGES OR DELAYS NECESSITATING A PUSH TO A SUBSEQUENT RELEASE, PROMPTLY INFORM US TO PREVENT PUBLISHING AS PER THE ORIGINAL SCHEDULE.
YES
Content access restriction: Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]
Note: If yes, ensure ‘Advanced Fields’ are visible by selecting ‘Show Advanced Field’ at the top right, then scroll to ‘Security’ and check ‘Confidential Mozilla Employee Bug (non-security)’.
Attention: Any content not marked as confidential will be accessible to both NDAd and non-NDAd contributors with a Bugzilla account. Drafts for non-confidential content will also follow the same access policy, being open to comments for anyone with the link. Non-confidential Bugzillas can benefit from contributions by community contributors, while confidential Bugzillas will be handled exclusively by staff.
NO
Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)
Choose one below and delete others. [REQUIRED]
Firefox for Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)
Firefox for Android
Select the type of request.
Choose one or more below and delete others. [REQUIRED]
KB content update, there is already a page about the current blocklist at: https://support.mozilla.org/en-US/kb/add-ons-cause-issues-are-on-blocklist
That said, if you think it'll be easier/better to have a new page, then this would be a content creation request (with an in-product link)
Please summarize the request, emphasizing any user-facing changes. Include historical context or background information if it helps users understand the new features or changes. [REQUIRED]
Quoted from the PRD:
Soft-blocking is a new capability that add-on reviewers will be able to use to disable a version of an add-on for all existing Firefox users. Unlike hard-blocking, Firefox users will be able to make a conscious choice to re-enable the add-on version after it has been soft-blocked if they wish to.
##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]
**Note: Specify if the user-facing changes mentioned above are final, experimental, or in beta. This information is crucial for determining the appropriate support and documentation level needed. Please note that SUMO KB articles only support the production version for Firefox.
PRODUCTION
Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]
**Note: Please confirm if these features or changes are limited to specific geographic regions and if they will be implemented gradually. Knowing this helps us tailor our documentation and support resources appropriately.
NO, NOT REGION-SPECIFIC
Please indicate if this is an on- or off-train release [REQUIRED]
**Note: If applicable, add the product version number to the end of the Summary field using the format: Summary [Product V123]. If this is an off-train release, please use the format: Summary [Product off-train].
NO
What is the anticipated release date? [REQUIRED]
Note: Content is typically published at, or within, 48 hours of the release.
We target Fx133 currently, and November 26, 2024 is the release date for that version.
Does the content need to be published prior to the release date? If so, when? [REQUIRED]
Note: If you don’t let us know if this date changes, it will be published on this date
Not necessarily.
Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]
Note: A minimum of 10 days is required for translation requests.
NO
Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]
- Main bug for Firefox (with a list of dependencies): https://bugzilla.mozilla.org/show_bug.cgi?id=1917845
- PRD: https://docs.google.com/document/d/1RgY1N5MCNQAiKM3EK0bgvw7CZ8TolR81dF2QCNzTM2s/edit
- Jira theme ticket: https://mozilla-hub.atlassian.net/browse/AOP-310
Please include links to any design assets, visuals, figma files, etc. [REQUIRED]
Note: Ensure to submit only final visual assets relevant to the Production release, excluding Nightly or Beta images, and favor 'Light mode' UI screenshots over 'Dark mode'
Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]
We don't have that yet. We'll update the bug when we get there. See also: https://mozilla-hub.atlassian.net/browse/QA-2626
Does the content need approval before publishing? If yes, identify the one approver responsible for this task.
Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]
Approval might not be needed but we'd like to read a draft before publication. Based on prior experience, we'll be working closely with the technical writer so I think that'll be fine :)
| Reporter | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 1•2 years ago
|
||
| Assignee | ||
Comment 2•1 year ago
|
||
| Assignee | ||
Comment 3•1 year ago
|
||
The updated article is now live: https://support.mozilla.org/en-US/kb/add-ons-cause-issues-are-on-blocklist
Comment 4•1 year ago
|
||
Lucas, I submitted a revision to add a note {for not fx133} that soft-blocking (restricting) applies to Firefox 133 and above. There are also other pending revisions that I combined. Can you review? See https://support.mozilla.org/en-US/kb/add-ons-cause-issues-are-on-blocklist/history
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 5•1 year ago
|
||
(In reply to Alice Wyman from comment #4)
Hey Alice! Thanks for bringing this up. I caught up with Andreas from the add-ons team, and they requested we make his edit live for now. There’s also a Google Doc where we’re discussing preferred terminology and how to present these features, so any updates will need to go through that process. I’ve added you as an editor: https://docs.google.com/document/d/1T5mb3r3N-c_I_9X5WWrIukSB_UL1ZvPqN8Eyhd8VlYg/edit?tab=t.0 . Feel free to suggest any changes there (suggestion mode works best), and Andreas or Will can review them. Thanks so much for jumping in on this!
Comment 6•1 year ago
•
|
||
Lucas, I already resubmitted my revision to add a note {for not fx133} and other edits. See https://support.mozilla.org/en-US/kb/add-ons-cause-issues-are-on-blocklist/history P.S. I also edited the Google Doc to add my proposed changes in Suggestion Mode
| Assignee | ||
Comment 7•1 year ago
|
||
(In reply to Alice Wyman from comment #6)
Lucas, I already resubmitted my revision to add a note {for not fx133} and other edits. See https://support.mozilla.org/en-US/kb/add-ons-cause-issues-are-on-blocklist/history (I'll take a look at the Google doc)
Thanks, Alice! Will, can you take a quick look at this and let me know if we’re good to proceed? https://support.mozilla.org/en-US/kb/add-ons-cause-issues-are-on-blocklist/review/289944 It includes a few style and formatting fixes, along with a note for non-V133 users stating that restricting is only available starting with V133.
Comment 8•1 year ago
|
||
Will, If you're not a SUMO KB reviewer and can't access the review link provided above by Lucas, see https://support.mozilla.org/en-US/kb/add-ons-cause-issues-are-on-blocklist/revision/289944 to view my revision source and content. To compare my revisions with the current version just approved by Lucas, please see https://support.mozilla.org/en-US/kb/add-ons-cause-issues-are-on-blocklist/compare?locale=en-US&to=289944&from=289943
| Reporter | ||
Comment 9•1 year ago
|
||
Thanks. Revision 289944 looks good enough, though maybe don't change the case for "Add-on Policies" and please do not add the for not fx133 note for now, this will require some more work.
Comment 10•1 year ago
|
||
(In reply to William Durand [:willdurand] from comment #9)
Thanks. Revision 289944 looks good enough, though maybe don't change the case for "Add-on Policies" and please do not add the
for not fx133note for now, this will require some more work.
I made those edits to my pending revision. See https://support.mozilla.org/en-US/kb/add-ons-cause-issues-are-on-blocklist/revision/289975 (Lucas, can you review?)
| Assignee | ||
Comment 11•1 year ago
|
||
(In reply to Alice Wyman from comment #10)
(In reply to William Durand [:willdurand] from comment #9)
Thanks. Revision 289944 looks good enough, though maybe don't change the case for "Add-on Policies" and please do not add the
for not fx133note for now, this will require some more work.I made those edits to my pending revision. See https://support.mozilla.org/en-US/kb/add-ons-cause-issues-are-on-blocklist/revision/289975 (Lucas, can you review?)
Thanks, Alice! Just made your revision live.
Description
•