av9ash/GitBugs huggingface dataset:
Bug: openBookmarkedURL trigger name & docs very confusingly wrong
Status: ASSIGNED
Priority: P3
Created: 2023-03-09 18:32:07+00:00
Resolved: 2023-03-24 16:17:51+00:00

https://firefox-source-docs.mozilla.org/toolkit/components/messaging-system/docs/TriggerActionSchemas/index.html#openbookmarkedurl says:

> Happens when the user bookmarks or navigates to a bookmarked URL.
>
> Does not filter by host or patterns.

Which would be great if the trigger worked the way it was named.

It actually waits for the [bookmark-icon-updated event](https://searchfox.org/mozilla-central/rev/2af0d81d29bcd264083e04a2473d82a91f0f7eb6/browser/base/content/browser-places.js#1906-1909), meaning that it actually fires when a bookmark is starred or unstarred in the UI (i.e. is added or deleted using the primary UI).

There are two pieces here, I think:

a) document what this trigger actually does sooner rather than later
b) alias `openBookmarkedURL` to something like `starOrUnstarBookmark`, and deprecate openBookmarkedURL.  We could call it `addOrDeleteBookmark` for simplicity, but then we'd have to explicitly document that this only includes actions that go through the UI star (which would be most of them, I'd think), not through the bookmarks manager.
Bug: Intermittent toolkit/components/translations/tests/browser/browser_about_translations.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INVALID
Created: 2023-03-09 19:57:02+00:00
Resolved: 2023-05-23 00:40:14+00:00

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

---
```
[task 2023-03-09T19:08:59.987Z] 19:08:59     INFO - TEST-PASS | toolkit/components/translations/tests/browser/browser_about_translations.js | The fromSelect starting value is "detect" - "detect" == "detect" - 
[task 2023-03-09T19:08:59.988Z] 19:08:59     INFO - Console message: [JavaScript Error: "Error: An error occured in the AboutTranslations actor."]
[task 2023-03-09T19:08:59.988Z] 19:08:59     INFO - Console message: [JavaScript Error: "Error: An error occured in the AboutTranslations actor."]
[task 2023-03-09T19:08:59.997Z] 19:08:59     INFO - Buffered messages finished
[task 2023-03-09T19:08:59.998Z] 19:08:59     INFO - TEST-UNEXPECTED-FAIL | toolkit/components/translations/tests/browser/browser_about_translations.js | Uncaught exception in test bound test_about_translations_language_identification - Waiting for placeholder text to be visible." - timed out after 50 tries.
[task 2023-03-09T19:08:59.999Z] 19:08:59     INFO - Leaving test bound test_about_translations_language_identification
[task 2023-03-09T19:08:59.999Z] 19:08:59     INFO - GECKO(23013) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2023-03-09T19:09:00.004Z] 19:09:00     INFO - GECKO(23013) | MEMORY STAT heapAllocated not supported in this build configuration.
[task 2023-03-09T19:09:00.005Z] 19:09:00     INFO - GECKO(23013) | MEMORY STAT | vsize 20975307MB | residentFast 1231MB
[task 2023-03-09T19:09:00.007Z] 19:09:00     INFO - TEST-OK | toolkit/components/translations/tests/browser/browser_about_translations.js | took 13899ms
[task 2023-03-09T19:09:00.007Z] 19:09:00     INFO - Not taking screenshot here: see the one that was previously logged
[task 2023-03-09T19:09:00.009Z] 19:09:00     INFO - TEST-UNEXPECTED-FAIL | toolkit/components/translations/tests/browser/browser_about_translations.js | Found an unexpected tab at the end of test run: about:translations - 
[task 2023-03-09T19:09:00.010Z] 19:09:00     INFO - checking window state
[task 2023-03-09T19:09:00.010Z] 19:09:00     INFO - TEST-START | toolkit/components/translations/tests/browser/browser_full_page.js
```
Bug: Jank in browser with very large number of tabs
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-03-09 23:14:29+00:00
Resolved: 2024-02-22 14:16:51+00:00

While investigating something else, a profile I took showed significant jank in the main process (>1/2 second) apparently writing out sessionstore data.   You can see the realloc behavior causing increasingly long memcpys, up to 70ms for one copy -- on a super-fast desktop.   It's possible this is hard to avoid, but perhaps it could be done on a Worker

recovery/previous.jsonlz4 are around 35MB.   36 windows, ~7700 tabs, 120 loaded.  System is largely idle (~2% cpu used)

https://share.firefox.dev/3J3EZQw
Bug: ShellService writes to console on every start
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2023-03-10 12:15:54+00:00
Resolved: 2023-03-16 19:08:35+00:00

I see this every time I start my local nightly build on my Windows 10 developer machine.

```
console.debug: ShellService:
  Found known browser prefix: Firefox
```

This is confusing because as shown in the screenshot I have not set a loglevel pref. I would not expect the default to be `debug`, but [that's what we're using to log this](https://searchfox.org/mozilla-central/rev/2f9a79d1c4ae7090cf50d93be86ba9dc2767a733/browser/components/shell/ShellService.jsm#255), so I think something is wonky.
Bug: Bookmark toolbar items button moves to the center area on a new profile after removing the Import Bookmarks button inside the Customize menu
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-03-10 13:05:11+00:00
Resolved: 2023-03-13 14:53:10+00:00

**Found in**
* 112.0a1 (2023-03-09)


**Affected versions**
* 112.0a1 (2023–03-08)




**Tested platforms**
* Affected platforms: Ubuntu 20.04, Windows 10x64, macOS 12
* Unaffected platforms: none




**Steps to reproduce**
1. Open Firefox with a new profile and enter Customize menu.
2. Drag the `Import Bookmarks...` button from the Bookmarks toolbar.


**Expected result**
* The Bookmarks toolbar items is placed on the left side.

**Actual result**
* The Bookmarks toolbar items is placed in the center.

**Regression range**
*  Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b7c72ebf0fba4d15597396db33c798bc4eaed488&tochange=cee1f3bbec04b3ced627321a44cc6db8a7179293 



**Additional notes**
* Attached a screen recording.
* The issue disappears after the bookmark toolbar is displayed on a new tab.
* The issue reapers after restarting Firefox while in Customize mode.
Bug: Perma Late Beta browser/components/urlbar/tests/engagementTelemetry/browser/browser_glean_telemetry_engagement_edge_cases.js when Gecko 112 switches to Late Beta 2023-02-24
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-03-10 13:37:05+00:00
Resolved: 2023-03-20 12:14:35+00:00

[Central-as-Beta simulation](https://treeherder.mozilla.org/jobs?repo=try&resultStatus=testfailed%2Cbusted%2Cexception%2Crunnable&revision=f2475c85ed2aa2c525ff329baee68675b5acfda0&selectedTaskRun=K00hzVXFS06ZzWSq4x0sQQ.0&searchStr=Linux%2C18.04%2Cx64%2CWebRender%2Ctsan%2Copt%2CMochitests%2Cwith%2Csoftware%2Cwebrender%2Cenabled%2Ctest-linux1804-64-tsan-qr%2Fopt-mochitest-browser-chrome-swr%2Cbc17)

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

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

```
INFO - TEST-PASS | browser/components/urlbar/tests/engagementTelemetry/browser/browser_glean_telemetry_engagement_edge_cases.js | groups is correct - "" == "" - 
[task 2023-03-10T12:20:34.047Z] 12:20:34     INFO - Buffered messages logged at 12:18:27
[task 2023-03-10T12:20:34.047Z] 12:20:34     INFO - Console message: [JavaScript Error: "1678450707340	addons.xpi	ERROR	System addon update list error Error: got node name: html, expected: updates" {file: "resource://gre/modules/Log.sys.mjs" line: 722}]
[task 2023-03-10T12:20:34.047Z] 12:20:34     INFO - append@resource://gre/modules/Log.sys.mjs:722:12
[task 2023-03-10T12:20:34.048Z] 12:20:34     INFO - log@resource://gre/modules/Log.sys.mjs:376:16
[task 2023-03-10T12:20:34.048Z] 12:20:34     INFO - error@resource://gre/modules/Log.sys.mjs:384:10
[task 2023-03-10T12:20:34.048Z] 12:20:34     INFO - updateSystemAddons/res<@resource://gre/modules/addons/XPIInstall.jsm:4104:25
[task 2023-03-10T12:20:34.048Z] 12:20:34     INFO - 
[task 2023-03-10T12:20:34.048Z] 12:20:34     INFO - Buffered messages finished
[task 2023-03-10T12:20:34.048Z] 12:20:34     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/engagementTelemetry/browser/browser_glean_telemetry_engagement_edge_cases.js | Test timed out - 
[task 2023-03-10T12:20:34.436Z] 12:20:34     INFO - GECKO(5454) | MEMORY STAT | vsize 130551597MB | residentFast 1348MB
[task 2023-03-10T12:20:34.438Z] 12:20:34     INFO - TEST-OK | browser/components/urlbar/tests/engagementTelemetry/browser/browser_glean_telemetry_engagement_edge_cases.js | took 240703ms
Bug: Image in `Media` tab  is clipped inside `Page Info` window
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-03-10 14:34:48+00:00
Resolved: 2023-03-16 09:56:23+00:00

Steps to reproduce:
1. Open https://www.wikipedia.org/
2. Open `Page Info` (Ctrl + I)
3. Select `Media` tab
4. Select a url of `https://www.wikipedia.org/portal/wikipedia.org/assets/img/sprite-e99844f6.svg` background

Actual Results:
The top half of the image is truncated. (Depends on the height of the dialog.)
Even if scrolled, you cannot see the whole image.

Expected Results:
Images should be displayed without being truncated. 
The whole image can be seen by scrolling

1st regression window: no scrollbar
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6d37ee664b922e926a686feba165b20a628626e3&tochange=62fd688e335958ef1e95328d7bab329be8ad3a0f

2nd regression window: scrollbar is sown, but this bug appears.
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=425fd934f38510050f3cc721708511a3aef5a9fc&tochange=dc16834bdd96e0fc1c355848d5c79a02d9424943
Bug: Unusually big overflow menu with massive padding between items
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-03-10 14:50:31+00:00
Resolved: 2023-03-13 15:55:29+00:00

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

Steps to reproduce:

Step 1: Open Firefox and go to "Customize Toolbar..."
Step 2: Drag anything to the overflow menu


Actual results:

Overflow menu is bigger than its actual size
Padding between items in the overflow menu doesn't come back to normal after adding at least 4 items


Expected results:

The overflow menu shouldn't be this big or have this much padding
Bug: Anti-user behavior available to websites
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-03-10 16:48:06+00:00
Resolved: 2023-04-19 15:52:42+00:00

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

Steps to reproduce:

Be a netizen


Actual results:

Firefox (mobile and desktop) breaks basic browser functionality at the behest of anti-user websites:
* Breaks right-click/long press
* Breaks selection
* Breaks zooming
* Breaks scrolling
* Breaks the back button/stack alteration/redirection
* Exploitation of the user agent string to force native application installation
* Probably more


Expected results:

Firefox does not break fundamental functionality
Bug: BUG: color picker crashes in headless on Ubuntu
Status: NEW
Priority: --
Created: 2023-03-10 19:04:46+00:00
Resolved: 2024-11-25 10:16:46+00:00

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

Steps to reproduce:

OS: Ubuntu 20.04
Firefox: 110 stable
Downstream bug: https://github.com/microsoft/playwright/issues/19929

Consider running the following puppeteer snippet:

```
// a.mjs
import puppeteer from 'puppeteer-core';

const browser = await puppeteer.launch({
  product: 'firefox',
  executablePath: '/usr/bin/firefox',
  dumpio: true,
});
const page = await browser.newPage();

await page.goto(
  'https://storage.googleapis.com/public-dev-test-lab/input/inputtypes.html'
);
const inputColorElement = await page.$('#input-color');
await inputColorElement?.click();

await browser.close();
```


Actual results:

Firefox crashes with the following output:


(firefox:3295229): Gtk-CRITICAL **: 11:03:34.737: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
[Parent 3295229, Main Thread] WARNING: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed: 'glib warning', file /build/firefox-jjwe4i/firefox-110.0.1+build2/toolkit/xre/nsSigHandlers.cpp:167


Expected results:

The browser should not crash.
Bug: Too many untrusted modules kept in UntrustedModulesData
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-03-10 19:42:27+00:00
Resolved: 2023-03-15 14:42:20+00:00

See the [logs posted here](https://bugzilla.mozilla.org/show_bug.cgi?id=1820900#c7); the failing assert and call stack are:

> [task 2023-03-09T04:07:42.455Z] 04:07:42     INFO - GECKO(6700) | #01: mozilla::UntrustedModulesData::AddNewLoads(mozilla::ModulesMap const&, mozilla::AutoCleanLinkedList<mozilla::ProcessedModuleLoadEventContainer>&&, mozilla::Vector<mozilla::Telemetry::ProcessedStack,0,mozilla::MallocAllocPolicy>&&) [toolkit/xre/dllservices/UntrustedModulesData.cpp:335]
[task 2023-03-09T04:07:42.470Z] 04:07:42     INFO - GECKO(6700) | #02: mozilla::UntrustedModulesProcessor::ProcessModuleLoadQueue() [toolkit/xre/dllservices/UntrustedModulesProcessor.cpp:715]
[task 2023-03-09T04:07:42.471Z] 04:07:42     INFO - GECKO(6700) | #03: mozilla::UntrustedModulesProcessor::BackgroundProcessModuleLoadQueue() [toolkit/xre/dllservices/UntrustedModulesProcessor.cpp:518]
[task 2023-03-09T04:07:42.471Z] 04:07:42     INFO - GECKO(6700) | #04: mozilla::detail::RunnableMethodImpl<mozilla::UntrustedModulesProcessor *,void (mozilla::UntrustedModulesProcessor::*)(),1,0>::Run() [xpcom/threads/nsThreadUtils.h:1219]
[task 2023-03-09T04:07:42.472Z] 04:07:42     INFO - GECKO(6700) | #05: mozilla::TaskQueue::Runner::Run() [xpcom/threads/TaskQueue.cpp:266]
[task 2023-03-09T04:07:42.472Z] 04:07:42     INFO - GECKO(6700) | #06: nsThreadPool::Run() [xpcom/threads/nsThreadPool.cpp:345]
[task 2023-03-09T04:07:42.473Z] 04:07:42     INFO - GECKO(6700) | #07: nsThread::ProcessNextEvent(bool, bool*) [xpcom/threads/nsThread.cpp:1234]
[task 2023-03-09T04:07:42.473Z] 04:07:42     INFO - GECKO(6700) | #08: NS_ProcessNextEvent(nsIThread*, bool) [xpcom/threads/nsThreadUtils.cpp:477]
[task 2023-03-09T04:07:42.474Z] 04:07:42     INFO - GECKO(6700) | #09: mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) [ipc/glue/MessagePump.cpp:301]
[task 2023-03-09T04:07:42.474Z] 04:07:42     INFO - GECKO(6700) | #10: MessageLoop::RunHandler() [ipc/chromium/src/base/message_loop.cc:375]
[task 2023-03-09T04:07:42.475Z] 04:07:42     INFO - GECKO(6700) | #11: MessageLoop::Run() [ipc/chromium/src/base/message_loop.cc:357]
[task 2023-03-09T04:07:42.475Z] 04:07:42     INFO - GECKO(6700) | #12: nsThread::ThreadFunc(void*) [xpcom/threads/nsThread.cpp:393]
[task 2023-03-09T04:07:42.643Z] 04:07:42     INFO - GECKO(6700) | #13: _PR_NativeRunThread(void*) [nsprpub/pr/src/threads/combined/pruthr.c:408]
[task 2023-03-09T04:07:42.654Z] 04:07:42     INFO - GECKO(6700) | #14: pr_root(void*) [nsprpub/pr/src/md/windows/w95thred.c:140]

The issue is that we assert that we don't have more than `kMaxEvents` entries in `mEvents`, but there are some places that we don't cap it to that.

This showed up intermittently while enabling debug MSIX tests, but it seems like we're just getting lucky most of the time and this could have happened before this.
Bug: "Open in Firefox" option is unavailable for application/xml files
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-03-10 22:03:02+00:00
Resolved: 2023-03-14 09:46:51+00:00

Steps to reproduce:
1. Go to <http://emk.name/test/bug1790641.html>.
2. Click the "Download" link in the "XML (application/xml)" row to download an XML file that is served with application/xml.
3. Open Download Manager.
4. Open the context menu on the downloaded file and choose "Always Open in Internet Explorer". (The "Internet Explorer" part may be different depending on your default apps setting.)
5. Go to Settings > General > Applications.
6. Click the Action column of "Extensible Markup Language (XML) (application/xml)" to open the dropdown menu.

Actual result:
"Open in Firefox" option is unavailable.

Expected result:
"Open in Firefox" option should be available.
Bug: Some shortcuts are not displayed in New Tab Page after resizing the browser window
Status: NEW
Priority: P3
Created: 2023-03-11 04:16:03+00:00
Resolved: 2023-06-06 21:59:29+00:00

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

Steps to reproduce:

I resized the window


Actual results:

When resizing the window, some of the shortcuts disappear


Expected results:

Nothing should have disappeared
Bug: Firefox starts completely frozen during desktop session restore on login
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-03-11 10:43:19+00:00
Resolved: 2024-01-19 17:22:30+00:00

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

Steps to reproduce:

My Kubuntu is configured to restore the desktop session after login. When Firefox was running when logging out, it will be started after the next login.


Actual results:

In this situation, Firefox starts (basically always, I think) to a completely frozen state, its window containing just a capture of the startup screen or desktop background or whatever else was in the framebuffer, when resized, the content is not repainted, etc. It cannot be closed, it can be only killed.

To add insult to injury, after I kill it and start manually again (it starts without a problem), the session is lost: it starts with a fresh session and the History/Restore previous session menu item is greyed out.

I have tried to capture a crash dump by sending Firefox a SIGSEGV (as I found on web) which worked, so I sent two crash reports for this situation: bp-44d520e2-6da6-4ab2-b632-1610e0230310 and bp-6408a60d-dceb-4304-9f80-8ae850230311.


Expected results:

Um… start normally?
Bug: Tab dragging: Firefox missed the mouse button release
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-03-11 10:45:40+00:00
Resolved: 2023-05-18 13:29:11+00:00

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

Steps to reproduce:

I dragged a tab to the tab bar of another window (in order to move the tab).


Actual results:

Everything happened as if I hadn't released the mouse button. I had to click (at the wanted position) to end the tab-dragging.


Expected results:

The mouse button release should have been taken into account.

Note: It seems that Firefox was taking CPU time, and AFAIK, this was the first time I had such an issue.
Bug: The Web viewer Save button will navigate instead of download when the file argument points at HTML content
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-03-11 21:17:40+00:00
Resolved: 2024-05-30 18:06:43+00:00

1- visit this link: https://mozilla.github.io/pdf.js/web/viewer.html?file=//www.google.com
2- click on the download button
3- you will find your self redirected to www.google.com

impact:
this redirection affect all pdf.js version which the attacker can use this to redirect the users to a malicious sites
Bug: Intermittent browser/components/urlbar/tests/engagementTelemetry/browser/browser_glean_telemetry_impression_interaction_persisted_search_terms_disabled.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2023-03-12 00:07:39+00:00
Resolved: 2024-02-07 12:03:03+00:00

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

---
```
[task 2023-03-11T23:05:54.435Z] 23:05:54     INFO - TEST-PASS | browser/components/urlbar/tests/engagementTelemetry/browser/browser_glean_telemetry_impression_interaction_persisted_search_terms_disabled.js | interaction is correct - "refined" == "refined" - 
[task 2023-03-11T23:05:54.436Z] 23:05:54     INFO - Leaving test bound persisted_search_terms_restarted_refined_via_abandonment
[task 2023-03-11T23:05:54.437Z] 23:05:54     INFO - Buffered messages finished
[task 2023-03-11T23:05:54.437Z] 23:05:54     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/engagementTelemetry/browser/browser_glean_telemetry_impression_interaction_persisted_search_terms_disabled.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - 
[task 2023-03-11T23:05:54.438Z] 23:05:54     INFO - GECKO(10020) | MEMORY STAT | vsize 2104419MB | vsizeMaxContiguous 68468200MB | residentFast 360MB | heapAllocated 135MB
[task 2023-03-11T23:05:54.438Z] 23:05:54     INFO - TEST-OK | browser/components/urlbar/tests/engagementTelemetry/browser/browser_glean_telemetry_impression_interaction_persisted_search_terms_disabled.js | took 76306ms
[task 2023-03-11T23:05:54.439Z] 23:05:54     INFO - checking window state
[task 2023-03-11T23:05:54.439Z] 23:05:54     INFO - TEST-START | browser/components/urlbar/tests/engagementTelemetry/browser/browser_glean_telemetry_impression_interaction_persisted_search_terms_enabled.js
```
Bug: My bank's PDF documents either don't load at all or they are incomplete
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-03-12 13:09:46+00:00
Resolved: 2023-05-27 15:17:50+00:00

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

Steps to reproduce:

Est-il possible de décrire un bug en français ?
Bug: Items exceeding pane width in about:preferences#privacy panel
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-03-12 17:47:00+00:00
Resolved: 2023-04-27 11:15:25+00:00

We are seeing content-blocking-etp-standard-tcp-title label is exceeding panel width in latest Firefox Nightly Slovak builds (v112) while this isn't the case for Beta builds (v111) (see attached screenshots Firefox111_content-blocking-etp-standard-tcp-title.png vs. Firefox112_content-blocking-etp-standard-tcp-title.png). The string itself hasn't changed recently, so this seems to be a regression from other changes to the panel.

There are even more strings exceeding the width, see Firefox112_privacy_panel_more_strings_affected.png. The affected labels are cookie-banner-handling-description (added very recently in Bug 1820560, a suspect maybe?), the other label is forms-windows-sso 

We are seeing this behaviour only in Privacy panel, the other Settings panels don't suffer from this.

FX112 build: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0, build 20230311212417

FX111 build: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0, build 20230309232128
Bug: BrowserUsageTelemetry should distinguish between bookmark items and history items
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2023-03-13 12:25:52+00:00
Resolved: 2023-03-28 17:28:02+00:00

I noticed while working on additional telemetry for the bookmarks library and sidebar (bug 1819081) that regardless of whether a history item or a bookmark item is clicked in the app menu or library navbar, it's being reported as 'bookmark-item' due to [this line of code](https://searchfox.org/mozilla-central/source/browser/modules/BrowserUsageTelemetry.jsm#700) and because both history items and bookmark items both contain the `.bookmark-items` class. 

I'm not sure if this was intentional with work done in bug 1620358, or something changed since that was implemented but we should probably distinguish between 'history items' and 'bookmark items'.

I haven't investigated all of the toolbar surfaces this telemetry covers to see if it applies to all surfaces, I only happened to notice the two surfaces previously mentioned while stepping through the debugger.