Issue_id
stringlengths 7
7
| Summary
stringlengths 10
255
| Description
stringlengths 12
2.29k
| Description_all
stringlengths 51
2.34k
| Priority
stringclasses 5
values | Status
stringclasses 6
values | Resolution
stringclasses 9
values | Created
stringdate 2020-01-02 13:46:45
2025-03-05 20:35:25
| Resolved
stringdate 2020-01-14 02:57:17
2025-03-05 21:47:22
| token_count
int16 12
511
| Priority_label
int16 1
5
|
|---|---|---|---|---|---|---|---|---|---|---|
1616832
|
gBrowserInit._delayedStartup shouldn't run code after announcing that delayed startup has finished
|
Bug 158968 and bug 1587492 added code to `gBrowserInit._delayedStartup` that runs after we call `_resolveDelayedStartup()`, send the `browser-delayed-startup-finished` notification and add the `delayedStartupFinished` telemetry timestamp. This shouldn't happen.
mkaply, would you take this?
|
gBrowserInit._delayedStartup shouldn't run code after announcing that delayed startup has finished Bug 158968 and bug 1587492 added code to `gBrowserInit._delayedStartup` that runs after we call `_resolveDelayedStartup()`, send the `browser-delayed-startup-finished` notification and add the `delayedStartupFinished` telemetry timestamp. This shouldn't happen.
mkaply, would you take this?
|
P2
|
RESOLVED
|
FIXED
|
2020-02-20 13:18:02+00:00
|
2020-02-25 19:35:37+00:00
| 114
| 2
|
1616834
|
Stub Installer Paveover update prompt is not displayed
|
* Follow up from Bug 1554141
**Affected versions**
* Firefox 73.0.1
* Firefox 74.0b5
* Firefox 75.0a1 (2020-02-20)
**Affected platforms**
* Windows 7x64
* Windwos 8.1x64
* Windows 10x64
**Steps to reproduce**
1. Install an older version of Firefox.
2. Run Firefox and close it.
3. Download and install Stub Installer build.
**Expected result**
* "The Firefox is already installed. Let's update it", prompt window is displayed.
**Actual result**
* Firefox is installed as a fresh install and "The Firefox is already installed. Let's update it", prompt window is not displayed.
**Regression range**
I will try to find a regression range asap if possible.
**Additional notes**
* This issue is also reproducible if step 2 is not performed.
* Since the Update prompt window is not displayed, 'Restore default settings and remove old add-ons for optimal performance.' option is not available.
|
Stub Installer Paveover update prompt is not displayed * Follow up from Bug 1554141
**Affected versions**
* Firefox 73.0.1
* Firefox 74.0b5
* Firefox 75.0a1 (2020-02-20)
**Affected platforms**
* Windows 7x64
* Windwos 8.1x64
* Windows 10x64
**Steps to reproduce**
1. Install an older version of Firefox.
2. Run Firefox and close it.
3. Download and install Stub Installer build.
**Expected result**
* "The Firefox is already installed. Let's update it", prompt window is displayed.
**Actual result**
* Firefox is installed as a fresh install and "The Firefox is already installed. Let's update it", prompt window is not displayed.
**Regression range**
I will try to find a regression range asap if possible.
**Additional notes**
* This issue is also reproducible if step 2 is not performed.
* Since the Update prompt window is not displayed, 'Restore default settings and remove old add-ons for optimal performance.' option is not available.
|
P3
|
RESOLVED
|
INVALID
|
2020-02-20 13:33:32+00:00
|
2020-03-13 15:14:23+00:00
| 263
| 3
|
1616863
|
Payment Request dialog container styles broken
|
Due to unrelated Firefox front-end changes and the fact we disabled tests while development of web payments was on hold, the PaymentRequest dialog position and size is now incorrect. We should run mozregression with the feature preffed on to see what broke it rather than layering new different CSS on top. The following is what I came up with for `toolkit/components/prompts/content/tabprompts.cs` when I didn't have access to mozregression:
```diff
/* Tab-Modal Payment Request widget */
.paymentDialogContainer:not([hidden]) {
/* Center the .paymentDialogContainerFrame horizontally with flexbox. */
display: flex;
flex-direction: column;
position: absolute;
+ z-index: 1000;
+ width: 100%;
}
```
|
Payment Request dialog container styles broken Due to unrelated Firefox front-end changes and the fact we disabled tests while development of web payments was on hold, the PaymentRequest dialog position and size is now incorrect. We should run mozregression with the feature preffed on to see what broke it rather than layering new different CSS on top. The following is what I came up with for `toolkit/components/prompts/content/tabprompts.cs` when I didn't have access to mozregression:
```diff
/* Tab-Modal Payment Request widget */
.paymentDialogContainer:not([hidden]) {
/* Center the .paymentDialogContainerFrame horizontally with flexbox. */
display: flex;
flex-direction: column;
position: absolute;
+ z-index: 1000;
+ width: 100%;
}
```
|
P1
|
RESOLVED
|
FIXED
|
2020-02-20 15:12:49+00:00
|
2020-07-15 02:08:06+00:00
| 200
| 1
|
1617150
|
Intermittent TEST-UNEXPECTED-TIMEOUT | browser/extensions/doh-rollout/test/unit/test_localStorageMigration.js | Test timed out
|
**Filed by:** cbrindusan [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=289867815&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/XeZtyF-GSduBJlNrRiGtwg/runs/0/artifacts/public/logs/live_backing.log
---
[task 2020-02-21T11:22:52.765Z] 11:22:52 INFO - TEST-START | browser/extensions/doh-rollout/test/unit/test_localStorageMigration.js
[task 2020-02-21T11:27:52.769Z] 11:27:52 WARNING - TEST-UNEXPECTED-TIMEOUT | browser/extensions/doh-rollout/test/unit/test_localStorageMigration.js | Test timed out
|
Intermittent TEST-UNEXPECTED-TIMEOUT | browser/extensions/doh-rollout/test/unit/test_localStorageMigration.js | Test timed out **Filed by:** cbrindusan [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=289867815&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/XeZtyF-GSduBJlNrRiGtwg/runs/0/artifacts/public/logs/live_backing.log
---
[task 2020-02-21T11:22:52.765Z] 11:22:52 INFO - TEST-START | browser/extensions/doh-rollout/test/unit/test_localStorageMigration.js
[task 2020-02-21T11:27:52.769Z] 11:27:52 WARNING - TEST-UNEXPECTED-TIMEOUT | browser/extensions/doh-rollout/test/unit/test_localStorageMigration.js | Test timed out
|
P5
|
RESOLVED
|
FIXED
|
2020-02-21 12:05:22+00:00
|
2020-07-12 22:24:57+00:00
| 285
| 5
|
1617171
|
Search suggestions dropdown from about:newtab search box is not re-adjusted at browser resize
|
**[Affected versions]:**
- Firefox Release 73.0.1 Build ID 20200217142647
- Firefox Beta 74.0b6 Build ID 20200221001238
- Firefox Nightly 75.0a1 Build ID 20200221095110
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Ubuntu 16.04
**[Steps to reproduce]:**
1. Open about:newtab page.
2. Resize the window to half size.
3. Type something in the in-content search field.
4. Observe the search suggestions.
**[Expected result]:**
- Search suggestions dropdown is adjusted according to the browser dimensions.
**[Actual result]:**
- Search suggestions dropdown is not re-adjusted after browser resize.
**[Notes]:**
- Issue is not reproducing for Awesome bar search suggestions.
|
Search suggestions dropdown from about:newtab search box is not re-adjusted at browser resize **[Affected versions]:**
- Firefox Release 73.0.1 Build ID 20200217142647
- Firefox Beta 74.0b6 Build ID 20200221001238
- Firefox Nightly 75.0a1 Build ID 20200221095110
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Ubuntu 16.04
**[Steps to reproduce]:**
1. Open about:newtab page.
2. Resize the window to half size.
3. Type something in the in-content search field.
4. Observe the search suggestions.
**[Expected result]:**
- Search suggestions dropdown is adjusted according to the browser dimensions.
**[Actual result]:**
- Search suggestions dropdown is not re-adjusted after browser resize.
**[Notes]:**
- Issue is not reproducing for Awesome bar search suggestions.
|
P5
|
NEW
|
2020-02-21 13:42:12+00:00
|
2025-01-09 09:06:24+00:00
| 228
| 5
|
|
1617197
|
Full installer header fonts look bad on some OS locales
|
When Windows is configured with certain locales (known to include Japanese, but likely others), the header text on all en-US (or presumably any Latin alphabet based) full installer pages uses a default system font that really looks quite rough. See attached screenshot, taken from bug 1515534 comment 14.
It might be tricky to detect this case, because presumably, for builds in the same locale as the system, the chosen font would be the correct one. But this looks so bad that it's worth at least investigating whether we can do anything.
|
Full installer header fonts look bad on some OS locales When Windows is configured with certain locales (known to include Japanese, but likely others), the header text on all en-US (or presumably any Latin alphabet based) full installer pages uses a default system font that really looks quite rough. See attached screenshot, taken from bug 1515534 comment 14.
It might be tricky to detect this case, because presumably, for builds in the same locale as the system, the chosen font would be the correct one. But this looks so bad that it's worth at least investigating whether we can do anything.
|
P3
|
NEW
|
2020-02-21 15:26:21+00:00
|
2022-10-11 23:59:09+00:00
| 130
| 3
|
|
1617211
|
Investigate ways to improve full installer image scaling
|
Bug 1515534 did make some improvement in how our full installer images (the welcome/finish page banner and the wizard page headers) scale up in above-100% DPI configurations, but it still doesn't look very good, especially at fractional scaling factors. We should investigate more ways to improve this, perhaps by using higher resolution assets and scaling them down, or possibly by finding better scaling methods and/or image formats.
|
Investigate ways to improve full installer image scaling Bug 1515534 did make some improvement in how our full installer images (the welcome/finish page banner and the wizard page headers) scale up in above-100% DPI configurations, but it still doesn't look very good, especially at fractional scaling factors. We should investigate more ways to improve this, perhaps by using higher resolution assets and scaling them down, or possibly by finding better scaling methods and/or image formats.
|
P3
|
NEW
|
2020-02-21 16:07:27+00:00
|
2022-10-11 23:59:10+00:00
| 101
| 3
|
|
1617275
|
TLS override page should not be displayed if the tls min version is locked to 1.2
|
Enterprise policy allows the min version of TLS to be locked to 1.2 (or 1.1).
If it is locked to a particular version, we should not be showing the deprecation page to allow someone to go below that version.
|
TLS override page should not be displayed if the tls min version is locked to 1.2 Enterprise policy allows the min version of TLS to be locked to 1.2 (or 1.1).
If it is locked to a particular version, we should not be showing the deprecation page to allow someone to go below that version.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-21 21:19:27+00:00
|
2021-12-13 01:28:52+00:00
| 74
| 1
|
1617280
|
Collection component dismiss
|
Right now the work in progress collection component does not have a working dismiss button.
Doing this work likely also means wiring up telemetry for dismiss.
|
Collection component dismiss Right now the work in progress collection component does not have a working dismiss button.
Doing this work likely also means wiring up telemetry for dismiss.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-21 21:34:38+00:00
|
2020-06-02 16:49:39+00:00
| 35
| 1
|
1617285
|
Possible Breakage in FxA App (Hamburger) Menu Telemetry in Version 73
|
[This chart](https://sql.telemetry.mozilla.org/queries/68484/source#172975) shows that the volume of events related to the FxA hamburger menu menu seem to be in a freefall from around the time 73 went to release.
A similar thing has NOT happened to the toolbar menu telemetry.
edit, talking about [these](https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/Events.yaml#711) events, they have not expired.
|
Possible Breakage in FxA App (Hamburger) Menu Telemetry in Version 73 [This chart](https://sql.telemetry.mozilla.org/queries/68484/source#172975) shows that the volume of events related to the FxA hamburger menu menu seem to be in a freefall from around the time 73 went to release.
A similar thing has NOT happened to the toolbar menu telemetry.
edit, talking about [these](https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/Events.yaml#711) events, they have not expired.
|
P1
|
RESOLVED
|
FIXED
|
2020-02-21 22:12:19+00:00
|
2020-03-24 15:56:51+00:00
| 147
| 1
|
1617333
|
Some top sites have incorrect favicons
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
the top sites list version of the megabar (sorry for the wording, I don't know how else to describe it) shows the incorrect favicon at least in some cases, such as twitter. See attached screenshot (I put red arrow). But when you actually type in the URL bar, the twitter entry has the correct favicon. (screenshot below)
|
Some top sites have incorrect favicons User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
the top sites list version of the megabar (sorry for the wording, I don't know how else to describe it) shows the incorrect favicon at least in some cases, such as twitter. See attached screenshot (I put red arrow). But when you actually type in the URL bar, the twitter entry has the correct favicon. (screenshot below)
|
P3
|
VERIFIED
|
FIXED
|
2020-02-22 02:16:43+00:00
|
2020-04-08 07:08:49+00:00
| 136
| 3
|
1617345
|
Disabling top sites on new tab causes top sites not to be shown in the urlbar after restarting Firefox
|
[Tracking Requested - why for this release]:
If you hide top sites on new tab (set `browser.newtabpage.activity-stream.feeds.topsites` to false) and restart Firefox, focusing the urlbar doesn't show the top sites anymore. That's because `this.activityStream.store.getState().TopSites.rows` is an empty array here: https://searchfox.org/mozilla-central/rev/c1e3d3edd4a9b784971555dc74a5de23d768b2e1/browser/modules/AboutNewTab.jsm#115 Which makes total sense because top sites are disabled.
Ed, how might we fix this? We need to show the top sites in the urlbar view even when they're hidden on new tab. Setting the pref to true, calling `AboutNewTab.getTopSites`, and then resetting it to false actually works, but it's hacky, and it also causes the top sites to flicker on and off if the current tab is new tab.
Requesting tracking because we want to enable top sites in the urlbar on release on 74.
|
Disabling top sites on new tab causes top sites not to be shown in the urlbar after restarting Firefox [Tracking Requested - why for this release]:
If you hide top sites on new tab (set `browser.newtabpage.activity-stream.feeds.topsites` to false) and restart Firefox, focusing the urlbar doesn't show the top sites anymore. That's because `this.activityStream.store.getState().TopSites.rows` is an empty array here: https://searchfox.org/mozilla-central/rev/c1e3d3edd4a9b784971555dc74a5de23d768b2e1/browser/modules/AboutNewTab.jsm#115 Which makes total sense because top sites are disabled.
Ed, how might we fix this? We need to show the top sites in the urlbar view even when they're hidden on new tab. Setting the pref to true, calling `AboutNewTab.getTopSites`, and then resetting it to false actually works, but it's hacky, and it also causes the top sites to flicker on and off if the current tab is new tab.
Requesting tracking because we want to enable top sites in the urlbar on release on 74.
|
P1
|
RESOLVED
|
FIXED
|
2020-02-22 05:48:54+00:00
|
2020-07-22 22:16:37+00:00
| 293
| 1
|
1617419
|
Feature recommendation shown even if disabled in settings
|
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
I surfed on youtube.com, nothing out of the ordinary, I reloaded the youtube homepage a few times, and on the second or third time, a feature recommendation message appeared in the address bar. This message persisted over mutiple page reloads.
I have not been able to reproduce this in another browser session, but AFAIK the recommendation message also only appears sporadically even if enabled.
I do have both "Recommend extensions as you browse" and "Recommend features as you browse" options unchecked aka. disabled in the "General" -> "Browsing" preferences page.
(Screenshot: https://i.imgur.com/EtKkzXo.png)
Browser version info:
Name Firefox
Version 73.0.1
Build-ID 20200217142647
User-Agent Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
System info:
OS: Ubuntu 18.04.4 LTS, x64
Packages:
firefox (amd64); Version "73.0.1+build1-0ubuntu0.18.04.1"
firefox-locale-de (amd64); Version "73.0.1+build1-0ubuntu0.18.04.1"
Actual results:
Firefox showed me a feature recommendation notification in the address bar for the feature "pinned tabs".
(See screenshot here: https://i.imgur.com/D8nknDR.png)
Expected results:
Firefox should not have shown this notification and respected the preferences ("Recommend extensions as you browse" and "Recommend features as you browse").
|
Feature recommendation shown even if disabled in settings User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
I surfed on youtube.com, nothing out of the ordinary, I reloaded the youtube homepage a few times, and on the second or third time, a feature recommendation message appeared in the address bar. This message persisted over mutiple page reloads.
I have not been able to reproduce this in another browser session, but AFAIK the recommendation message also only appears sporadically even if enabled.
I do have both "Recommend extensions as you browse" and "Recommend features as you browse" options unchecked aka. disabled in the "General" -> "Browsing" preferences page.
(Screenshot: https://i.imgur.com/EtKkzXo.png)
Browser version info:
Name Firefox
Version 73.0.1
Build-ID 20200217142647
User-Agent Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
System info:
OS: Ubuntu 18.04.4 LTS, x64
Packages:
firefox (amd64); Version "73.0.1+build1-0ubuntu0.18.04.1"
firefox-locale-de (amd64); Version "73.0.1+build1-0ubuntu0.18.04.1"
Actual results:
Firefox showed me a feature recommendation notification in the address bar for the feature "pinned tabs".
(See screenshot here: https://i.imgur.com/D8nknDR.png)
Expected results:
Firefox should not have shown this notification and respected the preferences ("Recommend extensions as you browse" and "Recommend features as you browse").
|
P1
|
VERIFIED
|
FIXED
|
2020-02-22 23:54:47+00:00
|
2020-10-24 16:03:51+00:00
| 453
| 1
|
1617428
|
URL tooltip not disappearing after search in page
|
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
go to https://www.mozilla.org/en/
place mouse at left page border (at no link)
hit ctrl+f
type "proj"
hit "esc"
scroll down using "page down" on keyboard without moving mouse or pressing any other key
Actual results:
URL tooltip shows address of "Projects" link on top of page. When scrolling down or moving the mouse in page (without hovering over any clickable link) URL tooltip stays forever unless you move the mouse over a link or click the left mouse button anywhere in the page.
Expected results:
Tooltip should disappear after x seconds, at mouse movement or when scrolling etc.
|
URL tooltip not disappearing after search in page User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
go to https://www.mozilla.org/en/
place mouse at left page border (at no link)
hit ctrl+f
type "proj"
hit "esc"
scroll down using "page down" on keyboard without moving mouse or pressing any other key
Actual results:
URL tooltip shows address of "Projects" link on top of page. When scrolling down or moving the mouse in page (without hovering over any clickable link) URL tooltip stays forever unless you move the mouse over a link or click the left mouse button anywhere in the page.
Expected results:
Tooltip should disappear after x seconds, at mouse movement or when scrolling etc.
|
P5
|
RESOLVED
|
INVALID
|
2020-02-23 03:37:50+00:00
|
2020-08-19 03:10:30+00:00
| 198
| 5
|
1617457
|
"Open with" add the extension .txt , "Save file" does not
|
Reproducible: always
Steps To Reproduce:
1. https://bugs.chromium.org/p/chromium/issues/detail?id=1022615
2. Left mouse click on "Download" link
3-a. "Open With" [Notepad(default)]
--- observe file name
3-b. "Save file"
Actual Results:
3-a: added .txt --- bug
3-b. saved with .html as expected
Expected Results:
File name should content-disposition filename attribute.
|
"Open with" add the extension .txt , "Save file" does not Reproducible: always
Steps To Reproduce:
1. https://bugs.chromium.org/p/chromium/issues/detail?id=1022615
2. Left mouse click on "Download" link
3-a. "Open With" [Notepad(default)]
--- observe file name
3-b. "Save file"
Actual Results:
3-a: added .txt --- bug
3-b. saved with .html as expected
Expected Results:
File name should content-disposition filename attribute.
|
P5
|
NEW
|
2020-02-23 13:58:14+00:00
|
2022-10-11 23:59:24+00:00
| 134
| 5
|
|
1617458
|
Firefox doesn't show certificate (and gives error) while the connection is marked as secure
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
I have a self-signed certificate chain and the root CA certificate imported to the system as well as in Firefox.
Actual results:
While accessing the TLS secured pages Firefox shows, that the connection is secured. If I wanna view the certificate, I get an error page: "Certificate. Something went wrong.
We were unable to find the certificate information, or the certificate is corrupted. Please try again."
Firefox Klar doesn't load/display the page at all, while the chromium certificate viewer gives me detailed information about the certificate as expected.
Expected results:
See the (details of that) certificate.
|
Firefox doesn't show certificate (and gives error) while the connection is marked as secure User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
I have a self-signed certificate chain and the root CA certificate imported to the system as well as in Firefox.
Actual results:
While accessing the TLS secured pages Firefox shows, that the connection is secured. If I wanna view the certificate, I get an error page: "Certificate. Something went wrong.
We were unable to find the certificate information, or the certificate is corrupted. Please try again."
Firefox Klar doesn't load/display the page at all, while the chromium certificate viewer gives me detailed information about the certificate as expected.
Expected results:
See the (details of that) certificate.
|
P2
|
NEW
|
2020-02-23 14:32:15+00:00
|
2022-10-11 23:59:24+00:00
| 197
| 2
|
|
1617503
|
Bookmark button not working after system returning from standby
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
I opened many tabs with websites loaded and/or multiple windows.
Actual results:
When I have lots of tabs open while working on stuff, the bookmark star button does not work. It does not show anything. I click on it and it does nothing. It does not bookmark the page. Note: the keyboard shortcut works to bookmark but the new bookmark menu still doesn't show up.
Expected results:
The website to be bookmarked and the new bookmark menu to pop up asking were i want the bookmark to be saved.
|
Bookmark button not working after system returning from standby User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
I opened many tabs with websites loaded and/or multiple windows.
Actual results:
When I have lots of tabs open while working on stuff, the bookmark star button does not work. It does not show anything. I click on it and it does nothing. It does not bookmark the page. Note: the keyboard shortcut works to bookmark but the new bookmark menu still doesn't show up.
Expected results:
The website to be bookmarked and the new bookmark menu to pop up asking were i want the bookmark to be saved.
|
P3
|
UNCONFIRMED
|
2020-02-24 03:32:38+00:00
|
2022-10-11 23:59:29+00:00
| 174
| 3
|
|
1617519
|
Intermittent browser/components/syncedtabs/test/browser/browser_sidebar_syncedtabslist.js | application terminated with exit code 1
|
**Filed by:** btara [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=290151272&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/XdhSNv8lTVeHzPok3yfa4w/runs/0/artifacts/public/logs/live_backing.log
---
[task 2020-02-24T06:42:49.037Z] 06:42:49 INFO - TEST-PASS | browser/components/syncedtabs/test/browser/browser_sidebar_syncedtabslist.js | Node at 9 should have selector -
[task 2020-02-24T06:42:49.037Z] 06:42:49 INFO - TEST-PASS | browser/components/syncedtabs/test/browser/browser_sidebar_syncedtabslist.js | Node 9 should match menuitem#syncedTabsRefreshFilter -
[task 2020-02-24T06:42:49.038Z] 06:42:49 INFO - Buffered messages finished
[task 2020-02-24T06:42:49.038Z] 06:42:49 ERROR - TEST-UNEXPECTED-FAIL | browser/components/syncedtabs/test/browser/browser_sidebar_syncedtabslist.js | application terminated with exit code 1
[task 2020-02-24T06:42:49.040Z] 06:42:49 INFO - runtests.py | Application ran for: 0:00:05.395256
|
Intermittent browser/components/syncedtabs/test/browser/browser_sidebar_syncedtabslist.js | application terminated with exit code 1 **Filed by:** btara [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=290151272&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/XdhSNv8lTVeHzPok3yfa4w/runs/0/artifacts/public/logs/live_backing.log
---
[task 2020-02-24T06:42:49.037Z] 06:42:49 INFO - TEST-PASS | browser/components/syncedtabs/test/browser/browser_sidebar_syncedtabslist.js | Node at 9 should have selector -
[task 2020-02-24T06:42:49.037Z] 06:42:49 INFO - TEST-PASS | browser/components/syncedtabs/test/browser/browser_sidebar_syncedtabslist.js | Node 9 should match menuitem#syncedTabsRefreshFilter -
[task 2020-02-24T06:42:49.038Z] 06:42:49 INFO - Buffered messages finished
[task 2020-02-24T06:42:49.038Z] 06:42:49 ERROR - TEST-UNEXPECTED-FAIL | browser/components/syncedtabs/test/browser/browser_sidebar_syncedtabslist.js | application terminated with exit code 1
[task 2020-02-24T06:42:49.040Z] 06:42:49 INFO - runtests.py | Application ran for: 0:00:05.395256
|
P5
|
RESOLVED
|
INCOMPLETE
|
2020-02-24 07:44:00+00:00
|
2022-06-14 17:00:38+00:00
| 449
| 5
|
1617560
|
Activity stream content is not vertically centered since 73
|
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Open New tab with Activity stream enabled
Actual results:
Content is not vertically centered and is displayed at the top of the page.
Expected results:
Top sites section is vertically centered just like in previous Firefox versions.
(Add align-items: center; to .outer-wrapper)
|
Activity stream content is not vertically centered since 73 User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Open New tab with Activity stream enabled
Actual results:
Content is not vertically centered and is displayed at the top of the page.
Expected results:
Top sites section is vertically centered just like in previous Firefox versions.
(Add align-items: center; to .outer-wrapper)
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-02-24 11:22:57+00:00
|
2020-02-24 18:33:13+00:00
| 117
| 3
|
1617603
|
Make browser_urlbar_event_telemetry.js more reliable
|
There are a lot of intermittent failures in browser_urlbar_event_telemetry.js, we should try to figure out why.
I couldn't reproduce those failures locally so far, there may also be some kind of interaction with other tests.
|
Make browser_urlbar_event_telemetry.js more reliable There are a lot of intermittent failures in browser_urlbar_event_telemetry.js, we should try to figure out why.
I couldn't reproduce those failures locally so far, there may also be some kind of interaction with other tests.
|
P3
|
RESOLVED
|
WORKSFORME
|
2020-02-24 14:30:35+00:00
|
2020-11-04 20:46:41+00:00
| 73
| 3
|
1617623
|
Popular image formats are not detected in Save as Type field
|
**Affected versions**
* 73.0.1 (ID:20200217142647)
*74.0b7(ID:20200221211950)
**Affected platforms**
* Windows 10x64
**Steps to reproduce**
1. Launch FF.
2. Go to http://cdn2.collective-evolution.com/assets/uploads/2009/09/url.jpeg
3. Right click the image , and in the context menu select "Save image as"
**Expected result**
* A new OS window is opened, with 2 fields in the lower side. The "Save as type" drop-down automatically detects the format of the image and the File name automatically fills with the default name
**Actual result**
* A new OS windows is opened with 2 fields in the lower side. The "Save as type" drop-down does not automatically detect the image format and the field remains empty.
**Regression range**
* Will return with regression ASAP
**Additional notes**
* This issue occurs only with image formats such as .jpg , .png , .gif , etc.
|
Popular image formats are not detected in Save as Type field **Affected versions**
* 73.0.1 (ID:20200217142647)
*74.0b7(ID:20200221211950)
**Affected platforms**
* Windows 10x64
**Steps to reproduce**
1. Launch FF.
2. Go to http://cdn2.collective-evolution.com/assets/uploads/2009/09/url.jpeg
3. Right click the image , and in the context menu select "Save image as"
**Expected result**
* A new OS window is opened, with 2 fields in the lower side. The "Save as type" drop-down automatically detects the format of the image and the File name automatically fills with the default name
**Actual result**
* A new OS windows is opened with 2 fields in the lower side. The "Save as type" drop-down does not automatically detect the image format and the field remains empty.
**Regression range**
* Will return with regression ASAP
**Additional notes**
* This issue occurs only with image formats such as .jpg , .png , .gif , etc.
|
P3
|
RESOLVED
|
FIXED
|
2020-02-24 15:27:34+00:00
|
2020-08-03 07:20:06+00:00
| 262
| 3
|
1617690
|
Tab dragging gives unintuitive feedback on macOS
|
When you go to drag a tab to a new window the drag canceled animation plays which suggest that drag failed but then a new tab is created. This feels really awkward.
|
Tab dragging gives unintuitive feedback on macOS When you go to drag a tab to a new window the drag canceled animation plays which suggest that drag failed but then a new tab is created. This feels really awkward.
|
P3
|
NEW
|
2020-02-24 19:36:50+00:00
|
2022-10-11 23:59:43+00:00
| 47
| 3
|
|
1617832
|
Changing the zoom level in one tab also affects another
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
When I open firefox, I have 3 or more tabs.
the first is for my synology NAS
The second is for Jeedom (domotic)
The last google (for example).
Actual results:
When i change the zoom for synology tab, it also change in the jeedom tab and vice versa.
But there is no effect on the other tabs.
Expected results:
Change zoom in a tab must not change the zoom in another tab
|
Changing the zoom level in one tab also affects another User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
When I open firefox, I have 3 or more tabs.
the first is for my synology NAS
The second is for Jeedom (domotic)
The last google (for example).
Actual results:
When i change the zoom for synology tab, it also change in the jeedom tab and vice versa.
But there is no effect on the other tabs.
Expected results:
Change zoom in a tab must not change the zoom in another tab
|
P3
|
NEW
|
2020-02-25 08:42:24+00:00
|
2022-10-11 23:59:52+00:00
| 153
| 3
|
|
1617899
|
gBrowserInit._delayedStartup shouldn't call SessionStore in the middle of announcing that delayed startup has finished
|
Following up from bug 1616832, we still call SessionStore in the middle of announcing that delayed startup has finished. Since it's an async call it's not a big deal, but would be good to clean up anyway.
|
gBrowserInit._delayedStartup shouldn't call SessionStore in the middle of announcing that delayed startup has finished Following up from bug 1616832, we still call SessionStore in the middle of announcing that delayed startup has finished. Since it's an async call it's not a big deal, but would be good to clean up anyway.
|
P2
|
RESOLVED
|
FIXED
|
2020-02-25 14:24:32+00:00
|
2020-02-26 21:41:42+00:00
| 80
| 2
|
1617942
|
Refactor usage of getLastModified() and DB connection closing
|
While working on https://phabricator.services.mozilla.com/D63207 we wanted to remove the duplication of `openCollection()` to retrieve the local timestamp.
We ran into some issues, most notably around DB connection closing.
This would deserve some further investigation.
|
Refactor usage of getLastModified() and DB connection closing While working on https://phabricator.services.mozilla.com/D63207 we wanted to remove the duplication of `openCollection()` to retrieve the local timestamp.
We ran into some issues, most notably around DB connection closing.
This would deserve some further investigation.
|
P2
|
RESOLVED
|
FIXED
|
2020-02-25 16:52:03+00:00
|
2020-03-04 03:53:16+00:00
| 86
| 2
|
1617987
|
https://magmalabs.io redirects to https://www.magmalabs.io in Chrome but not Firefox [SSLCommonNameMismatchHandling]
|
### Steps to reproduce
1. Load https://magmalabs.io/
### Expected results
https://magmalabs.io/ should redirect to https://www.magmalabs.io/ like Chrome does using its SSLCommonNameMismatchHandling heuristics. Here is a 2016 blog post about Chrome's SSLCommonNameMismatchHandling:
https://medium.com/servertastic/chrome-testing-https-redirect-when-certificate-hostname-is-invalid-925f0974c72b
### Actual results
https://magmalabs.io/ produces a TLS error in Firefox (and Safari and IE11):
> Nightly does not trust this site because it uses a certificate that is not valid for magmalabs.io. The certificate is only valid for the following names: m.magmalabs.io, www.magmalabs.io
>
> Error code: SSL_ERROR_BAD_CERT_DOMAIN
Firefox, Safari, and IE11 seem to be making a more conservative security stance here than Chrome, but this could be a webcompat problem for Firefox.
B.J. Herbison debugged in Chrome a bit and wrote:
> I opened up the Network panel in https://magmalabs.io/ and saw a request for magmalabs.io appear in red with the message Failed, and then it loaded www.magmalabs.io and went on--and it cleared the previous entries as it does when it starts the display of a new page. So it gives up quickly, tries an alternative, and doesn't report the original error to the user.
>
> Actually, going back to the console I find this:
>
> `Redirecting navigation magmalabs.io -> www.magmalabs.io because the server presented a certificate valid for www.magmalabs.io but not for magmalabs.io. To disable such redirects launch Chrome with the following flag: --disable-features=SSLCommonNameMismatchHandling`
|
https://magmalabs.io redirects to https://www.magmalabs.io in Chrome but not Firefox [SSLCommonNameMismatchHandling] ### Steps to reproduce
1. Load https://magmalabs.io/
### Expected results
https://magmalabs.io/ should redirect to https://www.magmalabs.io/ like Chrome does using its SSLCommonNameMismatchHandling heuristics. Here is a 2016 blog post about Chrome's SSLCommonNameMismatchHandling:
https://medium.com/servertastic/chrome-testing-https-redirect-when-certificate-hostname-is-invalid-925f0974c72b
### Actual results
https://magmalabs.io/ produces a TLS error in Firefox (and Safari and IE11):
> Nightly does not trust this site because it uses a certificate that is not valid for magmalabs.io. The certificate is only valid for the following names: m.magmalabs.io, www.magmalabs.io
>
> Error code: SSL_ERROR_BAD_CERT_DOMAIN
Firefox, Safari, and IE11 seem to be making a more conservative security stance here than Chrome, but this could be a webcompat problem for Firefox.
B.J. Herbison debugged in Chrome a bit and wrote:
> I opened up the Network panel in https://magmalabs.io/ and saw a request for magmalabs.io appear in red with the message Failed, and then it loaded www.magmalabs.io and went on--and it cleared the previous entries as it does when it starts the display of a new page. So it gives up quickly, tries an alternative, and doesn't report the original error to the user.
>
> Actually, going back to the console I find this:
>
> `Redirecting navigation magmalabs.io -> www.magmalabs.io because the server presented a certificate valid for www.magmalabs.io but not for magmalabs.io. To disable such redirects launch Chrome with the following flag: --disable-features=SSLCommonNameMismatchHandling`
|
P2
|
VERIFIED
|
FIXED
|
2020-02-25 19:30:09+00:00
|
2020-10-07 21:39:45+00:00
| 509
| 2
|
1618094
|
address bar search term is interpreted as scheme when Firefox runs in an environment where flatpak claims to understand all protocols/schemes
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Using the address bar for both search and direct address input (as is the default).
Searching for
"site:mozilla.org firefox"
as that's a common query for different search engines.
Actual results:
Firefox attempts to open the address "site:mozilla.org firefox", which results in a dialog to open the "site" with the default system handler for this scheme.
The search term is misinterpreted as scheme part of an URL. As soon as the query contains a colon and a character after it, the hint in the address bar changes from "search with x" to "visit q", resulting in the corresponding action.
I know that "//" are not necessarily part of an URI, but I think the space(s) in the search query should make it obvious that the user is not requesting an address directly.
Expected results:
The default search engine should be queried with the query string. I'm marking this as bug rather than feature request because it's a regression.
|
address bar search term is interpreted as scheme when Firefox runs in an environment where flatpak claims to understand all protocols/schemes User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Using the address bar for both search and direct address input (as is the default).
Searching for
"site:mozilla.org firefox"
as that's a common query for different search engines.
Actual results:
Firefox attempts to open the address "site:mozilla.org firefox", which results in a dialog to open the "site" with the default system handler for this scheme.
The search term is misinterpreted as scheme part of an URL. As soon as the query contains a colon and a character after it, the hint in the address bar changes from "search with x" to "visit q", resulting in the corresponding action.
I know that "//" are not necessarily part of an URI, but I think the space(s) in the search query should make it obvious that the user is not requesting an address directly.
Expected results:
The default search engine should be queried with the query string. I'm marking this as bug rather than feature request because it's a regression.
|
P3
|
RESOLVED
|
FIXED
|
2020-02-26 06:24:03+00:00
|
2024-10-30 07:27:59+00:00
| 293
| 3
|
1618115
|
tips/interventions -shown telemetry should not be incremented in the provider
|
The fact the provider returns a tip/intervention is not enough to tell whether it was shown, it's possible in the meanwhile the search was canceled and the providersManager will ignore those results.
We should probably increment telemetry in the frontend when tips/interventions are effectively shown.
|
tips/interventions -shown telemetry should not be incremented in the provider The fact the provider returns a tip/intervention is not enough to tell whether it was shown, it's possible in the meanwhile the search was canceled and the providersManager will ignore those results.
We should probably increment telemetry in the frontend when tips/interventions are effectively shown.
|
P3
|
NEW
|
2020-02-26 08:43:13+00:00
|
2020-07-09 04:32:30+00:00
| 80
| 3
|
|
1618123
|
[Protections Panel] Tracking Protection UI is overlapped in tracking content panel
|
**Affected versions**
- Firefox 73.0.1
- Firefox 74.0b8
- Firefox 75.0a1
**Affected platforms**
* macOS 10.XX retina based
**Steps to reproduce**
- Precondition - issue is reproducible only on retina based systems
1. Launch Firefox and access [Reddit](https://www.reddit.com/)
2. Open Tracking Protection panel by accessing the shield found in URL bar
3. Disable the protection and wait for the page to reload
4. Open Tracking Protection panel and access tracking content
5. Hover over "Manage protection settings"
**Expected result**
- The list is rendered correctly
**Actual result**
- "Manage protection settings" button is being overlapped on hover
**Regression range**
- Will see for a regression.
**Additional notes**
- The issue can be seen in this [attachment](https://drive.google.com/open?id=1TqJ4CW7yor5kokg0A47b9656BXwB9xyr).
- This is reproducible only on retina mac systems.
|
[Protections Panel] Tracking Protection UI is overlapped in tracking content panel **Affected versions**
- Firefox 73.0.1
- Firefox 74.0b8
- Firefox 75.0a1
**Affected platforms**
* macOS 10.XX retina based
**Steps to reproduce**
- Precondition - issue is reproducible only on retina based systems
1. Launch Firefox and access [Reddit](https://www.reddit.com/)
2. Open Tracking Protection panel by accessing the shield found in URL bar
3. Disable the protection and wait for the page to reload
4. Open Tracking Protection panel and access tracking content
5. Hover over "Manage protection settings"
**Expected result**
- The list is rendered correctly
**Actual result**
- "Manage protection settings" button is being overlapped on hover
**Regression range**
- Will see for a regression.
**Additional notes**
- The issue can be seen in this [attachment](https://drive.google.com/open?id=1TqJ4CW7yor5kokg0A47b9656BXwB9xyr).
- This is reproducible only on retina mac systems.
|
P3
|
RESOLVED
|
WORKSFORME
|
2020-02-26 09:40:18+00:00
|
2023-02-23 11:56:36+00:00
| 281
| 3
|
1618144
|
The "New Tab" page is wrongly scrolled down if the "Highlights" context menu button is clicked after navigating back to the page
|
**[Affected versions]:**
- Firefox Release 73.0.1 Build ID 20200217142647
- Firefox Beta 74.0b7 Build ID 20200221211950
- Firefox Nightly 75.0a1 Build ID 20200225214332
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Ubuntu 16.04
**[Prerequisites]:**
- Set “browser.search.region” to “US” or “CA”
- Restart the browser
**[Steps to reproduce]:**
1. Open a New Tab page.
2. Scroll down the page until the “Highlights” section.
3. Click on any of the highlighted cards.
4. Click the “Go back one page” arrow.
5. Click on the context menu button of the same card.
**[Expected result]:**
Context menu button is opened.
**[Actual result]:**
Page is scrolled down. Context menu is not opened (Win and Linux).
**[Notes]:**
- Issue is not reproducible if the Recommended by Pocket sections is disabled.
- On Mac OS, the context menu is displayed, but the scrolling issue remains.
|
The "New Tab" page is wrongly scrolled down if the "Highlights" context menu button is clicked after navigating back to the page **[Affected versions]:**
- Firefox Release 73.0.1 Build ID 20200217142647
- Firefox Beta 74.0b7 Build ID 20200221211950
- Firefox Nightly 75.0a1 Build ID 20200225214332
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Ubuntu 16.04
**[Prerequisites]:**
- Set “browser.search.region” to “US” or “CA”
- Restart the browser
**[Steps to reproduce]:**
1. Open a New Tab page.
2. Scroll down the page until the “Highlights” section.
3. Click on any of the highlighted cards.
4. Click the “Go back one page” arrow.
5. Click on the context menu button of the same card.
**[Expected result]:**
Context menu button is opened.
**[Actual result]:**
Page is scrolled down. Context menu is not opened (Win and Linux).
**[Notes]:**
- Issue is not reproducible if the Recommended by Pocket sections is disabled.
- On Mac OS, the context menu is displayed, but the scrolling issue remains.
|
P2
|
NEW
|
2020-02-26 11:04:56+00:00
|
2022-10-12 00:00:08+00:00
| 302
| 2
|
|
1618153
|
Add telemetry for downloads and download panel usage
|
UR revealed that users struggle to find the download panel once a download is made, leading to users redownloading files.
There is no telemetry currently for file downloads or download panel usage to understand how frequent of a use case downloading a file is and how much of a problem finding the download panel is once you achieve a file download.
User stories:
- As a product manager I'd like to understand if file download is a frequent use case, so that I can focus efforts on making it a great experience.
- As a product manager I want to understand if users experience pain when attempting to find doanloaded files, so I can clarify if it could be a churn driver.
Acceptance criteria:
- New telemetry allows identifying share of DAU/MAU that downloads files
- New telemetry allows identifying number of files downloaded per profile per day
- New telemetry allows understanding the ratio number of files downloaded / number of times download panel was opened per profile
|
Add telemetry for downloads and download panel usage UR revealed that users struggle to find the download panel once a download is made, leading to users redownloading files.
There is no telemetry currently for file downloads or download panel usage to understand how frequent of a use case downloading a file is and how much of a problem finding the download panel is once you achieve a file download.
User stories:
- As a product manager I'd like to understand if file download is a frequent use case, so that I can focus efforts on making it a great experience.
- As a product manager I want to understand if users experience pain when attempting to find doanloaded files, so I can clarify if it could be a churn driver.
Acceptance criteria:
- New telemetry allows identifying share of DAU/MAU that downloads files
- New telemetry allows identifying number of files downloaded per profile per day
- New telemetry allows understanding the ratio number of files downloaded / number of times download panel was opened per profile
|
P2
|
RESOLVED
|
DUPLICATE
|
2020-02-26 11:49:15+00:00
|
2022-01-28 08:26:06+00:00
| 210
| 2
|
1618160
|
A saved to Pocket highlight card redirects to 2 different pages at direct click vs. “Open in New (Private) Window” context menu click
|
**[Affected versions]:**
- Firefox Release 73.0.1 Build ID 20200217142647
- Firefox Beta 74.0b7 Build ID 20200221211950
- Firefox Nightly 75.0a1 Build ID 20200225214332
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Ubuntu 16.04
**[Prerequisites]:**
- Have a card from the Highlights section saved to Pocket.
**[Steps to reproduce]:**
1. Click the saved to pocket card from prerequisites.
2. Click the “Open in a New Window” option from the context menu for the same card.
**[Expected result]:**
Both actions redirect the user to the same page.
**[Actual result]:**
At step 1 the user is redirected to an app.getpocket.com specific page.
At step 2 the user is redirected to the original location of the card.
**[Notes]:**
- Reproducing also for “Open in a New Private Window” option.
- We should show consistency while accessing the same card in different ways.
|
A saved to Pocket highlight card redirects to 2 different pages at direct click vs. “Open in New (Private) Window” context menu click **[Affected versions]:**
- Firefox Release 73.0.1 Build ID 20200217142647
- Firefox Beta 74.0b7 Build ID 20200221211950
- Firefox Nightly 75.0a1 Build ID 20200225214332
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Ubuntu 16.04
**[Prerequisites]:**
- Have a card from the Highlights section saved to Pocket.
**[Steps to reproduce]:**
1. Click the saved to pocket card from prerequisites.
2. Click the “Open in a New Window” option from the context menu for the same card.
**[Expected result]:**
Both actions redirect the user to the same page.
**[Actual result]:**
At step 1 the user is redirected to an app.getpocket.com specific page.
At step 2 the user is redirected to the original location of the card.
**[Notes]:**
- Reproducing also for “Open in a New Private Window” option.
- We should show consistency while accessing the same card in different ways.
|
P2
|
NEW
|
2020-02-26 12:16:15+00:00
|
2024-02-27 16:49:52+00:00
| 300
| 2
|
|
1618179
|
[about:logins] Hover effect for [Sort by] button triggered of wrong element
|
**Affected versions**
* 74.0b8, 75.0a1 (2020-02-26);
**Affected platforms**
* Windows 10/8.1, Ubuntu 18.04, macOS 10.13;
**Steps to reproduce**
1. Launch Firefox, access about:logins
2. Move the mouse towards the Sort By (Name) button;
**Expected result**
* hover effect triggered when mouse reaches button;
**Actual result**
* hover effect triggered before;
**Regression range**
* will provide one asap;
* might be linked with bug 1584162 at first glimpse;
**Additional notes**
* attached recording with the issue;
|
[about:logins] Hover effect for [Sort by] button triggered of wrong element **Affected versions**
* 74.0b8, 75.0a1 (2020-02-26);
**Affected platforms**
* Windows 10/8.1, Ubuntu 18.04, macOS 10.13;
**Steps to reproduce**
1. Launch Firefox, access about:logins
2. Move the mouse towards the Sort By (Name) button;
**Expected result**
* hover effect triggered when mouse reaches button;
**Actual result**
* hover effect triggered before;
**Regression range**
* will provide one asap;
* might be linked with bug 1584162 at first glimpse;
**Additional notes**
* attached recording with the issue;
|
P3
|
VERIFIED
|
FIXED
|
2020-02-26 13:37:36+00:00
|
2020-11-10 17:45:25+00:00
| 176
| 3
|
1618184
|
The New folder input field is overextended if previously a long title one was created
|
**Affected versions**
* 75.0a1 (2020-02-25)
* 74.0b8
* 73.0
**Affected platforms**
* Windows 10
* macOS 10.15
* Ubuntu 18.04
**Steps to reproduce**
1. Open any site
2. Click on the Star icon inside the address bar
3. Expand the folder section
4. Create a new folder and rename it with a long title (that extends the visible input area)
5. Attempt to create a new folder
**Expected result**
* The New Folder input field keeps its default size
**Actual result**
* The New Folder input field increases its width
**Regression range**
* First bad: b0124f06562982dce60b820d95aad23afd5cec90
* Last good: 1e64b8a0c546a49459d404aaf930d5b1f621246a
* Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1e64b8a0c546a49459d404aaf930d5b1f621246a&tochange=b0124f06562982dce60b820d95aad23afd5cec90
**Additional notes**
* The scrollbar (when enabled) is already overlapped only by clicking the New folder button, but with the steps mentioned above the input field is way out of bound (see the screenshot)
|
The New folder input field is overextended if previously a long title one was created **Affected versions**
* 75.0a1 (2020-02-25)
* 74.0b8
* 73.0
**Affected platforms**
* Windows 10
* macOS 10.15
* Ubuntu 18.04
**Steps to reproduce**
1. Open any site
2. Click on the Star icon inside the address bar
3. Expand the folder section
4. Create a new folder and rename it with a long title (that extends the visible input area)
5. Attempt to create a new folder
**Expected result**
* The New Folder input field keeps its default size
**Actual result**
* The New Folder input field increases its width
**Regression range**
* First bad: b0124f06562982dce60b820d95aad23afd5cec90
* Last good: 1e64b8a0c546a49459d404aaf930d5b1f621246a
* Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1e64b8a0c546a49459d404aaf930d5b1f621246a&tochange=b0124f06562982dce60b820d95aad23afd5cec90
**Additional notes**
* The scrollbar (when enabled) is already overlapped only by clicking the New folder button, but with the steps mentioned above the input field is way out of bound (see the screenshot)
|
P5
|
NEW
|
2020-02-26 13:52:34+00:00
|
2024-09-23 15:44:08+00:00
| 376
| 5
|
|
1618218
|
"Start New Session" should store existing session in sessionstore-backups
|
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
1. Have an existing session.
2. Restart the browser.
3. Accidentally select "Start New Session" instead of "Restore Session."
Actual results:
The old session was destroyed without a current backup in sessionstore-backups. previous.jsonlz4 and the most recent upgrade.jsonlz4-[DATE] were 8 days old.
Expected results:
The most current existing session should be stored in sessionstore-backups when a user clicks "Start New Session."
|
"Start New Session" should store existing session in sessionstore-backups User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
1. Have an existing session.
2. Restart the browser.
3. Accidentally select "Start New Session" instead of "Restore Session."
Actual results:
The old session was destroyed without a current backup in sessionstore-backups. previous.jsonlz4 and the most recent upgrade.jsonlz4-[DATE] were 8 days old.
Expected results:
The most current existing session should be stored in sessionstore-backups when a user clicks "Start New Session."
|
P2
|
NEW
|
2020-02-26 15:00:20+00:00
|
2024-01-05 17:37:26+00:00
| 165
| 2
|
|
1618220
|
Cards/Section context menu dropdowns overlap snippets when the page is scrolled up
|
**[Affected versions]:**
- Firefox Release 73.0.1 Build ID 20200217142647
- Firefox Nightly 75.0a1 Build ID 20200225214332
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Ubuntu 16.04
**[Prerequisites]:**
- Have a snippet displayed.
**[Steps to reproduce]:**
1. Open a New Tab page.
2. Scroll down the page. (not necessarily until the bottom)
3. Click on any card context menu button.
4. Scroll up the page.
5. Observe context menu dropdown.
**[Expected result]:**
The context menu dropdown hides under the snippet.
**[Actual result]:**
The context menu dropdown overlaps the snippet.
**[Notes]:**
- The issue is not reproducible while scrolling the page content (with context menu opened) under the search bar layout.
|
Cards/Section context menu dropdowns overlap snippets when the page is scrolled up **[Affected versions]:**
- Firefox Release 73.0.1 Build ID 20200217142647
- Firefox Nightly 75.0a1 Build ID 20200225214332
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Ubuntu 16.04
**[Prerequisites]:**
- Have a snippet displayed.
**[Steps to reproduce]:**
1. Open a New Tab page.
2. Scroll down the page. (not necessarily until the bottom)
3. Click on any card context menu button.
4. Scroll up the page.
5. Observe context menu dropdown.
**[Expected result]:**
The context menu dropdown hides under the snippet.
**[Actual result]:**
The context menu dropdown overlaps the snippet.
**[Notes]:**
- The issue is not reproducible while scrolling the page content (with context menu opened) under the search bar layout.
|
P3
|
NEW
|
2020-02-26 15:01:51+00:00
|
2022-10-12 00:00:16+00:00
| 245
| 3
|
|
1618229
|
The “Dismiss” button’s icon does not respect the browser’s “Dark” theme colors scheme when hovered
|
**[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID 20200226092757
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64
**[Prerequisites]:**
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.endpoints` set to `http,https`.
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.config` set to `{"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}`.
- Have the value of the pref `browser.search.region` set to `US`.
- The “Dark” theme is enabled in the “Themes” section located in “about:addons”.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab.
3. Hover the “Dismiss” button.
4. Observe the “Dismiss” button’s icon color.
**[Expected result]:**
- The “Dismiss” icon color respects the “Dark” theme colors. (#F9F9FA, Grey 10)
**[Actual result]:**
- The “Dismiss” icon color is #2A2A2E.
**[Notes]:**
- Attached a screen recording of the issue.
|
The “Dismiss” button’s icon does not respect the browser’s “Dark” theme colors scheme when hovered **[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID 20200226092757
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64
**[Prerequisites]:**
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.endpoints` set to `http,https`.
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.config` set to `{"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}`.
- Have the value of the pref `browser.search.region` set to `US`.
- The “Dark” theme is enabled in the “Themes” section located in “about:addons”.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab.
3. Hover the “Dismiss” button.
4. Observe the “Dismiss” button’s icon color.
**[Expected result]:**
- The “Dismiss” icon color respects the “Dark” theme colors. (#F9F9FA, Grey 10)
**[Actual result]:**
- The “Dismiss” icon color is #2A2A2E.
**[Notes]:**
- Attached a screen recording of the issue.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-26 15:19:28+00:00
|
2020-03-04 11:50:23+00:00
| 453
| 1
|
1618268
|
Wrong context menu is displayed when right click on the website's link while in Edit mode
|
[Affected Versions]:
- Nightly 75.0a1
- Beta 74.0b7
- Firefox 73.0.1
[Affected Platforms]
- All Windows
- All Mac
- All Linux
[Prerequisites]
- Have a Firefox profile with multiple logins saved.
[Steps to reproduce]:
1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to "about:logins" page.
3. Select any saved login from the login list.
4. Click the "Edit" button.
5. Right click on the website's link.
3. Observe the opened context menu.
[Expected results]:
- The context menu with the "open/copy link" options is displayed.
[Actual results]:
- The context menu with the "Undo/Cut/Paste/Delete" options is displayed.
[Notes]:
- It seems that the link displayed in "Edit" mode has a different format than the link displayed in the Login item.
- Attached a screen recording with the issue.
|
Wrong context menu is displayed when right click on the website's link while in Edit mode [Affected Versions]:
- Nightly 75.0a1
- Beta 74.0b7
- Firefox 73.0.1
[Affected Platforms]
- All Windows
- All Mac
- All Linux
[Prerequisites]
- Have a Firefox profile with multiple logins saved.
[Steps to reproduce]:
1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to "about:logins" page.
3. Select any saved login from the login list.
4. Click the "Edit" button.
5. Right click on the website's link.
3. Observe the opened context menu.
[Expected results]:
- The context menu with the "open/copy link" options is displayed.
[Actual results]:
- The context menu with the "Undo/Cut/Paste/Delete" options is displayed.
[Notes]:
- It seems that the link displayed in "Edit" mode has a different format than the link displayed in the Login item.
- Attached a screen recording with the issue.
|
P3
|
VERIFIED
|
FIXED
|
2020-02-26 17:10:38+00:00
|
2020-03-04 12:11:45+00:00
| 240
| 3
|
1618354
|
Headless firefox is very slow to start up/shut down when another firefox is open
|
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36
Steps to reproduce:
1. Open normal firefox
2. Run the command
```
time firefox -headless -screenshot="a.png" about:blank
```
Actual results:
firefox -headless -screenshot="a.png" about:blank 0.09s user 0.04s system 2% cpu 5.156 total
5 seconds!
Expected results:
If there was not another instance of firefox open:
firefox -headless -screenshot="a.png" about:blank 0.96s user 0.39s system 196% cpu 0.691 total
0.7 seconds!
Compare this to chrome:
google-chrome --headless --screenshot="a.png" about:blank 0.14s user 0.12s system 99% cpu 0.262 total
0.26 seconds!
|
Headless firefox is very slow to start up/shut down when another firefox is open User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36
Steps to reproduce:
1. Open normal firefox
2. Run the command
```
time firefox -headless -screenshot="a.png" about:blank
```
Actual results:
firefox -headless -screenshot="a.png" about:blank 0.09s user 0.04s system 2% cpu 5.156 total
5 seconds!
Expected results:
If there was not another instance of firefox open:
firefox -headless -screenshot="a.png" about:blank 0.96s user 0.39s system 196% cpu 0.691 total
0.7 seconds!
Compare this to chrome:
google-chrome --headless --screenshot="a.png" about:blank 0.14s user 0.12s system 99% cpu 0.262 total
0.26 seconds!
|
P3
|
RESOLVED
|
INCOMPLETE
|
2020-02-26 21:00:51+00:00
|
2022-08-01 12:20:58+00:00
| 266
| 3
|
1618466
|
The “Collection Title” section title does not respect the browser’s “Dark” theme colors scheme
|
**[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID 20200226213903
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64
**[Prerequisites]:**
- Have the value of the pref browser.newtabpage.activity-stream.discoverystream.endpoints set to http,https.
- Have the value of the pref browser.newtabpage.activity-stream.discoverystream.config set to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}.
- Have the value of the pref browser.search.region set to US.
- The “Dark” theme is enabled in the “Themes” section located in “about:addons”.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab.
3. Open the “DOM and Style Inspector” by using CTRL/CMD+SHIFT+C.
4. Hover the “Collection title” and click it.
5. Observe the color displayed in the “Rules View list” section under “This Element”.
**[Expected result]:**
- The “Collection title” color displayed in “Inspector” is #D7D7DB.
**[Actual result]:**
- The “Collection title” color displayed in “Inspector” is #F9F9FA.
**[Notes]:**
- Attached a screen recording of the issue.
|
The “Collection Title” section title does not respect the browser’s “Dark” theme colors scheme **[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID 20200226213903
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64
**[Prerequisites]:**
- Have the value of the pref browser.newtabpage.activity-stream.discoverystream.endpoints set to http,https.
- Have the value of the pref browser.newtabpage.activity-stream.discoverystream.config set to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}.
- Have the value of the pref browser.search.region set to US.
- The “Dark” theme is enabled in the “Themes” section located in “about:addons”.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab.
3. Open the “DOM and Style Inspector” by using CTRL/CMD+SHIFT+C.
4. Hover the “Collection title” and click it.
5. Observe the color displayed in the “Rules View list” section under “This Element”.
**[Expected result]:**
- The “Collection title” color displayed in “Inspector” is #D7D7DB.
**[Actual result]:**
- The “Collection title” color displayed in “Inspector” is #F9F9FA.
**[Notes]:**
- Attached a screen recording of the issue.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-27 08:12:45+00:00
|
2020-03-04 11:50:57+00:00
| 470
| 1
|
1618477
|
The permissions prompt is not displayed by clicking on the control sharing panel
|
#### Affected versions:
ALL
#### Affected platforms:
Windows 10, Ubuntu 18.04
#### Steps:
1. Launch Firefox with a new profile and go to: https://joo.crater.uberspace.de/frame-permissions.html
2. Click on the notifications icon and click on "Allow notifications".
3. Click on the Camera or Microphone button from "https://permission.site with FP allowed" iFrame and click Allow.
4. In the "https://permission.site with FP allowed" iFrame right click -> This Frame -> Open Frame in New Tab.
5. In the new tab opened click on the Camera or Microphone and allow access.
6. Click on the Camera/Microphone icon from control sharing panel (the small upper panel).
#### Actual result:
The permission prompt is not displayed.
#### Expected result:
The permissions prompt should be displayed by clicking on the control sharing panel.
Note: This issue only occurs on Windows and Ubuntu, on Mac the permission prompt is displayed.
Please see the video attachment for a better understanding.
|
The permissions prompt is not displayed by clicking on the control sharing panel #### Affected versions:
ALL
#### Affected platforms:
Windows 10, Ubuntu 18.04
#### Steps:
1. Launch Firefox with a new profile and go to: https://joo.crater.uberspace.de/frame-permissions.html
2. Click on the notifications icon and click on "Allow notifications".
3. Click on the Camera or Microphone button from "https://permission.site with FP allowed" iFrame and click Allow.
4. In the "https://permission.site with FP allowed" iFrame right click -> This Frame -> Open Frame in New Tab.
5. In the new tab opened click on the Camera or Microphone and allow access.
6. Click on the Camera/Microphone icon from control sharing panel (the small upper panel).
#### Actual result:
The permission prompt is not displayed.
#### Expected result:
The permissions prompt should be displayed by clicking on the control sharing panel.
Note: This issue only occurs on Windows and Ubuntu, on Mac the permission prompt is displayed.
Please see the video attachment for a better understanding.
|
P3
|
RESOLVED
|
FIXED
|
2020-02-27 09:22:34+00:00
|
2020-06-13 22:51:30+00:00
| 266
| 3
|
1618553
|
pdf viewer should not fire the load event until it's ready for printing
|
Apparently this is something people commonly do: create an iframe pointing to a pdf, and in its load handler try to print. See bug 911444 comment 87 and some of the preceding comments.
The problem is that we currently fire the load event before `pageViewsReady` becomes true, because Gecko has no idea that's going on behind the scenes and thinks the pageload is done. Can we delay it until it's true? I can expose platform APIs here if needed, but someone who actually knows the PDF viewer should handle that side.
|
pdf viewer should not fire the load event until it's ready for printing Apparently this is something people commonly do: create an iframe pointing to a pdf, and in its load handler try to print. See bug 911444 comment 87 and some of the preceding comments.
The problem is that we currently fire the load event before `pageViewsReady` becomes true, because Gecko has no idea that's going on behind the scenes and thinks the pageload is done. Can we delay it until it's true? I can expose platform APIs here if needed, but someone who actually knows the PDF viewer should handle that side.
|
P1
|
RESOLVED
|
FIXED
|
2020-02-27 15:11:25+00:00
|
2021-02-11 07:38:28+00:00
| 134
| 1
|
1618626
|
Make programmatic printing of iframes containing PDFs sane
|
Right now there are various issues. See bug 911444 and its many dups for how much people want this. Other bugs blocking this one are also blockers for the actual thing people want to do.
|
Make programmatic printing of iframes containing PDFs sane Right now there are various issues. See bug 911444 and its many dups for how much people want this. Other bugs blocking this one are also blockers for the actual thing people want to do.
|
P1
|
RESOLVED
|
FIXED
|
2020-02-27 18:52:19+00:00
|
2021-02-10 14:25:11+00:00
| 56
| 1
|
1618662
|
Typing 'about:config' has a large jank during autocompletion
|
I get a large hang after typing the 'c' in about:config.
Here's the profile: https://perfht.ml/3cfolw8
|
Typing 'about:config' has a large jank during autocompletion I get a large hang after typing the 'c' in about:config.
Here's the profile: https://perfht.ml/3cfolw8
|
P1
|
RESOLVED
|
FIXED
|
2020-02-27 20:51:19+00:00
|
2020-04-06 13:22:20+00:00
| 60
| 1
|
1618721
|
Title separators became really hard to see, even more so when hovering an autocomplete item
|
Regressed by bug 1585994.
See attached before/after screenshots.
This was caused by this change:
https://hg.mozilla.org/mozilla-central/rev/739ac41b66834c61bb21e5b6a4411b456294b9f5#l2.32
Reverting it fixes it locally.
|
Title separators became really hard to see, even more so when hovering an autocomplete item Regressed by bug 1585994.
See attached before/after screenshots.
This was caused by this change:
https://hg.mozilla.org/mozilla-central/rev/739ac41b66834c61bb21e5b6a4411b456294b9f5#l2.32
Reverting it fixes it locally.
|
P2
|
VERIFIED
|
FIXED
|
2020-02-28 00:37:21+00:00
|
2020-03-20 13:35:58+00:00
| 112
| 2
|
1618783
|
Context menu mostly blank in window opened by -private-window command line option
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Right-click inside any tab (that doesn't disable context menu) in a private navigation window opened with command-line option -private-window. Menu actions are OK but have to blindly guess what line to clic!
Tried again after disabling all my extensions, same result. Tried both at home and office computers (both Windows 10 Pro v.1909, both Firefox 73). Bug didn't exist in older Firefox versions (not sure for v72).
Actual results:
Most of the context menu was blank (no visible text) except for top-line icons and extensions-provided options. However, sub-menu items of an blank item are visible.
Opening a private browsing window with the "mask" button or Ctrl-Shift+P doesn't produce the bug (context menu is displayed properly).
Expected results:
A readable context menu.
|
Context menu mostly blank in window opened by -private-window command line option User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Right-click inside any tab (that doesn't disable context menu) in a private navigation window opened with command-line option -private-window. Menu actions are OK but have to blindly guess what line to clic!
Tried again after disabling all my extensions, same result. Tried both at home and office computers (both Windows 10 Pro v.1909, both Firefox 73). Bug didn't exist in older Firefox versions (not sure for v72).
Actual results:
Most of the context menu was blank (no visible text) except for top-line icons and extensions-provided options. However, sub-menu items of an blank item are visible.
Opening a private browsing window with the "mask" button or Ctrl-Shift+P doesn't produce the bug (context menu is displayed properly).
Expected results:
A readable context menu.
|
P3
|
UNCONFIRMED
|
2020-02-28 08:54:28+00:00
|
2022-10-24 12:17:03+00:00
| 248
| 3
|
|
1618870
|
The “Collection” section is wrongly dismissed when a collection card is dismissed, archived, or deleted from Pocket
|
**[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID: 20200228092428
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64
**[Prerequisites]:**
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.endpoints` set to `http,https`.
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.config` set to `{"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}`.
- Have the value of the pref` browser.search.region` set to `US`.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab and hover a card from the “Collection” section.
3. Click the “Open menu” button and select the “Dismiss” option.
4. Observe the “Collection” section.
**[Expected result]:**
- The “Collection” section only has 2 cards left and the dismissed card disappears.
**[Actual result]:**
- The “Collection” section is completely dismissed.
**[Notes]:**
- This issue is also reproducible if the “Archive to pocket” or “Delete from Pocket” options are selected instead.
- If a “Sponsored Card” from the “Recommended by Pocket” section that has a URL shared with a card from the “Collection” section is dismissed, archived, or deleted from Pocket, the whole “Collection” section is dismissed.
- Attached a screen recording of the issue.
|
The “Collection” section is wrongly dismissed when a collection card is dismissed, archived, or deleted from Pocket **[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID: 20200228092428
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64
**[Prerequisites]:**
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.endpoints` set to `http,https`.
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.config` set to `{"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}`.
- Have the value of the pref` browser.search.region` set to `US`.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab and hover a card from the “Collection” section.
3. Click the “Open menu” button and select the “Dismiss” option.
4. Observe the “Collection” section.
**[Expected result]:**
- The “Collection” section only has 2 cards left and the dismissed card disappears.
**[Actual result]:**
- The “Collection” section is completely dismissed.
**[Notes]:**
- This issue is also reproducible if the “Archive to pocket” or “Delete from Pocket” options are selected instead.
- If a “Sponsored Card” from the “Recommended by Pocket” section that has a URL shared with a card from the “Collection” section is dismissed, archived, or deleted from Pocket, the whole “Collection” section is dismissed.
- Attached a screen recording of the issue.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-28 14:18:36+00:00
|
2020-03-10 16:07:10+00:00
| 505
| 1
|
1618878
|
Synced tabs results disappear when the 2-lines layout is displayed
|
[screencast attached]
STR:
1. Enter a query in the Urlbar that would cause synced tab results to appear. Just searching the open tabs restriction character, "%", is probably easiest.
2. Shrink the window horizontally until you pass the threshold where 2-line results would appear in the Urlbar.
Expected:
All the same results appear in the Urlbar.
Actual:
All the synced tab results disappear. They reappear when the window is expanded.
|
Synced tabs results disappear when the 2-lines layout is displayed [screencast attached]
STR:
1. Enter a query in the Urlbar that would cause synced tab results to appear. Just searching the open tabs restriction character, "%", is probably easiest.
2. Shrink the window horizontally until you pass the threshold where 2-line results would appear in the Urlbar.
Expected:
All the same results appear in the Urlbar.
Actual:
All the synced tab results disappear. They reappear when the window is expanded.
|
P1
|
RESOLVED
|
FIXED
|
2020-02-28 14:45:50+00:00
|
2020-03-05 21:55:41+00:00
| 118
| 1
|
1618892
|
Interventions button stays pressed when mouse is moved to another area
|
Checked on Windows10 64bit + Ubuntu 18.04 64bit + Macos 10.14
Firefox Beta 74.0b8 disabled
Firefox Nightly 75.0a1 affected
Firefox Release 73.0.1 not affected
Steps to reproduce:
- set user.js with these 2 lines
user_pref("browser.urlbar.update1", true);
user_pref("browser.urlbar.update1.interventions", true);
- Create new profile with the user.js
- Launch firefox
- In URL bar type "refresh firefox"
- hover mouse on button "Refresh"
- left mouse click on button and keep it pressed
- move mouse arrow away from button
Results: Button stays selected and pressed.
Expected result: if you click, then move the mouse out of button then release, it shouldn't do button_pressed
Notes:
Same thing happens to the button next to it "get help" Question mark.
Also happens with other buttons interventions like:
"Cache firefox"
"refresh firefox"
"update firefox"
|
Interventions button stays pressed when mouse is moved to another area Checked on Windows10 64bit + Ubuntu 18.04 64bit + Macos 10.14
Firefox Beta 74.0b8 disabled
Firefox Nightly 75.0a1 affected
Firefox Release 73.0.1 not affected
Steps to reproduce:
- set user.js with these 2 lines
user_pref("browser.urlbar.update1", true);
user_pref("browser.urlbar.update1.interventions", true);
- Create new profile with the user.js
- Launch firefox
- In URL bar type "refresh firefox"
- hover mouse on button "Refresh"
- left mouse click on button and keep it pressed
- move mouse arrow away from button
Results: Button stays selected and pressed.
Expected result: if you click, then move the mouse out of button then release, it shouldn't do button_pressed
Notes:
Same thing happens to the button next to it "get help" Question mark.
Also happens with other buttons interventions like:
"Cache firefox"
"refresh firefox"
"update firefox"
|
P3
|
RESOLVED
|
FIXED
|
2020-02-28 15:17:54+00:00
|
2020-07-09 04:33:02+00:00
| 252
| 3
|
1618936
|
An increase in the number of tabs not correctly connecting to content processes are being reported for recent Nightlies
|
Both tbabos and shorlander have been seeing this behaviour over the past two days or so.
From what I can gather, tabs don't have nsIRemoteTab available off of their browser's frameloaders, so a bunch of stuff in the front-end breaks because it's not designed to handle the case where the frameloader didn't successfully connect to a content process.
Putting this in DOM :: Content Processes for now, but perhaps this could also belong in Firefox :: Tabbed Browser, in the event that we're not handling a failure case properly here.
|
An increase in the number of tabs not correctly connecting to content processes are being reported for recent Nightlies Both tbabos and shorlander have been seeing this behaviour over the past two days or so.
From what I can gather, tabs don't have nsIRemoteTab available off of their browser's frameloaders, so a bunch of stuff in the front-end breaks because it's not designed to handle the case where the frameloader didn't successfully connect to a content process.
Putting this in DOM :: Content Processes for now, but perhaps this could also belong in Firefox :: Tabbed Browser, in the event that we're not handling a failure case properly here.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-28 18:09:15+00:00
|
2020-04-15 20:55:22+00:00
| 150
| 1
|
1618938
|
[macOS] Menulists in the prefs are not tall enough
|
Today in "no good deed goes unpunished" - I regressed this in bug 1616008 because I missed the macOS-only rule at https://searchfox.org/mozilla-central/rev/a3266997560904b484fd89d6a6bcdeace4a13652/toolkit/themes/osx/global/menulist.css#15 , which takes precedence over the `menulist` rule in the prefs, so it sets `min-height` to `20px` instead of `30px`.
|
[macOS] Menulists in the prefs are not tall enough Today in "no good deed goes unpunished" - I regressed this in bug 1616008 because I missed the macOS-only rule at https://searchfox.org/mozilla-central/rev/a3266997560904b484fd89d6a6bcdeace4a13652/toolkit/themes/osx/global/menulist.css#15 , which takes precedence over the `menulist` rule in the prefs, so it sets `min-height` to `20px` instead of `30px`.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-28 18:13:47+00:00
|
2020-03-24 07:22:31+00:00
| 149
| 1
|
1618990
|
Potentially confusing text on Protections drop-down regarding blocked cookies when site cookies are whitelisted
|
So I have all cookies blocked globally in my Firefox Nightly settings. I then whitelist sites I use frequently. For example, under the `Protections for bugzilla.mozilla.org` drop-down, it shows
```
Blocked
All Cookies >
```
(see https://i.imgur.com/1046uuK.png) and when you select `All Cookies` it shows https://bugzilla.mozilla.org (see https://i.imgur.com/qh5PlQe.png ). Which it really shouldn't, because if I select `Site information for bugzilla.mozilla.org` it shows that I have allowed the Set Cookies permission (see https://i.imgur.com/iJjTJ9j.png).
|
Potentially confusing text on Protections drop-down regarding blocked cookies when site cookies are whitelisted So I have all cookies blocked globally in my Firefox Nightly settings. I then whitelist sites I use frequently. For example, under the `Protections for bugzilla.mozilla.org` drop-down, it shows
```
Blocked
All Cookies >
```
(see https://i.imgur.com/1046uuK.png) and when you select `All Cookies` it shows https://bugzilla.mozilla.org (see https://i.imgur.com/qh5PlQe.png ). Which it really shouldn't, because if I select `Site information for bugzilla.mozilla.org` it shows that I have allowed the Set Cookies permission (see https://i.imgur.com/iJjTJ9j.png).
|
P3
|
RESOLVED
|
WORKSFORME
|
2020-02-28 21:16:40+00:00
|
2024-12-10 11:28:06+00:00
| 206
| 3
|
1619036
|
In full screen mode, the toolbar context menu does not allow toolbar customization or changing bookmarks toolbar visibility
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
Open context menu on tool bar in full screen mode.
Actual results:
The context menu shows wrong items.
Expected results:
I expected items like non full screen mode.
|
In full screen mode, the toolbar context menu does not allow toolbar customization or changing bookmarks toolbar visibility User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
Open context menu on tool bar in full screen mode.
Actual results:
The context menu shows wrong items.
Expected results:
I expected items like non full screen mode.
|
P2
|
NEW
|
2020-02-29 01:53:58+00:00
|
2021-07-19 03:09:41+00:00
| 103
| 2
|
|
1619069
|
new tab page shows sponsored content in wrong language
|
There is sponsored content in the Pocket section of the new tab page. But the sponsored content does not follow the language of Firefox. I attached a screenshot that shows a German Firefox with German Pocket stories and an English sponsored story. This one is not the only one in English I saw today. Firefox should never show content in the wrong language because not everyone speaks English.
(I am using Firefox Nightly 75)
|
new tab page shows sponsored content in wrong language There is sponsored content in the Pocket section of the new tab page. But the sponsored content does not follow the language of Firefox. I attached a screenshot that shows a German Firefox with German Pocket stories and an English sponsored story. This one is not the only one in English I saw today. Firefox should never show content in the wrong language because not everyone speaks English.
(I am using Firefox Nightly 75)
|
P1
|
RESOLVED
|
WONTFIX
|
2020-02-29 13:15:01+00:00
|
2020-03-30 17:39:47+00:00
| 101
| 1
|
1619099
|
The gray box with "Timed Out" on it on all websites.
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
The little gray box saying "Timed Out" occurs as a bug this day.
Actual results:
A little gray box with "Timed Out" was seen at the lower-left hand corner of the browser, meaning that there's a bug in the loading / connecting / performing TLS handshake bar. If you move the cursor towards it, the bar will move the right hand corner of the screen, but will revert to the left hand. Anyone else has the same?
Expected results:
It happened today.
|
The gray box with "Timed Out" on it on all websites. User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
The little gray box saying "Timed Out" occurs as a bug this day.
Actual results:
A little gray box with "Timed Out" was seen at the lower-left hand corner of the browser, meaning that there's a bug in the loading / connecting / performing TLS handshake bar. If you move the cursor towards it, the bar will move the right hand corner of the screen, but will revert to the left hand. Anyone else has the same?
Expected results:
It happened today.
|
P1
|
RESOLVED
|
INCOMPLETE
|
2020-02-29 23:02:19+00:00
|
2021-03-27 17:51:29+00:00
| 168
| 1
|
1619122
|
Firefox don't listed in context menu "open with..." with file type .jpg extension
|
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
With version 73.0.1 Firefox. Right click on file with .jpg extension
Actual results:
Since installation of version 73.01, Firefox is no longer offered in the list of the context menu "Open with ..." when you right-click on a .jpg file
Expected results:
Firefox should have been offered in the list of applications in the context menu "Open with ..."
|
Firefox don't listed in context menu "open with..." with file type .jpg extension User Agent: Mozilla/5.0 (Windows NT 6.1; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
With version 73.0.1 Firefox. Right click on file with .jpg extension
Actual results:
Since installation of version 73.01, Firefox is no longer offered in the list of the context menu "Open with ..." when you right-click on a .jpg file
Expected results:
Firefox should have been offered in the list of applications in the context menu "Open with ..."
|
P1
|
VERIFIED
|
FIXED
|
2020-03-01 08:01:18+00:00
|
2020-11-06 19:53:30+00:00
| 155
| 1
|
1619152
|
The ARES-6 benchmark fails when restored from previous session
|
The ARES-6 benchmark crashes on start.
Steps to reproduce:
1. Open https://browserbench.org/ARES-6/index.html
2. Click START.
The "START" button text changes to "Test failure — error in console", and the console displays:
```
Error encountered: ReferenceError: AirBenchmark is not defined https://browserbench.org/ARES-6/index.html line 170 > scriptElement 32 17 ReferenceError: "AirBenchmark is not defined"
<anonymous> https://browserbench.org/ARES-6/index.html line 170 > scriptElement:32
_iterate https://browserbench.org/ARES-6/driver.js:170
setTimeout handler*_iterate https://browserbench.org/ARES-6/driver.js:161
start https://browserbench.org/ARES-6/driver.js:73
driver https://browserbench.org/ARES-6/glue.js:31
readyTrigger https://browserbench.org/ARES-6/driver.js:49
<anonymous> https://browserbench.org/ARES-6/glue.js:54
```
followed by a bunch of warnings like:
```
‘src’ attribute of <script> element is not a valid URI: “Air/symbols.js”
```
The benchmark fails in Nightly 75.0a1 (2020-02-29) & 75.0a1 (2020-03-01). It worked in recent Nightly versions, I think even in the immediately preceding one to the one from 2020-02-29.
|
The ARES-6 benchmark fails when restored from previous session The ARES-6 benchmark crashes on start.
Steps to reproduce:
1. Open https://browserbench.org/ARES-6/index.html
2. Click START.
The "START" button text changes to "Test failure — error in console", and the console displays:
```
Error encountered: ReferenceError: AirBenchmark is not defined https://browserbench.org/ARES-6/index.html line 170 > scriptElement 32 17 ReferenceError: "AirBenchmark is not defined"
<anonymous> https://browserbench.org/ARES-6/index.html line 170 > scriptElement:32
_iterate https://browserbench.org/ARES-6/driver.js:170
setTimeout handler*_iterate https://browserbench.org/ARES-6/driver.js:161
start https://browserbench.org/ARES-6/driver.js:73
driver https://browserbench.org/ARES-6/glue.js:31
readyTrigger https://browserbench.org/ARES-6/driver.js:49
<anonymous> https://browserbench.org/ARES-6/glue.js:54
```
followed by a bunch of warnings like:
```
‘src’ attribute of <script> element is not a valid URI: “Air/symbols.js”
```
The benchmark fails in Nightly 75.0a1 (2020-02-29) & 75.0a1 (2020-03-01). It worked in recent Nightly versions, I think even in the immediately preceding one to the one from 2020-02-29.
|
P3
|
REOPENED
|
2020-03-01 18:12:59+00:00
|
2023-11-12 01:22:58+00:00
| 394
| 3
|
|
1619170
|
LinkHandlerChild has a useless "dispatcher" constructor argument
|
All it does with it is pass it to `super()`, but `JSWindowActorChild` does not take any constructor arguments.
Possible regression from bug 1592157? Before that it looks like the superclass was `ActorChild`, which actually does expect a dispatcher.
|
LinkHandlerChild has a useless "dispatcher" constructor argument All it does with it is pass it to `super()`, but `JSWindowActorChild` does not take any constructor arguments.
Possible regression from bug 1592157? Before that it looks like the superclass was `ActorChild`, which actually does expect a dispatcher.
|
P3
|
RESOLVED
|
FIXED
|
2020-03-01 23:46:21+00:00
|
2020-03-05 22:11:42+00:00
| 78
| 3
|
1619228
|
The user is able to add a separator to the Address Bar
|
**Affected versions**
- Firefox 68.5.0esr
- Firefox 73.0.1
- Firefox 74.0b9
- Firefox 75.0a1
**Affected platforms**
- Windows 10 & 7
- Ubuntu 18.04
- macOS 10.15 & 10.13
**Steps to reproduce**
1. Launch Firefox
2. Open a page, for example [Wikipedia](https://www.wikipedia.org) to trigger the extra controls from the Address Bar
3. Access the dropdown from the three dots and spam right click on the separator until the popup with Add to address bar is shown
**Expected result**
- The separator can't be added to Address Bar
**Actual result**
- The separator can be added to the Address Bar
**Regression range**
- I will see for a regression range.
**Additional notes**
- The issue can be seen in the attachment.
- There are only some points on the separator which will trigger the Add to address bar option.
|
The user is able to add a separator to the Address Bar **Affected versions**
- Firefox 68.5.0esr
- Firefox 73.0.1
- Firefox 74.0b9
- Firefox 75.0a1
**Affected platforms**
- Windows 10 & 7
- Ubuntu 18.04
- macOS 10.15 & 10.13
**Steps to reproduce**
1. Launch Firefox
2. Open a page, for example [Wikipedia](https://www.wikipedia.org) to trigger the extra controls from the Address Bar
3. Access the dropdown from the three dots and spam right click on the separator until the popup with Add to address bar is shown
**Expected result**
- The separator can't be added to Address Bar
**Actual result**
- The separator can be added to the Address Bar
**Regression range**
- I will see for a regression range.
**Additional notes**
- The issue can be seen in the attachment.
- There are only some points on the separator which will trigger the Add to address bar option.
|
P2
|
RESOLVED
|
FIXED
|
2020-03-02 10:08:18+00:00
|
2020-03-05 17:59:07+00:00
| 252
| 2
|
1619314
|
[Protection Report] The icon of the Mobile Call Out Card not visible enough in High Contrast Mode
|
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Build ID: 20200302094818
**Affected versions**
Nightly 75.0a1
**Affected platforms**
* Windows 10 x64
* Windows 7
**Prerequisites:**
* Start menu -> Settings - Turn high contrast on or off - Enable the high contrast and choose one of the dark themes
* In about:config change the pref "browser.contentblocking.report.show_mobile_app" to "true"
**Steps to reproduce**
1. Open Firefox.
2. Go to about: protections
3. Observe the "Mobile Call Card" icon
**Expected result**
* The "Mobile Call Card" icon is correctly displayed.
**Actual result**
* By comparison to other icons on the page, the icon of the "Mobile Call Card" is not properly displayed - the mobile shape is not visible enough.
**Additional notes**
* For more details, please see the screenshot.
|
[Protection Report] The icon of the Mobile Call Out Card not visible enough in High Contrast Mode Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Build ID: 20200302094818
**Affected versions**
Nightly 75.0a1
**Affected platforms**
* Windows 10 x64
* Windows 7
**Prerequisites:**
* Start menu -> Settings - Turn high contrast on or off - Enable the high contrast and choose one of the dark themes
* In about:config change the pref "browser.contentblocking.report.show_mobile_app" to "true"
**Steps to reproduce**
1. Open Firefox.
2. Go to about: protections
3. Observe the "Mobile Call Card" icon
**Expected result**
* The "Mobile Call Card" icon is correctly displayed.
**Actual result**
* By comparison to other icons on the page, the icon of the "Mobile Call Card" is not properly displayed - the mobile shape is not visible enough.
**Additional notes**
* For more details, please see the screenshot.
|
P3
|
VERIFIED
|
FIXED
|
2020-03-02 15:34:40+00:00
|
2020-04-29 09:05:00+00:00
| 263
| 3
|
1619318
|
The "X" button inside the cards is not focused while navigation with Tab key
|
**Affected versions**
* latest Nightly 75.0a1
**Affected platforms**
* Windows 10 x64
* macOS 10.15
* Ubuntu 18.04 x64
**Steps to reproduce**
1. Launch Firefox and navigate to "about:protections".
3. Navigate using the Tab key to the “X” button from the “Take your passwords everywhere” or “Block ad trackers across more devices” cards (to enable this last card you need to change the `browser.contentblocking.report.show_mobile_app` to true)
**Expected result**
- The “X” button is focused.
**Actual result**
- The “X” button cannot be focused; when reaching the iOS link from the card, it goes to the next button/link, skipping the close button.
**Regression range**
* This doesn’t seem to be a regression, I was able to reproduce this on an older Nightly build as well, e.g 75.0a1 (2020-02-25); one of the first builds with these banners implemented.
|
The "X" button inside the cards is not focused while navigation with Tab key **Affected versions**
* latest Nightly 75.0a1
**Affected platforms**
* Windows 10 x64
* macOS 10.15
* Ubuntu 18.04 x64
**Steps to reproduce**
1. Launch Firefox and navigate to "about:protections".
3. Navigate using the Tab key to the “X” button from the “Take your passwords everywhere” or “Block ad trackers across more devices” cards (to enable this last card you need to change the `browser.contentblocking.report.show_mobile_app` to true)
**Expected result**
- The “X” button is focused.
**Actual result**
- The “X” button cannot be focused; when reaching the iOS link from the card, it goes to the next button/link, skipping the close button.
**Regression range**
* This doesn’t seem to be a regression, I was able to reproduce this on an older Nightly build as well, e.g 75.0a1 (2020-02-25); one of the first builds with these banners implemented.
|
P2
|
VERIFIED
|
FIXED
|
2020-03-02 15:42:41+00:00
|
2020-04-14 15:41:04+00:00
| 252
| 2
|
1619442
|
Style status panel with visibility: hidden when not shown.
|
Currently the inactive `#statuspanel` is styled with opacity:0 when hidden.
Accessibility APIs exposed opacity:0 elements and most screen readers will read such content.
It would be useful if it is styled as visibility: hidden, so it is fully purged from the tree.
|
Style status panel with visibility: hidden when not shown. Currently the inactive `#statuspanel` is styled with opacity:0 when hidden.
Accessibility APIs exposed opacity:0 elements and most screen readers will read such content.
It would be useful if it is styled as visibility: hidden, so it is fully purged from the tree.
|
P1
|
RESOLVED
|
FIXED
|
2020-03-02 22:46:21+00:00
|
2020-03-05 14:46:09+00:00
| 75
| 1
|
1619466
|
DllBlocklist entries in BROWSER_PROCESS are blocked in the child process
|
Our blocklist consists of `ALL_PROCESSES`, `BROWSER_PROCESS`, and `CHILD_PROCESSES` in [WindowsDllBlocklistDefs.in](https://searchfox.org/mozilla-central/source/mozglue/dllservices/WindowsDllBlocklistDefs.in). Contrary to the name, entries of `BROWSER_PROCESS` are blocked not only in the browser process but also in the child process. On the other hand, entries of `CHILD_PROCESSES` are blocked only in the child process.
I think the variable `BROWSER_PROCESS` is a placeholder to define a new blocklist variable which is [commented out](https://searchfox.org/mozilla-central/rev/91f6c02fcf4c16f78fdc4417f61f192688294066/mozglue/dllservices/gen_dll_blocklist_defs.py#360) for now.
Since 73, we activate the same blocklist in the content process. We could implement `BROWSER_PROCESS` in the same way as `CHILD_PROCESSES` works.
|
DllBlocklist entries in BROWSER_PROCESS are blocked in the child process Our blocklist consists of `ALL_PROCESSES`, `BROWSER_PROCESS`, and `CHILD_PROCESSES` in [WindowsDllBlocklistDefs.in](https://searchfox.org/mozilla-central/source/mozglue/dllservices/WindowsDllBlocklistDefs.in). Contrary to the name, entries of `BROWSER_PROCESS` are blocked not only in the browser process but also in the child process. On the other hand, entries of `CHILD_PROCESSES` are blocked only in the child process.
I think the variable `BROWSER_PROCESS` is a placeholder to define a new blocklist variable which is [commented out](https://searchfox.org/mozilla-central/rev/91f6c02fcf4c16f78fdc4417f61f192688294066/mozglue/dllservices/gen_dll_blocklist_defs.py#360) for now.
Since 73, we activate the same blocklist in the content process. We could implement `BROWSER_PROCESS` in the same way as `CHILD_PROCESSES` works.
|
P3
|
RESOLVED
|
FIXED
|
2020-03-02 23:56:27+00:00
|
2020-03-09 03:46:53+00:00
| 279
| 3
|
1619503
|
Update experiments doc for the extensions.experiments.enabled pref
|
Starting in 74, the new `extensions.experiments.enabled` pref is required to allow unsigned addons to use privileged APIs, apparently even temporarily loaded addons. This pref is false by default. Info here (thanks to Harry for finding this): https://mail.mozilla.org/pipermail/dev-addons/2020-January/004261.html
This is an important change because previously a temporarily loaded addon could use privileged APIs in any build where the build setting `MOZ_ALLOW_LEGACY_EXTENSIONS` was true. iow you didn't have to do anything as long as you were testing in a Nightly or one-off build. Now you have to set `extensions.experiments.enabled` to true since it defaults to false, or your addon won't work.
Would be worth talking to Shane about defaulting it to true on Nightly and other unbranded builds, although I bet there's a reason it's false.
|
Update experiments doc for the extensions.experiments.enabled pref Starting in 74, the new `extensions.experiments.enabled` pref is required to allow unsigned addons to use privileged APIs, apparently even temporarily loaded addons. This pref is false by default. Info here (thanks to Harry for finding this): https://mail.mozilla.org/pipermail/dev-addons/2020-January/004261.html
This is an important change because previously a temporarily loaded addon could use privileged APIs in any build where the build setting `MOZ_ALLOW_LEGACY_EXTENSIONS` was true. iow you didn't have to do anything as long as you were testing in a Nightly or one-off build. Now you have to set `extensions.experiments.enabled` to true since it defaults to false, or your addon won't work.
Would be worth talking to Shane about defaulting it to true on Nightly and other unbranded builds, although I bet there's a reason it's false.
|
P3
|
RESOLVED
|
FIXED
|
2020-03-03 06:48:31+00:00
|
2021-02-02 04:35:06+00:00
| 224
| 3
|
1619517
|
Tooltip missing for the the "X" button inside the cards
|
**Affected versions**
* latest Nightly 75.0a1
**Affected platforms**
* Windows 10 x64
* macOS 10.15
* Ubuntu 18.04 x64
**Prerequisites**
* In about:config, set the preference "browser.contentblocking.report.show_mobile_app" to "true"
**Steps to reproduce**
1. Launch Firefox and navigate to "about:protections".
2. Scroll down the page and go to the "Mobile Call Card" section.
3. Hover your mouse over the "X" button.
**Expected result**
* The “X” button is focused and a proper tooltip is shown on hover.
**Actual result**
* The “X” button is focused but no there is no tooltip.
|
Tooltip missing for the the "X" button inside the cards **Affected versions**
* latest Nightly 75.0a1
**Affected platforms**
* Windows 10 x64
* macOS 10.15
* Ubuntu 18.04 x64
**Prerequisites**
* In about:config, set the preference "browser.contentblocking.report.show_mobile_app" to "true"
**Steps to reproduce**
1. Launch Firefox and navigate to "about:protections".
2. Scroll down the page and go to the "Mobile Call Card" section.
3. Hover your mouse over the "X" button.
**Expected result**
* The “X” button is focused and a proper tooltip is shown on hover.
**Actual result**
* The “X” button is focused but no there is no tooltip.
|
P2
|
RESOLVED
|
FIXED
|
2020-03-03 08:29:11+00:00
|
2020-05-07 05:32:08+00:00
| 192
| 2
|
1619529
|
The “Dismiss” button from the “Collection” section does not have a tooltip displayed when hovered
|
**[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID: 20200302212732
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64
**[Prerequisites]:**
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.endpoints` set to `http,https`.
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.config` set to `{"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}`.
- Have the value of the pref` browser.search.region` set to `US`.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab and hover the “Dismiss” button from the “Collection” section.
3. Observe the “Dismiss” button.
**[Expected result]:**
- The “Dismiss” button tooltip is correctly displayed.
**[Actual result]:**
- There is no tooltip displayed.
**[Notes]:**
- Attached a screen recording of the issue.
|
The “Dismiss” button from the “Collection” section does not have a tooltip displayed when hovered **[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID: 20200302212732
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64
**[Prerequisites]:**
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.endpoints` set to `http,https`.
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.config` set to `{"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}`.
- Have the value of the pref` browser.search.region` set to `US`.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab and hover the “Dismiss” button from the “Collection” section.
3. Observe the “Dismiss” button.
**[Expected result]:**
- The “Dismiss” button tooltip is correctly displayed.
**[Actual result]:**
- There is no tooltip displayed.
**[Notes]:**
- Attached a screen recording of the issue.
|
P1
|
VERIFIED
|
FIXED
|
2020-03-03 10:01:09+00:00
|
2020-03-18 12:40:17+00:00
| 407
| 1
|
1619547
|
Redirect Search tips (google.com) are flicker displayed
|
##### [Environment:]
Windows 10, Mac 10.15.3, Ubuntu 18.04
Firefox Nightly 75.0a1 20200302212732
Firefox 74.0b9 (enabling browser.urlbar.update1.searchTips & browser.urlbar.update1)
##### [Preconditions:]
1. Create a new profile.
2. Verify that no updates have been made in the last 24h (open about:support, update folder , open folder and delete update.xml if any is listed)
3. Set profile age to be older by running the following snippet in browser console: (async function() { let { ProfileAge } = ChromeUtils.import("resource://gre/modules/ProfileAge.jsm"); let age = await ProfileAge(); age._times = { firstUse: 1368255600000, created: 1368255600000 }; await age.writeTimes(); })();
4. Restart browser with restore session and a random youtube.com/video loaded
5. Default search is google.com.
##### [Steps:]
1. Browser is opened with your custom youtube link restored.
2. Focus address bar and type google.com
##### [Actual Result:]
Redirect search tips are displayed and imediately auto-dismissed.
##### [Expected Result:]
Redirect search tips are displayed upon redirecting to any of the google.com homepages.
##### [Note:]
Using the "cheat" preference browser.urlbar.searchTips.test.ignoreShowLimits to true will not reproduce the issue.
|
Redirect Search tips (google.com) are flicker displayed ##### [Environment:]
Windows 10, Mac 10.15.3, Ubuntu 18.04
Firefox Nightly 75.0a1 20200302212732
Firefox 74.0b9 (enabling browser.urlbar.update1.searchTips & browser.urlbar.update1)
##### [Preconditions:]
1. Create a new profile.
2. Verify that no updates have been made in the last 24h (open about:support, update folder , open folder and delete update.xml if any is listed)
3. Set profile age to be older by running the following snippet in browser console: (async function() { let { ProfileAge } = ChromeUtils.import("resource://gre/modules/ProfileAge.jsm"); let age = await ProfileAge(); age._times = { firstUse: 1368255600000, created: 1368255600000 }; await age.writeTimes(); })();
4. Restart browser with restore session and a random youtube.com/video loaded
5. Default search is google.com.
##### [Steps:]
1. Browser is opened with your custom youtube link restored.
2. Focus address bar and type google.com
##### [Actual Result:]
Redirect search tips are displayed and imediately auto-dismissed.
##### [Expected Result:]
Redirect search tips are displayed upon redirecting to any of the google.com homepages.
##### [Note:]
Using the "cheat" preference browser.urlbar.searchTips.test.ignoreShowLimits to true will not reproduce the issue.
|
P1
|
RESOLVED
|
FIXED
|
2020-03-03 10:50:16+00:00
|
2020-03-19 23:40:32+00:00
| 404
| 1
|
1619561
|
Search Tips are displayed when Captive Portal notification is displayed
|
##### [Description:]
According to the experiment documentation [link](https://docs.google.com/document/d/1cHur2z8B-YqxWqaJcN9ifK6WTr4vKO94fhLBaxPVASg/edit?pli=1#bookmark=id.p51u0i5s36ef) (uncertain if this applies to the "feature" version of Search Tips) , the Search tips should not be displayed when browser notifications are present.
##### [Environment:]
Windows 10, Mac 10.15.3, Ubuntu 18.04
Firefox Nightly 75.0a1 20200302212732
Firefox 74.0b9 (enabling browser.urlbar.update1.searchTips & browser.urlbar.update1)
##### [Preconditions:]
1. Create a new profile.
2. Verify that no updates have been made in the last 24h (open about:support, update folder , open folder and delete update.xml if any is listed)
3. Set profile age to be older by running the following snippet in browser console: (async function() { let { ProfileAge } = ChromeUtils.import("resource://gre/modules/ProfileAge.jsm"); let age = await ProfileAge(); age._times = { firstUse: 1368255600000, created: 1368255600000 }; await age.writeTimes(); })();
4. Restart browser. (session restore not enabled -> about:newtab default loaded)
5. Default search is google.com.
6. Wi-fi compatible device is connected to a captive portal network.
##### [Steps:]
1. Browser is opened with the about:newtab.
##### [Actual Result:]
Onboarding Search Tips are displayed
##### [Expected Result:]
According to the experiment documentation, given the fact that the Captive Portal notification is present, the Search tips should not be displayed
|
Search Tips are displayed when Captive Portal notification is displayed ##### [Description:]
According to the experiment documentation [link](https://docs.google.com/document/d/1cHur2z8B-YqxWqaJcN9ifK6WTr4vKO94fhLBaxPVASg/edit?pli=1#bookmark=id.p51u0i5s36ef) (uncertain if this applies to the "feature" version of Search Tips) , the Search tips should not be displayed when browser notifications are present.
##### [Environment:]
Windows 10, Mac 10.15.3, Ubuntu 18.04
Firefox Nightly 75.0a1 20200302212732
Firefox 74.0b9 (enabling browser.urlbar.update1.searchTips & browser.urlbar.update1)
##### [Preconditions:]
1. Create a new profile.
2. Verify that no updates have been made in the last 24h (open about:support, update folder , open folder and delete update.xml if any is listed)
3. Set profile age to be older by running the following snippet in browser console: (async function() { let { ProfileAge } = ChromeUtils.import("resource://gre/modules/ProfileAge.jsm"); let age = await ProfileAge(); age._times = { firstUse: 1368255600000, created: 1368255600000 }; await age.writeTimes(); })();
4. Restart browser. (session restore not enabled -> about:newtab default loaded)
5. Default search is google.com.
6. Wi-fi compatible device is connected to a captive portal network.
##### [Steps:]
1. Browser is opened with the about:newtab.
##### [Actual Result:]
Onboarding Search Tips are displayed
##### [Expected Result:]
According to the experiment documentation, given the fact that the Captive Portal notification is present, the Search tips should not be displayed
|
P1
|
RESOLVED
|
FIXED
|
2020-03-03 11:44:58+00:00
|
2020-03-13 10:03:16+00:00
| 482
| 1
|
1619577
|
No warning displayed when downloading malicious files using drag and drop
|
*Affected versions*
* 75.0a1 (20200302212732)
* 74.0 (20200302184608)
* 73.0.1 (20200217142647)
*Affected platforms*
* Ubuntu 18.04
* Windows 10x64
* macOS 10.15
*Steps to reproduce*
1. Open Firefox with a new profile and go to https://testsafebrowsing.appspot.com/.
2. Download a random file from “Desktop Download Warnings” (e.g 3).
3. Drag and drop a random link from “Desktop Download Warnings” to the download arrow.
4. Observe the download panel.
*Expected result*
* Both downloads have a warning displayed.
*Actual result*
* The downloaded file via drag and drop has no warning.
*Regression Range*
* I will search for one ASAP.
*Notes*
* Attached a screen recording.
|
No warning displayed when downloading malicious files using drag and drop *Affected versions*
* 75.0a1 (20200302212732)
* 74.0 (20200302184608)
* 73.0.1 (20200217142647)
*Affected platforms*
* Ubuntu 18.04
* Windows 10x64
* macOS 10.15
*Steps to reproduce*
1. Open Firefox with a new profile and go to https://testsafebrowsing.appspot.com/.
2. Download a random file from “Desktop Download Warnings” (e.g 3).
3. Drag and drop a random link from “Desktop Download Warnings” to the download arrow.
4. Observe the download panel.
*Expected result*
* Both downloads have a warning displayed.
*Actual result*
* The downloaded file via drag and drop has no warning.
*Regression Range*
* I will search for one ASAP.
*Notes*
* Attached a screen recording.
|
P3
|
NEW
|
2020-03-03 12:46:01+00:00
|
2022-10-12 00:01:32+00:00
| 213
| 3
|
|
1619587
|
Allow fallback to empty string when reading the geo pref in head_search.js
|
Bug 1589618 changed head_search.js so that it was no longer setting a `browser.search.geoSpecificDefaults.url` preference before potentially reading one.
This is causing Thunderbird to fail, since they don't have the preference set - we should just fallback to the empty string.
|
Allow fallback to empty string when reading the geo pref in head_search.js Bug 1589618 changed head_search.js so that it was no longer setting a `browser.search.geoSpecificDefaults.url` preference before potentially reading one.
This is causing Thunderbird to fail, since they don't have the preference set - we should just fallback to the empty string.
|
P3
|
RESOLVED
|
FIXED
|
2020-03-03 13:12:58+00:00
|
2020-03-05 22:15:03+00:00
| 92
| 3
|
1619591
|
Download manager animation is displayed improperly on Windows and Ubuntu
|
**Affected versions**
* 75.0a1(ID:20200302212732)
* 74.0(ID:20200302184608)
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04x64
* Windows 10x64 ARM
* Windows 7x64
**Steps to reproduce**
1. Launch Firefox and navigate to http://testsafebrowsing.appspot.com/
2. Go to Desktop Download Warnings
3. Right click the "link" in order to trigger the context menu.
4. Select "Save link as" option and save it locally.
**Expected result**
* Once the download starts, the animation is displayed only once, without any issues.
**Actual result**
* Once the download animation ends, the begging of the animation is displayed once again.
**Notes**
* This issue does not occur in 73.0.1.
* The animation issue occurs slightly different for Ubuntu. The animation starts with an irregularly big, pixelated download icon that is displayed out of its desginated area.
**Regression range**
* Will return with a regression ASAP
|
Download manager animation is displayed improperly on Windows and Ubuntu **Affected versions**
* 75.0a1(ID:20200302212732)
* 74.0(ID:20200302184608)
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04x64
* Windows 10x64 ARM
* Windows 7x64
**Steps to reproduce**
1. Launch Firefox and navigate to http://testsafebrowsing.appspot.com/
2. Go to Desktop Download Warnings
3. Right click the "link" in order to trigger the context menu.
4. Select "Save link as" option and save it locally.
**Expected result**
* Once the download starts, the animation is displayed only once, without any issues.
**Actual result**
* Once the download animation ends, the begging of the animation is displayed once again.
**Notes**
* This issue does not occur in 73.0.1.
* The animation issue occurs slightly different for Ubuntu. The animation starts with an irregularly big, pixelated download icon that is displayed out of its desginated area.
**Regression range**
* Will return with a regression ASAP
|
P3
|
NEW
|
2020-03-03 13:26:47+00:00
|
2022-10-12 00:01:33+00:00
| 269
| 3
|
|
1619611
|
Intermittent UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 59: ordinal not in range(128)
|
**Filed by:** armenzg [at] mozilla.com
**Parsed log:** http://localhost:5000/logviewer.html#?job_id=291333245&repo=servo-try
**Full log:** https://community-tc.services.mozilla.com/api/queue/v1/task/R6HHwJ64TBu51LM_U6bo5g/runs/0/artifacts/public/logs/live_backing.log
---
|
Intermittent UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 59: ordinal not in range(128) **Filed by:** armenzg [at] mozilla.com
**Parsed log:** http://localhost:5000/logviewer.html#?job_id=291333245&repo=servo-try
**Full log:** https://community-tc.services.mozilla.com/api/queue/v1/task/R6HHwJ64TBu51LM_U6bo5g/runs/0/artifacts/public/logs/live_backing.log
---
|
P5
|
RESOLVED
|
INVALID
|
2020-03-03 14:08:23+00:00
|
2020-03-09 06:15:43+00:00
| 166
| 5
|
1619612
|
Intermittent [taskcluster:error] exit status 1
|
**Filed by:** armenzg [at] mozilla.com
**Parsed log:** http://localhost:5000/logviewer.html#?job_id=291333236&repo=servo-try
**Full log:** https://community-tc.services.mozilla.com/api/queue/v1/task/N6dcpN4TQkKSJPJZIt-8Rg/runs/0/artifacts/public/logs/live_backing.log
---
|
Intermittent [taskcluster:error] exit status 1 **Filed by:** armenzg [at] mozilla.com
**Parsed log:** http://localhost:5000/logviewer.html#?job_id=291333236&repo=servo-try
**Full log:** https://community-tc.services.mozilla.com/api/queue/v1/task/N6dcpN4TQkKSJPJZIt-8Rg/runs/0/artifacts/public/logs/live_backing.log
---
|
P5
|
RESOLVED
|
INVALID
|
2020-03-03 14:09:06+00:00
|
2020-03-09 06:15:41+00:00
| 143
| 5
|
1619634
|
On First opening Firefox, the software hangs for 10 to 20 seconds when anthing is entered into the address bar
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
We have Firefox 68.5.0ESR. Installed using the .msi file via SCCM. We have a proxy server. GPO sets the following:
We can then set the following policies:
• Set the ImportEnterpriseRoots key to true.
• Under Proxy, set “Mode” to “autoDetect”
• DisableAppUpdate to true
• Under Homepage, setting URL to [intranet page], and StartPage to “homepage”
• Under PopupBlocking, setting “allow” to [intranet page];
• Under FlashPlugin, setting “allow” to [intranet page]
• Under OverrideFirstRunPage, set to Blank, so it will default to the homepage
• Under OverridePostUpdatePage, set to Blank, so it will default to the homepage
Actual results:
After start up, anything entered into the address bar followed by enter will cause the tab to go white and hang for about 10 to 20 seconds. It doesn't seem to matter if hardware acceleration is turned on or off. It doesn't seem to matter whether it be a bookmark shortcut, a search term or and actual address (in the format "www.google.com"). For a few minutes after the initial tab is resolved, there is no hanging. Then after a period of inactivity for Firefox, the hanging is observed again.
Expected results:
Page to resolve immediately, as they do in Edge or Chrome.
|
On First opening Firefox, the software hangs for 10 to 20 seconds when anthing is entered into the address bar User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
We have Firefox 68.5.0ESR. Installed using the .msi file via SCCM. We have a proxy server. GPO sets the following:
We can then set the following policies:
• Set the ImportEnterpriseRoots key to true.
• Under Proxy, set “Mode” to “autoDetect”
• DisableAppUpdate to true
• Under Homepage, setting URL to [intranet page], and StartPage to “homepage”
• Under PopupBlocking, setting “allow” to [intranet page];
• Under FlashPlugin, setting “allow” to [intranet page]
• Under OverrideFirstRunPage, set to Blank, so it will default to the homepage
• Under OverridePostUpdatePage, set to Blank, so it will default to the homepage
Actual results:
After start up, anything entered into the address bar followed by enter will cause the tab to go white and hang for about 10 to 20 seconds. It doesn't seem to matter if hardware acceleration is turned on or off. It doesn't seem to matter whether it be a bookmark shortcut, a search term or and actual address (in the format "www.google.com"). For a few minutes after the initial tab is resolved, there is no hanging. Then after a period of inactivity for Firefox, the hanging is observed again.
Expected results:
Page to resolve immediately, as they do in Edge or Chrome.
|
P3
|
RESOLVED
|
INCOMPLETE
|
2020-03-03 15:15:53+00:00
|
2021-08-05 15:57:09+00:00
| 387
| 3
|
1619651
|
The "Create New Login" button cannot be focused using the keyboard navigation
|
[Affected Versions]:
- Nightly 75.0a1
- Beta 74
- Firefox 73.0.1
[Affected Platforms]
- All Windows
- All Mac
- All Linux
[Prerequisites]
- Have a Firefox profile with logins saved.
[Steps to reproduce]:
1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to "about:logins" page.
3. Press the tab key until the "Create New Login" button is focused.
4. Observe the behavior.
[Expected results]:
- The "Create New Login" is correctly focused and remains in this state until the tab key is pressed again.
[Actual results]:
- The "Create New Login" is focused but the focus automatically jumps to the next item without pressing any key.
[Regression]:
- Using mozregression tools I have found a pushlog that contains the fix that introduced this behavior.
- Here are the results:
Last good revision: ddc25b4c28947b7c89a4d46b127b97bf245cb11a
First bad revision: ad32f331d00a2c42544570e740e6e6687cd71cd1
Pushlog: [LINK](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ddc25b4c28947b7c89a4d46b127b97bf245cb11a&tochange=ad32f331d00a2c42544570e740e6e6687cd71cd1)
[Notes]:
- The issue is also reproducible if no logins are saved.
- Attached a screen recording with the issue.
|
The "Create New Login" button cannot be focused using the keyboard navigation [Affected Versions]:
- Nightly 75.0a1
- Beta 74
- Firefox 73.0.1
[Affected Platforms]
- All Windows
- All Mac
- All Linux
[Prerequisites]
- Have a Firefox profile with logins saved.
[Steps to reproduce]:
1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to "about:logins" page.
3. Press the tab key until the "Create New Login" button is focused.
4. Observe the behavior.
[Expected results]:
- The "Create New Login" is correctly focused and remains in this state until the tab key is pressed again.
[Actual results]:
- The "Create New Login" is focused but the focus automatically jumps to the next item without pressing any key.
[Regression]:
- Using mozregression tools I have found a pushlog that contains the fix that introduced this behavior.
- Here are the results:
Last good revision: ddc25b4c28947b7c89a4d46b127b97bf245cb11a
First bad revision: ad32f331d00a2c42544570e740e6e6687cd71cd1
Pushlog: [LINK](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ddc25b4c28947b7c89a4d46b127b97bf245cb11a&tochange=ad32f331d00a2c42544570e740e6e6687cd71cd1)
[Notes]:
- The issue is also reproducible if no logins are saved.
- Attached a screen recording with the issue.
|
P1
|
VERIFIED
|
FIXED
|
2020-03-03 15:46:31+00:00
|
2020-03-12 00:51:05+00:00
| 413
| 1
|
1619654
|
Fluent changes in activity-stream.bundle.js from incorrect version
|
In bug 1617280 changes to the `activity-stream.bundle.js` landed that seem to be generated from the wrong version of Fluent. This causes `activity-stream.bundle.js` changes to show up every time `npm run bundle` is used even if no AS components have been changed.
@Scott can you please land a fix for this?
|
Fluent changes in activity-stream.bundle.js from incorrect version In bug 1617280 changes to the `activity-stream.bundle.js` landed that seem to be generated from the wrong version of Fluent. This causes `activity-stream.bundle.js` changes to show up every time `npm run bundle` is used even if no AS components have been changed.
@Scott can you please land a fix for this?
|
P1
|
RESOLVED
|
FIXED
|
2020-03-03 15:54:25+00:00
|
2020-03-05 22:17:38+00:00
| 94
| 1
|
1619695
|
Update about:welcome ping type in 76
|
Follow up to bug 1616371
```
const PING_TYPE = "onboarding";
```
> We could file an issue to change this once we start the new style of experiments in 76, but keeping this consistent with the existing experience for 75 sounds like the right thing to do
|
Update about:welcome ping type in 76 Follow up to bug 1616371
```
const PING_TYPE = "onboarding";
```
> We could file an issue to change this once we start the new style of experiments in 76, but keeping this consistent with the existing experience for 75 sounds like the right thing to do
|
P2
|
RESOLVED
|
INVALID
|
2020-03-03 18:08:38+00:00
|
2020-06-05 15:56:30+00:00
| 72
| 2
|
1619736
|
Clicking "Create New Login" does no longer shift focus to the first input in the form
|
This is a regression caused by bug 1578736.
STR:
1. Open about:logins
2. Click the "Create New Login" button
AR:
Focus is on the "Create New Login"
ER:
The focus should be shifted to the Website address field.
|
Clicking "Create New Login" does no longer shift focus to the first input in the form This is a regression caused by bug 1578736.
STR:
1. Open about:logins
2. Click the "Create New Login" button
AR:
Focus is on the "Create New Login"
ER:
The focus should be shifted to the Website address field.
|
P1
|
VERIFIED
|
FIXED
|
2020-03-03 19:36:31+00:00
|
2020-03-16 12:25:19+00:00
| 79
| 1
|
1619777
|
[RTL] The minimize button is 2px too far from the other controls, on Windows 7 Aero Basic
|
See attached for how this looks on RTL and LTR.
|
[RTL] The minimize button is 2px too far from the other controls, on Windows 7 Aero Basic See attached for how this looks on RTL and LTR.
|
P3
|
NEW
|
2020-03-03 21:25:02+00:00
|
2022-10-12 00:01:43+00:00
| 38
| 3
|
|
1619842
|
eslint integration with vscode broken in browser/components/newtab
|
As of last week(?) it looks like vscode's eslint plugin is having trouble finding the right packages when trying to lint code inside browser/component/newtab. I see a bunch of errors like this:
```
Definition for rule 'getter-return' was not found
Definition for rule 'no-global-assign' was not found
Definition for rule 'no-return-await' was not found
```
Some observations, although I don't know what the cause / fix is for this:
* deleting browser/components/newtab/node_modules fixes the issue, so probably a problem with the eslint plugin not adding the right folders to the node PATH
* mach lint is unaffected
|
eslint integration with vscode broken in browser/components/newtab As of last week(?) it looks like vscode's eslint plugin is having trouble finding the right packages when trying to lint code inside browser/component/newtab. I see a bunch of errors like this:
```
Definition for rule 'getter-return' was not found
Definition for rule 'no-global-assign' was not found
Definition for rule 'no-return-await' was not found
```
Some observations, although I don't know what the cause / fix is for this:
* deleting browser/components/newtab/node_modules fixes the issue, so probably a problem with the eslint plugin not adding the right folders to the node PATH
* mach lint is unaffected
|
P2
|
RESOLVED
|
FIXED
|
2020-03-04 03:40:56+00:00
|
2023-05-11 03:02:06+00:00
| 174
| 2
|
1619955
|
content process crash reporting dialog missing email address field
|
The crash report dialog you get when a content process crashes doesn't have an email address field.
We should add one so it's in parity with the main process crash report dialog.
Further, (and maybe this should be a new bug), when opting-in to auto-reporting content crashes, maybe Firefox should use the email address you filled in.
|
content process crash reporting dialog missing email address field The crash report dialog you get when a content process crashes doesn't have an email address field.
We should add one so it's in parity with the main process crash report dialog.
Further, (and maybe this should be a new bug), when opting-in to auto-reporting content crashes, maybe Firefox should use the email address you filled in.
|
P3
|
RESOLVED
|
WONTFIX
|
2020-03-04 14:13:40+00:00
|
2021-01-26 13:52:53+00:00
| 91
| 3
|
1619981
|
Investigate low enrollment rate for Chrome Switchers experiment
|
Experiment bug: https://experimenter.services.mozilla.com/experiments/chrome-switchers-card-for-onboarding-triplets-in-firefox-73/
Enrollments have been significantly lower than expected pointing to a problem with the attribution data not being available early enough at startup for all users.
|
Investigate low enrollment rate for Chrome Switchers experiment Experiment bug: https://experimenter.services.mozilla.com/experiments/chrome-switchers-card-for-onboarding-triplets-in-firefox-73/
Enrollments have been significantly lower than expected pointing to a problem with the attribution data not being available early enough at startup for all users.
|
P1
|
RESOLVED
|
WONTFIX
|
2020-03-04 15:39:49+00:00
|
2020-03-30 21:54:29+00:00
| 83
| 1
|
1620037
|
new certificate viewer doesn't show signature algorithm for (at least) md5 signatures
|
STR:
* visit https://wiki.cacert.org/
* click "advanced"
* click "view certificate"
* click "CA Cert Signing Authority"
The "Signature Algorithm" item is missing from "Miscellaneous" (possibly because it's md5-based?)
|
new certificate viewer doesn't show signature algorithm for (at least) md5 signatures STR:
* visit https://wiki.cacert.org/
* click "advanced"
* click "view certificate"
* click "CA Cert Signing Authority"
The "Signature Algorithm" item is missing from "Miscellaneous" (possibly because it's md5-based?)
|
P3
|
VERIFIED
|
FIXED
|
2020-03-04 19:13:39+00:00
|
2020-04-14 12:32:34+00:00
| 81
| 3
|
1620048
|
"There are no downloads." text in about:downloads is pretty much unreadable - should use photon colours
|
Tested on macOS nightly in case it matters.
The text is grey, and so is the background. The text is also tiny.
I have to assume this regressed at some point, it seems unlikely we shipped it with contrast this low.
|
"There are no downloads." text in about:downloads is pretty much unreadable - should use photon colours Tested on macOS nightly in case it matters.
The text is grey, and so is the background. The text is also tiny.
I have to assume this regressed at some point, it seems unlikely we shipped it with contrast this low.
|
P3
|
VERIFIED
|
FIXED
|
2020-03-04 19:56:22+00:00
|
2020-04-09 02:11:49+00:00
| 74
| 3
|
1620068
|
Captive portal tab opens in every browser window, not just the active one
|
I don't have STR but I think this can probably be reproduced easily with a captive portal network…
The captive portal login network error page was opened in every Firefox window while at an airport so I had to close it in all my 16 windows. I'm not sure what the purpose of the error page is vs. the notification bar but it probably shouldn't open in every window and if it does it should close when I log in to the portal.
|
Captive portal tab opens in every browser window, not just the active one I don't have STR but I think this can probably be reproduced easily with a captive portal network…
The captive portal login network error page was opened in every Firefox window while at an airport so I had to close it in all my 16 windows. I'm not sure what the purpose of the error page is vs. the notification bar but it probably shouldn't open in every window and if it does it should close when I log in to the portal.
|
P3
|
NEW
|
2020-03-04 21:27:03+00:00
|
2022-10-12 00:02:04+00:00
| 113
| 3
|
|
1620094
|
If a tab opens a download popup as you are moving it, you can't move or close any tab in the window.
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
1. Open a Firefox window with lots of tabs.
2. Open a new tab that will create a Download popup.
3. Before the tab loads in and opens the popup, start dragging it sideways as if to reorder tabs. Don't release the tab until the download popup opens.
Actual results:
No tabs in the window can be moved or closed. There is also a visual glitch where the dragged tab appears to remain where it was at the moment the popup opened rather than snapping to the align with the other tabs.
Expected results:
When Firefox is restarted, the tab returns to its original position before dragging. It should return there without restarting Firefox.
|
If a tab opens a download popup as you are moving it, you can't move or close any tab in the window. User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
1. Open a Firefox window with lots of tabs.
2. Open a new tab that will create a Download popup.
3. Before the tab loads in and opens the popup, start dragging it sideways as if to reorder tabs. Don't release the tab until the download popup opens.
Actual results:
No tabs in the window can be moved or closed. There is also a visual glitch where the dragged tab appears to remain where it was at the moment the popup opened rather than snapping to the align with the other tabs.
Expected results:
When Firefox is restarted, the tab returns to its original position before dragging. It should return there without restarting Firefox.
|
P3
|
RESOLVED
|
WORKSFORME
|
2020-03-04 23:30:28+00:00
|
2022-06-15 09:17:04+00:00
| 223
| 3
|
1620101
|
Session restore to virtual desktop does not work on KDE Plasma
|
With KDE Plasma 5.17.5 on Fedora 31 and the latest Nightly containing changeset [`323e2a212629`](https://hg.mozilla.org/mozilla-central/rev/323e2a21262949647c7237ad1a73fde670efb13a), session restore does not save the `workspaceID` to `sessionstore.jsonlz4`.
Using `xprop` I see the correct [`_NET_WM_DESKTOP`](https://specifications.freedesktop.org/wm-spec/1.3/ar01s05.html#idm46041655366880) property. I verified the runtime dynamically linked `libgdk-3.so.0` has the required symbols and I don't see a "... not available" log message with `MOZ_LOG='Widget:10'` (not sure if this is correct).
I was hoping this would just work on Plasma since the implementation looks DE-generic :/
|
Session restore to virtual desktop does not work on KDE Plasma With KDE Plasma 5.17.5 on Fedora 31 and the latest Nightly containing changeset [`323e2a212629`](https://hg.mozilla.org/mozilla-central/rev/323e2a21262949647c7237ad1a73fde670efb13a), session restore does not save the `workspaceID` to `sessionstore.jsonlz4`.
Using `xprop` I see the correct [`_NET_WM_DESKTOP`](https://specifications.freedesktop.org/wm-spec/1.3/ar01s05.html#idm46041655366880) property. I verified the runtime dynamically linked `libgdk-3.so.0` has the required symbols and I don't see a "... not available" log message with `MOZ_LOG='Widget:10'` (not sure if this is correct).
I was hoping this would just work on Plasma since the implementation looks DE-generic :/
|
P2
|
VERIFIED
|
FIXED
|
2020-03-05 00:08:49+00:00
|
2020-03-17 15:16:43+00:00
| 264
| 2
|
1620184
|
Fix drag/drop functionality in about:downloads to download things
|
Per bug 978291, this is supposed to work on both the list and the "no downloads" text. That last part I expect broke (at the latest) in bug 1605939.
However, I can't get it to work at all (testing on Windows on beta), dragging either URLs or images from other tabs into either the list or the text - they just replace the about:downloads content with the URL of the dragged item. Maybe I'm doing it wrong? The code and event handlers are still there, it would seem.
|
Fix drag/drop functionality in about:downloads to download things Per bug 978291, this is supposed to work on both the list and the "no downloads" text. That last part I expect broke (at the latest) in bug 1605939.
However, I can't get it to work at all (testing on Windows on beta), dragging either URLs or images from other tabs into either the list or the text - they just replace the about:downloads content with the URL of the dragged item. Maybe I'm doing it wrong? The code and event handlers are still there, it would seem.
|
P3
|
VERIFIED
|
FIXED
|
2020-03-05 10:28:14+00:00
|
2020-04-21 11:59:56+00:00
| 131
| 3
|
1620227
|
Search service can install extensions after shutdown has started which makes things sad
|
I spotted some errors in a log that indicated that we're trying to `installBuiltinAddon` after the addon manager shuts down, which ends in tears because it throws errors.
https://searchfox.org/mozilla-central/rev/c79c0d65a183d9d38676855f455a5c6a7f7dadd3/toolkit/components/search/SearchService.jsm#1301
and
https://searchfox.org/mozilla-central/rev/c79c0d65a183d9d38676855f455a5c6a7f7dadd3/toolkit/components/search/SearchService.jsm#2544
(that one is the one this is hitting, AFAICT)
should probably catch exceptions, and/or we should bail out if `Services.startup.isShuttingDown` is true or `AddonManager.isReady` is false.
|
Search service can install extensions after shutdown has started which makes things sad I spotted some errors in a log that indicated that we're trying to `installBuiltinAddon` after the addon manager shuts down, which ends in tears because it throws errors.
https://searchfox.org/mozilla-central/rev/c79c0d65a183d9d38676855f455a5c6a7f7dadd3/toolkit/components/search/SearchService.jsm#1301
and
https://searchfox.org/mozilla-central/rev/c79c0d65a183d9d38676855f455a5c6a7f7dadd3/toolkit/components/search/SearchService.jsm#2544
(that one is the one this is hitting, AFAICT)
should probably catch exceptions, and/or we should bail out if `Services.startup.isShuttingDown` is true or `AddonManager.isReady` is false.
|
P1
|
VERIFIED
|
FIXED
|
2020-03-05 12:51:33+00:00
|
2020-03-30 13:51:43+00:00
| 247
| 1
|
1620231
|
Crop urls in the middle in the results panel
|
Being able to quickly and efficiently search one's history for specific pages was one of the strongest features of the urlbar.
For this, one needs to be able to see the relevant parts of the URL and/or title directly in the results.
Comically short truncation of URLs and titles in the design update means this will, in many cases become a super tedious task of tooltipping or cycling through many results instead of a single look, zero effort operation.
It is especially troubling, that this functionality now directly depends on the amount of UI elements competing for space against the urlbar (breaking web-search out into its own bar for more/better history-search results in the urlbar dropdown makes those same results less useful!).
It's clear that no amount of stripping www or http(s), shifting weights between titles and URLs will alleviate this considerably in the available amount of space.
From other bugs it is clear you are unwilling to change the default horizontal size of the dropdown for the sake of it becoming a single but rather useless widget in this configuration and that there is an automatically triggered 2-line mode for ultra-slim window sizes beyond use which thus ends up giving equally short results.
Two reasonable solutions which should remove everyone's gripes about the changes jump to mind:
1. Resizable urlbar dropdown
Optionally a drag handle for discoverability, it would give users a choice, when they feel the extra space for useful results would outweigh the developers wish for this widget to be visually one consistent thing in width.
_Default configuration users who don't care one way or the other will see no difference to your current implementation._
2. Give a pref to force enable 2-line mode manually.
IIRC back then this was default, the need for a super wide dropown only came about the then equally controversial decision to put URLs and titles on one line. It's already implemented, let users have the choice.
_Again, no impact on default configuration users._
Would these still collide with your design goals?
|
Crop urls in the middle in the results panel Being able to quickly and efficiently search one's history for specific pages was one of the strongest features of the urlbar.
For this, one needs to be able to see the relevant parts of the URL and/or title directly in the results.
Comically short truncation of URLs and titles in the design update means this will, in many cases become a super tedious task of tooltipping or cycling through many results instead of a single look, zero effort operation.
It is especially troubling, that this functionality now directly depends on the amount of UI elements competing for space against the urlbar (breaking web-search out into its own bar for more/better history-search results in the urlbar dropdown makes those same results less useful!).
It's clear that no amount of stripping www or http(s), shifting weights between titles and URLs will alleviate this considerably in the available amount of space.
From other bugs it is clear you are unwilling to change the default horizontal size of the dropdown for the sake of it becoming a single but rather useless widget in this configuration and that there is an automatically triggered 2-line mode for ultra-slim window sizes beyond use which thus ends up giving equally short results.
Two reasonable solutions which should remove everyone's gripes about the changes jump to mind:
1. Resizable urlbar dropdown
Optionally a drag handle for discoverability, it would give users a choice, when they feel the extra space for useful results would outweigh the developers wish for this widget to be visually one consistent thing in width.
_Default configuration users who don't care one way or the other will see no difference to your current implementation._
2. Give a pref to force enable 2-line mode manually.
IIRC back then this was default, the need for a super wide dropown only came about the then equally controversial decision to put URLs and titles on one line. It's already implemented, let users have the choice.
_Again, no impact on default configuration users._
Would these still collide with your design goals?
|
P5
|
NEW
|
2020-03-05 13:17:48+00:00
|
2025-03-02 14:54:26+00:00
| 448
| 5
|
|
1620283
|
The “Collections Promo” section is redisplayed on a new tab after it was previously dismissed
|
**[Affected versions]:**
Firefox Nightly 75.0a1 Build ID: 20200305095541
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Ubuntu Linux 18.04 x64
**[Prerequisites]:**
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.spocs-endpoint` set to `https://spocs.getpocket.com/spocs?site=1116390`.
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.isCollectionDismissible` set to `true`.
- Have the value of the pref` browser.search.region` set to `US`.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites and open a new tab.
2. Press the “Dismiss” button from the “Collections Promo” section.
3. Open a new tab and observe the page.
**[Expected result]:**
- The “Collections Promo” section is no longer displayed.
**[Actual result]:**
- The “Collections Promo” section is redisplayed with 3 new cards.
**[Notes]:**
- The issue is also reproducible after dismissing, saving to Pocket, or deleting from Pocket.
- Attached a screen recording of the issue.
|
The “Collections Promo” section is redisplayed on a new tab after it was previously dismissed **[Affected versions]:**
Firefox Nightly 75.0a1 Build ID: 20200305095541
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Ubuntu Linux 18.04 x64
**[Prerequisites]:**
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.spocs-endpoint` set to `https://spocs.getpocket.com/spocs?site=1116390`.
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.isCollectionDismissible` set to `true`.
- Have the value of the pref` browser.search.region` set to `US`.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites and open a new tab.
2. Press the “Dismiss” button from the “Collections Promo” section.
3. Open a new tab and observe the page.
**[Expected result]:**
- The “Collections Promo” section is no longer displayed.
**[Actual result]:**
- The “Collections Promo” section is redisplayed with 3 new cards.
**[Notes]:**
- The issue is also reproducible after dismissing, saving to Pocket, or deleting from Pocket.
- Attached a screen recording of the issue.
|
P1
|
VERIFIED
|
FIXED
|
2020-03-05 15:41:52+00:00
|
2020-03-09 16:09:35+00:00
| 347
| 1
|
1620299
|
URLBar Interventions should honor policy (and be able to be disabled by policy)
|
Currently URLBar Interventions tells users they can refresh Firefox, but if refresh has been turned off by policy, they cannot.
The same is true of the update policy. If update is turned off, that policy should not show.
Any interventions that intersect with policy should check policy to see if they should be displayed.
In addition, we should provide a policy to completely turn off interventions. This can go in the new "UserMessaging" section of policy.
|
URLBar Interventions should honor policy (and be able to be disabled by policy) Currently URLBar Interventions tells users they can refresh Firefox, but if refresh has been turned off by policy, they cannot.
The same is true of the update policy. If update is turned off, that policy should not show.
Any interventions that intersect with policy should check policy to see if they should be displayed.
In addition, we should provide a policy to completely turn off interventions. This can go in the new "UserMessaging" section of policy.
|
P1
|
VERIFIED
|
FIXED
|
2020-03-05 16:29:36+00:00
|
2020-03-26 15:31:38+00:00
| 116
| 1
|
1620351
|
Element h2 not allowed as child of element span in this context
|
I copy/pasted the generated source (via inspect element and copying the outer <html> tag's content) into https://validator.w3.org/nu/#textarea and got a few of these messages:
Error: Element h2 not allowed as child of element span in this context. (Suppressing further errors from this subtree.)
Error: Element p not allowed as child of element span in this context. (Suppressing further errors from this subtree.)
|
Element h2 not allowed as child of element span in this context I copy/pasted the generated source (via inspect element and copying the outer <html> tag's content) into https://validator.w3.org/nu/#textarea and got a few of these messages:
Error: Element h2 not allowed as child of element span in this context. (Suppressing further errors from this subtree.)
Error: Element p not allowed as child of element span in this context. (Suppressing further errors from this subtree.)
|
P2
|
RESOLVED
|
INVALID
|
2020-03-05 18:59:54+00:00
|
2020-06-05 15:41:51+00:00
| 119
| 2
|
1620434
|
flexible space is too narrow in the navbar in customize mode
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
add spacers to the left of the "previous page" button (left of URL bar)
Actual results:
tiny spacers appear in customization-view.
Expected results:
should appear just as wide in customization-view as they appear in bookmark-bar.
|
flexible space is too narrow in the navbar in customize mode User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
add spacers to the left of the "previous page" button (left of URL bar)
Actual results:
tiny spacers appear in customization-view.
Expected results:
should appear just as wide in customization-view as they appear in bookmark-bar.
|
P1
|
VERIFIED
|
FIXED
|
2020-03-05 21:26:18+00:00
|
2020-03-13 09:49:54+00:00
| 117
| 1
|
1620531
|
about:logins - have [Sort by] button share the same width as the dropdown menu
|
**Affected versions**
* 70.0, 73.0.1, 74.0b8, 75.0a1 (2020-02-26);
**Affected platforms**
* Windows 10, macOS 10.15, Ubuntu 19.04;
**Steps to reproduce**
1. Launch Firefox, access about:logins
2. Input any dummy_logins if none added in the list;
3. Click on the [Sort by] button;
**Expected result / Enhancement suggestion**
* dropdwn menu is of the same width as the button;
**Actual result**
* dropdown menu width is greater than the button;
**Regression range**
* Pushlog: [URL](https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2c268d869bc48dc4d5e8ff036cac82375ecf507a&tochange=993cf82f6bbf09537f4cec8144cb69bfdf26bff3);
* Potential regressor: 1576029
**Additional notes**
* attached screenshot with the issue;
|
about:logins - have [Sort by] button share the same width as the dropdown menu **Affected versions**
* 70.0, 73.0.1, 74.0b8, 75.0a1 (2020-02-26);
**Affected platforms**
* Windows 10, macOS 10.15, Ubuntu 19.04;
**Steps to reproduce**
1. Launch Firefox, access about:logins
2. Input any dummy_logins if none added in the list;
3. Click on the [Sort by] button;
**Expected result / Enhancement suggestion**
* dropdwn menu is of the same width as the button;
**Actual result**
* dropdown menu width is greater than the button;
**Regression range**
* Pushlog: [URL](https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2c268d869bc48dc4d5e8ff036cac82375ecf507a&tochange=993cf82f6bbf09537f4cec8144cb69bfdf26bff3);
* Potential regressor: 1576029
**Additional notes**
* attached screenshot with the issue;
|
P5
|
RESOLVED
|
WONTFIX
|
2020-03-06 09:05:22+00:00
|
2020-04-08 19:30:16+00:00
| 297
| 5
|
1620536
|
"Import from another browser" menu adds noise and scroll bar to the app menu
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Recently a new button "Import from another browser" was added to the root of App/Hamburger button.
Expected results:
An additional button in the root of the menu makes it too crowded. Taking into account that this functionality is not used daily, moving it to "Help" sub-menu
|
"Import from another browser" menu adds noise and scroll bar to the app menu User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Recently a new button "Import from another browser" was added to the root of App/Hamburger button.
Expected results:
An additional button in the root of the menu makes it too crowded. Taking into account that this functionality is not used daily, moving it to "Help" sub-menu
|
P1
|
RESOLVED
|
FIXED
|
2020-03-06 09:39:30+00:00
|
2020-03-30 15:30:07+00:00
| 122
| 1
|
1620570
|
Wrong Region For Search Engines (when in austria)
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
My Firefox browser is in English (UK), the "browser.search.region" is set to "AT" (for Austria) and so is my Windows 10 region.
Actual results:
My default search engines are for the UK, e.g. amazon.co.uk and chambers (UK).
Expected results:
My default search engines should be for Austria, e.g. amazon.de or wikipedia.at
|
Wrong Region For Search Engines (when in austria) User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
My Firefox browser is in English (UK), the "browser.search.region" is set to "AT" (for Austria) and so is my Windows 10 region.
Actual results:
My default search engines are for the UK, e.g. amazon.co.uk and chambers (UK).
Expected results:
My default search engines should be for Austria, e.g. amazon.de or wikipedia.at
|
P3
|
RESOLVED
|
WORKSFORME
|
2020-03-06 12:53:21+00:00
|
2021-06-17 15:34:55+00:00
| 146
| 3
|
1620576
|
UrlbarProviderSearchTips.jsm triggers main thread I/O to updates.xml to fetch the updateCount
|
The `lastBrowserUpdateDate` function in UrlbarProviderSearchTips.jsm is async so it looks like it was meant to not block the main thread, but calling updateManager.updateCount at https://searchfox.org/mozilla-central/rev/13b081a62d3f3e3e3120f95564529257b0bf451c/browser/components/urlbar/UrlbarProviderSearchTips.jsm#464 triggers main thread I/O to updates.xml. See this profile: https://perfht.ml/2vIUtI3
This code is from bug 1606909 and just got enabled in bug 1617029.
|
UrlbarProviderSearchTips.jsm triggers main thread I/O to updates.xml to fetch the updateCount The `lastBrowserUpdateDate` function in UrlbarProviderSearchTips.jsm is async so it looks like it was meant to not block the main thread, but calling updateManager.updateCount at https://searchfox.org/mozilla-central/rev/13b081a62d3f3e3e3120f95564529257b0bf451c/browser/components/urlbar/UrlbarProviderSearchTips.jsm#464 triggers main thread I/O to updates.xml. See this profile: https://perfht.ml/2vIUtI3
This code is from bug 1606909 and just got enabled in bug 1617029.
|
P3
|
RESOLVED
|
FIXED
|
2020-03-06 13:19:52+00:00
|
2024-03-20 19:00:41+00:00
| 206
| 3
|
1620582
|
aboutwelcome.css has changes after npm run bundle
|
Right now there are changes to this file when running `npm run bundle`:
```diff
diff --git a/browser/components/newtab/aboutwelcome/content/aboutwelcome.css b/browser/components/newtab/aboutwelcome/content/aboutwelcome.css
index 74953be4dfe0..121795c9b396 100644
--- a/browser/components/newtab/aboutwelcome/content/aboutwelcome.css
+++ b/browser/components/newtab/aboutwelcome/content/aboutwelcome.css
@@ -49,7 +49,6 @@ body {
background-color: var(--trailhead-cards-background-color);
font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', 'Ubuntu', 'Helvetica Neue', sans-serif;
font-size: 16px;
- min-height: 100vh;
position: relative; }
.trailheadCardGrid {
```
|
aboutwelcome.css has changes after npm run bundle Right now there are changes to this file when running `npm run bundle`:
```diff
diff --git a/browser/components/newtab/aboutwelcome/content/aboutwelcome.css b/browser/components/newtab/aboutwelcome/content/aboutwelcome.css
index 74953be4dfe0..121795c9b396 100644
--- a/browser/components/newtab/aboutwelcome/content/aboutwelcome.css
+++ b/browser/components/newtab/aboutwelcome/content/aboutwelcome.css
@@ -49,7 +49,6 @@ body {
background-color: var(--trailhead-cards-background-color);
font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', 'Ubuntu', 'Helvetica Neue', sans-serif;
font-size: 16px;
- min-height: 100vh;
position: relative; }
.trailheadCardGrid {
```
|
P1
|
RESOLVED
|
FIXED
|
2020-03-06 13:38:38+00:00
|
2020-04-27 10:49:19+00:00
| 273
| 1
|
1620717
|
Add an enterprise policy to allow disabling the lax-by-default feature
|
It would be nice to add an enterprise policy to allow disabling this temporarily similar to what Chrome is planning to do.
|
Add an enterprise policy to allow disabling the lax-by-default feature It would be nice to add an enterprise policy to allow disabling this temporarily similar to what Chrome is planning to do.
|
P2
|
RESOLVED
|
FIXED
|
2020-03-06 23:09:52+00:00
|
2022-01-12 18:08:16+00:00
| 43
| 2
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.