av9ash/GitBugs huggingface dataset:
Bug: Intermittent TV browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_multistage_mr.js | Test timed out -
Status: NEW
Priority: P5
Created: 2023-11-28 04:29:32+00:00
Resolved: 2023-12-19 14:45:21+00:00

**Filed by:** csabou [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=437911586&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Y1aElNM4SbmNrDX2lmvwbw/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/Y1aElNM4SbmNrDX2lmvwbw/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2023-11-28T02:59:44.601Z] 02:59:44     INFO - TEST-PASS | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_multistage_mr.js | "page-selection" == "page-selection" - 
[task 2023-11-28T02:59:44.601Z] 02:59:44     INFO - Buffered messages logged at 02:58:05
[task 2023-11-28T02:59:44.601Z] 02:59:44     INFO - Leaving test bound test_aboutwelcome_embedded_migration
[task 2023-11-28T02:59:44.601Z] 02:59:44     INFO - Entering test bound test_aboutwelcome_multiselect
[task 2023-11-28T02:59:44.601Z] 02:59:44     INFO - Buffered messages finished
[task 2023-11-28T02:59:44.601Z] 02:59:44     INFO - TEST-UNEXPECTED-FAIL | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_multistage_mr.js | Test timed out - 
[task 2023-11-28T02:59:44.648Z] 02:59:44     INFO - GECKO(7069) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2023-11-28T02:59:44.649Z] 02:59:44     INFO - GECKO(7069) | MEMORY STAT heapAllocated not supported in this build configuration.
[task 2023-11-28T02:59:44.650Z] 02:59:44     INFO - GECKO(7069) | MEMORY STAT | vsize 130552136MB | residentFast 1317MB
[task 2023-11-28T02:59:44.658Z] 02:59:44     INFO - TEST-OK | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_multistage_mr.js | took 120498ms
[task 2023-11-28T02:59:44.660Z] 02:59:44     INFO - Not taking screenshot here: see the one that was previously logged
[task 2023-11-28T02:59:44.663Z] 02:59:44     INFO - TEST-UNEXPECTED-FAIL | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_multistage_mr.js | Found a tab after previous test timed out: about:welcome - 
[task 2023-11-28T02:59:44.849Z] 02:59:44     INFO - checking window state
[task 2023-11-28T02:59:48.110Z] 02:59:48     INFO - GECKO(7069) | Completed ShutdownLeaks collections in process 7174
[task 2023-11-28T02:59:48.122Z] 02:59:48     INFO - GECKO(7069) | Completed ShutdownLeaks collections in process 7215
[task 2023-11-28T02:59:48.133Z] 02:59:48     INFO - GECKO(7069) | Completed ShutdownLeaks collections in process 7347
[task 2023-11-28T02:59:48.327Z] 02:59:48     INFO - GECKO(7069) | Completed ShutdownLeaks collections in process 7145
[task 2023-11-28T02:59:49.466Z] 02:59:49     INFO - GECKO(7069) | Completed ShutdownLeaks collections in process 7069
[task 2023-11-28T02:59:49.468Z] 02:59:49     INFO - TEST-START | Shutdown
```
Bug: Intermittent TV browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_configurable_ui.js | Uncaught exception in test bound test_aboutwelcome_with_noodles - Should render main.TEST_NOODLE_STEP[pos='center'] in renders screen with noodles
Status: NEW
Priority: P5
Created: 2023-11-28 04:31:22+00:00
Resolved: 2023-12-19 14:45:17+00:00

**Filed by:** csabou [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=437912133&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Pshw7pdlTOuqqZB_bfV4AQ/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/Pshw7pdlTOuqqZB_bfV4AQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2023-11-28T03:03:08.520Z] 03:03:08     INFO - TEST-OK | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_configurable_ui.js | took 34530ms
[task 2023-11-28T03:03:08.577Z] 03:03:08     INFO - checking window state
[task 2023-11-28T03:03:08.809Z] 03:03:08     INFO - TEST-START | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_configurable_ui.js
[task 2023-11-28T03:03:18.892Z] 03:03:18     INFO - TEST-INFO | started process screencapture
[task 2023-11-28T03:03:19.009Z] 03:03:19     INFO - TEST-INFO | screencapture: exit 0
[task 2023-11-28T03:03:19.009Z] 03:03:19     INFO - Buffered messages logged at 03:03:08
[task 2023-11-28T03:03:19.010Z] 03:03:19     INFO - Entering test bound test_aboutwelcome_with_noodles
[task 2023-11-28T03:03:19.010Z] 03:03:19     INFO - Buffered messages finished
[task 2023-11-28T03:03:19.011Z] 03:03:19     INFO - TEST-UNEXPECTED-FAIL | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_configurable_ui.js | Uncaught exception in test bound test_aboutwelcome_with_noodles - Should render main.TEST_NOODLE_STEP[pos='center'] in renders screen with noodles - timed out after 50 tries.
[task 2023-11-28T03:03:19.011Z] 03:03:19     INFO - Leaving test bound test_aboutwelcome_with_noodles
[task 2023-11-28T03:03:19.012Z] 03:03:19     INFO - Entering test bound test_aboutwelcome_with_customized_logo
[task 2023-11-28T03:03:20.165Z] 03:03:20     INFO - TEST-PASS | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_configurable_ui.js |
```
Bug: Bookmark panel has Tree element editBMPanel_folderTree that is not labeled
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2023-11-28 14:48:15+00:00
Resolved: 2023-12-02 09:38:28+00:00

The Bookmark overlay panel includes a tree view for the [editBMPanel_folderTree](https://searchfox.org/mozilla-central/source/browser/components/places/content/bookmarksSidebar.xhtml#59-69) which is programmatically not labeled. 

Reference: [ARIA Design pattern for Tree view](www.w3.org/WAI/ARIA/apg/patterns/treeview/#wai-ariaroles,states,andproperties)
Bug: The Adjusted ratings card is displayed for unknown products
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-11-28 15:11:18+00:00
Resolved: 2023-12-05 17:13:48+00:00

**Found in**
* Nightly 122.0a1 (2023-11-27)

**Affected versions**
* Nightly 122.0a1 (2023-11-27)

**Affected platforms**
* ALL

**Preconditions:**
browser.shopping.experience2023.enabled - true
browser.shopping.experience2023.optedIn = 0

**Steps to reproduce**
1. Reach https://www.amazon.de/Amazon-brand-Movian-computer-drawers/product-reviews/B07GFRCZWY/ref=cm_cr_arp_d_paging_btm_next_2?ie=UTF8&reviewerType=all_reviews&pageNumber=2

**Expected result**
*  We should not get a product_id for unknown products : https://searchfox.org/mozilla-central/rev/9bc264fbc5d6e618d8f3b9677a8f5e8550b94dbc/browser/components/shopping/content/shopping-container.mjs#217,224-225

**Actual result**
* The Product page showed an unanalyzed card, after which the Not enough reviews message was displayed and finally after refresh the Adjusted card is displayed with 0 stars.

**Regression range**
Not Applicable

This is a new Feature that brings Shopping support to amazon.fr and amazon.de.
Bug: Firefox doesn't follow symlinks when checking for default browser
Status: RESOLVED
Priority: P3
Resolution: INCOMPLETE
Created: 2023-11-28 15:41:51+00:00
Resolved: 2024-02-07 20:57:41+00:00

Steps to reproduce:

- Start on Debian bookworm with Firefox installed systemwide and `x-www-browser` set to `/usr/bin/firefox` using `update-alternatives`
- Create `x-www-browser.desktop` in `/usr/share/applications/` containing the following
```
[Desktop Entry]
Type=Application
Name=Preferred Browser
TryExec=/usr/bin/x-www-browser
Exec=x-www-browser %U
Terminal=false
StartupNotify=true
NoDisplay=true
MimeType=text/html;text/xml;application/xml;application/xhtml+xml;application/xhtml_xml;x-scheme-handler/http;x-scheme-handler/https
```
- `xdg-settings set default-web-browser x-www-browser.desktop`
- Now, start Firefox and look in Settings to see if it thinks it's the default browser


Actual results:

Firefox says it isn't the default browser


Expected results:

Firefox is the default browser.  It thinks it isn't because `/usr/bin/x-www-browser` is not `/usr/bin/firefox`.  But `/usr/bin/x-www-browser` is a symlink to `/etc/alternatives/x-www-browser` which is a symlink to `/usr/bin/firefox`.

When working out what the current default browser is, Firefox should follow symlinks (probably in `nsGNOMEShellService::KeyMatchesAppName()` in `browser/components/shell/nsGNOMEShellService.cpp`).  For this case to work it would have to follow multiple levels of symlinks.
Bug: New tab opened by reset PBM feature uses `BROWSER_NEW_TAB_URL` which may be overwritten by extensions
Status: NEW
Priority: P3
Created: 2023-11-28 16:10:01+00:00
Resolved: 2023-11-28 16:10:01+00:00

The reset PBM feature opens a new tab before clearing data. This works fine assuming the new tab page doesn't set any state. However, it's possible for extensions to overwrite this URL. In this case the newly added tab could carry over state into the next PBM session.
Bug: Consider ensuring the disabled Send button on the new webcompat reporter does not change on hover or click
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-11-28 17:22:24+00:00
Resolved: 2023-12-06 09:43:04+00:00

**Found in**
* Beta v121.0b1

**Affected versions**
* Nightly v121.0a1
* Beta v121.0b1

**Tested platforms**
* Affected platforms: Windows 10, MacOS 11, Ubuntu 22
* Unaffected platforms: -

**Steps to reproduce**
1. Make sure new webcopmpat feature is enabled:
ui.new-webcompat-reporter.enabled  = true
2. Set up the mandatory drop-down:
ui.new-webcompat-reporter.reason-dropdown = 2
3. Load any webpage
4. Open the new webcompat reporter tool
5. Send the report without choosing a reason from the drop-down.
**Expected result**
* Upon clicking the disabled "Send" button, a message should be displayed stating why it can't be sent.
**Actual result**
* Upon clicking the disabled "Send" button, nothing happens. The user is confused.
6. Choose a reason from the drop-down. (the "Send" button enables)
7. Insert a space character anywhere inside the domain portion of the URL. (the Send button is disabled)
8. Hover over the `Send` button and observe the styling change for `:hover` state
9. Click and hold the disabled `Send` button and observe the styling change for `:active` state
**Expected result**
* There are no visual changes of the disabled `Send` button on hover or click
**Actual result**
* There are some visual changes of the disabled `Send` button on hover or click that appears to be partially transparent styles that are used for active buttons

**Additional information**
* Ensuring there are no visual changes would help users with cognitive difficulties to confirm that the button is, in fact, disabled and something in the form above needs to be fixed, while the bug 1866291 being worked on
Bug: Session Restore shouldn't save redundant copies of the same data URI for a favicon over and over, if you have hundreds of tabs that share the same favicon
Status: NEW
Priority: P3
Created: 2023-11-28 21:42:23+00:00
Resolved: 2024-01-29 13:20:02+00:00

I've been investigating some session-restore-serialization hangs that happen periodically (noticeably janking the Firefox parent process), and I'm filing this bug for the first issue that I noticed there that's causing this serialization to be heavier than it should be.

If you've got e.g. hundreds of tabs from the same site open (bugzilla in my case), then Session Store appears to save a distinct copy of the base64-encoded favicon for each tab.  For [bugzilla.mozilla.org's 128x128 PNG favicon](https://bugzilla.mozilla.org/extensions/BMO/web/images/favicon.ico), that data URI is `186969` characters long, i.e. nearly 200KB i.e. 0.2MB.  So: if you have 200 bugzilla tabs open, then that represents 200 * 0.2MB = 40MB of json that Firefox needs to re-serialize as part of your session state.  That's quite a lot.

I recognize this isn't trivial, but: in the interests of making session-store reserialization a "lightweight" operation (since it janks the frontend process), could we somehow de-duplicate these data URIs and only serialize them once when we're generating JSON?
Bug: Session restore causes noticeable jank and memory spike every 15 seconds, if you've got hundreds of tabs open
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-11-28 23:31:27+00:00
Resolved: 2023-12-04 03:03:28+00:00

STR:
1. Open a single Firefox window with 500 Bugzilla tabs. (See [1] for a quick way to do that.)  Some of these may result in `429 Too Many Requests`; that's fine and doesn't impact the reproducibility of this bug. (Hopefully this doesn't annoy BMO admins too much. :) )
2. Start profiling with the Firefox profiler (https://profiler.firefox.com/ )
3. Perform some interactive/smooth task for 30+ seconds -- e.g.:
- watch [a video on Twitter/X](https://twitter.com/CalIMeDon/status/1729230725608853819) or [a video on YouTube](https://www.youtube.com/watch?v=1295Eet15ps)
- or just visit https://paste.mozilla.org/ and hold down the `a` character on your keyboard to watch the character repeat at a predictable rate
4. Watch for periods where Firefox seems to briefly freeze. Capture the profile after a minute or so.

ACTUAL RESULTS:
Every 15 seconds, Firefox freezes for a half-second or so.
The profile shows that these are ~500ms calls to `write` in `resource:///modules/sessionstore/SessionWriter.sys.mjs`.
The profile's memory track also shows memory usage **persistently increasing by 225MB** with each call;  some of the memory is freed, but not all.  So e.g. after 1 minute, the memory usage has gone up by 900MB.

EXPECTED RESULTS:
No such jank at such a frequent interval, especially not while I'm actively using the browser (typing or watching a video).  Particularly when I'm watching a video and haven't done any sessionstore-impacting operations (no new form state, tabs, etc), it's not obvious why sessionstore is jumping in every 15s.
When sessionstore does jump in, it ideally shouldn't have such a persistent memory-usage increase. These lead to enormous GCs after a while, I think (I'm pretty sure this is what bit me in bug 1866145, for example).

[1] Here's one way to get a window with 500 Bugzilla tabs:
a) In a fresh Firefox profile, visit `about:preferences`, click "Home" on the left, and then click the dropdown for "Homepage and new windows" and choose "Custom URLs"
b) Paste the contents of the attached textfile into the textbox that appears.
c) Ctrl+N to open a new window.
d) Back in your `about:preferences` tab, return from "Custom URLs" to "Firefox Home (Default)" (so that you don't inadvertently create any more hundred-tab windows)
e) (optional) close your initial about:preferences window, and now just use the window that you opened in (c), which has 500 Bugzilla tabs.
Bug: Kopier funktion verbuggt
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-11-29 04:51:11+00:00
Resolved: 2024-02-12 15:07:07+00:00

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

Steps to reproduce:

Wenn mehrere Tabs im Mozilla Firefox geöffnet sind und auf einer Webseite die Maus zum Markieren von Text verwendet wird, tritt ein Problem mit der Kopierfunktion auf. Das Kontextmenü zum Kopieren wird grau und ist nicht aktiv, obwohl der Text erfolgreich markiert wurde. Dieses Verhalten tritt auf, wenn zwischen den Tabs gewechselt wird.


Actual results:

Wenn mehrere Tabs im Mozilla Firefox geöffnet sind und auf einer Webseite die Maus zum Markieren von Text verwendet wird, tritt ein Problem mit der Kopierfunktion auf. Das Kontextmenü zum Kopieren wird grau und ist nicht aktiv, obwohl der Text erfolgreich markiert wurde. Dieses Verhalten tritt auf, wenn zwischen den Tabs gewechselt wird.


Expected results:

Wörter Kopieren
Bug: Kopier funktion verbuggt
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-11-29 04:54:23+00:00
Resolved: 2023-11-29 07:39:16+00:00

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

Steps to reproduce:

Wenn mehrere Tabs im Mozilla Firefox geöffnet sind und auf einer Webseite die Maus zum Markieren von Text verwendet wird, tritt ein Problem mit der Kopierfunktion auf. Das Kontextmenü zum Kopieren wird grau und ist nicht aktiv, obwohl der Text erfolgreich markiert wurde. Dieses Verhalten tritt auf, wenn zwischen den Tabs gewechselt wird.


Actual results:

Öffnen Sie mehrere Tabs im Mozilla Firefox.
Navigieren Sie zu einer Webseite in einem der Tabs.
Versuchen Sie, Text auf der Webseite zu markieren.
Beachten Sie, dass das Kontextmenü zum Kopieren grau ist und nicht auswählbar ist.
Wechseln Sie zu einem anderen Tab und kehren Sie dann zum ursprünglichen Tab zurück.
Versuchen Sie es erneut, Text zu markieren und zu kopieren.


Expected results:

Die Kopierfunktion sollte auch nach dem Wechseln zwischen Tabs weiterhin korrekt funktionieren. Das Kontextmenü zum Kopieren sollte aktiv und auswählbar sein, sobald Text markiert wurde.
Bug: data URL can be utilized to hide download origin in download list
Status: NEW
Priority: P5
Created: 2023-11-29 09:21:33+00:00
Resolved: 2024-05-30 18:16:43+00:00

When Firefox attempts to download a file as a data URI from a website, it should display the origin of the site. However, instead, it is showing 'data resource' in the location placeholder, which can be exploited by an attacker to deceive users into trusting malicious downloads.

Steps to Reproduce:
1. Download poc.html and set up a web server with it.
2. Visit poc.html on the server and observe that it shows 'data resource' instead of the web server URL that initiated the download.
Bug: No fullscreen notification for non-DOM fullscreen (F11 / cmd-ctrl-f)
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2023-11-29 10:48:53+00:00
Resolved: 2024-09-30 05:22:18+00:00

In Firefox, users can use F11 for fullscreen, and this functionality lacks any notification upon activation. An attacker could exploit this to spoof the browser and deceive unsuspecting users.

Steps to Reproduce:
1. Download and extract the file poc.zip to a folder.
2. Open poc.html in a Firefox browser to Begin testing.
Bug: Intermittent browser/components/sessionstore/test/browser_closed_tabs_closed_windows.js | single tracking bug
Status: NEW
Priority: P5
Created: 2023-11-29 11:17:41+00:00
Resolved: 2025-02-17 07:12:33+00:00

**Filed by:** ctuns [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=438115260&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CJMuy_piSsOKIjA9MhcBbw/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/CJMuy_piSsOKIjA9MhcBbw/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2023-11-29T11:12:17.098Z] 11:12:17     INFO - TEST-PASS | browser/components/sessionstore/test/browser_closed_tabs_closed_windows.js | Re-opened tabs not listed in closed tabs - [] deepEqual [] - 
[task 2023-11-29T11:12:17.098Z] 11:12:17     INFO - Buffered messages logged at 11:12:16
[task 2023-11-29T11:12:17.098Z] 11:12:17     INFO - Leaving test bound undo_closed_tabs_from_closed_windows
[task 2023-11-29T11:12:17.098Z] 11:12:17     INFO - Buffered messages finished
[task 2023-11-29T11:12:17.099Z] 11:12:17     INFO - TEST-UNEXPECTED-FAIL | browser/components/sessionstore/test/browser_closed_tabs_closed_windows.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-11-29T11:12:17.099Z] 11:12:17     INFO - GECKO(2572) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2023-11-29T11:12:17.099Z] 11:12:17     INFO - GECKO(2572) | MEMORY STAT | vsize 16425MB | residentFast 374MB | heapAllocated 154MB
[task 2023-11-29T11:12:17.100Z] 11:12:17     INFO - TEST-OK | browser/components/sessionstore/test/browser_closed_tabs_closed_windows.js | took 48438ms
```
Bug: The "Lean more" button is missing from the CBH continuous onboarding CFR
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-11-29 12:32:21+00:00
Resolved: 2024-03-07 12:53:59+00:00

**[Affected versions]:**
- Firefox Nightly Version 122.0a1, Build ID 20231128094907
- Firefox Beta Version 121.0b4, Build ID 20231127091758

**[Affected platforms]:**
- Windows 10 x64

**[Prerequisites]:**
- Have the latest Firefox Beta 121 installed.
- Have a browser client enrolled in a Nimbus experiment that enables both CBH and the CFR. (e.g. https://stage.experimenter.nonprod.dataops.mozgcp.net/nimbus/ppop-cbh-test-2/summary)

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new Private browsing window and navigate to a supported website (e.g. cnn.com)
3. Observe the CBH continuous onboarding CFR.

**[Expected result]:**
- The CFR is displayed with all its elements.

**[Actual result]:**
- The "Learn more" button is missing from the CFR.

**[Notes]:**
- The learn more button is not present in the current payload for the Nimbus CBH CFR. 
- Attached a screenshot of the issue.
Bug: Bookmarks lose their original "Added" date when they were cut-and-pasted into a different folder
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2023-11-29 13:35:45+00:00
Resolved: 2023-12-27 12:56:35+00:00

Tested on 119.0.1.

STR:

1. Open the Library.
2. Right-click on any of the column headers to add both the `Added` and `Last Modified` date column.
3. Drag-and-drop/cut-and-paste one or more bookmarks within the same folder.
4. Observe that both the `Added` and `Last Modified` date did not change.
5. Drag-and-drop one or more bookmarks into a different folder.
6. Observe that only the `Last Modified` date was updated.
7. Cut-and-paste one or more bookmarks into a different folder.

Expected Behavior:

Only the `Last Modified` date for these bookmarks were updated, whilst the `Added` date remain unchanged.

Actual Behavior:

The `Added` date was updated and identical to the `Last Modified` date when bookmarks were cut-and-pasted into a different folder.


Mozregression returned

Last good revision: 8f9703d8891ede813e3ce97435d50f0cb69a1a55
First bad revision: 1be4cb72888eb43d48eb98b0daf847eeaf34adc1
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8f9703d8891ede813e3ce97435d50f0cb69a1a55&tochange=1be4cb72888eb43d48eb98b0daf847eeaf34adc1

During mozregression, I noticed in some of the 116.0a1 bad builds that bookmarks also lost their name when they were cut-and-pasted into a different folder, an issue of which seemed to be addressed in bug 1840207.