av9ash/GitBugs huggingface dataset:
Bug: Nvidia Wayland Frequent Crashes; explicit sync is used, but no acquire point is set
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-07-01 19:50:14+00:00
Resolved: 2024-07-02 09:16:35+00:00

Frequent crashing when using the browser, it happens seemingly at random but I am not technical enough to determine that.

```
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1#64: error 4: explicit sync is used, but no acquire point is set
 (t=806.736) [GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1#64: error 4: explicit sync is used, but no acquire point is set

Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=805.798) Exiting due to channel error.
Segmentation fault (core dumped)
```

I am using EndeavourOS, KDE Plasma, and I am using the nvidia drivers 555.58
This version of the stable drivers brings explicit sync to wayland.
The codeblock above shows what was printed in console when running librewolf through it.
I have attached a link to the core dump of when it happened right after launching librewolf.
Bug: HTTP/3 is not functional when building Firefox with PGO.
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-07-01 20:16:17+00:00
Resolved: 2024-07-03 02:51:05+00:00

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

Steps to reproduce:

Build Firefox without PGO (Profile Guided Optimization)


Actual results:

It is somewhat unusual, but I have observed a peculiar behavior in the process of building Firefox. Specifically, when compiling Firefox without the use of the PGO (Profile-Guided Optimization) option, the HTTP/3 protocol appears to function correctly. However, when PGO is enabled, it appears that HTTP/3 is completely unable to operate. I would appreciate understanding the underlying cause of this issue.
Bug: [WCAG, a11y] Custom color settings overwrite `fill` attributes of SVG elements
Status: NEW
Priority: --
Created: 2024-07-02 07:54:45+00:00
Resolved: 2024-07-31 12:17:37+00:00

Steps to reproduce:

1. Start Firefox
2. Go to "Settings" -> "General" -> "Language and appearance"
3. Under "Colors" click the "Manage colors button"
4. Define custom colors for "Text and Background" and "Link colors"
5. Do NOT check "Use system colors"
6. In the "Override the colors..." dropdown select "Always"
7. Click "OK" and leave the "Settings" page
8. Open example page at https://www.highcharts.com/demo/highcharts/accessible-pie



Actual results:

The example page renders a pie chart SVG. However, the areas of the chart cannot be distinguished from each other, since they are all in the same color. The chart is not accessible and fails international a11y tests.

Inspecting the HTML in the Developer Tools shows that the `fill` attributes of the child elements of the SVG are set to `window`.


Expected results:

The areas of the chart should be rendered with different patterns that are accessible for users with visual impairments.

The `fill` attributes of the SVG's child elements should be respected and point to the pattern definitions via `url(#highcharts-pattern-...)`.
Bug: The progress on the progressbar is not visible in the about:downloads page with High Contrast White enabled
Status: NEW
Priority: --
Created: 2024-07-02 13:09:42+00:00
Resolved: 2024-07-23 08:27:04+00:00

**Note**
* When the user Activates the High COntrast White (Win10), starts downloading a larger file, opens the about:downloads page and selects the ongoing download, he will notice that the progress in the progress bar is not visible.

**Found in**
* Nightly v129.0a1

**Affected versions**
* Nightly v129.0a1

**Tested platforms**
* Affected platforms: Windows 10
* Unaffected platforms: Ubuntu, MacOS

**Steps to reproduce**
Enable High Contrast - White
1. Download a larger file
https://ubuntu.com/download/desktop/thank-you?version=24.04&architecture=amd64&lts=true
2. Load about:downloads
3. Select the downloading file (it is automatically selected if it's the only one in the list)

**Expected result**
* The download progress is visible.

**Actual result**
* The progress bar is visible, but the progression bar inside is not.

**Regression range**
* unknown
Bug: Intermittent [TV] browser/components/shell/test/browser_setDefaultBrowser.js | Exception thrown - at resource://testing-common/sinon-7.2.7.js:3605 - TypeError: Attempted to wrap sendTriggerMessage which is already wrapped
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2024-07-02 15:26:26+00:00
Resolved: 2024-07-09 13:47:20+00:00

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

---
```
[task 2024-07-02T13:30:21.791Z] 13:30:21     INFO - TEST-START | browser/components/shell/test/browser_setDefaultBrowser.js
[task 2024-07-02T13:30:21.796Z] 13:30:21     INFO - TEST-INFO | started process screentopng
[task 2024-07-02T13:30:21.975Z] 13:30:21     INFO - TEST-INFO | screentopng: exit 0
[task 2024-07-02T13:30:21.975Z] 13:30:21     INFO - TEST-UNEXPECTED-FAIL | browser/components/shell/test/browser_setDefaultBrowser.js | Exception thrown - at resource://testing-common/sinon-7.2.7.js:3605 - TypeError: Attempted to wrap sendTriggerMessage which is already wrapped
[task 2024-07-02T13:30:22.213Z] 13:30:22     INFO - GECKO(1096) | MEMORY STAT | vsize 11513MB | residentFast 498MB | heapAllocated 261MB
[task 2024-07-02T13:30:22.216Z] 13:30:22     INFO - TEST-OK | browser/components/shell/test/browser_setDefaultBrowser.js | took 425ms
```
Bug: Building with `ac_add_options --disable-launcher-process` is currently broken
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-07-02 15:41:10+00:00
Resolved: 2024-07-09 09:53:38+00:00

Building with `ac_add_options --disable-launcher-process` is currently broken on Windows:

```
 0:08.91 E:/mozilla/source/trunk/browser/app/winlauncher/LauncherProcessWin.cpp(62,14): error: no member named 'nt' in namespace 'mozilla'
 0:08.91    62 |     mozilla::nt::CrossExecTransferManager txManager(aChildProcess);
 0:08.91       |     ~~~~~~~~~^
 0:08.92 E:/mozilla/source/trunk/browser/app/winlauncher/LauncherProcessWin.cpp(63,10): error: use of undeclared identifier 'txManager'
 0:08.92    63 |     if (!txManager) {
 0:08.92       |          ^
 0:08.92 E:/mozilla/source/trunk/browser/app/winlauncher/LauncherProcessWin.cpp(71,24): error: use of undeclared identifier 'txManager'
 0:08.92    71 |     auto const guard = txManager.Protect(
 0:08.92       |                        ^
 0:08.94 E:/mozilla/source/trunk/browser/app/winlauncher/LauncherProcessWin.cpp(75,9): error: use of undeclared identifier 'txManager'
 0:08.94    75 |         txManager.Transfer(targetAddress, &aDStatus, sizeof(aDStatus));
 0:08.94       |         ^
 0:08.95 4 errors generated.
 0:08.95 mozmake[4]: *** [E:/mozilla/source/trunk/config/rules.mk:676: LauncherProcessWin.obj] Error 1
 0:08.95 mozmake[3]: *** [E:/mozilla/source/trunk/config/recurse.mk:72: browser/app/winlauncher/target-objects] Error 2
```
Bug: Automated redirection will expand URL bar behind selection, instead of adding to existing selection
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2024-07-02 20:44:26+00:00
Resolved: 2024-07-29 16:36:01+00:00

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

Steps to reproduce:

Simply search for something (in this case using DuckDuckGo, which appends `&ia=web` after loading the page), but make a typo in the search query. Quickly realise your mistake, press the muscle-memory [Ctrl]+[L] hotkey to select the URL bar, and re-type your query, assuming the act of selecting the entire URL bar and typing something will replace whatever might have been in that bar otherwise.


Actual results:

Instead of going to the query I intended to type, it sent me to `[Indended query]&ia=web`. This is particularly annoying when using the built-in keywords for search bars, but making a typo. For example, if I have a keyword for "foo" to go to a particular page on a website I frequent, but I make a typo in that keyword, and spot the mistake just a fraction of a second after pressing enter. I therefore press [Ctrl]+[L] to re-type "foo" and press enter, but in the meantime, DuckDuckGo has loaded and appended `&ia=web` to the query.


Expected results:

Instead of allowing a website to alter the URL bar's contents after the user has made *any* modification, the URL bar should be left alone whenever the user has selected any part of it. Selecting the URL bar signals an intention to modify it, so allowing a website to append anything to it will cause confusion for users. Instead, the current URL should be registered somewhere internally, while allowing the user to type in their URL bar. If the user presses [Enter], the modified URL should be wholly irrelevant to the user, who appears to have regretted their visit to this page. If the user presses [Esc], or triggers another way to reset the URL bar that is currently built into the browser, this indicates they wish to stay on this page, so then the (internally maintained) current URL should be reinstated in the URL bar.

Changing a user input while the user is actively manipulating said input is VERY unintuitive and should be done only when it has been considered well. This just looks like unintended behaviour, and very annoying behaviour at that.
Bug: Intermittent browser/components/customizableui/test/browser_proton_moreTools_panel.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-07-02 21:53:32+00:00
Resolved: 2025-01-20 12:07:10+00:00

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

---
```
[task 2024-07-02T21:40:34.497Z] 21:40:34     INFO - checking window state
[task 2024-07-02T21:40:34.508Z] 21:40:34     INFO - TEST-START | browser/components/customizableui/test/browser_proton_moreTools_panel.js
[task 2024-07-02T21:40:34.751Z] 21:40:34     INFO - GECKO(2704) | 1719956434740	Marionette	TRACE	Received observer notification browser-delayed-startup-finished
[task 2024-07-02T21:40:43.600Z] 21:40:43     INFO - GECKO(2704) | console.warn: WindowsJumpLists: "Failed to fetch favicon for " "http://mochi.test:8888/#0" ({})
[task 2024-07-02T21:41:19.529Z] 21:41:19     INFO - TEST-INFO | started process screenshot
[task 2024-07-02T21:41:19.855Z] 21:41:19     INFO - TEST-INFO | screenshot: exit 0
[task 2024-07-02T21:41:19.856Z] 21:41:19     INFO - Buffered messages logged at 21:40:34
[task 2024-07-02T21:41:19.857Z] 21:41:19     INFO - Entering test bound testDevToolsPanelInToolbar
[task 2024-07-02T21:41:19.857Z] 21:41:19     INFO - Buffered messages finished
[task 2024-07-02T21:41:19.858Z] 21:41:19     INFO - TEST-UNEXPECTED-FAIL | browser/components/customizableui/test/browser_proton_moreTools_panel.js | Test timed out - 
[task 2024-07-02T21:41:19.858Z] 21:41:19     INFO - GECKO(2704) | Completed ShutdownLeaks collections in process 2472
[task 2024-07-02T21:41:19.859Z] 21:41:19     INFO - TEST-START | Shutdown
[task 2024-07-02T21:41:19.860Z] 21:41:19     INFO - Browser Chrome Test Summary
[task 2024-07-02T21:41:19.860Z] 21:41:19     INFO - Passed:  2247
[task 2024-07-02T21:41:19.860Z] 21:41:19     INFO - Failed:  1
[task 2024-07-02T21:41:19.861Z] 21:41:19     INFO - Todo:    0
[task 2024-07-02T21:41:19.862Z] 21:41:19     INFO - Mode:    e10s
[task 2024-07-02T21:41:19.862Z] 21:41:19     INFO - *** End BrowserChrome Test Results ***
[task 2024-07-02T21:41:19.863Z] 21:41:19     INFO - GECKO(2704) | Exiting due to channel error.
[task 2024-07-02T21:41:19.863Z] 21:41:19     INFO - GECKO(2704) | Exiting due to channel error.
[task 2024-07-02T21:41:19.864Z] 21:41:19     INFO - TEST-INFO | Main app process: exit 0
[task 2024-07-02T21:41:19.864Z] 21:41:19     INFO - runtests.py | Application ran for: 0:02:45.128693
```
Bug: A box with a white outline but without an image was shown to the left of Update to 129.0a1 (2024-07-02) in About Firefox Nightly
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2024-07-03 01:14:52+00:00
Resolved: 2024-07-09 13:45:07+00:00

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

Steps to reproduce:

I ran Firefox 129.0a1 20240701221157 to 20240702212506 on Wayland in Plasma 6.1.1 in a Fedora 40 KDE installation. I had previously enabled the menu bar. I selected Help in the menu bar and then About Nightly.


Actual results:

A box with a white outline but without an image was shown to the left of Update to 129.0a1 (2024-07-02) in About Firefox Nightly with 129.0a1 20240701221157 to 20240702212506. The middle of the box was black like the background of the About Firefox Nightly window which might've meant the box was transparent. This box wasn't shown with 129.0a1 20240701094548 or earlier. I bisected between 129.0a1 20240701094548 and 20240701221157 with mozregression. The first bad change was for Bug 1905704 - Use single image element for about dialog updater icons.

17:24.41 INFO: Narrowed integration regression window from [d88355e1, 0558f0d3] (3 builds) to [d88355e1, 942908c2] (2 builds) (~1 steps left)
17:24.41 INFO: No more integration revisions, bisection finished.
17:24.41 INFO: Last good revision: d88355e1c5cdeac1e4b56016c3193ef019861a0e
17:24.41 INFO: First bad revision: 942908c28bf32f5dd392fc4418eda3d9477ccea9
17:24.41 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d88355e1c5cdeac1e4b56016c3193ef019861a0e&tochange=942908c28bf32f5dd392fc4418eda3d9477ccea9

The box with the white outline was also shown to the left of the Updates disabled by system administrator when using mozregression. 


Expected results:

An image should have been shown where the box with the white outline but no image was shown to the left of Update to 129.0a1 (2024-07-02) in About Firefox Nightly. Such images as spinners or a checkmark are shown where the box with the white outline was at other steps of checking for updates or updating.
Bug: unable to pin shortcuts on homepage OSX 14.4 and Firefox 127.0.2
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-07-03 05:54:14+00:00
Resolved: 2024-07-10 14:51:57+00:00

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

Steps to reproduce:

try to pin a shortcut to my homepage by following the following procedure
To pin a Shortcut (make it stay): Hover over the tile until the menu (three dots) appears. Click Pin. A pin icon will show up on your pinned Shortcut.
however the menu (three dots) don't appear anymore.


Actual results:

unable to pin/unpin


Expected results:

the menu (three dots) should appear
Bug: Dark theme active tab has too faint background color (and/or missing outline) to distinguish it from the other tabs
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-07-03 06:16:47+00:00
Resolved: 2024-07-03 16:09:07+00:00

It's hard to see what is the active tab with Firefox' built-in dark theme.

Other themes will often have a light border around it in case its background color is too similar to the other tabs.
Bug: macOS dialog windows missing tinting after bug 1867854
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-07-03 06:17:59+00:00
Resolved: 2024-08-28 06:41:58+00:00

After bug 1867854, dialog windows on macOS no longer show desktop tinting on the window background. Since this requires a transparent Gecko background, the `-moz-mac-unified-toolbar-window` appearance added in bug 1870481 should be applied to every window.
Bug: Base domain formatting should use display IDN format
Status: NEW
Priority: P3
Created: 2024-07-03 08:16:06+00:00
Resolved: 2024-07-08 15:22:28+00:00

In reference to https://phabricator.services.mozilla.com/D206579#inline-1195440 in the review of bug 1889536:

https://searchfox.org/mozilla-central/rev/3d173a6ad865eb778eb7a85de900e92774559ed6/browser/components/urlbar/UrlbarValueFormatter.sys.mjs#382 undoes `Services.eTLD.getBaseDomainFromHost(origin);` turning the base domain to the ASCII/Punycode form by calling `IDNService.convertACEtoUTF8`, i.e. by running the pure ToUnicode operation as opposed to calling `convertToDisplayIDN`, which runs ToUnicode in general but ToASCII for labels that we consider to have confusables.

AFAICT, this means that the URL bar implicitly makes the assumption that the base domain can't have confusables. While this is hopefully generally true, I think we can't categorically expect never to encounter an exception, though it might be hard to get the Public Suffix List to include an exception. Therefore, it seems proper to convert to display IDN here.

(This is one of the two uses of the pure ToUnicode operation in the entire Firefox, both of which are questionable. If we managed to make both cases use something more appropriate than pure ToUnicode, we could stop offering API surface for pure ToUnicode, which would nicely steer future code towards converting to display IDN, etc.)
Bug: Intermittent browser/components/translations/tests/browser/browser_translations_select_telemetry_keypresses_translate_full_page_button.js | single tracking bug
Status: REOPENED
Priority: P5
Created: 2024-07-03 09:23:31+00:00
Resolved: 2025-03-03 06:16:44+00:00

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

---
```
[task 2024-07-03T08:41:24.007Z] 08:41:24     INFO - TEST-PASS | browser/components/translations/tests/browser/browser_translations_select_telemetry_keypresses_translate_full_page_button.js | The element 'translateFullPageButton should be enabled. - 
[task 2024-07-03T08:41:24.008Z] 08:41:24     INFO - Resolving 3 mocked downloads for "test-translation-models-0"
[task 2024-07-03T08:41:24.009Z] 08:41:24     INFO - Waiting for SelectTranslationsPanel to change state from "translating" to "translated"
[task 2024-07-03T08:41:24.010Z] 08:41:24     INFO - Buffered messages finished
[task 2024-07-03T08:41:24.011Z] 08:41:24     INFO - TEST-UNEXPECTED-FAIL | browser/components/translations/tests/browser/browser_translations_select_telemetry_keypresses_translate_full_page_button.js | Test timed out - 
[task 2024-07-03T08:41:24.017Z] 08:41:24     INFO - GECKO(1067) | Completed ShutdownLeaks collections in process 1067
[task 2024-07-03T08:41:24.018Z] 08:41:24     INFO - TEST-START | Shutdown
```
Bug: Intermittent browser/components/sessionstore/test/browser_scrollPositions.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-07-03 11:02:10+00:00
Resolved: 2024-08-02 12:04:07+00:00

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

---
```
[task 2024-07-03T10:16:51.023Z] 10:16:51     INFO - TEST-PASS | browser/components/sessionstore/test/browser_scrollPositions.js | force-reload resets scroll positions - 
[task 2024-07-03T10:16:51.024Z] 10:16:51     INFO - Buffered messages logged at 10:10:01
[task 2024-07-03T10:16:51.024Z] 10:16:51     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 9
[task 2024-07-03T10:16:51.024Z] 10:16:51     INFO - Buffered messages logged at 10:10:46
[task 2024-07-03T10:16:51.026Z] 10:16:51     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 8
[task 2024-07-03T10:16:51.026Z] 10:16:51     INFO - Buffered messages logged at 10:11:31
[task 2024-07-03T10:16:51.026Z] 10:16:51     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 7
[task 2024-07-03T10:16:51.027Z] 10:16:51     INFO - Buffered messages logged at 10:12:20
[task 2024-07-03T10:16:51.027Z] 10:16:51     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 6
[task 2024-07-03T10:16:51.028Z] 10:16:51     INFO - Buffered messages logged at 10:13:05
[task 2024-07-03T10:16:51.028Z] 10:16:51     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 5
[task 2024-07-03T10:16:51.028Z] 10:16:51     INFO - Buffered messages logged at 10:13:50
[task 2024-07-03T10:16:51.029Z] 10:16:51     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 4
[task 2024-07-03T10:16:51.029Z] 10:16:51     INFO - Buffered messages logged at 10:14:35
[task 2024-07-03T10:16:51.030Z] 10:16:51     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 3
[task 2024-07-03T10:16:51.030Z] 10:16:51     INFO - Buffered messages logged at 10:15:20
[task 2024-07-03T10:16:51.031Z] 10:16:51     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 2
[task 2024-07-03T10:16:51.031Z] 10:16:51     INFO - Buffered messages logged at 10:16:05
[task 2024-07-03T10:16:51.032Z] 10:16:51     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 1
[task 2024-07-03T10:16:51.032Z] 10:16:51     INFO - Buffered messages finished
[task 2024-07-03T10:16:51.033Z] 10:16:51     INFO - TEST-UNEXPECTED-FAIL | browser/components/sessionstore/test/browser_scrollPositions.js | Test timed out - 
[task 2024-07-03T10:16:51.033Z] 10:16:51     INFO - GECKO(152) | Completed ShutdownLeaks collections in process 6128
[task 2024-07-03T10:16:51.034Z] 10:16:51     INFO - TEST-START | Shutdown
```
Bug: Add localized string for Show Trending Suggestion preference
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-07-03 13:06:47+00:00
Resolved: 2024-07-30 15:40:24+00:00

Starting 128, Recent Searches is default on for everyone, however the string **Show trending search suggestions** exposed in about:prefreces#search is not in the ln file: https://searchfox.org/mozilla-central/source/browser/components/urlbar/content/enUS-searchFeatures.ftl#351
Bug: Focusing the urlbar with the mouse sometimes doesn't select all because the URL shifts due to icons inserted/removed before it
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2024-07-03 13:35:21+00:00
Resolved: 2025-01-29 12:31:16+00:00

Clicking on the urlbar to focus it, should normally Select All, so its contents are ready to be replaced.
Unfortunately often this doesn't work and I end up inserting some text in the middle of the URL.
I found this is due to a few (1px, 2px) mousemove between mousedown and mouseup, that I may inadvertently do.
This is normally not a problem, but because the URL shifts when we insert or remove icons before it, we end up causing a selection change (the mouse moved by 1 px, the url moved by many pixels, so now 1-3 characters are selected).

Other browsers solved this by not shifting the url between focused and unfocused state, though that means we can only have a fixed amount of space for icons before the url, we cannot dynamically insert or remove icons then.
Possible solutions to evaluate:
1. don't collapse/uncollapse icons on focus change if mousedown. We can probably do this with a `mousedown` attribute and changing a few `focused` css rules. Icons would instead appear/disappear on mouseup
2. we could ignore small mousemove (less than half of a character) when passing from focused to unfocused... this may potentially prevent some wanted selection change, or not catch larger mousemove that users with accessibility problems may do