av9ash/GitBugs huggingface dataset:
Bug: Intermittent browser/components/preferences/tests/browser_searchShowSuggestionsFirst.js | Test timed out -
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-01-16 02:44:10+00:00
Resolved: 2021-02-09 17:04:20+00:00

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

---
```
[task 2021-01-16T01:25:37.088Z] 01:25:37     INFO - TEST-PASS | browser/components/preferences/tests/browser_searchShowSuggestionsFirst.js | Checkbox should become checked after clearing pref - true == true - 
[task 2021-01-16T01:25:37.088Z] 01:25:37     INFO - Leaving test bound openWithSearchSuggestionsShownFirst
[task 2021-01-16T01:25:37.088Z] 01:25:37     INFO - Entering test bound openWithHistoryShownFirst
[task 2021-01-16T01:25:37.088Z] 01:25:37     INFO - Buffered messages finished
[task 2021-01-16T01:25:37.088Z] 01:25:37     INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/tests/browser_searchShowSuggestionsFirst.js | Test timed out - 
[task 2021-01-16T01:25:37.218Z] 01:25:37     INFO - GECKO(1570) | MEMORY STAT | vsize 130552385MB | residentFast 4492MB
[task 2021-01-16T01:25:37.219Z] 01:25:37     INFO - TEST-OK | browser/components/preferences/tests/browser_searchShowSuggestionsFirst.js | took 197665ms
[task 2021-01-16T01:25:37.223Z] 01:25:37     INFO - Not taking screenshot here: see the one that was previously logged
[task 2021-01-16T01:25:37.223Z] 01:25:37     INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/tests/browser_searchShowSuggestionsFirst.js | Found a tab after previous test timed out: about:preferences#search - 
[task 2021-01-16T01:25:37.459Z] 01:25:37     INFO - checking window state```
Bug: [Windows][Linux] About Firefox "Firefox Help" and "Submit Feedback" links do nothing
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-01-16 16:09:11+00:00
Resolved: 2021-01-22 04:41:01+00:00

The links in the Firefox about dialog  "Firefox Help" and "Submit Feedback" do nothing. 

22:39.26 INFO: No more integration revisions, bisection finished.
22:39.26 INFO: Last good revision: a673fcbd7a067815aa8b8966e134283aae5a4e56
22:39.26 INFO: First bad revision: b1628ddad29124227e334e82e9fac863bc877e4d
22:39.26 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a673fcbd7a067815aa8b8966e134283aae5a4e56&tochange=b1628ddad29124227e334e82e9fac863bc877e4d
Bug: Up-arrow -> enter opens preferences unintentionally (search settings selection persists on input)
Status: NEW
Priority: P3
Created: 2021-01-16 18:59:15+00:00
Resolved: 2024-10-08 21:14:53+00:00

Ctrl-T, type in something, hit up-arrow and continue typing. Keyboard focus is still in the right place, but hitting enter takes you to preferences.

I probably open my preferences a dozen times a day by accident as a result.

This is somewhat baffling, considering how many text fields use up-arrow to mean "home" for single line input. I'm not sure what the right thing here is, but perhaps up-arrow should return to the beginning of the entered text and not "loop around" the bottom of the awesomebar focus options.
Bug: Search keyword is not consistent with localized Wikipedia search engine name
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2021-01-17 07:55:41+00:00
Resolved: 2024-11-09 15:25:18+00:00

The Wikipedia has a search keyword @wikipedia in Firefox, however in Czech the name is Wikipedi**e** (see the logo in the top left https://cs.wikipedia.org/wiki/Hlavn%C3%AD_strana) and so the keyword should match the name.
Bug: browser.tabs.unloadOnLowMemory = true still gets Firefox killed by earlyoom
Status: UNCONFIRMED
Priority: --
Created: 2021-01-17 15:49:56+00:00
Resolved: 2021-03-01 15:00:58+00:00

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

Steps to reproduce:

1. Use a 16GiB desktop linux system with earlyoom and use firefox, and leave it running for days (via suspend) with moderate usage, 40-50 idle tabs with 1-2 active ones with Youtube, regular websites, etc.
2. Set browser.tabs.unloadOnLowMemory to true
3. Firefox will get shot down by earlyoom, always.


Actual results:

Firefox bloats up until it is killed by earlyoom


Expected results:

Actually unload tabs, otherwise what's the point? It is really not acceptable that on a 16GiB system with otherwise no really demanding programs running, Firefox will reliably die with moderate usage every 2-3 days. It seems like Firefox's memory handling is fundamentally not working.
Bug: Close tabs to the right does not close pinned tabs to the right
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2021-01-17 18:58:59+00:00
Resolved: 2021-01-22 12:08:31+00:00

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

Steps to reproduce:

Clicked close tabs to the right



Actual results:

Only normal tab was closed, six other pinned tabs to the right did nit close


Expected results:

All tabs to the right (including the pinned ones) should be closed.

Setting a defect, but maybe this is a feature request, not sure.
Bug: "About Firefox" dialog now has two side-by-side links with no separation ("Firefox Help Submit Feedback") which feels a bit jumbled/awkward
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2021-01-18 00:37:53+00:00
Resolved: 2021-08-02 07:54:33+00:00

The "About Firefox" dialog changed its content a little in bug 1660848, and now it has a line with two side-by-side links: `Firefox Help Submit Feedback`.  See attached screenshot.

These links feel a little jumbled - in particular:
 - They don't have any separation between them (besides a space character) which makes it hard to see where one link stops and the next begins.  Especially because the "p" interrupts the first link's underline.
 - The rest of the dialog (after this point) is all either complete sentences ("You are currently on the nightly update channel."), so this one line of four random words ("Firefox Help Submit Feedback") feels a little weird/jumpy.

I'm not a designer, and I don't know what best practices are for this sort of thing; but I wonder if maybe we should add a little more space between these links?  As an example of a piece of this UI that's got similar content but feels cleaner see the *very bottom* of the dialog where we have a link bar, which says "Licensing Information" [lots of space] "End-User Rights" [lots of space] "Privacy Policy".  The spacing there makes the links easier to distinguish and prevents them from feeling like a weird sentence fragment.
Bug: Can't close tab when opening Google Meet
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-01-18 10:15:38+00:00
Resolved: 2021-01-19 15:40:10+00:00

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

Steps to reproduce:

Open a Google Meet link

This is on 84.0.2, on MacOS 10.15.7


Actual results:

I'm not able to close the tab or any other tabs in the same window, nor am I able to reorder them. When rightclicking on any of the tabs I get the same menu as if I were rightclicking on empty area next to the tabs, instead of the tab-specific context-menu
I can switch tabs. and open new ones in the same window. New tabs in the same window have the same behavior, other windows don't.


Expected results:

I can close and move around tabs normally.
Bug: Resizing the browser horizontally while in customize mode does not respect the minimum width
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2021-01-18 11:54:04+00:00
Resolved: 2022-11-08 10:40:45+00:00

*Affected versions*
* 86.0a1 (20210117214903)
* 85.0b9 (20210114193053)
* 84.0.2 (20210105180113)
* 78.6.1esr (20210105204613)

*Affected platforms*
* Windows 10x64
* MacOS 11
* Ubuntu 18.04

*Steps to reproduce*
1. Open Firefox and go to the Customize menu.
2. Resize the browser horizontally making it smaller.

*Expected result*
* Browser is resized as expected respecting the minimum width.

*Actual result*
* On Windows 10x64 the Minimize, Maximize buttons are cut off: [screenshot](https://drive.google.com/file/d/1CYDnV_mK1glRU6BZEQlH1eZGqrhqV1m6/view?usp=sharing)
* On macOS 11 there is only Back and Forward buttons displayed: [screenshot](https://drive.google.com/file/d/15PubKbI_IuIJoVe0ZfQ_B9uNgECVtfdd/view?usp=sharing)
* On Ubuntu 18.04 the entire browser can be hidden while resizing (see attached screen recording)

*Regression range*
* Last good revision: caf55914ccddba34d462a1206530d7868b6c4992 (2019-11-09)
* First bad revision: 72c52c0101cfd102b207224646c3007d6872e65c (2019-11-10)
* Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=caf55914ccddba34d462a1206530d7868b6c4992&tochange=72c52c0101cfd102b207224646c3007d6872e65c


*Notes*
* Attached a screen recording. 
* The issue can be reproducible only in customize mode.
Bug: Failures to access IndexedDB are not being reported
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-01-18 13:50:04+00:00
Resolved: 2021-01-21 09:22:39+00:00

ASRouter is using [IndexedDB storage](https://searchfox.org/mozilla-central/rev/dac45cc7020dfddbcc937827810dd11550c07dc3/browser/components/newtab/lib/ASRouterDefaultConfig.jsm#33) for persisting impressions and blocks but not reporting back telemetry in case of failures.
Bug: Intermittent browser/components/newtab/test/browser/browser_customize_menu_content.js | Uncaught exception - Snippets pref is turned on after click - timed out after 50 tries.
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-01-18 17:55:48+00:00
Resolved: 2023-10-20 12:02:06+00:00

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

---
```
[task 2021-01-18T17:24:13.312Z] 17:24:13     INFO - TEST-PASS | browser/components/newtab/test/browser/browser_customize_menu_content.js | Snippets pref is turned off - true == true - 
[task 2021-01-18T17:24:13.312Z] 17:24:13     INFO - Buffered messages finished
[task 2021-01-18T17:24:13.312Z] 17:24:13     INFO - TEST-UNEXPECTED-FAIL | browser/components/newtab/test/browser/browser_customize_menu_content.js | Uncaught exception - Snippets pref is turned on after click - timed out after 50 tries.
[task 2021-01-18T17:24:13.312Z] 17:24:13     INFO - Leaving test bound test_render_customizeMenu
[task 2021-01-18T17:24:13.313Z] 17:24:13     INFO - GECKO(1930) | MEMORY STAT | vsize 130551400MB | residentFast 2528MB
[task 2021-01-18T17:24:13.313Z] 17:24:13     INFO - TEST-OK | browser/components/newtab/test/browser/browser_customize_menu_content.js | took 13088ms```
Bug: Sync problem
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-01-18 18:34:22+00:00
Resolved: 2021-02-23 20:22:35+00:00

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

Steps to reproduce:

Format my computer and install firefox, log in firefox account to sync but never get my data. I use this for more than a year and no problems until today.


Actual results:

I lost all my history, fav's, cookies and passwords.


Expected results:

Restore all my data from the cloud.
Bug: window.alert plays sound when `prompts.contentPromptSubDialog=true`
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2021-01-18 21:13:32+00:00
Resolved: 2021-02-05 22:40:51+00:00

1. Open `data:text/html,<script>alert("hello")</script>`

Expected: No sound
Actual: It sounds on Windows
Bug: test_headless.js doesn't work in Thunderbird with E10s enabled
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-01-19 09:20:24+00:00
Resolved: 2021-01-20 11:52:21+00:00

I'm working to enable E10s on Thunderbird. For a Thunderbird build, XPCShell tests run with a profile that loads the default prefs (which is not the case for Firefox builds) so this test runs with browser.tabs.remote.autostart set to true. It doesn't work. Here's a log:
```
widget/headless/tests/test_headless.js | Starting test_snapshot
(xpcshell/head.js) | test test_snapshot pending (2)
(xpcshell/head.js) | test run_next_test 0 finished (2)
"CONSOLE_MESSAGE: (error) [JavaScript Error: "NetworkError when attempting to fetch resource." {file: "/builds/worker/workspace/build/tests/xpcshell/head.js" line: 239}]
_do_main@/builds/worker/workspace/build/tests/xpcshell/head.js:239:6
_execute_test@/builds/worker/workspace/build/tests/xpcshell/head.js:567:5
```
I'll probably end up just turning the test off for Thunderbird. Unless somebody out there has a brilliant idea?
Bug: [Ubuntu 20] Permission panel isn’t displayed for tel links from outlook
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2021-01-19 11:10:39+00:00
Resolved: 2021-01-20 08:34:29+00:00

**Affected versions**
* 86.0a1 (2021-01-18)
* 85.0b9
* 85.0

**Affected platforms**
* Ubuntu 20.04


**Steps to reproduce**
1. Launch Firefox.
2. Access the following [webpage](https://outlook.live.com/people/)
3. Click on the mobile number.


**Expected result**
* The "Allow this site to open the tel link?" doorhanger is displayed.

**Actual result**
* Permission doorhanger isn’t displayed.

**Regression range**
* I don’t think this issue is a regression since it is reproducible only on the ubuntu 20 machine, but I’ll investigate to see if it’s one.

**Additional notes**
* This issue isn't reproducible on Ubuntu 18.04
Bug: The "Close" button is not automatically focused if the "Customize" menu is opened via keyboard navigation
Status: VERIFIED
Priority: P2
Resolution: WORKSFORME
Created: 2021-01-19 12:39:37+00:00
Resolved: 2024-02-08 15:24:19+00:00

**[Affected versions]:**
- Firefox Beta 85.0 RC1 - Build ID: 20210118153634
- Firefox Nightly 86.0a1 - Build ID: 20210118214232

**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Linux Mint 20

**[Prerequisites]:**
- Have a Firefox profile with the "browser.newtabpage.activity-stream.newNewtabExperience.enabled" pref set to "true" in the "about:config" page.

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites and open a "New Tab".
2. Press the "Tab" key four times and press the "Enter" key.
3. Observe the behavior.

**[Expected result]:**
- The "Close" button from the top-right part of the "Customize" menu is focused.
	
**[Actual result]:**
- No element from the "Customize" menu is visibly focused.

**[Additional Notes]:**
- If the "Enter" or the "Space" key is pressed after following the steps from above, nothing happens.
- If the "Tab" key is pressed once more after following the steps from above, the "Close" button is focused.
- This behavior was supposed to be fixed by Bug 1682055 based on its description.
- Attached a screen recording of the issue.
Bug: The "Personalize" button is not automatically focused if the "Customize" menu is dismissed via keyboard navigation
Status: VERIFIED
Priority: P2
Resolution: WORKSFORME
Created: 2021-01-19 12:39:41+00:00
Resolved: 2024-02-08 15:24:06+00:00

**[Affected versions]:**
- Firefox Beta 85.0 RC1 - Build ID: 20210118153634
- Firefox Nightly 86.0a1 - Build ID: 20210118214232

**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Linux Mint 20

**[Prerequisites]:**
- Have a Firefox profile with the "browser.newtabpage.activity-stream.newNewtabExperience.enabled" pref set to "true" in the "about:config" page.

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites and open a "New Tab".
2. Press the "Tab" key four times and press the "Enter" key.
3. Press the "Tab" key once and press the "Enter" key again.
4. Observe the behavior.

**[Expected result]:**
- The "Personalize" button from the top-right part of the "New Tab" page is focused.
	
**[Actual result]:**
- No element from the "New Tab" page is visibly focused.

**[Additional Notes]:**
- If the "Enter" or the "Space" key is pressed after following the steps from above, nothing happens.
- This behavior was supposed to be fixed by Bug 1682055 based on its description.
- Attached a screen recording of the issue.
Bug: Firefox frozen upon every other startup
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2021-01-19 15:17:38+00:00
Resolved: 2021-01-28 14:28:07+00:00

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

Steps to reproduce:

- Start Firefox. (Mine loads to about:blank.)
- Then shut it down. On the console, upon shutdown:

###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

- Note that "ps -e | grep firefox" turns up nothing and Firefox has closed.
- Start Firefox up again. Either no window appears, or the browser window appears but it is completely frozen and cannot be interacted with.
- Force Quit.
- Start Firefox up and be asked if I want to restore my tabs from a couple of sessions ago.

This began in v85b9 (v85b8 at the earliest) and now in v85. Debian 10.7 in Gnome. Occurs even with no active browser add-ons.
Bug: $ and # searches in the awesomebar should not display web search suggestions
Status: NEW
Priority: P5
Created: 2021-01-19 17:00:30+00:00
Resolved: 2021-01-19 17:00:30+00:00

When searching for `$ foo` or `# bar` the awesomebar still show search suggestions, even though those prefixes are meant to filter for results that include the keywords in the URL and/or page title.

We shouldn't do search suggestions nor should we send the query to the search engine at all for privacy reasons.

Marco says this is a result of these prefixes not having been converted to chiclets yet.
Bug: pressing Ctrl+v+enter does not prepend www. and append .com to the pasted text
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2021-01-19 18:09:44+00:00
Resolved: 2021-01-19 21:18:50+00:00

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

Steps to reproduce:

1. Copy the word google to the clipboard.
2. Go to the Address Bar
3. Press Ctrl+V+Enter (hold down the control key the entire time)


Actual results:

firefox searches for the word google


Expected results:

firefox should have gone to www.google.com
Bug: Beim Start von Firefox im Privaten Modus muss man extra die Adress-Zeile anklicken, um eine Adresse einzugeben
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-01-19 18:27:59+00:00
Resolved: 2021-04-22 12:44:09+00:00

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

Steps to reproduce:

Hallo, 
seit langem ärgere ich mich darüber: 

Ich starte Firefox in der Taskleiste mit der rechten Maus-Taste im "Privaten Fenster"

Mein System: 
Windows 10 Home Edition, Version 20H2
Firefox: 84.0.2. (64 Bit)

Erweiterungen:
Adblock Plus
Avast Online Security
Bookmark Manage and Viewer
Clear Flash Cookies
DownThemAll!
EPubReader
NoScript
Video DownloadHelper

Plugins:
OpenH264-Videocodec




Actual results:

Ich kann nicht gleich eine Adresse in die Adressleiste eingeben, obwohl der Cursor dort blinkt. Ich muss extra in die Adresszeile klicken, um dort schreiben zu können.


Expected results:

Nach dem Start von Firefox in einem "Privaten Fenster" sollte ich sofort am blinkenden Cursor in der Adress-Zeile schreiben können.
Bug: Pages do not load completely
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2021-01-19 22:23:05+00:00
Resolved: 2021-01-22 19:14:38+00:00

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

Steps to reproduce:

Went to open Facebook, and page partially loads and stops. 

Also happens when I try to log into my SmugMug account. 


Actual results:

Page partially loads and stalls out. No links work within page. 


Expected results:

To be able to scroll through Facebook and click on links for groups and people and stories. Seems to have started with the push for 84.0.2 as it started yesterday (1/18/21). Screen shot show how far down I can go (and it won't load any more stories). 

As for my SmugMug account, if I've tried to go to Facebook it won't let me even see the main page of my personal site (www.parkergolfphotography.com); I just see the bottom description of the photo that should be across the page. If I quit FF and try again, I can get to the login screen where I can log in, but again it brings me to the black screen (which I'd attach but can only add one screen shot on this request) with just a footer showing. Chrome and Safari both currently work for both pages.
Bug: About Firefox green checkmark is not centered with the message that follows it
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2021-01-20 07:34:04+00:00
Resolved: 2021-05-28 13:22:54+00:00

**Affected versions**
- Firefox 86.0a1

**Affected platforms**
- Windows 10
- macOS 10.15.7
- Ubuntu 20.04

**Steps to reproduce**
1. Launch Firefox
2. Access About Nightly

**Expected result**
- The newly added green checkmark is centered with the message following it

**Actual result**
- The checkmark is not centered

**Regression range**
- This is not a regression, as it was just implemented in Nightly builds

**Additional notes**
- The issue can be seen in the attachment
- There is an added restart sign if an update is downloaded and Firefox prompts the user which is affected too.
Bug: Event retargeting though target exists
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-01-20 09:53:53+00:00
Resolved: 2021-01-26 11:04:40+00:00

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

Steps to reproduce:

  1. go to https://codepen.io/swiod/pen/zYKbJKQ in Firefox for Android
  2. touch close to the left edge of "button by click"


Actual results:

both buttons ("button by touchstart", "button by click") trigger


Expected results:

only "button by click" should trigger
Bug: Selected tab may not be part of a multiselection
Status: NEW
Priority: --
Created: 2021-01-20 11:46:46+00:00
Resolved: 2021-01-20 11:46:46+00:00

Make sure you have 3 tabs and run this code in the browser console:

```js
var [tab1, tab2, tab3] = gBrowser.tabs;
gBrowser.selectedTabs = [tab1, tab2];
gBrowser.lockClearMultiSelectionOnce();
gBrowser.selectedTab = tab3;
console.assert(tab1.multiselected === true, 'tab1');
console.assert(tab2.multiselected === true, 'tab2');
console.assert(tab3.multiselected === true, 'tab3'); // fails
```

`tab3` is the selected tab, and there is a multiselection since `tab1` and `tab2` are multiselected. Then, the selected tab should be part of the multiselection, but it isn't!

The bug can be triggered without the console, just by using the UI:

1. Open a window with 4 tabs
2. Select the 4th tab, and multiselect the 1st and 2nd ones
3. Right-click the 3rd tab (not selected nor multiselected) and choose "Close Multiple Tabs > Close Tabs to the Right".
4. That closes the 4th tab, which was selected, so the 3rd one becomes selected.
5. Now we still have a multiselection, but `gBrowser.selectedTab.multiselected === false`

In practice this doesn't seem a big deal since `gBrowser.selectedTabs` makes sure to include the selected tab. But having a wrong `multiselected` might break webextensions. And it creates inconsistencies, e.g. if you try to follow the steps above but with just 3 tabs

1. Open a window with 3 tabs
2. Select the 3rd tab, and multiselect the 1st one
3. Right-click the 2nd tab (not selected nor multiselected) and choose "Close Multiple Tabs > Close Tabs to the Right".
4. That closes the 3rd tab, which was selected, so the 2nd one becomes selected.

This time the 1st tab stops being multiselected! That's because, since it was the only multiselected tab, the multiselection is cleared.

Actually there is the test browser_multiselect_tabs_close_other_tabs.js which expects the multiselection to be cleared, even if it's due to a bug. So maybe the test is wrong, or maybe the multiselection shouldn't be locked when removing tabs.