av9ash/GitBugs huggingface dataset:
Bug: Intermittent browser/base/content/test/static/browser_all_files_referenced.js | there should be no unreferenced files - Got 1, expected 0
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-05-12 18:13:31+00:00
Resolved: 2020-06-09 17:03:00+00:00

**Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=301960951&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/E4om5ODZRrmmzApE5SPHEg/runs/0/artifacts/public/logs/live_backing.log

---

[task 2020-05-12T17:53:09.574Z] 17:53:09     INFO - TEST-START | browser/base/content/test/static/browser_all_files_referenced.js
[task 2020-05-12T17:53:16.454Z] 17:53:16     INFO - indirectly whitelisted file: chrome://fxr/content/prefs.js used from chrome://fxr/content/prefs.html
[task 2020-05-12T17:53:16.455Z] 17:53:16     INFO - Buffered messages finished
[task 2020-05-12T17:53:16.456Z] 17:53:16     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/static/browser_all_files_referenced.js | there should be no unreferenced files - Got 1, expected 0
[task 2020-05-12T17:53:16.456Z] 17:53:16     INFO - Stack trace:
[task 2020-05-12T17:53:16.456Z] 17:53:16     INFO - chrome://mochikit/content/browser-test.js:test_is:1327
[task 2020-05-12T17:53:16.457Z] 17:53:16     INFO - chrome://mochitests/content/browser/browser/base/content/test/static/browser_all_files_referenced.js:checkAllTheFiles:953
[task 2020-05-12T17:53:16.457Z] 17:53:16     INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1064
[task 2020-05-12T17:53:16.457Z] 17:53:16     INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1104
[task 2020-05-12T17:53:16.457Z] 17:53:16     INFO - chrome://mochikit/content/browser-test.js:nextTest/<:927
[task 2020-05-12T17:53:16.457Z] 17:53:16     INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:918
[task 2020-05-12T17:53:16.458Z] 17:53:16     INFO - Not taking screenshot here: see the one that was previously logged
Bug: Intermittent browser/base/content/test/tabs/browser_new_tab_in_privilegedabout_process_pref.js | leaked 2 window(s) until shutdown [url = about:newtab]
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-05-12 18:17:47+00:00
Resolved: 2023-06-19 12:02:06+00:00

**Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=301941347&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Xa4Lpfh9RxKHa1EQLPFKjA/runs/0/artifacts/public/logs/live_backing.log

---

[task 2020-05-12T17:06:56.853Z] 17:06:56     INFO - TEST-START | browser/base/content/test/tabs/browser_visibleTabs_contextMenu.js
[task 2020-05-12T17:07:07.837Z] 17:07:07     INFO - GECKO(5216) | [Parent 1572, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005 (NS_ERROR_FAILURE): file /builds/worker/checkouts/gecko/caps/ContentPrincipal.cpp, line 423
[task 2020-05-12T17:07:07.877Z] 17:07:07     INFO - GECKO(5216) | [Parent 1572, Main Thread] WARNING: Extra shutdown CC: 'i < NORMAL_SHUTDOWN_COLLECTIONS', file /builds/worker/checkouts/gecko/xpcom/base/nsCycleCollector.cpp, line 3359
[task 2020-05-12T17:07:08.224Z] 17:07:08     INFO - TEST-INFO | Main app process: exit 0
[task 2020-05-12T17:07:08.224Z] 17:07:08     INFO - TEST-INFO | Confirming we saw 633 DOCSHELL created and 633 destroyed log strings.
[task 2020-05-12T17:07:08.225Z] 17:07:08     INFO - TEST-INFO | Confirming we saw 1878 DOMWINDOW created and 1878 destroyed log strings.
[task 2020-05-12T17:07:08.225Z] 17:07:08    ERROR - TEST-UNEXPECTED-FAIL | browser/base/content/test/tabs/browser_new_tab_in_privilegedabout_process_pref.js | leaked 2 window(s) until shutdown [url = about:newtab]
[task 2020-05-12T17:07:08.226Z] 17:07:08     INFO - TEST-INFO | browser/base/content/test/tabs/browser_new_tab_in_privilegedabout_process_pref.js | windows(s) leaked: [pid = 5396] [serial = 91], [pid = 5396] [serial = 89]
[task 2020-05-12T17:07:08.226Z] 17:07:08     INFO - TEST-INFO | browser/base/content/test/tabs/browser_new_tab_in_privilegedabout_process_pref.js | This test created 1 hidden window(s)
[task 2020-05-12T17:07:08.226Z] 17:07:08     INFO - TEST-INFO | browser/base/content/test/tabs/browser_new_tab_in_privilegedabout_process_pref.js | This test created 1 hidden docshell(s)
Bug: Copying an autosuggested URL does not include protocol
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2020-05-12 20:31:37+00:00
Resolved: 2023-09-28 14:05:54+00:00

This has been annoying me for a while and I finally looked for a reliable STR to report.

Steps to reproduce:

1. Open https://musicbrainz.org
2. Open tab
3. Close original tab
4. type `music` and allow Firefox to autosuggest to `musicbrainz.org/`
5. Select all
6. Paste anywhere

What happens:

Protocol information (`https://`) is not included, making the pasted string much less useful to people receiving it in chat applications (since the URL is not clickable).

Expected result:

The copied string should be `https://musicbrainz.org/` as it was previous to regression.

30:17.50 INFO: No more integration revisions, bisection finished.
30:17.50 INFO: Last good revision: 45856f355629679c4f8708fe4d1d97027aa58e8d
30:17.50 INFO: First bad revision: 202e520935200bc0ed6da749bc11673244f3089d
30:17.50 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=45856f355629679c4f8708fe4d1d97027aa58e8d&tochange=202e520935200bc0ed6da749bc11673244f3089d
Bug: startup error on aboutNewTabService.newTabURL in config
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-05-12 21:01:25+00:00
Resolved: 2020-05-13 18:08:16+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

All through version 75 I had a custom new tab page set via config file and it worked great. 

/usr/lib/firefox/browser/defaults/preferences/enable-autoconfig.js 
   // enable config file  
   pref("general.config.sandbox_enabled", false);  
   pref("general.config.filename", "autoconfig.cfg");  
   pref("general.config.obscure_value", 0);  

/usr/lib/firefox/autoconfig.cfg

  // set new tab page  
   var {classes:Cc,interfaces:Ci,utils:Cu} = Components;  
   aboutNewTabService = Cc["@mozilla.org/browser/aboutnewtab-service;1"].getService(Ci.nsIAboutNewTabService);  
   aboutNewTabService.newTabURL = "file:///<path_to_file>";  


Actual results:

After upgrading to 76, on startup, Firefox gives a popup saying it cannon read the config file and to contact the system admin. 

In the console I get:

    NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN: Cannot modify properties of a WrappedNative  

Happens on both Windows 10 and Manjaro Cinnamon.


Expected results:

It should load my defined new tab page like it used it.
Bug: Logins page cannot reveal or edit passwords
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-05-12 21:04:37+00:00
Resolved: 2020-07-02 00:36:42+00:00

Pressing any of the "Reveal password", "Copy password" or "Edit" buttons does nothing.

The browser console reports some errors whenever one of the buttons is clicked:

```
[fluent] Missing translations in en-US: about-logins-reveal-password-os-auth-dialog-message-linux. Localization.jsm:202:13

AboutLoginsChild: error recording telemetry event: message.data.telemetryEvent is undefined AboutLoginsChild.jsm:217
    receiveMessage resource:///actors/AboutLoginsChild.jsm:217
    (Async: JSActor query)
    receiveMessage resource:///actors/AboutLoginsParent.jsm:413
    AsyncFunctionNext self-hosted:693
    (Async: async)
    promptForMasterPassword resource:///actors/AboutLoginsChild.jsm:71
    masterPasswordAuth chrome://browser/content/aboutlogins/components/login-item.js:353
    handleEvent chrome://browser/content/aboutlogins/components/login-item.js:352
    (Async: EventListener.handleEvent)
    connectedCallback chrome://browser/content/aboutlogins/components/login-item.js:112
    <anonymous> chrome://browser/content/aboutlogins/components/login-item.js:899
    InnerModuleEvaluation self-hosted:1572
    evaluation self-hosted:1543

TypeError: can't access property "value", messageText is null AboutLoginsParent.jsm:370:1

AboutLoginsChild: error recording telemetry event: message.data.telemetryEvent is undefined AboutLoginsChild.jsm:217
    receiveMessage resource:///actors/AboutLoginsChild.jsm:217
    (Async: JSActor query)
    receiveMessage resource:///actors/AboutLoginsParent.jsm:413
    AsyncFunctionNext self-hosted:693
    (Async: async)
    promptForMasterPassword resource:///actors/AboutLoginsChild.jsm:71
    masterPasswordAuth chrome://browser/content/aboutlogins/components/login-item.js:353
    handleEvent chrome://browser/content/aboutlogins/components/login-item.js:352
    (Async: EventListener.handleEvent)
    connectedCallback chrome://browser/content/aboutlogins/components/login-item.js:112
    <anonymous> chrome://browser/content/aboutlogins/components/login-item.js:899
    InnerModuleEvaluation self-hosted:1572
    evaluation self-hosted:1543
```

Disabling `signon.management.page.os-auth.enabled` fixes it.

Firefox Nightly,
Arch Linux.
Bug: about:config setting are getting overwritten every time there is a new update.
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-05-13 03:15:09+00:00
Resolved: 2020-05-13 06:38:42+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36

Steps to reproduce:

Updated firefox


Actual results:

about:config got overwritten.


Expected results:

about:config should have not been overwritten.

I don't want to disable that annoying effect on the search bar every time there is a new update. That effect is just horrible and everyone hates it.
Bug: Perma build failure line anyhow 1.0.28] error[E0554]: `#![feature]` may not be used on the stable release channel
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2020-05-13 08:59:25+00:00
Resolved: 2020-05-18 06:27:24+00:00

Build logs contain this since bug 1628068 landed:

[task 2020-05-13T08:19:34.793Z] 08:19:34    ERROR -  [anyhow 1.0.28] error[E0554]: `#![feature]` may not be used on the stable release channel
[task 2020-05-13T08:19:34.793Z] 08:19:34     INFO -  [anyhow 1.0.28]  --> /builds/worker/workspace/obj-build/release/build/anyhow-2fb262225263c2f8/out/probe.rs:2:5
[task 2020-05-13T08:19:34.793Z] 08:19:34     INFO -  [anyhow 1.0.28]   |
[task 2020-05-13T08:19:34.793Z] 08:19:34     INFO -  [anyhow 1.0.28] 2 |     #![feature(backtrace)]
[task 2020-05-13T08:19:34.794Z] 08:19:34     INFO -  [anyhow 1.0.28]   |     ^^^^^^^^^^^^^^^^^^^^^^
[task 2020-05-13T08:19:34.794Z] 08:19:34     INFO -  [anyhow 1.0.28]
[task 2020-05-13T08:19:34.794Z] 08:19:34    ERROR -  [anyhow 1.0.28] error: aborting due to previous error
[task 2020-05-13T08:19:34.794Z] 08:19:34     INFO -  [anyhow 1.0.28]
[task 2020-05-13T08:19:34.795Z] 08:19:34     INFO -  [anyhow 1.0.28] For more information about this error, try `rustc --explain E0554`.

Log: https://treeherder.mozilla.org/logviewer.html#?job_id=302067922&repo=autoland

Recent push:
https://treeherder.mozilla.org/#/jobs?repo=autoland&group_state=expanded&selectedTaskRun=Zk1B_pXCSeO6HGX7vyEdLw-0&resultStatus=superseded%2Cusercancel%2Cretry%2Csuccess%2Ctestfailed%2Cbusted%2Cexception&revision=f0c71e1de58cf4cf883a48c3e847e774a9719694&searchStr=build
Bug: No label on screenshot frame in responsive design mode
Status: RESOLVED
Priority: P3
Resolution: WORKSFORME
Created: 2020-05-13 09:29:33+00:00
Resolved: 2023-01-19 22:55:33+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

- I go to a website
- I use the responsive design mode
- I want to use the screenshot feature


Actual results:

No label in RWD contrary to desktop version.

cf: attachment.
Bug: Flexible space is wrongly positioned in Customize menu after dragging the Search bar on the left side
Status: NEW
Priority: P3
Created: 2020-05-13 11:42:22+00:00
Resolved: 2020-05-27 14:52:56+00:00

*Affected versions*
* 78.0a1 (20200512212513)
* 77.0b5 (20200512163137)
* 76.0.1 (20200507114007)


*Affected platforms*
* Windows 10x64
* Ubuntu 16.04
* macOS 10.12


*Steps to reproduce*
1. Open Firefox with a new profile and go to the Customize page.
2. Drag the Search bar on the left side of the flexible space from the URL bar.

*Expected result*
* The drag space is shrunk as expected.


*Actual result*
* Flexible space is moved over the address bar.

*Regression range*
* Will search for one ASAP.

*Notes*
* Attached a screen recording.
Bug: The card is not dismissed after it's archived to pocket and the browser is restarted
Status: NEW
Priority: P5
Created: 2020-05-13 13:27:39+00:00
Resolved: 2020-08-04 17:53:36+00:00

**Affected versions**
* Firefox 77.0b5-build1
* Firefox 78.0a1

**Affected platforms**
* Windows 7 x86
* Windows 10 x64
*macOS 10.15
*Ubuntu 18.04 x64

**Steps to reproduce**
1. Click the "..." button for a "Saved to Pocket" card.
2. click the "Archive in Pocket" option.
3. Restart the browser. 

**Expected result**
* The card is not displayed anymore. 

**Actual result**
* The card is still displayed. 

**Regression range**
* If it's a regression I will find it as soon as possible. 

**Additional notes**
* The card has the same url as the one from steps 1 and 2.
Bug: The removed search engine resurrects after browser restart
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-05-13 14:10:51+00:00
Resolved: 2020-07-02 00:36:54+00:00

Reproducible: always

Steps To Reproduce:
1. Install a search engine
  https://addons.mozilla.org/en-US/firefox/addon/msn-homepage-bing-searchengine/?src=search
2. Open about:preferences#search
3. Remove the search engine that was added in step 1
4. Restart Browser
5. about:preferences#search
   --- observe, the search engine

Actual Results:
The removed search engine resurrects after browser restart

Expected Results:
should not resurrect
Bug: The "What's New" doorhanger is wrongly dismissed when clicking the left or right borders of the panel
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2020-05-13 14:36:18+00:00
Resolved: 2020-06-08 15:16:36+00:00

**[Affected versions]:**
- Firefox Nightly 78.0a1
- Firefox Beta 77.0b5
- Firefox Release 76.0.1

**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Ubuntu 18.04 x64

**[Steps to reproduce]:**
1. Open the browser.
2. Click the hamburger menu button and click the "What's New" button.
3. Click on the left or right side border of the doorhanger and observe the behavior.

**[Expected result]:**
- The "What's New" doorhanger remains displayed and nothing happens.

**[Actual result]:**
- The "What's New" doorhanger is dismissed.

**[Notes]:**
- Attached a screen recording of the issue:
Bug: File:error-sync-1588863580727.txt  42 KB  5/7/2020  7:59:40 AM
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-05-13 14:52:20+00:00
Resolved: 2020-06-18 05:09:54+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Firefox for Android

Steps to reproduce:

sync


Actual results:

not synced between devices
Index of file:///C:/Users/ORNY.DESKTOP-AJN2BLN/AppData/Roaming/Mozilla/Firefox/Profiles/2lzyvkxh.default-1477943024411-1547594216851/weave/logs/

Up to higher level directory
Name 	Size 	Last Modified
File:error-sync-1588863580727.txt
	42 KB 	5/7/2020 	7:59:40 AM
File:error-sync-1588863582376.txt
	10 KB 	5/7/2020 	7:59:42 AM
File:error-sync-1588863624570.txt
	21 KB 	5/7/2020 	8:00:24 AM
File:error-sync-1588863888512.txt
	11 KB 	5/7/2020 	8:04:48 AM


Expected results:

bookmarks should have updated
Bug: Firefox disconnects everyone in Jitsi-Meet conference room
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-05-13 17:28:07+00:00
Resolved: 2020-05-16 19:57:52+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

1. Enter (create) a new jitsi-meet conference room with an Electron browser.

2. Enter the jitsi-meet conference room with Firefox.


Actual results:

Both participants lost connection to the conference room.


Expected results:

Both participants should have remained in the conference room.
Bug: After updating to Firefox 76.0.1 (64-bit) today, the Outlook app within Office 365 started crashing
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-05-13 17:47:04+00:00
Resolved: 2020-10-14 06:58:16+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

I logged into office.com in Firefox on my Mac desktop with my saved password.  Suite of apps opens, I selected Outlook.  It opens, but when I attempt to do anything it crashes and I get a message that it cannot log me in.


Actual results:

: AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: 'e48d4214-364e-4731-b2b6-47dabf529218'.

Request Id: 464b0146-8ff7-4e8f-9935-dc98145c2d00
Correlation Id: 8fe689d9-6e34-441b-bc42-87d463d3c3b7
Timestamp: 2020-05-13T17:41:28Z
Message: AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: 'e48d4214-364e-4731-b2b6-47dabf529218'.


Expected results:

I should have been able to open an email, or write a new message.  Won't let me do anything within Outlook.  I was able to open it and work with it fine within Safari, by the way.
Bug: enableAppmenuButton test fails
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2020-05-13 17:50:44+00:00
Resolved: 2020-05-14 02:42:50+00:00

Pretty sure there is a race condition in the tests for enableAppmenuButton.

It does these calls in "should registerCallback on enableAppmenuButton() if there are messages"

```
      await instance.init(waitForInitializedStub, {
        getMessages: sandbox.stub().resolves([{}, {}]),
      });
      // init calls `enableAppmenuButton`
      everyWindowStub.registerCallback.resetHistory();

      await instance.enableAppmenuButton();

      assert.calledOnce(everyWindowStub.registerCallback);
```

In init, it's calling enableAppmenuButton, then it resets it, then calls it directly. Expecting it to only be called once.

However, the enableAppmenuButton call in init isn't await, and probably should be.

What I think that means is the call to enableAppmenuButton in init can finish after resetHistory, causing the test to fail with two calls.

I think.

If I add await to the call in init, the test fails go away.

I can make a patch.
Bug: Microphone usage overlay does not fully disappear after use
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-05-13 19:50:49+00:00
Resolved: 2020-06-03 09:25:16+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0

Steps to reproduce:

I used the microphone in an online meeting, and then closed the tab after it was finished. This was on the Linux version of Firefox, 77.0b3.


Actual results:

The overlay at the top of the screen that shows that the microphone is in use did not disappear. The microphone icon did disappear, but the Firefox logo next to it did not. 


Expected results:

The entire overlay should have disappeared.
Bug: AutoComplete for URLs isn't working. (urlbar)
Status: RESOLVED
Priority: P2
Resolution: INVALID
Created: 2020-05-13 20:43:53+00:00
Resolved: 2023-08-09 14:34:40+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15

Steps to reproduce:

I can reproduce by following these steps:

1. Type visir.is in the URL bar and select the top link in the suggested list (highlighted in attachment)
2. Close the tab, open a new one and type in "v".


Actual results:

Visir.is as previously visited does not appear or is auto-completed in the URL bar unless typing in the full address (visir.is). Then I'll have the same results as the very first time I typed "visir.is".


Expected results:

As soon as I typed in "v" I expected "visir.is" to be autocompleted as it's the only website starting with "v" that I have visited. 

However, if I type in "visir.is" again and select the 3rd link in the suggested list (see attachment), close the tab, open a new one and type in "v" then "visir.is" is auto-completed.

In the attached file, there are 3 links. First is visir.is (http!), second is a google search with the param "visir.is" and the 3rd link is visir.is (https).

By entering "visir.is" with the 3rd link (the https) then autocomplete works. The default link is http, it redirects to https but doesn't auto-complete. I don't know why http is the default suggested link. 

This happens with various domains, another example is "mbl.is".
Bug: Email Link broken in 76.0.1
Status: UNCONFIRMED
Priority: P3
Created: 2020-05-13 23:06:14+00:00
Resolved: 2020-06-15 15:50:40+00:00

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

I updated my Dell Latitude E6510, Windows 7 Pro 32 bit running FireFox 75.0 to FireFox 76.0.1.

I have Windows Live Mail as my mail client and under Options/Applications I have "Windows Live Mail"  (wlmail.exe) set for "mailto".  

I've got 2 hard drives configured identically (image copies of one another), one still has FF 75.0 installed and the other has FF 76.0.1 so I was able to open FF on both systems and compare every "Option" setting and make them identical.



Actual results:

Under FF 76.0.1 clicking on "Email Link" starts Live Mail, but does NOT create a new email message and doesn't copy the desired link (it simply starts Live Mail).  

When I want to send someone a link that I'm looking at, once FF has started Live Mail I need to manually create a new message then manually copy/paste the link from FF into the message before I can send it.  



Expected results:

Under 75.0, clicking on "Email Link" starts Live Mail, goes into create new email, and generates a new email message that contains the link I want to send.

The behavior of Email Link in FF 76.0.1 is an annoying backward step that feels like a bug.
Bug: Overhaul sync ping telemetry error reporting
Status: RESOLVED
Priority: P3
Resolution: WONTFIX
Created: 2020-05-13 23:30:06+00:00
Resolved: 2020-05-28 22:56:32+00:00

Error reporting in sync pings is, frankly, useless:

* Many "reasons" include strings which are variable per user - eg, they include timestamps or guids. Thus, dashboards see thousands of low-rate errors instead of a single high-rate error. See, eg, normalizeFailure in https://gist.github.com/mhammond/749d59be7357eeedce31a1df5ac370b1

* They are implementation specific - eg, a DNS failure on desktop is reported as `nserror` with an obscure hex string. A dns failure on Android is reported differently (but I've no idea how off the top of my head. It does not make sense to report `nserror` - it makes sense to report some nserror codes as 'network error', some as others, etc

* etc.

The error reporting should be designed to be analyzed.

(This is going to be trickier than it sounds. We will still need some way of handling truly unknown or unexpected errors)