av9ash/GitBugs huggingface dataset:
Bug: Intermittent TV browser/components/urlbar/tests/browser/browser_urlbar_telemetry_dynamic.js | Test timed out -
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2022-06-17 11:20:00+00:00
Resolved: 2022-06-23 01:12:31+00:00

**Filed by:** ctuns [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=381665261&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ZRHAK1cOSdqtNJraph1vbA/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ZRHAK1cOSdqtNJraph1vbA/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2022-06-17T10:31:52.429Z] 10:31:52     INFO - TEST-START | browser/components/urlbar/tests/browser/browser_urlbar_telemetry_dynamic.js
[task 2022-06-17T10:32:37.600Z] 10:32:37     INFO - TEST-INFO | started process screentopng
[task 2022-06-17T10:32:37.859Z] 10:32:37     INFO - TEST-INFO | screentopng: exit 0
[task 2022-06-17T10:32:37.859Z] 10:32:37     INFO - Buffered messages logged at 10:31:52
[task 2022-06-17T10:32:37.860Z] 10:32:37     INFO - Entering test bound test
[task 2022-06-17T10:32:37.860Z] 10:32:37     INFO - Buffered messages finished
[task 2022-06-17T10:32:37.861Z] 10:32:37     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_urlbar_telemetry_dynamic.js | Test timed out - 
[task 2022-06-17T10:32:37.862Z] 10:32:37     INFO - GECKO(493) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2022-06-17T10:32:37.862Z] 10:32:37     INFO - GECKO(493) | MEMORY STAT | vsize 3191MB | residentFast 459MB | heapAllocated 214MB
[task 2022-06-17T10:32:37.863Z] 10:32:37     INFO - TEST-OK | browser/components/urlbar/tests/browser/browser_urlbar_telemetry_dynamic.js | took 45175ms
[task 2022-06-17T10:32:37.863Z] 10:32:37     INFO - checking window state
[task 2022-06-17T10:32:37.864Z] 10:32:37     INFO - GECKO(493) | Completed ShutdownLeaks collections in process 493
[task 2022-06-17T10:32:37.865Z] 10:32:37     INFO - TEST-START | Shutdown
```
Bug: Library automatically adjusts scroll position to selected bookmark/history item upon refocus
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2022-06-17 13:37:18+00:00
Resolved: 2022-10-28 01:35:37+00:00

Just noticed this on 101.0.1 when I was trying to organize my bookmarks.

STR:

1. (Depending on your screen resolution) create enough bookmark/history items in the same folder in the Library (around 50 to 100 should do).

2. Navigate to that specific folder in the Library and select any bookmark/history item.

3. Scroll up/down until the selected item moves out of sight.

4. Change the active window to something else (Firefox or not).

5. Change the active window back to the Library.


Expected Behavior:

The Library does not automatically adjust its scroll position upon refocus.

Actual Behavior:

The Library automatically adjusts its scroll position to the selected bookmark/history item upon refocus. During mozregression, I noticed when I use `Alt + Tab` (as opposed to left mouse click), this sometimes happens right after I change the active window away from the Library instead.


I appreciate that the library infopane can no longer obscure bookmarks located towards the end of a long list, but the current fix is not really helpful for organizing bookmarks. I could be looking at other parts of my unsorted bookmarks or other opened tabs in another Firefox window in order to decide how to organize this mess, or I could be simply distracted by something else (notifications maybe?). Having to remember to select a random item to retain scroll position is not fun, and should I need to refocus to the selected bookmark's position, I could have simply used the up/down arrow keys.


INFO: Last good revision: 2e154dcda079ad6ca50bc5d18cbd0991386c5989
INFO: First bad revision: 2ca189b8925dba3f28a1cefdc3e6f143ffbee290
INFO: Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2e154dcda079ad6ca50bc5d18cbd0991386c5989&tochange=2ca189b8925dba3f28a1cefdc3e6f143ffbee290
Bug: Settings content too wide for window
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-06-17 18:57:26+00:00
Resolved: 2022-06-20 17:22:15+00:00

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

Steps to reproduce:

Open the Firefox settings, then the pricacy section. Decent window width of about 1200 pixels. Locale is de-DE if relevant.


Actual results:

Horizontal scrollbar, cropped content. Makes using these settings hard and ugly.


Expected results:

Should see everything without scrolling to the right. This has worked in a previous version of Firefox.
Bug: Avoid the term “third-party cookies” in Enhanced Tracking Protection preferences
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2022-06-17 22:03:28+00:00
Resolved: 2023-02-24 15:08:01+00:00

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

Steps to reproduce:

1. In Firefox on desktop, open the privacy section of Settings: about:preferences#privacy
2. In the Enhanced Tracking Protection section, choose the Custom option and open the Cookies drop-down menu


Actual results:

The menu contains both the terms “cross-site cookies” and “third-party cookies”.


Expected results:

The menu should use the term “cross-site cookies” exclusively and avoid using the term “third-party cookies” completely.

According to the Cookies spec [1], “third-party cookies” is an informal synonym for “cross-site cookies”.

[1]: https://httpwg.org/http-extensions/draft-ietf-httpbis-rfc6265bis.html#name-third-party-cookies
Bug: Autocomplete suggest wrong URL
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-06-17 22:14:13+00:00
Resolved: 2022-06-23 09:14:22+00:00

When typing "red", the URL bar will now autocomplete as _red_`.reddit.com/r/linux`. This doesn't really make sense. The URL in the dropdown is still correct. I think I've seen this bug for the first time this week (using Nightly).
Bug: Perma Bustage/Timeout | JavaScript error: chrome://browser/content/browser.js, line 10037: TypeError: document.getElementById(...) is null when Gecko 103 merges to Beta on 2022-06-27
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-06-18 13:57:18+00:00
Resolved: 2022-06-23 13:46:27+00:00

[Central-as-beta simulation](https://treeherder.mozilla.org/jobs?repo=try&group_state=expanded&resultStatus=testfailed%2Cbusted%2Cexception%2Crunnable&revision=21ae65ddae329ae6f15c7450932043aab8a40080&selectedTaskRun=dCeKNKZiQaOP5YJWzs7cGA.1)

[How to run these simulations](https://wiki.mozilla.org/Sheriffing/How_To/Beta_simulations#TRUNK_AS_EARLY_BETA)

[Failure log bustage](https://treeherder.mozilla.org/logviewer?job_id=381783304&repo=try&lineNumber=295)

[Failure log timeout](https://treeherder.mozilla.org/logviewer?job_id=381782133&repo=try&lineNumber=2323)

```
INFO - 1655551048384	Marionette	DEBUG	Waiting for initial application window
[task 2022-06-18T11:17:32.522Z] 11:17:32     INFO - JavaScript error: chrome://browser/content/browser.js, line 10037: TypeError: document.getElementById(...) is null
[task 2022-06-18T11:17:32.596Z] 11:17:32     INFO - console.warn: SearchSettings: "get: No settings file exists, new profile?" (new NotFoundError("Could not open the file at /tmp/tmpl1sguvmj.mozrunner/search.json.mozlz4", (void 0)))
[task 2022-06-18T11:23:28.163Z] 11:23:28     INFO - JavaScript error: chrome://remote/content/marionette/driver.js, line 2273: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIObserverService.removeObserver]
[task 2022-06-18T11:29:38.168Z] 11:29:38    ERROR - REFTEST ERROR | None | application timed out after 370 seconds with no output
```
@Dao, can you take a look at this timeouts that are affecting beta-sims?
thank you
Bug: BSOD - ALWAYS when on online stores
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-06-18 18:18:03+00:00
Resolved: 2022-07-19 19:30:19+00:00

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

Steps to reproduce:

on Windows 10 - broswing online store www.odkarla.cz, www.alza.cz, and if I remember correctly also a www.czc.cz. (its more than two years from time I bought my PC, updated, firefox also updated) few times even reinstalled windows 10


Actual results:

BSOD driver IRQL or equal


Expected results:

..no BSOD :)
Bug: Recommended by Pocket turns itself back on.
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-06-18 20:26:17+00:00
Resolved: 2022-10-12 09:09:03+00:00

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

Steps to reproduce:

I turned off 'Recommended by Pocket,' and when I opened Firefox after restarting my PC it had turned itself back on. This is not the first time this has happened. It will usually save the setting in one session and sometimes even after restarting, but not every time. Not sure if it's being triggered by auto-updates or what. It is not the only setting that seems to reset itself, either. 


Actual results:

'Recommended by Pocket' turned itself back on.


Expected results:

I would expect that once turned off or on, all settings within Firefox would remain as set by the user after a restart or even an update.
Bug: Inconsistent event.target / z-index when controlled by :focus pseudoselector
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-06-19 10:30:18+00:00
Resolved: 2022-06-19 10:40:17+00:00

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

Steps to reproduce:

I have a table with a sticky first column and input fields in the others. The input fields show a toolbar when focused. Here is some example code:

```
<table>
<tr>
<td class="sticky">Lorem Ipsum</td>
<td>
    <input>
	<div class="toolbar"></div>
</td>
<td>
    <input>
	<div class="toolbar"></div>
</td>
<td>
    <input>
	<div class="toolbar"></div>
</td>
</tr>
</table>

<style>
td {
    position: relative;
}
#sticky {
    position: sticky;
    left: 0;
    background-color: white;
    z-index: 1;
    white-space: nowrap
}
.toolbar {
    position: absolute;
    top: 0;
    left: -20px;
    width: 20px;
    height: 20px;
    opacity: 0;
    background-color: red;
}
input:focus + .toolbar {
    opacity: 1;
    z-index: 2;
    cursor: pointer;
}
</style>
<script>
document.getElementById('table').addEventListener('click', function(e) {
	console.log(e.target);
});
</script>
```


Actual results:

When I click on the red box next to the second or third input field, the `event.target` is shown as `<div class="toolbar">`. When I click on the red box next to the first input,  `event.target` is shown as `<tr>`. 


Expected results:

When I hover over the red box next to the first input, the appropriate CSS (cursor: pointer) is applied, so you would think that this is the target for your click. But somehow it seems as if FF registers the click, updates the focus and only then looks for the target of the click event, which is now below the sticky `td`, so it falls back to the parent node.

I don't know if this is the expected behavior according to the specs, but it is very unintuitive, because the click that caused the loss of focus clearly happened while the input still had focus, so the event.target should be acquired before the new CSS is applied
Bug: Sync is not working anymore after a machine name change
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-06-19 12:03:06+00:00
Resolved: 2022-11-16 03:13:46+00:00

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

Steps to reproduce:

I changed the name of my Windows 10 machine a few days ago. 
Today I disconnected Firefox (and Waterfox) from Firefox Sync, and since, the two browsers won't connect, more exactly I can connect to the account, but the sync feature stays disconnected. Watch the attached video for an example of this behavior.


Actual results:

I'm unable to use to Firefox Sync service


Expected results:

I should be able to use it.
Bug: internet connection interrupted
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-06-19 17:42:12+00:00
Resolved: 2022-06-24 09:34:03+00:00

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

Steps to reproduce:

Il fatto
Ho cambiato Provider Internet passando a POSTE MOBILE (Italia) da 10 giorni.
Con questo provider e utilizzandi Firefox la connessione internet si interrompe dopo l'apertura di 3 max 4 Schede. La navigazione internet con Firefox semplicemente si blocca e devo chiudere Firefox, riaprirlo, e dopo max 3 schede aperte chiuderlo e riaprirlo perchè si blocca di nuovo, ecc.
Questo non accade con EDGE, e con Chrome.
Ho già fatto tutte le prove necessarie, ma sembra che Firefox sia incompatibile, o non ottimizzato con le connessioni internet del Provider Poste Mobile.
Se passo dalla rete del Provider Poste Mobile ad un altro Provider come TIM tutto va bene.
Il Provider Tim non posso utilizzarlo costantemente perchè ho l'abbonamento con il Provider POSTE MOBILE.


Actual results:

Blocco della navigazione internet connettendo Firefox alla Rete Internet con il Provider POSTE MOBILE Italiane dopo l'apertura di 2 max 3 schede. 


Expected results:

Non sarebbe dovuto succedere nulla perchè il mio pc:
- Windows 10 64 bit - Versione 10.0.19044
- Rete Ethernet
- Router Huawei B525s-23a
- Firefox 101.0.1 64 bit
si collegano a internet senza blocchi con altri provider ma non sempre con POSTE MOBILE.
Bug: your tab has just crashed, strace log is attached
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-06-19 18:33:01+00:00
Resolved: 2022-09-14 14:53:33+00:00

User Agent: Mozilla/5.0 (Android 10; Mobile; rv:91.0) Gecko/91.0 Firefox/91.0
Firefox for Android

Steps to reproduce:

installed firefox-esr 91.10.0esr on debian sid. debian sid is installed on my mobile device on userland app.


Actual results:

start firefox. it shows gah. your tab has just crashed. unable to browse anything. ddg.com, google.com, ask.com all of them show same message.


Expected results:

vsit any wensite.
Bug: Firefox 101.0.1 hangs in RDP session
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-06-19 21:56:49+00:00
Resolved: 2024-09-22 20:24:39+00:00

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

Steps to reproduce:

A nasty bug in the current version of Firefox 101.0.1.
How to reproduce it:
1) Run this version of Firefox on Windows 7 64 bit.
2) RDP into this computer (laptop etc.) from android device with any rdp-client and try to work in RDP-session with Firefox.



Actual results:

Firefox hangs tightly the first time you open a new tab.


Expected results:

But the interesting thing is that if you do the same but open Firefox 101.0.1 strictly after RDP session is created, Firefox works without any hangs.
 
This bug only appeared on the current release and maybe one more previous version. In the "nineties" series.  There was definitely no version of him!
Bug: One click custom search in address bar does not submit search query
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-06-19 23:07:39+00:00
Resolved: 2022-07-13 18:17:51+00:00

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

Steps to reproduce:

1. Launch Firefox (Windows or Ubuntu)
2. Type "sennheiser" in the address bar
3. Click a custom search provider's icon (e.g. Wikipedia)


Actual results:

UI elements change in the address bar (see screenshots)


Expected results:

I expected to see a list of search results on Wikipedia or the Sennheiser Wikipedia page.

https://support.mozilla.org/en-US/kb/search-firefox-address-bar says that "You can choose an alternative search type and use it for your search with one click if you don't want to use the current default."
Bug: The bottom over link does not disappear
Status: RESOLVED
Priority: P3
Resolution: WORKSFORME
Created: 2022-06-20 03:27:42+00:00
Resolved: 2022-10-04 15:20:24+00:00

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

Steps to reproduce:

This happens when streaming on Netflix, Amazon or HBO, the bottom left address bar does not disappear when going to full screen mode and need to reload the page for it to work.


Actual results:

Bottom left address bar does not disappear


Expected results:

Bottom left address bar should disappear when going to full screen mode.
Bug: FIx timeout failure for urlbar browser tests on Linux TV
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-06-20 05:14:45+00:00
Resolved: 2022-06-23 01:13:27+00:00

If we edit/add urlbar browser tests that use promiseAutocompleteResultPopup, timeout failures often happen on Linux TV.
In this bug, fix the issue.
Bug: [Experiment] An "Uncaught (in promise) TypeError: window.AWWaitForMigrationClose is not a function" error is displayed in the "Browser Console" after an import action is performed from the ECO Import spotlight
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-06-20 10:13:45+00:00
Resolved: 2022-06-21 18:22:44+00:00

**[Affected versions]:**
- Firefox Release 100.0.2 - Build ID: 20220519220738
- Firefox Release 101.0.1 - Build ID: 20220608170832

**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.2
- Linux Mint 20.2 x64

**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
  - "nimbus.debug" pref set to "true".
- Have the "Browser Console" opened.

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to the "about:studies?optin_slug=import-infrequent-eco2204-en&optin_branch=treatment-c&optin_collection=nimbus-preview" URL.
3. Restart the browser and click the "Import to Firefox" spotlight button.
4. Focus the "Browser Console" and observe if there are any errors displayed.

**[Expected result]:**
- There is no error displayed.

**[Actual result]:**
- The "Uncaught (in promise) TypeError: window.AWWaitForMigrationClose is not a function" error is displayed.

**[Notes]:**
- This issue is reproducible on all the "treatment" branches of the experiment.
- This issue is not reproducible if the import action is performed from the "File" browser menu.
- Attached a screen recording of the issue.
Bug: Firefox does not restore previous session if update is installed during program start after the crash
Status: UNCONFIRMED
Priority: --
Created: 2022-06-20 14:18:43+00:00
Resolved: 2025-02-03 13:25:00+00:00

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

Steps to reproduce:

I had multiple Firefox windows and tabs open.
The update was pending, but I was delaying it.
The computer crashed due to a power outage.
When the computer was restarted, Firefox asked if it is ok to install the update. I agreed.



Actual results:

When the update was installed, Firefox started with the "Restore previous session" window and nothing available in it.
This is the 2nd time this happened to me.


Expected results:

Firefox should preserve the previous session over the update process, or, otherwise warn that the previous session won't be preserved while offering to install the update.
Bug: browser-toolbarKeyNav.js thinks focus is moving backwards when it's moving forward, focus gets stuck
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-06-20 17:49:07+00:00
Resolved: 2022-09-30 21:39:57+00:00

There's a bug that I hit with the patch from bug 1774742. This is with `browser.tabs.firefox-view = false`, the current default, but the `toolbartabstop` we added for that button still being in place (which I think is the correct thing to do, because the user could still at their own buttons there.)

`toolkit/components/printing/tests/browser_modal_print.js` hits that bug when trying to Tab away from the print preview. browser-toolbarKeyNav.js thinks focus is moving backwards when it's really moving forward. So it calls rewindFocus, reverting focus to where it was before.
Bug: bookmark_validator.js appears to be unused in production code
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-06-20 21:53:14+00:00
Resolved: 2022-06-21 15:54:46+00:00

It looks like the last production use of `bookmark_validator.js` was removed in bug 1449730.

Although it is still referenced in `services/sync/modules/engines/bookmarks.js`, it isn't actually used there.

It is still [referenced in a few places](https://searchfox.org/mozilla-central/search?q=bookmark_validator.js&path=&case=false&regexp=false), including the tps extension and in tests.
Bug: Nothing happens when I click a mailto link, select "Firefox" from the application list and click "open link" button
Status: NEW
Priority: P5
Created: 2022-06-21 12:46:22+00:00
Resolved: 2024-02-27 18:22:44+00:00

I am not sure if the current behavior is kinda expected or not. 

STR:
1) Go to about:preferences#general , scroll the page down to the "Applications" section. Choose the action "Always Ask" for the content type "mailto"
2) Open Firefox, click a mailto link, for example "send mail" link on https://www.rapidtables.com/web/html/mailto.html#examples 
3) Select "Firefox" from the application list, then click "open link"

Actual result:
Nothing happens

If I select "Chrome" for step 3) and then click "open link", a new Chrome browser's window is opened with the black URL bar.
Bug: (MacOS) Interface shifts when menubar is once used
Status: NEW
Priority: P3
Created: 2022-06-21 14:43:43+00:00
Resolved: 2024-06-11 07:30:36+00:00

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

Steps to reproduce:

Start FF, click on any menubar item


Actual results:

Interface shifts. Tabs go lower, window button - higher. 


Expected results:

Nothing (in a matter of interface)
Bug: pdf.js loading bar not showing
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-06-21 15:40:24+00:00
Resolved: 2022-06-24 07:24:20+00:00

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

Steps to reproduce:

Try to access a non-local pdf file from Firefox.


Actual results:

The pdf.js loading bar, which was shown in older versions, is no longer appearing. There most probably is a link with bug #1768481


Expected results:

The loading bar should appear.
Bug: Facebook search in groups
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-06-21 16:19:10+00:00
Resolved: 2022-07-04 15:51:20+00:00

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

Steps to reproduce:

I can no longer use the Facebook "Search" function inside my Facebook Groups. The site attempts to execute my search (for a specific term or phrase) but then halts before returning any results. This has been going on for months.  On the same hardware I do not get this issue with Edge browser. 


Actual results:

In the screen capture I provided with this report, you can see the thin blue line that appears below the address bar as Facebook attempts to process my search request. This is as far as it gets however, no actual search results ever appear.


Expected results:

Summary of all found search terms
Bug: Glean default search engine data is reporting errors when submitting an empty submission URL
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-06-21 16:44:28+00:00
Resolved: 2022-07-21 14:19:35+00:00

When submitting the default search engine data to glean, we will sometimes submit `undefined` as the value for [the submission url](https://searchfox.org/mozilla-central/rev/b1a5802e0f73bfd6d2096e5fefc2b47831a50b2d/toolkit/components/search/SearchService.jsm#2894-2896,2910-2912).

This is because we do not report the submission URL for every engine - only specific ones that we're interested in.

The problem here is because we're using the `application` lifetime, we need to be able to clear the submission URL if we move from an engine where we normally submit the url to one where we don't.