Closed Bug 1910137 Opened 1 year ago Closed 3 months ago

KB article: How to set Firefox as your mail-to default [Desktop V129]

Categories

(support.mozilla.org :: Knowledge Base Content, task, P1)

Product:
support.mozilla.org
Component:
Knowledge Base Content
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: vtay, Assigned: dgalindo)

Details

Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED] YES

**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.

Content access restriction: Is the content restricted to staff or under embargo (yes or no)? [REQUIRED] NO

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.

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)

Select the type of request.

Choose one or more below and delete others. [REQUIRED]
KB content update/ new content

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]

We will provide prompts (for users that have set Firefox as their default browser) for:

  • Firefox to be set as the Windows OS default handler for mail sites,
  • The mail site to be set as the default handler for mail links,

##Are the user-facing changes mentioned above for the production release, or is the feature/change experimental/ beta? (Production, Experimental or Beta) [REQUIRED]
Experiment in Fx129 - 67% of the population will see this
Experiment brief
https://docs.google.com/document/d/1Gqc7KrUm-wh46ZSWaq7FPDwtc44pCtlDDHLmqVAvEIw/edit#heading=h.il190ggzaaw1

**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.

Are the new features or changes region-specific? Are they going to be released in a gradual rollout? [REQUIRED]

No specific regions or locale.
Launching as an experiment first, and then rolling out 100%

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].

On train release;

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.
target date is Aug 13 to launch experiment

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

N/A

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

The usual locales

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://mozilla-hub.atlassian.net/browse/QA-2405
Experiment brief
https://docs.google.com/document/d/1Gqc7KrUm-wh46ZSWaq7FPDwtc44pCtlDDHLmqVAvEIw/edit#heading=h.il190ggzaaw1

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]

visit about:config and search for dualPrompt, and activate browser.mailto.dualPromptand browser.mailto.dualPrompt.onLocationChange

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]

Assignee: nobody → lsiebert
Summary: KB article: How to set Firefox as your mail-to default → KB article: How to set Firefox as your mail-to default [Desktop V129]
Priority: -- → P1

Hi Lucas, what's the status on this?

Flags: needinfo?(lsiebert)
Assignee: lsiebert → dgalindo
Status: NEW → ASSIGNED
Flags: needinfo?(lsiebert)

(In reply to Ryan VanderMeulen [:RyanVM] from comment #3)

Hi Lucas, what's the status on this?

Hi Ryan, I'll be helping Lucas with this task. I'm currently reviewing all the info. Is there anything you want to add to put me in context?

(In reply to Alice Wyman from comment #2)

Related KB article: https://support.mozilla.org/en-US/kb/change-program-used-open-email-links

Thank you Alice

Hi Max, once you check the g-doc let me know what you think.

Flags: needinfo?(mpohle)

We do not currently have a manual way to add custom webmailers through the Options dialog, and it would also require users to have technical knowledge of the target URL, which only the web site hosting the webmail application knows. While many users find it challenging to configure IMAP and SMTP servers and look up the correct server names, we have have an API in the browser that websites can use to prompt users to configure the site as a mailto site and automatically set Firefox as the default handler for mailto, called registerProtocolHandler. This allows users to configure a specific webmailer as their default within Firefox and Firefox as their default application to handle mailto.

This is not to say that it is completely unnecessary, but I think that we have several audiences for the article:

  1. Mail service providers who may want to implement registerProtocolHandler for mailto.
  2. Users who want to understand what they are doing when interacting with the mailto prompt that appears on websites.
  3. Users who want to be in control and understand more about what is going on and/or troubleshoot problems they are experiencing.

The document linked in comment 5 is interesting for the second group and the article Change the program used to open email links is for the third group since we introduced the so-called dualPrompt for mailto, which configures the webmailer in Firefox and the OS default at the same time, hence the name.

What I think is missing is a broader overview that addresses all three audiences to create common expectations of what a user experience should ideally look like:

  1. The website calls registerProtocolHandler.
  2. Users get to see the mailto prompt.
  3. They click on a button to accept the new default.

and then explain how the third step changes the settings as described in the document and article.

Flags: needinfo?(mpohle)

Venetia -- is approval needed from anyone else in order to publish? If not, we will proceed. https://docs.google.com/document/d/1zcJ79wk7XH48AcN1prZ38MM0TEtZnbIYRe5uLsLV4QQ/edit?tab=t.0

Flags: needinfo?(vtay)

Looks good.
Ok to publish

Flags: needinfo?(vtay)
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED

(In reply to Vtay from comment #0)

Experiment in Fx129 - 67% of the population will see this
<snip>

Launching as an experiment first, and then rolling out 100%

I added "Starting in Firefox version 129" and other edits. See https://support.mozilla.org/en-US/kb/set-firefox-mail-default-windows/history Dayani, can you review? Related discussion: https://support.mozilla.org/en-US/kb/set-firefox-mail-default-windows/discuss/13916 MAILTO section

P.S. the description says,

We will provide prompts (for users that have set Firefox as their default browser) for:
Firefox to be set as the Windows OS default handler for mail sites,
The mail site to be set as the default handler for mail links

I wasn't sure if only the prompts started in version 129, when Firefox is the default browser, or if the option to set Firefox as the default mail handler started with version 129. Can you check? The article doesn't mention prompts.

Status: RESOLVED → REOPENED
Flags: needinfo?(dgalindo)
Resolution: FIXED → ---

I added specific instructions for Windows 10 and thus {for} tags.

(In reply to Mozinet from comment #13)

I added specific instructions for Windows 10 and thus {for} tags.

I approved your revision but noticed that most of the Set Firefox as your mail-to default on Windows article only displays when viewed in Windows 10 or 11. I made a few more edits that are pending review. See https://support.mozilla.org/en-US/kb/set-firefox-mail-default-windows/history

Dayani approved my last revision (thanks!) so I'll close this bug.

Status: REOPENED → RESOLVED
Closed: 6 months ago → 3 months ago
Flags: needinfo?(dgalindo)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.