av9ash/GitBugs huggingface dataset:
Bug: forums.ubports.com - The main content does not get translated when using a preferred language, only some sections
Status: NEW
Priority: P3
Created: 2024-12-13 11:06:55+00:00
Resolved: 2024-12-13 11:40:46+00:00

From github: https://github.com/webcompat/web-bugs/issues/145110.

> <!-- @browser: Firefox 135.0 -->
> <!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:135.0) Gecko/20100101 Firefox/135.0 -->
> <!-- @reported_with: desktop-reporter -->
> <!-- @public_url: https://github.com/webcompat/web-bugs/issues/145110 -->
> 
> **URL**: https://forums.ubports.com/
> 
> **Browser / Version**: Firefox 135.0
> **Operating System**: Windows 10
> **Tested Another Browser**: Yes Chrome
> 
> **Problem type**: Something else
> **Description**: Mir wird auf der Webseite keine Automatische üubersetzung Angezeit.  in was ich es Übersetz haben möchte !!
> **Steps to Reproduce**:
> Mir wird auf der Webseite keine Automatische ubersetzung Angezeit. 
> in was ich es übersetz haben möchte !!
> <details>
>       <summary>View the screenshot</summary>
>       <img alt="Screenshot" src="https://webcompat.com/uploads/2024/12/1c633b55-8ac2-442b-b5ab-c0698ab7d382.jpeg">
>       </details>
> 
> <details>
> <summary>Browser Configuration</summary>
> <ul>
>   <li>gfx.webrender.software: false</li><li>blockList: basic</li><li>channel: nightly</li><li>defaultUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:135.0) Gecko/20100101 Firefox/135.0</li><li>hasTouchScreen: false</li><li>frameworks: {'fastclick': False, 'mobify': False, 'marfeel': False}</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li><li>btp has purged site: false</li>
> </ul>
> </details>
> 
> [View console log messages](https://webcompat.com/console_logs/2024/12/d1869368-77d6-495d-8a89-fd103d7af6ee)
> 
> _From [webcompat.com](https://webcompat.com/) with ❤️_

Change performed by the [Move to Bugzilla add-on](https://addons.mozilla.org/en-US/firefox/addon/move-to-bugzilla/).
Bug: Unremovable flexible space in Nightly 135.0a1 (2024-12-12) (64-bit)
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2024-12-13 11:53:32+00:00
Resolved: 2025-02-21 12:22:47+00:00

Since the update to nightly 135, There has been an addition to the toolbar of a un-removable flexible space
Bug: Sometimes after exiting Firefox, background processes will remain, causing the second startup to be very slow
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-12-13 12:10:39+00:00
Resolved: 2025-01-02 03:21:46+00:00

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

Steps to reproduce:

1. Set Firefox to clear history when Firefox is closed.
2. When you close Firefox, the Windows Task Manager background process will have a residual Firefox process, and each time you close it, a residual process will be added.
3. When you start Firefox, it takes about five seconds to open. If you terminate all the remaining background processes, it will open immediately.


Actual results:

If there are Firefox processes left in the background, each startup will take a long time


Expected results:

There should be no residual processes in the background, which causes Firefox to start slowly
Bug: 2.48% bing-search SpeedIndex (Linux) regression on Thu December 5 2024
Status: RESOLVED
Priority: P2
Resolution: WONTFIX
Created: 2024-12-13 12:44:18+00:00
Resolved: 2025-01-24 09:45:02+00:00

Perfherder has detected a browsertime performance regression from push [5c927e89451bcf64289953bc6e478bfe3197cb3a](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=5c927e89451bcf64289953bc6e478bfe3197cb3a). As author of one of the patches included in that push, we need your help to address this regression.

### Regressions:

| **Ratio** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)** |  **Performance Profiles** | 
|--|--|--|--|--|--| 
| [2%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4405557,1,13)  | [bing-search](https://firefox-source-docs.mozilla.org/testing/perfdocs/raptor.html#bing-search-d) SpeedIndex | linux1804-64-shippable-qr | bytecode-cached cold fission webrender | [630.44](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/DmRlVENLRxi60tuk58SQSw/runs/0/artifacts/public/test_info/browsertime-results.tgz) -> [646.06](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/EvyJnl8uTZie7cBSk-ssTQ/runs/0/artifacts/public/test_info/browsertime-results.tgz) | [Before](https://profiler.firefox.com/from-url/https%3A%2F%2Ffirefox-ci-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2FDmRlVENLRxi60tuk58SQSw%2Fruns%2F0%2Fartifacts%2Fpublic%2Ftest_info%2Fprofile_bing-search.zip)/[After](https://profiler.firefox.com/from-url/https%3A%2F%2Ffirefox-ci-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2FEvyJnl8uTZie7cBSk-ssTQ%2Fruns%2F0%2Fartifacts%2Fpublic%2Ftest_info%2Fprofile_bing-search.zip) |


Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=43009), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the patch(es) may be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/).

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

You can run all of these tests on try with `./mach try perf --alert 43009`

The following [documentation link](https://firefox-source-docs.mozilla.org/testing/perfdocs/mach-try-perf.html#running-alert-tests) provides more information about this command.

For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).

If you have any questions, please do not hesitate to reach out to afinder@mozilla.com.
Bug: Unified Search Button shows icon of normal default engine instead of private default engine in private browsing mode
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-12-13 13:37:33+00:00
Resolved: 2024-12-20 13:28:59+00:00

**STR**

1: Set the following pref to true:
`browser.search.separatePrivateDefault.ui.enabled`

2: Set a default private search engine in `about:settings#search`

3: Open a private window and click the addressbar

Expected: USB shows icon of the default private engine
Actual: USB shows icon of normal default engine
Bug: Private default search engine set by enterprise policy is lost after restoring the default search engines
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-12-13 14:05:59+00:00
Resolved: 2024-12-21 09:45:23+00:00

This bug is similar to 1797965 but with the private default.

**Preconditions**
Add the following code inside the policies.json file:

```
policies: {
  SearchEngines: {
    DefaultPrivate: "Bing",
  },
}
```
Set the following pref:
`browser.search.separatePrivateDefault.ui.enabled`


After resetting to the default engine, `Services.search.defaultPrivateEngine` does not return the correct engine.
Bug: about:logins opens in Sign-In popup window instead of main Firefox window
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2024-12-13 14:08:48+00:00
Resolved: 2025-01-28 08:41:12+00:00

**Found in**
* Nightly 135.0a1

**Affected versions**
* Nightly 135.0a1
* Firefox 134.0b9
* Firefox 133.0.3
* Firefox 128.5.2esr

**Tested platforms**
* Affected platforms: macOS 15, Windows 10 and Ubuntu 24.04

**Preconditions**
* Launch Firefox on a new profile.

**Steps to reproduce**
1. Navigate to a website that allows Sign up with Google, e.g., x.com.
2. Click on the Sign up with Google button.
3. In the newly opened Sign in with Google window, click in the email input field.
4. Click on Manage Passwords from the dropdown.

**Expected result**
* The about:logins page should open in a new tab in the main Firefox window.

**Actual result**
* The about:logins page opens in a new tab within the Sign in with Google popup window instead of the main Firefox window.

**Regression range**
* This issue is not reproducible on Firefox 115.18.0esr, where about:logins opens in a new tab in the main Firefox window.
* I narrowed a regression window using Mozregression tool but couldn't pinpoint the exact bug as it appears to be an older regression.
* Last good revision: 2c44d59dd29eb01ea0b484c9f3f8691861118073 (2023-10-31)
* First bad revision: b73ef4c8979fb0702de9f4bf2fdf986b1d0fd487 (2023-11-01)
* Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2c44d59dd29eb01ea0b484c9f3f8691861118073&tochange=b73ef4c8979fb0702de9f4bf2fdf986b1d0fd487
Bug: [Rollout] The string “Terms of use” is displayed instead the “Privacy Notice” string on the second screen of the Microsurvey
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-12-13 15:16:57+00:00
Resolved: 2024-12-17 08:14:36+00:00

**[Affected versions]:**
- Firefox build version: Firefox Release 133.0.3, en-US locale, Build ID: 20241209150345

**[Affected Platforms]:**
- Windows 10 x64;
- macOS 14.5
- Linux Mint 21.1

**[Prerequisites]:**
- Have a new profile created and opened.
- Have this [user.js](https://drive.google.com/file/d/1AWAFKZOnBf9Q3j-Xdm7-k2ReI595MP-J/view?usp=sharing) file saved on the computer.
- Have this [ExperimentStoreData.json](https://drive.google.com/file/d/1OFytdntmoZyqqkmS2rkfqFoZRVsm-f2s/view?usp=sharing) file saved on the computer.

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to the “about:support” page and open the Profile Folder.
3. Paste the “user.js” and “ExperimentStoreData.json” file into the Profile Folder.
4. Restart the browser two times (Cmd/Ctrl+Shift+J, Cmd/Ctrl+Option/Alt +R).
5. Open a New Tab page.
6. Choose any option on the first screen of the Microsurvey and Click the “Next” button.
7. Observe the string of the hyperlink from the second screen of the Microsurvey.


**[Expected result]:**
- The "Privacy Notice” string is displayed as a hyperlink according to the [documentation](https://docs.google.com/document/d/1JKoA2gAYociZPdx5kkdUO0Rm_wZQy-sGNgss-YKfPnM/edit?tab=t.0).

**[Actual result]:**
- The “Terms of use” is displayed instead of the “Privacy Notice” on the second screen of the Microsurvey.

**[Additional Notes]:**
- This issue is reproducible on all three rollouts.
- This issue is not reproducible for the first screen of the Microsurvey.
- A screenshot of the issue is attached.
Bug: Http Exceptionality preferences should be enabled by scotchbonnet pref
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2024-12-13 16:10:55+00:00
Resolved: 2025-02-24 10:50:05+00:00

**Found in**
* Nightly 134.0b9;

**Affected versions**
* 134.0b9
* most likely 135.0b as well


**Tested platforms**
* Affected platforms: Windows 11, Mac 13, Ubuntu 24

**Steps to reproduce**
 1. Open 134 beta version (nightly135 has different default preferences for this area, but we're assuming these preferences should be controlled by *browser.urlbar.scotchBonnet.enableOverride*)
 2. Navigate to about:config, flip *browser.urlbar.scotchBonnet.enableOverride* to true, restarting the browser. 
 3. Navigate to about:config and check values for the following preferences:
- browser.urlbar.trimURLs
- browser.urlbar.trimHttps 
- browser.urlbar.untrimOnUserInteraction.featureGate
- dom.security.https_first_schemeless
- Dom.security.https_first 
- security.insecure_connection_text.enabled


**Expected result**
- browser.urlbar.trimURLs true
- browser.urlbar.trimHttps true
- browser.urlbar.untrimOnUserInteraction.featureGate true
- dom.security.https_first_schemeless true
- Dom.security.https_first false
- security.insecure_connection_text.enabled true

**Actual result**
- browser.urlbar.trimURLs
- *browser.urlbar.trimHttps false*
- **browser.urlbar.untrimOnUserInteraction.featureGate false**
- dom.security.https_first_schemeless true
- Dom.security.https_first false
- **security.insecure_connection_text.enabled false**

**Regression range**
* N/A
Bug: Removed sidebar-button reappears on browser restart
Status: RESOLVED
Priority: P2
Resolution: WORKSFORME
Created: 2024-12-13 19:34:04+00:00
Resolved: 2025-01-07 18:07:45+00:00

STR:

1. Set `sidebar-revamp` to true.
2. Remove the `sidebar-button` from the nav bar in Customize Mode.
3. Set `sidebar-revamp` to false.
4. Set `sidebar-revamp` to true.

Expected: 
The sidebar button should no longer be in the nav bar

Actual:
The sidebar button has been added back to the nav bar.

The button is added back in here: https://searchfox.org/mozilla-central/rev/d8f4a94563b0a28c485f0dbfaf56b92434242d1e/browser/components/customizableui/CustomizableUI.sys.mjs#221-227

We should rethink how we want to handle if a user has actually removed the button themselves versus a user switching on `sidebar.revamp` for the first time.
Bug: Tab group panel should close when expanding/collapsing a group
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2024-12-13 20:09:09+00:00
Resolved: 2025-03-05 04:56:01+00:00

**Steps to reproduce [can add screenshots or video recordings for reference]:**

1. Open the "Create tab group panel"
2. Click on the tab group label in the tab strip

**Expected behavior [What should have happened?]:**

Tab group collapses and create tab group panel closes

**Actual behavior [What actually happened?]:**

Tab group collapses and create tab group panel remains opened

Same behavior is seen when you open the "Manage tab group" panel and collapse the group (the group collapses but the panel remains opened)
Bug: tab play/mute audio button hard to see, same color as tab background
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-12-13 21:53:06+00:00
Resolved: 2024-12-16 21:58:44+00:00

Firefox 135.0a1 20241213094257 on Windows 10

The button on the tab to play or mute its audio is difficult to spot here because both the button and the background are grey.
Bug: Sidebar no longer saves the last used location when firefox is closed.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-12-13 22:50:44+00:00
Resolved: 2024-12-17 00:09:24+00:00

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

Steps to reproduce:

I use history sometimes to find a website i visited. I usually have sidebar set at the beginning of my bookmark bar for easy access to that history. Because I would close sidebar with history open it would return to history later when reloading firefox. Now it always reverts back to bookmarks and I have to click sidebar, then bookmarks, then click on history but before I just needed to click on sidebar. I went back to version 126 and it worked as I remember but somewhere between ver 126 and 129 it changed.
Bug: can not see page title when too many tab
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2024-12-14 02:57:58+00:00
Resolved: 2025-01-27 14:11:01+00:00

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

Steps to reproduce:

this change come from https://bugzilla.mozilla.org/show_bug.cgi?id=1921060
may be this is you intention. but may be you miss this case

step to reproduce
1. open too many tabs (press ctrl + t until tab size is smallest)
2. search some video
3. right click  open in new tabs 



Actual results:

youtube tab in background has favicon, and mute button. no more space for page title


Expected results:

it should has a little bit space for page title. if this is you design feel free to close this.


workaround for this issue:
set `browser.tabs.tabMinWidth` to 100
Bug: Regression: NTP Search Bar flickers/jumps when scrolling
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2024-12-14 10:36:49+00:00
Resolved: 2025-01-27 15:26:30+00:00

Nightly 135.0a1 (2024-12-13) (aarch64)
macOS 15.2

1.) Open the New Tab Page
2.) Start to scroll slowly

Actual: Search bar flickers jumps during scrolling.

Expected: No Search bar flicker or jumping.

A video of the issue is attached.

Thanks for checking.
Bug: The close tab icon (⨯) shifts when pointed to for a narrow muted tab
Status: NEW
Priority: --
Created: 2024-12-14 10:54:04+00:00
Resolved: 2024-12-30 12:20:05+00:00

Steps to reproduce:
1) In a new new profile create a window with lots of tabs.
2) Mute a tab.
3) Put the pointer below the close tab symbol ⨯.
4) Move the pointer up.

Expected:
4) The ⨯ stays in the same place.

Actual:
4) The ⨯ shifts right.

Version 	135.0a1
Build ID 	20241213161049
ASan Nightly on Ubuntu 24.04.1 LTS using XFCE.
Bug: Perma [tier 2] browser/components/urlbar/tests/browser/browser_searchModeSwitcher_appProvidedEngines.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2024-12-14 13:58:57+00:00
Resolved: 2024-12-23 06:57:07+00:00

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

---
```
[task 2024-12-14T13:39:18.243Z] 13:39:18     INFO - TEST-START | browser/components/urlbar/tests/browser/browser_searchModeSwitcher_appProvidedEngines.js
[task 2024-12-14T13:39:18.260Z] 13:39:18     INFO - TEST-INFO | started process screencapture
[task 2024-12-14T13:39:18.374Z] 13:39:18     INFO - TEST-INFO | screencapture: exit 0
[task 2024-12-14T13:39:18.374Z] 13:39:18     INFO - Buffered messages logged at 13:39:18
[task 2024-12-14T13:39:18.374Z] 13:39:18     INFO - Entering setup bound setup
[task 2024-12-14T13:39:18.374Z] 13:39:18     INFO - Leaving setup bound setup
[task 2024-12-14T13:39:18.374Z] 13:39:18     INFO - Entering test bound test_search_mode_app_provided_engines
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - Install Search Engines related to Persisted Search Tests
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - Example
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - Buffered messages finished
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_searchModeSwitcher_appProvidedEngines.js | false == true - 
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - Stack trace:
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - resource://testing-common/UrlbarTestUtils.sys.mjs:openSearchModeSwitcher:1386
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - chrome://mochitests/content/browser/browser/components/urlbar/tests/browser/browser_searchModeSwitcher_appProvidedEngines.js:test_search_mode_app_provided_engines:19
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - chrome://mochikit/content/browser-test.js:handleTask:1147
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - chrome://mochikit/content/browser-test.js:_runTaskBasedTest:1219
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1360
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - chrome://mochikit/content/browser-test.js:nextTest/<:1136
[task 2024-12-14T13:39:18.375Z] 13:39:18     INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/<:1058
[task 2024-12-14T13:39:18.714Z] 13:39:18     INFO - Press on the example menu button and enter search mode
[task 2024-12-14T13:39:18.718Z] 13:39:18     INFO - Search mode has been changed
[task 2024-12-14T13:39:18.719Z] 13:39:18     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_searchModeSwitcher_appProvidedEngines.js | Urlbar should never be in search mode without the corresponding attribute. - true == true - 
```
Bug: Intermittent browser/components/places/tests/browser/browser_library_bulk_tag_bookmarks.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-12-14 16:32:05+00:00
Resolved: 2025-01-08 12:06:25+00:00

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

---
```
[task 2024-12-14T15:32:14.534Z] 15:32:14     INFO - TEST-PASS | browser/components/places/tests/browser/browser_library_bulk_tag_bookmarks.js | Current view is shown - true == true - 
[task 2024-12-14T15:32:14.535Z] 15:32:14     INFO - Buffered messages finished
[task 2024-12-14T15:32:14.536Z] 15:32:14     INFO - TEST-UNEXPECTED-FAIL | browser/components/places/tests/browser/browser_library_bulk_tag_bookmarks.js | Test timed out - 
[task 2024-12-14T15:32:14.536Z] 15:32:14     INFO - GECKO(3416) | Completed ShutdownLeaks collections in process 9748
[task 2024-12-14T15:32:14.536Z] 15:32:14     INFO - TEST-START | Shutdown
```
Bug: Touch support on version 115
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-12-14 17:30:02+00:00
Resolved: 2024-12-19 19:35:46+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36

Steps to reproduce:

Open Firefox v115.18 esr on a Tablet PC in full screen mode.  The Exit button in the top right does not work when you touch it.  It works fine with mouse only. I suspect testing Firefox in tablet PC mode may be lacking because its a very obvious bug. I also noticed tablet PC full screen mode on newer Firefox versions have the same problem.


Actual results:

Firefox does not exit. Reproduced on Windows 8 and 10 in Tablet PC mode.


Expected results:

Firefox should register the touch event properly when pressing the Exit button.
Bug: I always receve canonical message whit several website.it is very incomodient
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-12-14 17:49:03+00:00
Resolved: 2024-12-14 18:50:09+00:00

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

Steps to reproduce:

When I connect to certain websites, I have my Internet Download Manager constantly loading error pages.urs 


Actual results:

I have to reboot my PC 


Expected results:

Mozilla Firefox
Bug: "Cookies and Site Data" in about:preferences#privacy don't show directly real count.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-12-14 18:33:57+00:00
Resolved: 2025-02-20 17:13:52+00:00

Steps to reproduce:

Hello!
I see this problem since years, but today I still see it, in FF ESR 128.5 and FF Snap 133.0 (under Lubuntu 22.04).

1/ Have not all cookies blocked in settings.
2/ Clear all cookies so about:preferences#privacy > History >  [Clear History]  > Cookies and site data" says "0 bytes" .
3/ Do some navigation on sites that install cookies or "site data".
4/ Come back in
  about:preferences#privacy > Cookies and Site Data > [Clear Data...]
  or
  about:preferences#privacy > History >  [Clear History].
  You should see that both say to "Cookies and site data" line: "0 bytes" (while they shouldn't) .
5/ Reload the page.
6/ Go back in same place.
  "Cookies and site data" line should then show content.


Actual results:

Was described in "Steps to reproduce".
The problem with this can be that when at first the user sees the wrong "0 data", he may think it's odd, but finally cancel this operation. Then he will leave the data he wanted to erase, which can go against the privacy/security (or else) he wanted. But I don't have the impression that it is though a real big "security" issue.

I made also a small test that showed that clicking on [Clear] even if the displaying is false clears data.
Simply by:
1/ Ensuring I have some "data and cookies" with some browsing.
2/ Checking that "Cookies and site data" (wrongly) shows 0 of them.
3/ [Clear].
4/ Reload the page.
  "Cookies and site data" (rightly this time) shows 0 of them.

So they have been clear even if they weren't displayed.



Expected results:

I guess these lines should show the actual cookies/data amount when asked, without need to reload the page.