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
|
---|---|---|---|---|---|---|---|---|---|---|
1611689
|
Text in Search Bar are deleted after exit DOM FullScreen
|
Reproducible: always
Steps to reproduce:
1. Enable Search Bar
2. Type something in the Search Bar
3. Open any video
4. Enter DOM FullScreen and exit DOM FullScreen
Actual Results:
Text in Search Bar are deleted
Expected Results:
The text should be retained
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ac5fc1e491a2bb5481d47247bea3c2b22318001c&tochange=517c9efa9592ad0c103ec2542e4bc7fcaf06c505
|
Text in Search Bar are deleted after exit DOM FullScreen Reproducible: always
Steps to reproduce:
1. Enable Search Bar
2. Type something in the Search Bar
3. Open any video
4. Enter DOM FullScreen and exit DOM FullScreen
Actual Results:
Text in Search Bar are deleted
Expected Results:
The text should be retained
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ac5fc1e491a2bb5481d47247bea3c2b22318001c&tochange=517c9efa9592ad0c103ec2542e4bc7fcaf06c505
|
P1
|
VERIFIED
|
FIXED
|
2020-01-26 13:45:49+00:00
|
2020-02-04 14:56:19+00:00
| 159 | 1 |
1611690
|
Send tab to device not triggering master password anymore and not sending tabs
|
### Prerequisite
Firefox with
- master password set
- sync enabled
- other devices syncing as well to have a list of at least one device to send to
- Add "Send Tab to Device" to address bar (via "..." in address bar) to show icon (_that's just how I set it up really_)
### Steps
- restart Firefox
- in case a master password prompt comes up, close it for now (e.g. hit `esc`)
- trigger "send tab" from address bar icon
### Expected
The master password comes up to enable the tab syncing.
### Actual
Several weeks ago this behaviour stopped. Now the device list comes up directly and can be clicked, but the tab does not get sent.
### Work around
The master password has to be trigger differently* and filled in first, before tabs can be sent.
*for example: Toolbar > Firefox Account icon > "Sync now"
|
Send tab to device not triggering master password anymore and not sending tabs ### Prerequisite
Firefox with
- master password set
- sync enabled
- other devices syncing as well to have a list of at least one device to send to
- Add "Send Tab to Device" to address bar (via "..." in address bar) to show icon (_that's just how I set it up really_)
### Steps
- restart Firefox
- in case a master password prompt comes up, close it for now (e.g. hit `esc`)
- trigger "send tab" from address bar icon
### Expected
The master password comes up to enable the tab syncing.
### Actual
Several weeks ago this behaviour stopped. Now the device list comes up directly and can be clicked, but the tab does not get sent.
### Work around
The master password has to be trigger differently* and filled in first, before tabs can be sent.
*for example: Toolbar > Firefox Account icon > "Sync now"
|
P1
|
VERIFIED
|
FIXED
|
2020-01-26 14:13:43+00:00
|
2020-02-25 15:48:25+00:00
| 225 | 1 |
1611870
|
Restoring pinned tabs sometimes leaves the tab with the right favicon but an empty url
|
I've noticed this twice already over the last couple of days... The url bar is empty when I look at some of my pinned tabs, even though the favicon is right, see attached screenshot.
|
Restoring pinned tabs sometimes leaves the tab with the right favicon but an empty url I've noticed this twice already over the last couple of days... The url bar is empty when I look at some of my pinned tabs, even though the favicon is right, see attached screenshot.
|
P3
|
NEW
|
2020-01-27 23:57:14+00:00
|
2023-10-12 12:13:59+00:00
| 68 | 3 |
|
1611903
|
Zoom level is not applied correctly without a page refresh after changing "Zoom text only" option in about:preferences.
|
#### Affected versions:
Nightly 74.0a1 (2020-01-28), Beta 73.0b10
#### Affected platforms:
ALL
#### Steps:
1. Launch Firefox with a new profile and go to about:preferences.
2. Under General, go to Zoom section and select 133% value (or any other) from the "Default zoom" dropdown.
3. Perform a zoom in or zoom out using ctrl + mousewheel and then click on the zoom level badge from the address bar in order to return to the default zoom level.
4. Check the "Zoom text only" checkbox and perform another zoom in or out like in step 3.
#### Actual result:
After checking the Zoom text only box and perform a zoom change using ctrl + mousewheel, the zoom level is applied for text only but starting from 100% instead from the default zoom level.
#### Expected result:
The zoom level should be applied starting from the default zoom level value set in step 2 (133% in our case).
NOTE: After checking the "Zoom text only" option from step 4, if the user refresh the page it works ok, the zoom changes are applied starting from the default zoom value. Note that other checkbox options like "Use smooth scrolling" from Browsing section is applied immediately without refreshing the page. Also if I change the Zoom text only option from menu bar->view->zoom->zoom text only, it works ok, the zoom level is changed starting from the default zoom level set in step 2, not from the 100%.
Please see the attachment.
|
Zoom level is not applied correctly without a page refresh after changing "Zoom text only" option in about:preferences. #### Affected versions:
Nightly 74.0a1 (2020-01-28), Beta 73.0b10
#### Affected platforms:
ALL
#### Steps:
1. Launch Firefox with a new profile and go to about:preferences.
2. Under General, go to Zoom section and select 133% value (or any other) from the "Default zoom" dropdown.
3. Perform a zoom in or zoom out using ctrl + mousewheel and then click on the zoom level badge from the address bar in order to return to the default zoom level.
4. Check the "Zoom text only" checkbox and perform another zoom in or out like in step 3.
#### Actual result:
After checking the Zoom text only box and perform a zoom change using ctrl + mousewheel, the zoom level is applied for text only but starting from 100% instead from the default zoom level.
#### Expected result:
The zoom level should be applied starting from the default zoom level value set in step 2 (133% in our case).
NOTE: After checking the "Zoom text only" option from step 4, if the user refresh the page it works ok, the zoom changes are applied starting from the default zoom value. Note that other checkbox options like "Use smooth scrolling" from Browsing section is applied immediately without refreshing the page. Also if I change the Zoom text only option from menu bar->view->zoom->zoom text only, it works ok, the zoom level is changed starting from the default zoom level set in step 2, not from the 100%.
Please see the attachment.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-28 09:52:57+00:00
|
2020-02-07 08:11:47+00:00
| 366 | 1 |
1611929
|
Urlbar background-color does not align with the Photon colors
|
The design update 1 Urlbar background-color is [`rgb(71, 71, 73)`](https://searchfox.org/mozilla-central/rev/cbd110d718bc89a499d3f996af24532abbf6f8ea/browser/themes/addons/dark/manifest.json#28). This is not a [Photon colour](https://design.firefox.com/photon/visuals/color.html#grey). The design update 1 spec calls for the Urlbar background to be Gray 60, but that reduces contrast too much. We can't make it Gray 70 because that's the colour of the toolbar. We maybe need something along the lines of a Gray 65.
|
Urlbar background-color does not align with the Photon colors The design update 1 Urlbar background-color is [`rgb(71, 71, 73)`](https://searchfox.org/mozilla-central/rev/cbd110d718bc89a499d3f996af24532abbf6f8ea/browser/themes/addons/dark/manifest.json#28). This is not a [Photon colour](https://design.firefox.com/photon/visuals/color.html#grey). The design update 1 spec calls for the Urlbar background to be Gray 60, but that reduces contrast too much. We can't make it Gray 70 because that's the colour of the toolbar. We maybe need something along the lines of a Gray 65.
|
P3
|
NEW
|
2020-01-28 13:43:03+00:00
|
2023-03-06 20:14:36+00:00
| 192 | 3 |
|
1611930
|
Left-side Home toolbar button does not reliably overflow
|
When the Home button is in its default position in the toolbar next to the Refresh button, it does not reliably overflow when the window is small. This is probably true of any left-side toolbar button in Home's default position, although I haven't checked this. Dao identified that this seems to be caused by the [Urlbar sizing at small window widths](https://searchfox.org/mozilla-central/rev/cbd110d718bc89a499d3f996af24532abbf6f8ea/browser/base/content/browser.css#743,757,768). His work on bug 1610497 seems to improve the overflow behaviour, so we should check this again when that bug lands.
|
Left-side Home toolbar button does not reliably overflow When the Home button is in its default position in the toolbar next to the Refresh button, it does not reliably overflow when the window is small. This is probably true of any left-side toolbar button in Home's default position, although I haven't checked this. Dao identified that this seems to be caused by the [Urlbar sizing at small window widths](https://searchfox.org/mozilla-central/rev/cbd110d718bc89a499d3f996af24532abbf6f8ea/browser/base/content/browser.css#743,757,768). His work on bug 1610497 seems to improve the overflow behaviour, so we should check this again when that bug lands.
|
P2
|
RESOLVED
|
FIXED
|
2020-01-28 13:51:14+00:00
|
2020-02-25 13:58:40+00:00
| 196 | 2 |
1612045
|
"Use Current Pages" is wrongly active even if no new tabs are opened
|
**[Affected versions]:**
- Firefox 74.0a1 Build ID 20200128214036
- Firefox 73.0b10 Build ID 20200125104833
- Firefox 72.0.2 Build ID 20200117190643
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[Prerequisites]:**
- Have only one tab opened.
**[Steps to reproduce]:**
1. Open about:preferences#home page in the same tab.
2. From the "Homepage and new window" dropdown select "Custom URLs..." option.
3. Observe the "Use Current Pages" button.
**[Expected result]:**
- "Use Current Pages" button is inactive.
**[Actual result]:**
- "Use Current Pages" button is active.
**[Additional notes]:**
- After a few clicks the button turns inactive.
- The button is activated back after the "Use Bookmark" action is used.
|
"Use Current Pages" is wrongly active even if no new tabs are opened **[Affected versions]:**
- Firefox 74.0a1 Build ID 20200128214036
- Firefox 73.0b10 Build ID 20200125104833
- Firefox 72.0.2 Build ID 20200117190643
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[Prerequisites]:**
- Have only one tab opened.
**[Steps to reproduce]:**
1. Open about:preferences#home page in the same tab.
2. From the "Homepage and new window" dropdown select "Custom URLs..." option.
3. Observe the "Use Current Pages" button.
**[Expected result]:**
- "Use Current Pages" button is inactive.
**[Actual result]:**
- "Use Current Pages" button is active.
**[Additional notes]:**
- After a few clicks the button turns inactive.
- The button is activated back after the "Use Bookmark" action is used.
|
P3
|
NEW
|
2020-01-29 08:14:22+00:00
|
2022-10-11 23:53:43+00:00
| 251 | 3 |
|
1612058
|
[L10n] about:newtab search field does not list search suggestions in RTL when using a LTR language
|
**[Affected versions]:**
- Firefox 74.0a1 Build ID 20200128214036
- Firefox 73.0b10 Build ID 20200125104833
- Firefox 72.0.2 Build ID 20200117190643
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[Prerequisites]:**
- Have an βarβ Firefox build installed.
**[Steps to reproduce]:**
1. Open about:newtab page.
2. Type a search keyword in the search field using a LTR language.
3. Observe the search suggestions.
**[Expected result]:**
- Search suggestions are displayed on the right side.
**[Actual result]:**
- Search suggestions are displayed on the left side.
**[Additional notes]:**
- This is not reproducible if the search is performed from Awesome bar or toolbar search.
- This issue is not reproducible using a RTL language.
- This issue might not be encountered in real life scenarios.
|
[L10n] about:newtab search field does not list search suggestions in RTL when using a LTR language **[Affected versions]:**
- Firefox 74.0a1 Build ID 20200128214036
- Firefox 73.0b10 Build ID 20200125104833
- Firefox 72.0.2 Build ID 20200117190643
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[Prerequisites]:**
- Have an βarβ Firefox build installed.
**[Steps to reproduce]:**
1. Open about:newtab page.
2. Type a search keyword in the search field using a LTR language.
3. Observe the search suggestions.
**[Expected result]:**
- Search suggestions are displayed on the right side.
**[Actual result]:**
- Search suggestions are displayed on the left side.
**[Additional notes]:**
- This is not reproducible if the search is performed from Awesome bar or toolbar search.
- This issue is not reproducible using a RTL language.
- This issue might not be encountered in real life scenarios.
|
P2
|
NEW
|
2020-01-29 09:24:46+00:00
|
2022-10-10 19:29:19+00:00
| 268 | 2 |
|
1612108
|
Onboarding Triplets can be wrongly dismissed from about:welcome page while the onboarding modal is still displayed
|
**[Affected versions]:**
- Firefox 73.0b11 Build-ID 20200128001646
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[Steps to reproduce]:**
1. Open about:welcome page.
2. Observe the top-right side of the page.
**[Expected result]:**
- A grayed out and unactionable βXβ button is displayed.
**[Actual result]:**
- An actionable βXβ button is displayed.
**[Regression]:**
- Last good revision: 63822634f6ffb878bd3aa64c1789b3452d178bee
- First bad revision: 0152641c5419db9c9e723afe55bef1b63c699e96
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=63822634f6ffb878bd3aa64c1789b3452d178bee&tochange=0152641c5419db9c9e723afe55bef1b63c699e96
**[Additional notes]:**
- The onboarding Triplets are dismissed if the βXβ button is clicked.
- This issue was fixed on Firefox Nightly 74.0a1 (Build 20200129093157) by Bug 1609462.
@thecount, @pdahiya could you please take a look at Bug 1609462 and see if it will be safe to be uplifted in Beta?
|
Onboarding Triplets can be wrongly dismissed from about:welcome page while the onboarding modal is still displayed **[Affected versions]:**
- Firefox 73.0b11 Build-ID 20200128001646
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[Steps to reproduce]:**
1. Open about:welcome page.
2. Observe the top-right side of the page.
**[Expected result]:**
- A grayed out and unactionable βXβ button is displayed.
**[Actual result]:**
- An actionable βXβ button is displayed.
**[Regression]:**
- Last good revision: 63822634f6ffb878bd3aa64c1789b3452d178bee
- First bad revision: 0152641c5419db9c9e723afe55bef1b63c699e96
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=63822634f6ffb878bd3aa64c1789b3452d178bee&tochange=0152641c5419db9c9e723afe55bef1b63c699e96
**[Additional notes]:**
- The onboarding Triplets are dismissed if the βXβ button is clicked.
- This issue was fixed on Firefox Nightly 74.0a1 (Build 20200129093157) by Bug 1609462.
@thecount, @pdahiya could you please take a look at Bug 1609462 and see if it will be safe to be uplifted in Beta?
|
P1
|
VERIFIED
|
FIXED
|
2020-01-29 13:49:49+00:00
|
2020-02-06 06:39:39+00:00
| 408 | 1 |
1612122
|
Copy / Cut options from context menu are available on empty searchbar
|
**Affected versions**
- Firefox 74.0a1
- Firefox 73.0b11
- Firefox 72.0
**Affected platforms**
- Windows 10 & 7
- macOS 10.13
- Ubuntu 18.04
**Steps to reproduce**
1. Open Firefox and go to Options / Preferences
2. Enable the search bar
3. Right click on the added search bar
**Expected result**
- The copy / cut options are greyed out as there is no input text
**Actual result**
- The copy / cut options are available
**Regression range**
- I will see for a regression. On a look over, 69.0b8 seems to not be affected, but
71.0 is affected.
**Additional notes**
- The behavior can be seen in the attachment
- Context menu options both in pages and the search bar from toolbar are affected by this issue.
- A page affected by this is [example](https://www.roboform.com/filling-test-all-fields).
- 68.4.2esr is affected too.
- If considered, a separate bug should be opened for the issue on pages, as opposed to just the search bar.
|
Copy / Cut options from context menu are available on empty searchbar **Affected versions**
- Firefox 74.0a1
- Firefox 73.0b11
- Firefox 72.0
**Affected platforms**
- Windows 10 & 7
- macOS 10.13
- Ubuntu 18.04
**Steps to reproduce**
1. Open Firefox and go to Options / Preferences
2. Enable the search bar
3. Right click on the added search bar
**Expected result**
- The copy / cut options are greyed out as there is no input text
**Actual result**
- The copy / cut options are available
**Regression range**
- I will see for a regression. On a look over, 69.0b8 seems to not be affected, but
71.0 is affected.
**Additional notes**
- The behavior can be seen in the attachment
- Context menu options both in pages and the search bar from toolbar are affected by this issue.
- A page affected by this is [example](https://www.roboform.com/filling-test-all-fields).
- 68.4.2esr is affected too.
- If considered, a separate bug should be opened for the issue on pages, as opposed to just the search bar.
|
P3
|
VERIFIED
|
FIXED
|
2020-01-29 14:25:44+00:00
|
2020-06-05 12:46:04+00:00
| 281 | 3 |
1612206
|
Ensure maybeReloadEngines is not missed
|
Spinning this out of https://bugzilla.mozilla.org/show_bug.cgi?id=1589618
|
Ensure maybeReloadEngines is not missed Spinning this out of https://bugzilla.mozilla.org/show_bug.cgi?id=1589618
|
P1
|
RESOLVED
|
FIXED
|
2020-01-29 20:28:47+00:00
|
2020-02-23 19:22:10+00:00
| 43 | 1 |
1612254
|
Keyboard shortcut (cmd + ,) does not create subscript as it does in other browsers
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Reproduction:
1. Open Firefox
2. Go to drive.google.com
3. Open document in Google docs
4. Highlight character in google docs (such as the "2" in H20)
5. Press command + , (comma)
Actual results:
Command + , opens a new tab in firefox - about:preferences
Expected results:
Highlighted character should turn into a subscript
(this works in google docs in other browsers and is listed as the proper shortcut for a subscript; superscript, command + . works)
|
Keyboard shortcut (cmd + ,) does not create subscript as it does in other browsers User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Reproduction:
1. Open Firefox
2. Go to drive.google.com
3. Open document in Google docs
4. Highlight character in google docs (such as the "2" in H20)
5. Press command + , (comma)
Actual results:
Command + , opens a new tab in firefox - about:preferences
Expected results:
Highlighted character should turn into a subscript
(this works in google docs in other browsers and is listed as the proper shortcut for a subscript; superscript, command + . works)
|
P2
|
VERIFIED
|
FIXED
|
2020-01-30 06:25:44+00:00
|
2020-05-18 14:38:48+00:00
| 182 | 2 |
1612261
|
PDF.js does not render borders consistently
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Opened attached PDF in Firefox, Chrome, and Adobe Reader DC
Actual results:
If you scroll to the bottom and see that there is a line under "Saturday 22 December 2018" in Chrome and Adobe Acrobat Reader, but not in Firefox.
Expected results:
Firefox, Chrome and Adobe Reader DC should all display consistently.
|
PDF.js does not render borders consistently User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Opened attached PDF in Firefox, Chrome, and Adobe Reader DC
Actual results:
If you scroll to the bottom and see that there is a line under "Saturday 22 December 2018" in Chrome and Adobe Acrobat Reader, but not in Firefox.
Expected results:
Firefox, Chrome and Adobe Reader DC should all display consistently.
|
P3
|
RESOLVED
|
FIXED
|
2020-01-30 07:56:15+00:00
|
2021-10-11 08:57:50+00:00
| 127 | 3 |
1612268
|
dragging a tab after restarting firefox not possible while tab is still loading
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Close firefox with saving the current opened tabs.
Start Firefox, now move mouse cursor to a tab that's not (re)loaded yet, then hold left mousbutton and try to drag it left or right (over another tab).
Actual results:
not working
|
dragging a tab after restarting firefox not possible while tab is still loading User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Close firefox with saving the current opened tabs.
Start Firefox, now move mouse cursor to a tab that's not (re)loaded yet, then hold left mousbutton and try to drag it left or right (over another tab).
Actual results:
not working
|
P3
|
RESOLVED
|
WORKSFORME
|
2020-01-30 08:46:11+00:00
|
2024-12-05 14:48:08+00:00
| 126 | 3 |
1612403
|
File extensions are duplicated for file inputs with custom 'accept'
|
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Firefox 72 on Windows 7 and Windows 10.
Given a file input element with a custom 'accept' attribute:
<input type="file" name="file" accept="application/pdf,application/msword,application/vnd.openxmlformats-officedocument.wordprocessingml.document,application/vnd.ms-excel,application/vnd.openxmlformats-officedocument.spreadsheetml.sheet,text/plain" multiple="multiple">
Actual results:
When clicked, a file dialog is displayed where the file extensions are duplicated in both the "All supported types" item and in the individual file type items (see screenshot):
All Supported Types (*.pdf;*.pdf;*.doc;*.doc;*.docx;*.docx;*.xls;*.xls;*.xlsx;*.xlsx;*.txt*.txt)
Adobe Acrobat Document (*.pdf;*.pdf)
Microsoft Word 97 - 2003 Document (*.doc;*.doc)
Microsoft Word Document (*.docx;*.docx)
Microsoft Excel 97-2003 Worksheet (*.xls;*.xls)
Microsoft Excel Worksheet (*.xlsx;*.xlsx)
Text Document (*.txt;*.txt)
Expected results:
File extensions in the file types list are not duplicated:
All Supported Types (*.pdf; *.doc; *.docx; *.xls; *.xlsx; *.txt)
Adobe Acrobat Document (*.pdf)
Microsoft Word 97 - 2003 Document (*.doc)
Microsoft Word Document (*.docx)
Microsoft Excel 97-2003 Worksheet (*.xls)
Microsoft Excel Worksheet (*.xlsx)
Text Document (*.txt)
|
File extensions are duplicated for file inputs with custom 'accept' User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Firefox 72 on Windows 7 and Windows 10.
Given a file input element with a custom 'accept' attribute:
<input type="file" name="file" accept="application/pdf,application/msword,application/vnd.openxmlformats-officedocument.wordprocessingml.document,application/vnd.ms-excel,application/vnd.openxmlformats-officedocument.spreadsheetml.sheet,text/plain" multiple="multiple">
Actual results:
When clicked, a file dialog is displayed where the file extensions are duplicated in both the "All supported types" item and in the individual file type items (see screenshot):
All Supported Types (*.pdf;*.pdf;*.doc;*.doc;*.docx;*.docx;*.xls;*.xls;*.xlsx;*.xlsx;*.txt*.txt)
Adobe Acrobat Document (*.pdf;*.pdf)
Microsoft Word 97 - 2003 Document (*.doc;*.doc)
Microsoft Word Document (*.docx;*.docx)
Microsoft Excel 97-2003 Worksheet (*.xls;*.xls)
Microsoft Excel Worksheet (*.xlsx;*.xlsx)
Text Document (*.txt;*.txt)
Expected results:
File extensions in the file types list are not duplicated:
All Supported Types (*.pdf; *.doc; *.docx; *.xls; *.xlsx; *.txt)
Adobe Acrobat Document (*.pdf)
Microsoft Word 97 - 2003 Document (*.doc)
Microsoft Word Document (*.docx)
Microsoft Excel 97-2003 Worksheet (*.xls)
Microsoft Excel Worksheet (*.xlsx)
Text Document (*.txt)
|
P2
|
RESOLVED
|
FIXED
|
2020-01-30 17:34:58+00:00
|
2020-02-28 15:42:18+00:00
| 482 | 2 |
1612509
|
System Highlight colour is not respected for the Urlbar result highlight in Dark theme
|
In default/light mode, we support using the system Highlight colour as the background colour for selected Urlbar results. In Dark Mode it is always blue.
|
System Highlight colour is not respected for the Urlbar result highlight in Dark theme In default/light mode, we support using the system Highlight colour as the background colour for selected Urlbar results. In Dark Mode it is always blue.
|
P3
|
RESOLVED
|
FIXED
|
2020-01-31 09:53:31+00:00
|
2020-02-04 16:23:16+00:00
| 50 | 3 |
1612522
|
Tracking Protection Shield inactive after going back to a previous page
|
**Affected versions**
- Firefox 72.0.2
- Firefox 73.0b11
- Firefox 74.0a1
**Affected platforms**
- Windows 10 & 7
- macOS 10.15
- Ubuntu 18.04
**Steps to reproduce**
1. Launch Firefox
2. Access this [link](https://senglehardt.com/test/trackingprotection/test_pages/tracking_protection)
3. Now access this [link](https://senglehardt.com/test/trackingprotection/test_pages/fingerprinting.html) in the same tab.
4. Go back to the previous page
**Expected result**
- The tracking protection shield is active and blocking
**Actual result**
- The tracking protection shield is inactive and "No trackers known to Firefox/Nightly were detected on this page" message is shown
**Regression range**
I will see for a regression
**Additional notes**
- The issue can be seen in the attachment.
- By doing the steps and refreshing the page after, the tracking protection will be active again.
|
Tracking Protection Shield inactive after going back to a previous page **Affected versions**
- Firefox 72.0.2
- Firefox 73.0b11
- Firefox 74.0a1
**Affected platforms**
- Windows 10 & 7
- macOS 10.15
- Ubuntu 18.04
**Steps to reproduce**
1. Launch Firefox
2. Access this [link](https://senglehardt.com/test/trackingprotection/test_pages/tracking_protection)
3. Now access this [link](https://senglehardt.com/test/trackingprotection/test_pages/fingerprinting.html) in the same tab.
4. Go back to the previous page
**Expected result**
- The tracking protection shield is active and blocking
**Actual result**
- The tracking protection shield is inactive and "No trackers known to Firefox/Nightly were detected on this page" message is shown
**Regression range**
I will see for a regression
**Additional notes**
- The issue can be seen in the attachment.
- By doing the steps and refreshing the page after, the tracking protection will be active again.
|
P3
|
NEW
|
2020-01-31 10:25:54+00:00
|
2022-10-11 23:54:18+00:00
| 261 | 3 |
|
1612588
|
_adjustFocusAfterTabSwitch can run before or after TabSelect
|
For Bug 1601052 I'm implementing a workaround where I have to wait for both TabSelect and the focus change, to be sure we touch the urlbar at the right time after a tab switch.
This happens more often when switching tabs repeatedly, the TabSelect event normally fires after _adjustFocusAfterTabSwitch, but sometimes it fires before it, so we get a TabSelect and then the focus changes to/from the urlbar.
Having a reliable timeline would help with implementing features, and it's unclear if this may be a cause for intermittent failures.
|
_adjustFocusAfterTabSwitch can run before or after TabSelect For Bug 1601052 I'm implementing a workaround where I have to wait for both TabSelect and the focus change, to be sure we touch the urlbar at the right time after a tab switch.
This happens more often when switching tabs repeatedly, the TabSelect event normally fires after _adjustFocusAfterTabSwitch, but sometimes it fires before it, so we get a TabSelect and then the focus changes to/from the urlbar.
Having a reliable timeline would help with implementing features, and it's unclear if this may be a cause for intermittent failures.
|
P2
|
NEW
|
2020-01-31 16:14:26+00:00
|
2022-10-11 23:54:26+00:00
| 146 | 2 |
|
1612648
|
Picture in picture icon overlay overlaps mute tab
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Open a tab with a site that has a video that can be played using picture in picture.
Convert the video into a picture in picture overlay.
Note that the close button of the tab is preceded by the picture in picture icon.
Hover over the picture in picture icon on the tab (see screenshot)
Actual results:
The tooltip displays Mute tab
The icon displayed is not for muting tab but picture in picture icon
Clicking on the picture in picture icon mutes the tab
Expected results:
The icon on tab should be Mute icon.
The picture in picture icon on tab shouldn't overlap the Mute icon.
|
Picture in picture icon overlay overlaps mute tab User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Open a tab with a site that has a video that can be played using picture in picture.
Convert the video into a picture in picture overlay.
Note that the close button of the tab is preceded by the picture in picture icon.
Hover over the picture in picture icon on the tab (see screenshot)
Actual results:
The tooltip displays Mute tab
The icon displayed is not for muting tab but picture in picture icon
Clicking on the picture in picture icon mutes the tab
Expected results:
The icon on tab should be Mute icon.
The picture in picture icon on tab shouldn't overlap the Mute icon.
|
P2
|
RESOLVED
|
FIXED
|
2020-02-01 02:18:17+00:00
|
2021-05-11 13:46:07+00:00
| 180 | 2 |
1612650
|
Shift clicking navigation buttons in private browsing opens content in non-private browsing window
|
As reported by a user on the support forums, there appears to be an issue when shift clicking the navigation buttons in private browsing mode.
To reproduce the issue, open a new private window and navigate to a few different websites. Then, hold down shift on the keyboard and click the back button on the toolbar. Since the history of that tab is tied into private browsing, it would be expected that the shift shortcut would open a new private browsing window.
However, it opens the page in a new non-private browsing window. This issue is a potential privacy bug, since the page would then be logged into the user's history and cache/cookies would be saved.
I've been able to reproduce the issue on Windows 10, but I assume the bug happens on all systems.
|
Shift clicking navigation buttons in private browsing opens content in non-private browsing window As reported by a user on the support forums, there appears to be an issue when shift clicking the navigation buttons in private browsing mode.
To reproduce the issue, open a new private window and navigate to a few different websites. Then, hold down shift on the keyboard and click the back button on the toolbar. Since the history of that tab is tied into private browsing, it would be expected that the shift shortcut would open a new private browsing window.
However, it opens the page in a new non-private browsing window. This issue is a potential privacy bug, since the page would then be logged into the user's history and cache/cookies would be saved.
I've been able to reproduce the issue on Windows 10, but I assume the bug happens on all systems.
|
P2
|
VERIFIED
|
FIXED
|
2020-02-01 03:22:17+00:00
|
2020-04-14 11:31:41+00:00
| 182 | 2 |
1612653
|
On the first click, "Bookmark this page" or "Edit This Bookmark" in the "Bookmark menu" is blank or obsolete.
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
1. Quit Firefox.
2. Launch Firefox.
3. Click "Bookmarks menu".
Actual results:
On the first click, "Bookmark this page" or "Edit This Bookmark" in the "Bookmarks menu" is blank.
On the second click, "Bookmark this page" or "Edit This Bookmark" in the "Bookmarks menu" is not blank.
Expected results:
"Bookmark this page" or "Edit This Bookmark" in the "Bookmarks menu" shoul not be blank.
|
On the first click, "Bookmark this page" or "Edit This Bookmark" in the "Bookmark menu" is blank or obsolete. User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
1. Quit Firefox.
2. Launch Firefox.
3. Click "Bookmarks menu".
Actual results:
On the first click, "Bookmark this page" or "Edit This Bookmark" in the "Bookmarks menu" is blank.
On the second click, "Bookmark this page" or "Edit This Bookmark" in the "Bookmarks menu" is not blank.
Expected results:
"Bookmark this page" or "Edit This Bookmark" in the "Bookmarks menu" shoul not be blank.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-01 04:32:13+00:00
|
2022-08-17 16:59:55+00:00
| 188 | 1 |
1612789
|
Dragging imported folders in bookmark manager does not move all nested bookmarks
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Exit Chrome browser
Open Firefox browser
Open Library > Bookmarks > Show All Bookmarks
Select Import and backup your bookmarks > Import Data from Another Browser ...
Select Chrome
Click Continue
Check all items for importing
Click Continue
Provide authorization for access to Chrome data
Click Done at the Import Complete dialog box
Drag top-level folders from "From Google Chrome" to "Bookmarks Toolbar"
Actual results:
Nested folders on the bookmarks toolbar are empty.
Expected results:
The nested bookmarks should appear on the bookmarks toolbar.
|
Dragging imported folders in bookmark manager does not move all nested bookmarks User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Exit Chrome browser
Open Firefox browser
Open Library > Bookmarks > Show All Bookmarks
Select Import and backup your bookmarks > Import Data from Another Browser ...
Select Chrome
Click Continue
Check all items for importing
Click Continue
Provide authorization for access to Chrome data
Click Done at the Import Complete dialog box
Drag top-level folders from "From Google Chrome" to "Bookmarks Toolbar"
Actual results:
Nested folders on the bookmarks toolbar are empty.
Expected results:
The nested bookmarks should appear on the bookmarks toolbar.
|
P3
|
UNCONFIRMED
|
2020-02-03 08:57:56+00:00
|
2023-08-02 14:35:16+00:00
| 176 | 3 |
|
1612838
|
Duplicate submission of the form with file in Firefox 68 onwards
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I am calling below javascript function(debugFF) to submit form with a .xml file using enctype="multipart/form-data" and post method.
function debugFF() {
var myForm=document.getElementById("myForm");
var event1=document.createEvent("HTMLEvents");
event1.initEvent("submit",true,true);
if(myForm.dispatchEvent(event1)){
myForm.submit();
}
}
Actual results:
The form is being submitted twice to action URL in Firefox V68 (Also reproducible in latest Firfox 72.0.2). And If I don't select any file then there is no such issue.
Expected results:
It should be submitted only once regardless any file is chosen or not. This issue doesn't exist in old Firefox (V67 and earlier).
|
Duplicate submission of the form with file in Firefox 68 onwards User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I am calling below javascript function(debugFF) to submit form with a .xml file using enctype="multipart/form-data" and post method.
function debugFF() {
var myForm=document.getElementById("myForm");
var event1=document.createEvent("HTMLEvents");
event1.initEvent("submit",true,true);
if(myForm.dispatchEvent(event1)){
myForm.submit();
}
}
Actual results:
The form is being submitted twice to action URL in Firefox V68 (Also reproducible in latest Firfox 72.0.2). And If I don't select any file then there is no such issue.
Expected results:
It should be submitted only once regardless any file is chosen or not. This issue doesn't exist in old Firefox (V67 and earlier).
|
P1
|
RESOLVED
|
DUPLICATE
|
2020-02-03 13:04:02+00:00
|
2020-02-12 20:21:52+00:00
| 269 | 1 |
1612882
|
Social category is shown under None Detected even when blocking
|
On https://senglehardt.com/test/trackingprotection/test_pages/social_tracking_protection.html, the content blocking log shows social cookies blocked but the UI says none detected. Need to investigate this...
|
Social category is shown under None Detected even when blocking On https://senglehardt.com/test/trackingprotection/test_pages/social_tracking_protection.html, the content blocking log shows social cookies blocked but the UI says none detected. Need to investigate this...
|
P3
|
NEW
|
2020-02-03 14:56:52+00:00
|
2022-10-11 23:54:45+00:00
| 64 | 3 |
|
1612902
|
[Custom mode] Social Media Trackers donβt appear in the "Allowed" sections
|
**Affected versions**
* Firefox 74.a01
* Firefox 73.0b11
*Firefox 72.0.2
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04 x64
* macOS 10.13
**Steps to reproduce**
1. Go to about:preferences#privacy.
2. Select Custom mode and make sure that everything is selected except "Cookies".
3. Go to https://www.boredpanda.com/ or any other site that has Social Media Trackers.
4. Click on the shield icon.
**Expected result**
* Social Media Trackers are displayed in the "Allowed" section.
**Actual result**
* Social Media Trackers are displayed in the "None Detected" section.
**Regression range**
* last good: 01-11-2019
* first bad: 04-11-2019
* I can't find the exact regression, because on the builds that between 02-11-2019 and 02-11-2019, Social Media trackers are not detected.
**Additional notes**
* If you select everything from Custom, Social Media Trackers are listed in the "Blocked" section.
|
[Custom mode] Social Media Trackers donβt appear in the "Allowed" sections **Affected versions**
* Firefox 74.a01
* Firefox 73.0b11
*Firefox 72.0.2
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04 x64
* macOS 10.13
**Steps to reproduce**
1. Go to about:preferences#privacy.
2. Select Custom mode and make sure that everything is selected except "Cookies".
3. Go to https://www.boredpanda.com/ or any other site that has Social Media Trackers.
4. Click on the shield icon.
**Expected result**
* Social Media Trackers are displayed in the "Allowed" section.
**Actual result**
* Social Media Trackers are displayed in the "None Detected" section.
**Regression range**
* last good: 01-11-2019
* first bad: 04-11-2019
* I can't find the exact regression, because on the builds that between 02-11-2019 and 02-11-2019, Social Media trackers are not detected.
**Additional notes**
* If you select everything from Custom, Social Media Trackers are listed in the "Blocked" section.
|
P3
|
NEW
|
2020-02-03 15:32:11+00:00
|
2022-10-11 23:54:47+00:00
| 276 | 3 |
|
1613076
|
Checkbox and radio button toggles when click on the empty area following the label
|
This is very annoying. The problem happens on about:preferences.
Steps to reproduce:
1. Open about:preferences
2. Click on the empty area following the label of checkbox/radio button
Actual results:
checkbox/radio button toggles unexpectedly.
Expected results:
should not toggle
|
Checkbox and radio button toggles when click on the empty area following the label This is very annoying. The problem happens on about:preferences.
Steps to reproduce:
1. Open about:preferences
2. Click on the empty area following the label of checkbox/radio button
Actual results:
checkbox/radio button toggles unexpectedly.
Expected results:
should not toggle
|
P5
|
RESOLVED
|
DUPLICATE
|
2020-02-04 11:24:49+00:00
|
2024-02-20 10:16:01+00:00
| 76 | 5 |
1613093
|
The βPopular Topicsβ navigation section is not displayed for the βUSβ and βCAβ regions in a New Tab page
|
**[Affected versions]:**
- Firefox 73.0 Build ID 20200203203546
- Firefox 74.0a1 Build ID 20200203214717
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[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 after the βRecommended by Pocketβ section.
**[Expected result]:**
βPopular Topicsβ are displayed.
**[Actual result]:**
βPopular Topicsβ are missing.
**[Regression]:**
Last good revision: 8680f0205149f322f6646c4d4db896f2ebbb5881
First bad revision: 7fcdfe9a24e467bd95219eaa331aa13c1575796a
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8680f0205149f322f6646c4d4db896f2ebbb5881&tochange=7fcdfe9a24e467bd95219eaa331aa13c1575796a
It looks like bug 1598724 has caused this issue.
**[Additional notes]:**
No matter how many new tabs are opened, βPopular Topicsβ are not displayed.
βPopular Topicsβ are displayed after page refresh.
@thecount could you please take a look at this?
|
The βPopular Topicsβ navigation section is not displayed for the βUSβ and βCAβ regions in a New Tab page **[Affected versions]:**
- Firefox 73.0 Build ID 20200203203546
- Firefox 74.0a1 Build ID 20200203214717
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[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 after the βRecommended by Pocketβ section.
**[Expected result]:**
βPopular Topicsβ are displayed.
**[Actual result]:**
βPopular Topicsβ are missing.
**[Regression]:**
Last good revision: 8680f0205149f322f6646c4d4db896f2ebbb5881
First bad revision: 7fcdfe9a24e467bd95219eaa331aa13c1575796a
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8680f0205149f322f6646c4d4db896f2ebbb5881&tochange=7fcdfe9a24e467bd95219eaa331aa13c1575796a
It looks like bug 1598724 has caused this issue.
**[Additional notes]:**
No matter how many new tabs are opened, βPopular Topicsβ are not displayed.
βPopular Topicsβ are displayed after page refresh.
@thecount could you please take a look at this?
|
P1
|
VERIFIED
|
FIXED
|
2020-02-04 12:48:37+00:00
|
2020-02-28 10:04:01+00:00
| 416 | 1 |
1613264
|
Double clicking to select the text in the urlbar doesn't work for some completions anymore
|
STR:
- Type "goo"
- This will autocomplete to "google.com" and will suggest "https://google.com/ -- Visit"
- Double clicking in the urlbar should select all the text but it doesn't. It selects it momentarily and then unselects it.
I did a regression window and found this:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b9ffa67dd4dfb935b4f39010eefd615c6d70fdab&tochange=32f7019f65826f9aab0d36d177064461ed1f9b40
|
Double clicking to select the text in the urlbar doesn't work for some completions anymore STR:
- Type "goo"
- This will autocomplete to "google.com" and will suggest "https://google.com/ -- Visit"
- Double clicking in the urlbar should select all the text but it doesn't. It selects it momentarily and then unselects it.
I did a regression window and found this:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b9ffa67dd4dfb935b4f39010eefd615c6d70fdab&tochange=32f7019f65826f9aab0d36d177064461ed1f9b40
|
P1
|
RESOLVED
|
FIXED
|
2020-02-04 23:06:28+00:00
|
2020-02-08 18:30:53+00:00
| 187 | 1 |
1613276
|
data URIs are misinterpreted as a search, if they include a question mark and a space
|
STR:
1. Type or copypaste this data URI into your location bar, and then hit enter:
```
data:text/html,oh hi?
```
(Notice the space character - it is important.)
EXPECTED RESULTS:
Firefox should show me a basic document with content `oh hi?`
ACTUAL RESULTS:
Firefox takes me to a google search for the **search string** `data:text/html,oh hi?`
---
Here's a slightly more complex data URI that's a bit clearer about why it needs spaces and a question mark (and also triggers this issue):
> data:text/html,<div style="color:green">Is this green?
In Chrome and older versions of Firefox, this ^^ URI produces a basic document with some green text saying "Is this green?". In current Firefox and Firefox Nightly, it gives ACTUAL RESULTS (a google search page for the raw data URI).
mozregression gives me this range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f3e62cd8aef6a739ec433be0c43837fd23af2426&tochange=7a266c35cb309b3be5686b2814947092623bd36e
...which means this was a regression from:
https://hg.mozilla.org/integration/autoland/rev/7a266c35cb309b3be5686b2814947092623bd36e
> Ed Lee β Bug 1541502 - Add Pocket menu, triggering improvements and bug fixes to Activity Stream r=k88hudson
|
data URIs are misinterpreted as a search, if they include a question mark and a space STR:
1. Type or copypaste this data URI into your location bar, and then hit enter:
```
data:text/html,oh hi?
```
(Notice the space character - it is important.)
EXPECTED RESULTS:
Firefox should show me a basic document with content `oh hi?`
ACTUAL RESULTS:
Firefox takes me to a google search for the **search string** `data:text/html,oh hi?`
---
Here's a slightly more complex data URI that's a bit clearer about why it needs spaces and a question mark (and also triggers this issue):
> data:text/html,<div style="color:green">Is this green?
In Chrome and older versions of Firefox, this ^^ URI produces a basic document with some green text saying "Is this green?". In current Firefox and Firefox Nightly, it gives ACTUAL RESULTS (a google search page for the raw data URI).
mozregression gives me this range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f3e62cd8aef6a739ec433be0c43837fd23af2426&tochange=7a266c35cb309b3be5686b2814947092623bd36e
...which means this was a regression from:
https://hg.mozilla.org/integration/autoland/rev/7a266c35cb309b3be5686b2814947092623bd36e
> Ed Lee β Bug 1541502 - Add Pocket menu, triggering improvements and bug fixes to Activity Stream r=k88hudson
|
P3
|
VERIFIED
|
FIXED
|
2020-02-05 01:05:14+00:00
|
2020-04-30 15:02:42+00:00
| 426 | 3 |
1613308
|
Cannot drag and drop the padlock icon to make a bookmark when the site specifies an invalid favicon
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
1. Visit https://blog.lizzie.io/linux-containers-in-500-loc.html .
2. To make a bookmark, I tried to drag the padlock icon which is at the right side of a shield icon in an address bar.
Actual results:
I could not drag the padlock icon.
Expected results:
I expected that I can drag the padlock icon and drop it into a bookmark bar.
|
Cannot drag and drop the padlock icon to make a bookmark when the site specifies an invalid favicon User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
1. Visit https://blog.lizzie.io/linux-containers-in-500-loc.html .
2. To make a bookmark, I tried to drag the padlock icon which is at the right side of a shield icon in an address bar.
Actual results:
I could not drag the padlock icon.
Expected results:
I expected that I can drag the padlock icon and drop it into a bookmark bar.
|
P3
|
VERIFIED
|
FIXED
|
2020-02-05 08:04:33+00:00
|
2020-03-13 13:43:28+00:00
| 161 | 3 |
1613320
|
Tooltip is not displayed when the user hover the mouse over the protection panel shield icon in the highlighted area
|
#### Affected versions:
ALL
#### Affected platforms:
ALL
#### Steps:
1. Launch Firefox with a new profile access any website e.g www.wikipedia.org
2. Hover with the mouse over the shield icon near the address bar, in the highlighted area but not right on the shield icon.
#### Actual result:
The shield icon is highlighted but the tooltip is displayed only if the user hover the mouse cursor exactly on the shield icon. If hover the mouse in the highlighted zone but not directly on the shield icon the tooltip is not displayed.
#### Expected result:
The tooltip should be displayed when the user hover the mouse anywhere in the highlighted area, like on the other buttons or menus.
Please see the video attachment for a better understanding.
|
Tooltip is not displayed when the user hover the mouse over the protection panel shield icon in the highlighted area #### Affected versions:
ALL
#### Affected platforms:
ALL
#### Steps:
1. Launch Firefox with a new profile access any website e.g www.wikipedia.org
2. Hover with the mouse over the shield icon near the address bar, in the highlighted area but not right on the shield icon.
#### Actual result:
The shield icon is highlighted but the tooltip is displayed only if the user hover the mouse cursor exactly on the shield icon. If hover the mouse in the highlighted zone but not directly on the shield icon the tooltip is not displayed.
#### Expected result:
The tooltip should be displayed when the user hover the mouse anywhere in the highlighted area, like on the other buttons or menus.
Please see the video attachment for a better understanding.
|
P3
|
VERIFIED
|
FIXED
|
2020-02-05 09:15:11+00:00
|
2020-03-04 12:10:35+00:00
| 198 | 3 |
1613337
|
Support login import from Chrome/Edge 80+ on Windows
|
https://bugs.chromium.org/p/chromium/issues/detail?id=1000799
Seems like we might need migrator updates to continue migrating things chromium is encrypting with oscrypt (the issue mentions cookies, though information elsewhere seems to indicate this may also affect passwords?).
|
Support login import from Chrome/Edge 80+ on Windows https://bugs.chromium.org/p/chromium/issues/detail?id=1000799
Seems like we might need migrator updates to continue migrating things chromium is encrypting with oscrypt (the issue mentions cookies, though information elsewhere seems to indicate this may also affect passwords?).
|
P1
|
VERIFIED
|
FIXED
|
2020-02-05 10:46:44+00:00
|
2020-03-03 18:18:39+00:00
| 88 | 1 |
1613477
|
Cert exception UI in captive portal error page looks broken and doesn't work
|
[edited]
The "advanced" section in the captive portal error page currently looks like it's missing information, and the "accept risk and continue" button doesn't seem to do anything.
|
Cert exception UI in captive portal error page looks broken and doesn't work [edited]
The "advanced" section in the captive portal error page currently looks like it's missing information, and the "accept risk and continue" button doesn't seem to do anything.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-05 20:03:34+00:00
|
2020-03-30 13:40:21+00:00
| 58 | 1 |
1613557
|
"Our Sponsors And Your Privacy" dialog has awkward blank space on its left and right side
|
STR:
1. Hover some sponsored new-tab tile, and click its "..." menu when it appears.
2. Choose "Our sponsors and your privacy.
ACTUAL RESULTS:
The dialog that appears has an awkwardly large amount of blank space to its left and right sides. (It's awkwardly wide, as compared to its content)
EXPECTED RESULTS:
Content should be wider, to fit the dialog (or the dialog should be smaller, to fit the content).
--
Analysis:
Looking in devtools, it looks like the extra space is created by the difference between the widths in these two rules:
```
.modalOverlayInner {
...
max-width: 960px;
}
```
(This is what constrains the width of the dialog.)
Vs...
```
.ds-privacy-modal .privacy-notice {
max-width: 572px;
```
(This is what constrains the width of the dialog's contents).
If I untick the latter max-width, then the content fills the space on either side (and the dialog's height is reduced accordingly, since there are fewer lines of text).
Is there a reason we're using such a small max-width for the content here, given that the dialog allows itself to be significantly wider?
|
"Our Sponsors And Your Privacy" dialog has awkward blank space on its left and right side STR:
1. Hover some sponsored new-tab tile, and click its "..." menu when it appears.
2. Choose "Our sponsors and your privacy.
ACTUAL RESULTS:
The dialog that appears has an awkwardly large amount of blank space to its left and right sides. (It's awkwardly wide, as compared to its content)
EXPECTED RESULTS:
Content should be wider, to fit the dialog (or the dialog should be smaller, to fit the content).
--
Analysis:
Looking in devtools, it looks like the extra space is created by the difference between the widths in these two rules:
```
.modalOverlayInner {
...
max-width: 960px;
}
```
(This is what constrains the width of the dialog.)
Vs...
```
.ds-privacy-modal .privacy-notice {
max-width: 572px;
```
(This is what constrains the width of the dialog's contents).
If I untick the latter max-width, then the content fills the space on either side (and the dialog's height is reduced accordingly, since there are fewer lines of text).
Is there a reason we're using such a small max-width for the content here, given that the dialog allows itself to be significantly wider?
|
P2
|
NEW
|
2020-02-06 01:46:05+00:00
|
2022-10-11 23:55:25+00:00
| 313 | 2 |
|
1613577
|
Some pending/discarded tabs are loaded when dragged to an existing window
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
0. Have at least two windows, at least one of which has at least four tabs. The Auto Tab Discard extension is helpful but not required.
1. Select a window with at least four tabs.
2. Select the leftmost tab (tab 1).
3. Discard the other tabs. If using the Auto Tab Discard extension, right-click on the active tab and select "Auto Tab Discard", then "Discard Other Tabs in This Window". Alternatively, restart Firefox and restore the session.
4. Shift-click on tab 4 to highlight tabs 1-4.
5. Click on tab 3 and drag the highlighted tabs to the tab bar of any other window.
6. Repeat with different selections in steps 2, 4, and 5.
Actual results:
Tabs 1-4 are moved to the other window. Tab 1 remains loaded, tab 2 remains unloaded, tab 3 begins to load before moving, and tab 4 begins to load after moving.
More generally, any highlighted pending/discarded tabs to right of the active tab are loaded when moved to an existing window. This is consistent whether the left or right edge is selected first. The same tabs remain unloaded if moved to a new window instead, either by dragging or with the "Move to New Window" context menu item.
Expected results:
Pending/discarded tabs should remain pending/discarded when moved.
It looks like browser/components/sessionstore/test/browser_movePendingTabToNewWindow.js tries to test for this, but it uses the rightmost tab as the active tab, so no additional tabs are loaded.
|
Some pending/discarded tabs are loaded when dragged to an existing window User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
0. Have at least two windows, at least one of which has at least four tabs. The Auto Tab Discard extension is helpful but not required.
1. Select a window with at least four tabs.
2. Select the leftmost tab (tab 1).
3. Discard the other tabs. If using the Auto Tab Discard extension, right-click on the active tab and select "Auto Tab Discard", then "Discard Other Tabs in This Window". Alternatively, restart Firefox and restore the session.
4. Shift-click on tab 4 to highlight tabs 1-4.
5. Click on tab 3 and drag the highlighted tabs to the tab bar of any other window.
6. Repeat with different selections in steps 2, 4, and 5.
Actual results:
Tabs 1-4 are moved to the other window. Tab 1 remains loaded, tab 2 remains unloaded, tab 3 begins to load before moving, and tab 4 begins to load after moving.
More generally, any highlighted pending/discarded tabs to right of the active tab are loaded when moved to an existing window. This is consistent whether the left or right edge is selected first. The same tabs remain unloaded if moved to a new window instead, either by dragging or with the "Move to New Window" context menu item.
Expected results:
Pending/discarded tabs should remain pending/discarded when moved.
It looks like browser/components/sessionstore/test/browser_movePendingTabToNewWindow.js tries to test for this, but it uses the rightmost tab as the active tab, so no additional tabs are loaded.
|
P3
|
UNCONFIRMED
|
2020-02-06 05:02:56+00:00
|
2023-02-20 12:13:21+00:00
| 405 | 3 |
|
1613580
|
about:logins login view is not wide enough
|
I haven't checked w/ mozregression, but from the [login-item.css log](https://hg.mozilla.org/mozilla-central/log/tip/browser/components/aboutlogins/content/components/login-item.css), bug 1597993 seems like the only bug that could have possibly regressed this.
|
about:logins login view is not wide enough I haven't checked w/ mozregression, but from the [login-item.css log](https://hg.mozilla.org/mozilla-central/log/tip/browser/components/aboutlogins/content/components/login-item.css), bug 1597993 seems like the only bug that could have possibly regressed this.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-06 06:56:27+00:00
|
2022-04-09 16:43:39+00:00
| 103 | 1 |
1613612
|
Revert 1603071 - using release snippets in Nightly
|
In bug 1603071 we added a pref controlled way to display release snippets in Nightly without telemetry. This was a workaround for the Nightly channel that did not have content making it easy to overlook regressions.
We can revert that bug as we now have support from the snippets backend for this.
* there will be Nightly channel specific content
* we will still replicate the Release channel content in Nightly but have `&& false` appended to all targeting expressions
* this is meant to replicate the overhead of selecting a snippet that would happen in release
|
Revert 1603071 - using release snippets in Nightly In bug 1603071 we added a pref controlled way to display release snippets in Nightly without telemetry. This was a workaround for the Nightly channel that did not have content making it easy to overlook regressions.
We can revert that bug as we now have support from the snippets backend for this.
* there will be Nightly channel specific content
* we will still replicate the Release channel content in Nightly but have `&& false` appended to all targeting expressions
* this is meant to replicate the overhead of selecting a snippet that would happen in release
|
P1
|
VERIFIED
|
FIXED
|
2020-02-06 09:59:05+00:00
|
2020-02-20 15:45:02+00:00
| 139 | 1 |
1613640
|
[RTL] A vertical scrollbar is wrongly displayed on the onboarding modal if the "Continue" button is clicked while the email field is empty
|
**[Affected versions]:**
- Firefox 74.0a1 Build ID 20200205215017
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Ubuntu 16.04
**[Prerequisites]:**
- Use a RTL Firefox Nightly build.
**[Steps to reproduce]:**
1. Open about:welcome page.
2. Click the βContinueβ button.
**[Expected result]:**
βEnter emailβ field is highlighted in red and the "Valid email required" message is displayed.
**[Actual result]:**
A vertical scrollbar is also displayed in the left part of the onboarding modal.
**[Additional notes]:**
- Issue is also reproducible if invalid values are typed in the e-mail field.
- On Mac OS an horizontal scrollbar is also displayed for a few seconds.
- Issue is not reproducible using LTR builds
|
[RTL] A vertical scrollbar is wrongly displayed on the onboarding modal if the "Continue" button is clicked while the email field is empty **[Affected versions]:**
- Firefox 74.0a1 Build ID 20200205215017
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Ubuntu 16.04
**[Prerequisites]:**
- Use a RTL Firefox Nightly build.
**[Steps to reproduce]:**
1. Open about:welcome page.
2. Click the βContinueβ button.
**[Expected result]:**
βEnter emailβ field is highlighted in red and the "Valid email required" message is displayed.
**[Actual result]:**
A vertical scrollbar is also displayed in the left part of the onboarding modal.
**[Additional notes]:**
- Issue is also reproducible if invalid values are typed in the e-mail field.
- On Mac OS an horizontal scrollbar is also displayed for a few seconds.
- Issue is not reproducible using LTR builds
|
P1
|
VERIFIED
|
FIXED
|
2020-02-06 12:45:36+00:00
|
2020-02-19 10:55:36+00:00
| 245 | 1 |
1613662
|
Search Tip delay can interfere with typing
|
Search Tips are only shown after [a 200ms delay](https://searchfox.org/mozilla-central/rev/3a0a8e2762821c6afc1d235b3eb3dde63ad3b01a/browser/components/urlbar/UrlbarProviderSearchTips.jsm#75). If a user opens a page and quickly starts typing, their query will be deleted after 200ms when the Search Tip calls [`search("")`](https://searchfox.org/mozilla-central/rev/3a0a8e2762821c6afc1d235b3eb3dde63ad3b01a/browser/components/urlbar/UrlbarProviderSearchTips.jsm#317). This is made worse because the user continuing to type is enough to dismiss the tip, so it just flashes on screen for a moment.
|
Search Tip delay can interfere with typing Search Tips are only shown after [a 200ms delay](https://searchfox.org/mozilla-central/rev/3a0a8e2762821c6afc1d235b3eb3dde63ad3b01a/browser/components/urlbar/UrlbarProviderSearchTips.jsm#75). If a user opens a page and quickly starts typing, their query will be deleted after 200ms when the Search Tip calls [`search("")`](https://searchfox.org/mozilla-central/rev/3a0a8e2762821c6afc1d235b3eb3dde63ad3b01a/browser/components/urlbar/UrlbarProviderSearchTips.jsm#317). This is made worse because the user continuing to type is enough to dismiss the tip, so it just flashes on screen for a moment.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-06 13:57:46+00:00
|
2020-03-05 09:00:14+00:00
| 229 | 1 |
1613788
|
URL not selected with Ctrl+L/Command-L if a result is highlighted
|
STR:
1) Open https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Guide/Internal_strings
2) Open new tab
3) In awesome bar enter "Mozilla internal string guide" (the title of the page above)
4) Tab down to the entry that has "Switch to tab"
5) Hit CMD(or CTRL) + l
Expected:
The url will be selected
Actual:
The cursor ends up at the end of the URL
Note: You can repeat the above with any URL
This is seems to be a regression, as I do this quiet often to copy/paste urls.
|
URL not selected with Ctrl+L/Command-L if a result is highlighted STR:
1) Open https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Guide/Internal_strings
2) Open new tab
3) In awesome bar enter "Mozilla internal string guide" (the title of the page above)
4) Tab down to the entry that has "Switch to tab"
5) Hit CMD(or CTRL) + l
Expected:
The url will be selected
Actual:
The cursor ends up at the end of the URL
Note: You can repeat the above with any URL
This is seems to be a regression, as I do this quiet often to copy/paste urls.
|
P1
|
RESOLVED
|
DUPLICATE
|
2020-02-06 23:14:08+00:00
|
2020-02-07 09:41:06+00:00
| 167 | 1 |
1613801
|
macOS' Window menu has the brand-full-name suffix repeated at the end of every browser window title
|
Every window listed in the macOS "Window" menu now duplicates the `-brand-full-name` causing the menu items to be longer and more noisy.
Last good revision: eb874118621070fa4ef69cb951b2dd7a51f93d66
First bad revision: bff9eef8191f12cee9af275966a563517dcdf429
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=eb874118621070fa4ef69cb951b2dd7a51f93d66&tochange=bff9eef8191f12cee9af275966a563517dcdf429
From skimming bug 1591328 and the Phabricator reviews I don't think this was intentional, or was it?
|
macOS' Window menu has the brand-full-name suffix repeated at the end of every browser window title Every window listed in the macOS "Window" menu now duplicates the `-brand-full-name` causing the menu items to be longer and more noisy.
Last good revision: eb874118621070fa4ef69cb951b2dd7a51f93d66
First bad revision: bff9eef8191f12cee9af275966a563517dcdf429
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=eb874118621070fa4ef69cb951b2dd7a51f93d66&tochange=bff9eef8191f12cee9af275966a563517dcdf429
From skimming bug 1591328 and the Phabricator reviews I don't think this was intentional, or was it?
|
P1
|
RESOLVED
|
FIXED
|
2020-02-07 00:51:45+00:00
|
2020-02-25 15:02:38+00:00
| 234 | 1 |
1613953
|
doh-rollout local storage migration test times out locally due to add-on not being recognized as privileged
|
I don't know why this doesn't happen in automation, but Shane found a fix and I think we should land it.
|
doh-rollout local storage migration test times out locally due to add-on not being recognized as privileged I don't know why this doesn't happen in automation, but Shane found a fix and I think we should land it.
|
P1
|
RESOLVED
|
FIXED
|
2020-02-07 15:54:41+00:00
|
2020-07-12 22:24:28+00:00
| 51 | 1 |
1614133
|
Some previously visited URIs do not autocomplete
|
This has to be a dup, but I can't find it.
Firefox 72.0.2 is not completing URIs of some sites that are visited in the past, although it "knows" about them as evidenced by appearing in the Address Bar dropdown.
|
Some previously visited URIs do not autocomplete This has to be a dup, but I can't find it.
Firefox 72.0.2 is not completing URIs of some sites that are visited in the past, although it "knows" about them as evidenced by appearing in the Address Bar dropdown.
|
P5
|
RESOLVED
|
INVALID
|
2020-02-08 15:55:55+00:00
|
2020-02-28 23:16:29+00:00
| 70 | 5 |
1614187
|
context menu spawn under mouse cursor thus leading you to click on the uppermost item.
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
right click and sometimes it will just happen.
Actual results:
context menu spawns at the mouse down event and at the mouse up event the item the cursor is erroneously hovering over will get activated.
Expected results:
context menu opens.
|
context menu spawn under mouse cursor thus leading you to click on the uppermost item. User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
right click and sometimes it will just happen.
Actual results:
context menu spawns at the mouse down event and at the mouse up event the item the cursor is erroneously hovering over will get activated.
Expected results:
context menu opens.
|
P3
|
NEW
|
2020-02-09 11:11:37+00:00
|
2022-10-11 23:56:02+00:00
| 112 | 3 |
|
1614516
|
Probably bad handling of HTTP headers
|
User Agent: Mozilla/5.0 (Windows NT 6.3; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
My local server sends proxied images as "image/JPEG (From:...)" to show origin of the image.
Actual results:
In Media Window I see HTTP comments but HTTP comments should be ommited. If the comments are not ommited, there can be a security issue. This happens for CSS requests for images. It doesn't happen for request from <img/>. Other sources and types not tested.
Expected results:
The browser should cut out the HTTP comments before further processing. If comment will include CRLF and colon, there can be a security risk (by header injection). Please also test NULL characters.
|
Probably bad handling of HTTP headers User Agent: Mozilla/5.0 (Windows NT 6.3; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
My local server sends proxied images as "image/JPEG (From:...)" to show origin of the image.
Actual results:
In Media Window I see HTTP comments but HTTP comments should be ommited. If the comments are not ommited, there can be a security issue. This happens for CSS requests for images. It doesn't happen for request from <img/>. Other sources and types not tested.
Expected results:
The browser should cut out the HTTP comments before further processing. If comment will include CRLF and colon, there can be a security risk (by header injection). Please also test NULL characters.
|
P5
|
UNCONFIRMED
|
2020-02-11 00:17:15+00:00
|
2024-07-30 22:29:10+00:00
| 185 | 5 |
|
1614541
|
small number of libxul / omni.ja build ID mismatches
|
The telemetry in bug 1608308 has been in place for a few days now. I'm seeing a very small number of libxul / omni.ja build ID mismatches (4 out of 215K):
https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2020-02-08&include_spill=0&keys=__none__!__none__!__none__&max_channel_version=nightly%252F74&measure=SCALARS_CORROBORATE.OMNIJAR_MISMATCH&min_channel_version=null&processType=*&product=Firefox&sanitize=1&sort_by_value=0&sort_keys=submissions&start_date=2020-02-06&table=0&trim=1&use_submission_date=0
Not really sure where to go from here.
|
small number of libxul / omni.ja build ID mismatches The telemetry in bug 1608308 has been in place for a few days now. I'm seeing a very small number of libxul / omni.ja build ID mismatches (4 out of 215K):
https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2020-02-08&include_spill=0&keys=__none__!__none__!__none__&max_channel_version=nightly%252F74&measure=SCALARS_CORROBORATE.OMNIJAR_MISMATCH&min_channel_version=null&processType=*&product=Firefox&sanitize=1&sort_by_value=0&sort_keys=submissions&start_date=2020-02-06&table=0&trim=1&use_submission_date=0
Not really sure where to go from here.
|
P3
|
NEW
|
2020-02-11 03:21:18+00:00
|
2022-06-06 20:59:37+00:00
| 238 | 3 |
|
1614544
|
About Firefox window size is calculated incorrectly
|
I noticed that when I open the `About Firefox` dialog with the browser window on my second monitor the dialog has an extra white bar on the bottom (see attached image). This only happens when I have the browser on the second monitor. If I move the browser window to the primary monitor and open the dialog it looks correct (no extra bar). I have been seeing this for ages but never really thought much of it since it is pretty minor.
My primary monitor resolution is 3840x2160 and the second monitor resolution is 1920x1200. The machine is running Windows 10.
I do also see something similar on my laptop (X1 Carbon) running Firefox (release) on Ubuntu 18.04. I don't have any external monitors attached and the screen resolution is 2560x1440. Something HiDPI related maybe?
|
About Firefox window size is calculated incorrectly I noticed that when I open the `About Firefox` dialog with the browser window on my second monitor the dialog has an extra white bar on the bottom (see attached image). This only happens when I have the browser on the second monitor. If I move the browser window to the primary monitor and open the dialog it looks correct (no extra bar). I have been seeing this for ages but never really thought much of it since it is pretty minor.
My primary monitor resolution is 3840x2160 and the second monitor resolution is 1920x1200. The machine is running Windows 10.
I do also see something similar on my laptop (X1 Carbon) running Firefox (release) on Ubuntu 18.04. I don't have any external monitors attached and the screen resolution is 2560x1440. Something HiDPI related maybe?
|
P5
|
NEW
|
2020-02-11 03:57:47+00:00
|
2022-06-06 20:53:36+00:00
| 192 | 5 |
|
1614555
|
The tab manager menu doesn't update when tabs are modified through their context menu
|
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.87 Safari/537.36
Steps to reproduce:
1. Open a few tabs in the browser.
2. Open the tab manager menu.
3. Duplicate a tab using its context menu.
Actual results:
The duplicate tab can be seen in the tab browser but not tab manager menu.
Expected results:
The duplicate tab should be present in the list of tabs in tab manager menu as well.
|
The tab manager menu doesn't update when tabs are modified through their context menu User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.87 Safari/537.36
Steps to reproduce:
1. Open a few tabs in the browser.
2. Open the tab manager menu.
3. Duplicate a tab using its context menu.
Actual results:
The duplicate tab can be seen in the tab browser but not tab manager menu.
Expected results:
The duplicate tab should be present in the list of tabs in tab manager menu as well.
|
P2
|
RESOLVED
|
FIXED
|
2020-02-11 05:45:30+00:00
|
2020-03-22 02:11:53+00:00
| 148 | 2 |
1614656
|
Search Tips shownCount prefs are set incorrectly
|
Bug 1613855 [erroneously sets](https://hg.mozilla.org/mozilla-central/rev/1b407a1a33d6#l2.202) the prefs `searchTips.(type).shownCount` rather than `browser.urlbar.searchTips.(type).shownCount`, meaning that `shownCount` will not be meaningfully recorded. This should be corrected and uplifted to beta.
|
Search Tips shownCount prefs are set incorrectly Bug 1613855 [erroneously sets](https://hg.mozilla.org/mozilla-central/rev/1b407a1a33d6#l2.202) the prefs `searchTips.(type).shownCount` rather than `browser.urlbar.searchTips.(type).shownCount`, meaning that `shownCount` will not be meaningfully recorded. This should be corrected and uplifted to beta.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-11 14:52:30+00:00
|
2020-02-26 14:41:58+00:00
| 119 | 1 |
1614689
|
0.12ms uninterruptible reflow at _ensureFormattedHostVisible/<@resource:///modules/UrlbarValueFormatter.sys.mjs:96:9
|
Here's the stack:
_ensureFormattedHostVisible/<@resource:///modules/UrlbarValueFormatter.jsm:96:9
Version: 75.0a1
Build: 20200211094607
That's this line: https://searchfox.org/mozilla-central/rev/7e92a667e3829831c31e8d46aefe7ef67ad5be1c/browser/components/urlbar/UrlbarValueFormatter.jsm#96
|
0.12ms uninterruptible reflow at _ensureFormattedHostVisible/<@resource:///modules/UrlbarValueFormatter.sys.mjs:96:9 Here's the stack:
_ensureFormattedHostVisible/<@resource:///modules/UrlbarValueFormatter.jsm:96:9
Version: 75.0a1
Build: 20200211094607
That's this line: https://searchfox.org/mozilla-central/rev/7e92a667e3829831c31e8d46aefe7ef67ad5be1c/browser/components/urlbar/UrlbarValueFormatter.jsm#96
|
P2
|
NEW
|
2020-02-11 16:14:33+00:00
|
2024-04-03 16:05:44+00:00
| 180 | 2 |
|
1614716
|
Uptake reported age seems to be wrong in some situations
|
We report the age of obtained data when changes are pulled from the server.
For scheduled or startup synchronizations, the reported age increases with the time passing (until a new change is published). In the uptake telemetry, we can observe this through the Β«sawtoothΒ» aspect of the graph (switchback?).
But for broadcast synchronizations, the reported age should roughly be stable, and should not follow the pattern of those described above.
However, it does. Meaning that we may have an issue with the code that reports the age.
One possibility would be that client reconnections are handled as "broadcast" and would thus spoil the proper realtime broadcast reported values.
|
Uptake reported age seems to be wrong in some situations We report the age of obtained data when changes are pulled from the server.
For scheduled or startup synchronizations, the reported age increases with the time passing (until a new change is published). In the uptake telemetry, we can observe this through the Β«sawtoothΒ» aspect of the graph (switchback?).
But for broadcast synchronizations, the reported age should roughly be stable, and should not follow the pattern of those described above.
However, it does. Meaning that we may have an issue with the code that reports the age.
One possibility would be that client reconnections are handled as "broadcast" and would thus spoil the proper realtime broadcast reported values.
|
P1
|
RESOLVED
|
FIXED
|
2020-02-11 17:31:23+00:00
|
2022-04-27 14:17:50+00:00
| 158 | 1 |
1614787
|
Unexpectedly wide clickable region for "Learn More" link in DoH/Cloudflare doorhanger-alert
|
Today I saw a doorhanger alert for the DoH rollout (see attached screenshot).
Minor papercut: the "Learn More" link's clickable-area extends all the way to the right (see screenshot where I've focused the link to show its whole click area via the dotted focus-outline. Note that this outline is not normally present unless you focus the link.)
I'm guessing the <a> element here is styled to be a block-level element (and hence it stretches to fit the containing block), when really we'd like to make it inline-level so that the element (and in particular, its clickable region) shrinkwraps the width of its contents.
|
Unexpectedly wide clickable region for "Learn More" link in DoH/Cloudflare doorhanger-alert Today I saw a doorhanger alert for the DoH rollout (see attached screenshot).
Minor papercut: the "Learn More" link's clickable-area extends all the way to the right (see screenshot where I've focused the link to show its whole click area via the dotted focus-outline. Note that this outline is not normally present unless you focus the link.)
I'm guessing the <a> element here is styled to be a block-level element (and hence it stretches to fit the containing block), when really we'd like to make it inline-level so that the element (and in particular, its clickable region) shrinkwraps the width of its contents.
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-02-11 20:32:12+00:00
|
2020-07-10 14:47:22+00:00
| 175 | 3 |
1614833
|
Tabbing through address bar and separate search bar results in inconsistent behavior
|
Spawned from bug 1608766
I noticed while testing the new behavior in bug 1608766, that tabbing through the search box and address bar results in inconsistent behavior.
Steps to reproduce:
1. Enable separate search bar.
2. Do `control-l` or `control-k`
3. type in query
4. press `tab` key
What happens:
The result is inconsistent.
In the address bar, tapping tab moves focus to the search box.
In the search box, tapping tab moves focus through the one off search engines.
Expected result:
The behavior should be consistent. I would prefer to have tab move focus to the one off search engines in both places, but that does open up some questions about whether tab should move through the engines (this was rejected in 1608766 for autocomplete entries) -- this may be solved by using the arrow keys to move between search engines once focus has moved to the search engines.
FWIW, the arrow keys (both left and right and up and down) both work in the separate search box to move the selection between search engines.
I think that ideally, the interaction would look like this (for example on this page):
1. `Control-l`
2. `tab` (this moves to one off search engines)
3. User can switch between search engines using arrow keys
4. `tab` (this moves to "change search settings")
5. `tab` (user is moved to separate search box)
6. `tab` (this moves to one off search engines)
7. `tab` (this moves to "add search engine")
8. `tab` (this moves to "change search settings")
That would result in a consistent user interaction and expected results when using `tab`.
|
Tabbing through address bar and separate search bar results in inconsistent behavior Spawned from bug 1608766
I noticed while testing the new behavior in bug 1608766, that tabbing through the search box and address bar results in inconsistent behavior.
Steps to reproduce:
1. Enable separate search bar.
2. Do `control-l` or `control-k`
3. type in query
4. press `tab` key
What happens:
The result is inconsistent.
In the address bar, tapping tab moves focus to the search box.
In the search box, tapping tab moves focus through the one off search engines.
Expected result:
The behavior should be consistent. I would prefer to have tab move focus to the one off search engines in both places, but that does open up some questions about whether tab should move through the engines (this was rejected in 1608766 for autocomplete entries) -- this may be solved by using the arrow keys to move between search engines once focus has moved to the search engines.
FWIW, the arrow keys (both left and right and up and down) both work in the separate search box to move the selection between search engines.
I think that ideally, the interaction would look like this (for example on this page):
1. `Control-l`
2. `tab` (this moves to one off search engines)
3. User can switch between search engines using arrow keys
4. `tab` (this moves to "change search settings")
5. `tab` (user is moved to separate search box)
6. `tab` (this moves to one off search engines)
7. `tab` (this moves to "add search engine")
8. `tab` (this moves to "change search settings")
That would result in a consistent user interaction and expected results when using `tab`.
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-02-11 23:59:28+00:00
|
2020-11-04 12:50:29+00:00
| 382 | 3 |
1614861
|
Slow startup notification bar can somehow get negative samples
|
The slow startup notification bar samples the time between process start and shortly after browser-delayed-startup-finished fires, and after 5 such samples, checks to see if the average time was over 20s. If so, a slow startup notification shows.
In https://www.reddit.com/r/firefox/comments/eul2fg/mozilla_firefox_seems_slow_to_start_umm_no_it/, a user reports that they're seeing this notification bar, despite the fact that Firefox is starting quite quickly. I reached out to this user, and this is some of the values that were stored for startup samples:
`browser.slowStartup.averageTime: -1607100339`,
`browser.slowStartup.samples: 2`,
`browser.slowStartup.maxSamples: 5`,
`browser.slowStartup.timeThreshold: 20000`
That `averageTime` is _really_ suspect. How are we getting this very negative value?
|
Slow startup notification bar can somehow get negative samples The slow startup notification bar samples the time between process start and shortly after browser-delayed-startup-finished fires, and after 5 such samples, checks to see if the average time was over 20s. If so, a slow startup notification shows.
In https://www.reddit.com/r/firefox/comments/eul2fg/mozilla_firefox_seems_slow_to_start_umm_no_it/, a user reports that they're seeing this notification bar, despite the fact that Firefox is starting quite quickly. I reached out to this user, and this is some of the values that were stored for startup samples:
`browser.slowStartup.averageTime: -1607100339`,
`browser.slowStartup.samples: 2`,
`browser.slowStartup.maxSamples: 5`,
`browser.slowStartup.timeThreshold: 20000`
That `averageTime` is _really_ suspect. How are we getting this very negative value?
|
P3
|
RESOLVED
|
FIXED
|
2020-02-12 03:05:02+00:00
|
2020-02-14 10:08:59+00:00
| 237 | 3 |
1614911
|
Focus menu for search results displayed on Wikipedia when focus is restored to the webpage after accessing options from address bar
|
**Affected versions**
* 72.0, 74.0b2, 75.0a1 (2020-02-11), 68.4.2esr
**Affected platforms**
* Windows 10, macOS 10.15, Kubuntu 19;
**Steps to reproduce**
1. Launch Firefox;
2. access https://www.wikipedia.org/
3. Inside the pagesearch for: sws+
4. Click on the EPT button;
5. Click away to close the ETP menu;
Alternative steps:
2. Set Wikipedia as the default search engine;
3. In the Adress bar search for sws+
**Expected result**
* no unexpected issues;
**Actual result**
* the search_results dropdown from inside the website is displayed;
**Regression range**
* last good build_date: 2019-03-16
* first bad build_date: 2019-03-17
* Pushlog [URL](https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2a96d8f9339f49e84789bbe3899699c5d7185406&tochange=1735fe85436911fca7c7e5837e4cbc94040b8825)
* potential regressor: 1506510
**Additional notes**
* attached recording with the issue.
|
Focus menu for search results displayed on Wikipedia when focus is restored to the webpage after accessing options from address bar **Affected versions**
* 72.0, 74.0b2, 75.0a1 (2020-02-11), 68.4.2esr
**Affected platforms**
* Windows 10, macOS 10.15, Kubuntu 19;
**Steps to reproduce**
1. Launch Firefox;
2. access https://www.wikipedia.org/
3. Inside the pagesearch for: sws+
4. Click on the EPT button;
5. Click away to close the ETP menu;
Alternative steps:
2. Set Wikipedia as the default search engine;
3. In the Adress bar search for sws+
**Expected result**
* no unexpected issues;
**Actual result**
* the search_results dropdown from inside the website is displayed;
**Regression range**
* last good build_date: 2019-03-16
* first bad build_date: 2019-03-17
* Pushlog [URL](https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2a96d8f9339f49e84789bbe3899699c5d7185406&tochange=1735fe85436911fca7c7e5837e4cbc94040b8825)
* potential regressor: 1506510
**Additional notes**
* attached recording with the issue.
|
P3
|
VERIFIED
|
FIXED
|
2020-02-12 11:56:30+00:00
|
2020-02-28 11:21:49+00:00
| 349 | 3 |
1614984
|
Some searches are incorrectly interpreted as URLs
|
1) Enable Omnibar/Megabar (the default now)
2) Enter "105m/60s"
Expected result:
Google search, which gives the correct answer.
Actual result:
Firefox "completes" this to http://www.105m.com/60s, which a) Is nonsensical b) Does not exist. The domain 105m.com doesn't even exist.
Chrome works correctly.
|
Some searches are incorrectly interpreted as URLs 1) Enable Omnibar/Megabar (the default now)
2) Enter "105m/60s"
Expected result:
Google search, which gives the correct answer.
Actual result:
Firefox "completes" this to http://www.105m.com/60s, which a) Is nonsensical b) Does not exist. The domain 105m.com doesn't even exist.
Chrome works correctly.
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-02-12 16:37:52+00:00
|
2020-02-21 04:07:29+00:00
| 99 | 3 |
1615027
|
SERIOUS BUG Cannot launch many things after update 73.0
|
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.79 Safari/537.36 AVG/79.0.3064.81
Steps to reproduce:
updated to 73.0
"Launcher Process" failed
CANNOT REMOVE AND REINSTALL WITHOUT SAME FAILURE
Actual results:
SERIOUS BUG FAILURE
Updated 20200212 failed:
Cannot launch many things. "Launcher Process" failed.
CANNOT REMOVE AND REINSTALL WITHOUT SAME FAILURE
about:config does nothing, blank content
I have no idea why
[email protected]
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0 [Windows 7]
I want to clean all reference to Firefox AND RELATED CONTENT from my computer so I do not get a "reinstall" message.
message. I tried to find and delete all information re Firefox and failed.
I want to install Firefox with out any past reference and without nuking and reinstalling Windows.
How? Link?
Expected results:
just keep working after update.
"clean virgin reinstall" should be easy to find and do
|
SERIOUS BUG Cannot launch many things after update 73.0 User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.79 Safari/537.36 AVG/79.0.3064.81
Steps to reproduce:
updated to 73.0
"Launcher Process" failed
CANNOT REMOVE AND REINSTALL WITHOUT SAME FAILURE
Actual results:
SERIOUS BUG FAILURE
Updated 20200212 failed:
Cannot launch many things. "Launcher Process" failed.
CANNOT REMOVE AND REINSTALL WITHOUT SAME FAILURE
about:config does nothing, blank content
I have no idea why
[email protected]
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0 [Windows 7]
I want to clean all reference to Firefox AND RELATED CONTENT from my computer so I do not get a "reinstall" message.
message. I tried to find and delete all information re Firefox and failed.
I want to install Firefox with out any past reference and without nuking and reinstalling Windows.
How? Link?
Expected results:
just keep working after update.
"clean virgin reinstall" should be easy to find and do
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-02-12 19:05:44+00:00
|
2020-03-10 15:42:46+00:00
| 298 | 3 |
1615042
|
Horizontal alignment issue when select item in Applications Action
|
This is trivial visual issue.
Steps To Reproduce:
1. open about:preferences
2. Select item in Applications Action
Actual Results:
Icon and text shift to the left
Expected Results:
No shift
|
Horizontal alignment issue when select item in Applications Action This is trivial visual issue.
Steps To Reproduce:
1. open about:preferences
2. Select item in Applications Action
Actual Results:
Icon and text shift to the left
Expected Results:
No shift
|
P5
|
VERIFIED
|
FIXED
|
2020-02-12 19:56:50+00:00
|
2020-11-17 14:47:30+00:00
| 49 | 5 |
1615149
|
Changing the search string when a one-off is selected doesn't reset the selection
|
Was seeing this on 74 Nightly, and still happens on the latest 75 Nightly (2020-02-12). On macOS 10.14, if that matters.
STR:
1. Go to a URL like `https://tools.ietf.org/html/rfc822#section-3.1.1`
2. Click on the URL bar and hit backspace a couple of times to trim off a few chars from the end of the URL
3. Press the up button. This should put focus on the settings icon in the bottom-right corner of the URL bar dropdown, but ALSO keeps the blinking cursor in the text-entry part of the URL bar.
4. Continue editing the URL, e.g. continue backspacing until the entire URL fragment portion (`#section-3.1.1`) is deleted. For good measure even click and highlight parts of the URL with the mouse, just to be extra sure that the focus is on the text entry part of the URL bar.
5. Hit enter
Expected:
The edited URL is navigated to
Actual:
`about:preferences#search` is opened in a new tab, because apparently that settings icon in the bottom-right that got focus in step 3 gets activated in step 5.
|
Changing the search string when a one-off is selected doesn't reset the selection Was seeing this on 74 Nightly, and still happens on the latest 75 Nightly (2020-02-12). On macOS 10.14, if that matters.
STR:
1. Go to a URL like `https://tools.ietf.org/html/rfc822#section-3.1.1`
2. Click on the URL bar and hit backspace a couple of times to trim off a few chars from the end of the URL
3. Press the up button. This should put focus on the settings icon in the bottom-right corner of the URL bar dropdown, but ALSO keeps the blinking cursor in the text-entry part of the URL bar.
4. Continue editing the URL, e.g. continue backspacing until the entire URL fragment portion (`#section-3.1.1`) is deleted. For good measure even click and highlight parts of the URL with the mouse, just to be extra sure that the focus is on the text entry part of the URL bar.
5. Hit enter
Expected:
The edited URL is navigated to
Actual:
`about:preferences#search` is opened in a new tab, because apparently that settings icon in the bottom-right that got focus in step 3 gets activated in step 5.
|
P3
|
NEW
|
2020-02-13 02:58:27+00:00
|
2024-04-14 05:56:49+00:00
| 295 | 3 |
|
1615286
|
The Enhanced Tracking Protection report is no longer displayed when the user turns Protections OFF
|
[Affected versions]:
Nightly 75.0a1
[Affected platforms]:
Platforms: all
Steps :
1. Open the Firefox Browser and reach reddit.com, CNN.com and other websites in order to block some Cookies or trackers (try Strict mode)
2. Reach about:protections and notice the blocked content.
3. Reach about:preferences#privacy and turn off protections by unchecking all options from Custom.
4. Reach about:protections.
Expected Results :
The report with the previously blocked content should still be displayed.
Actual Results :
The Content blocking report is no longer displayed after the user turns it off.
|
The Enhanced Tracking Protection report is no longer displayed when the user turns Protections OFF [Affected versions]:
Nightly 75.0a1
[Affected platforms]:
Platforms: all
Steps :
1. Open the Firefox Browser and reach reddit.com, CNN.com and other websites in order to block some Cookies or trackers (try Strict mode)
2. Reach about:protections and notice the blocked content.
3. Reach about:preferences#privacy and turn off protections by unchecking all options from Custom.
4. Reach about:protections.
Expected Results :
The report with the previously blocked content should still be displayed.
Actual Results :
The Content blocking report is no longer displayed after the user turns it off.
|
P3
|
VERIFIED
|
FIXED
|
2020-02-13 14:23:05+00:00
|
2020-05-12 07:51:10+00:00
| 145 | 3 |
1615302
|
Issues with the back/forward buttons on new tabs created with moz-extension URLs that are updated to different URLs through the location bar (Firefox 74).
|
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
1) Install the 'Group Speed Dial' extension which creates a new tab page that is a moz-extension URL: https://addons.mozilla.org/en-US/firefox/addon/groupspeeddial/
2) Create a new tab (Ctrl+T), which should be the 'Group Speed Dial' new tab page.
3) Type "https://www.duckduckgo.com" in the location bar and hit enter.
4) Click on the back arrow after the new page has loaded.
5) Type "https://www.startpage.com" in the location bar and hit enter.
6) Press the back arrow twice after the new page has loaded or right click the back arrow and select 'Group Speed Dial'.
Actual results:
On step 4) with Firefox 74, the back button will not allow access to the previous page. On step 6) the forward history of the tab is lost.
Expected results:
Firefox 73 did not have these issues. This new behavior only seems to happen when a new tab is created with a moz-extension URL, not if the moz-extension URL is loaded into the tab after it is created. Also, the URL has to be changed through the location bar after the tab is created with the moz-extension URL. Note that the moz-extension URL could be replaced with a file URL and the behavior would also be the same on steps 4) and 6) with Firefox 74.
|
Issues with the back/forward buttons on new tabs created with moz-extension URLs that are updated to different URLs through the location bar (Firefox 74). User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
1) Install the 'Group Speed Dial' extension which creates a new tab page that is a moz-extension URL: https://addons.mozilla.org/en-US/firefox/addon/groupspeeddial/
2) Create a new tab (Ctrl+T), which should be the 'Group Speed Dial' new tab page.
3) Type "https://www.duckduckgo.com" in the location bar and hit enter.
4) Click on the back arrow after the new page has loaded.
5) Type "https://www.startpage.com" in the location bar and hit enter.
6) Press the back arrow twice after the new page has loaded or right click the back arrow and select 'Group Speed Dial'.
Actual results:
On step 4) with Firefox 74, the back button will not allow access to the previous page. On step 6) the forward history of the tab is lost.
Expected results:
Firefox 73 did not have these issues. This new behavior only seems to happen when a new tab is created with a moz-extension URL, not if the moz-extension URL is loaded into the tab after it is created. Also, the URL has to be changed through the location bar after the tab is created with the moz-extension URL. Note that the moz-extension URL could be replaced with a file URL and the behavior would also be the same on steps 4) and 6) with Firefox 74.
|
P2
|
VERIFIED
|
FIXED
|
2020-02-13 15:07:35+00:00
|
2020-03-27 13:11:24+00:00
| 411 | 2 |
1615308
|
The "firefox.exe - Application Error" dialog is popped up when Compatibility mode is on
|
On Windows 10, if Compatibility mode for firefox.exe is set to Windows 7, the [firefox.exe - Application Error] dialog saying "The application was unable to start correctly (0xc0000005). Click OK to close the application." is popped up at startup.
|
The "firefox.exe - Application Error" dialog is popped up when Compatibility mode is on On Windows 10, if Compatibility mode for firefox.exe is set to Windows 7, the [firefox.exe - Application Error] dialog saying "The application was unable to start correctly (0xc0000005). Click OK to close the application." is popped up at startup.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-13 15:20:05+00:00
|
2020-04-12 11:44:58+00:00
| 91 | 1 |
1615316
|
Library - Can't create a new folder if places.xhtml is open in content
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
1) open the Library,
2) select any folder in the sidebar,
3) right mouse click "New folder" in the bookmarks panel,
4) nothing happens or only an empty dialog box is showing up.
There's a SUMO report about this issue: https://support.mozilla.org/questions/1279599#answer-1289597 and I can confirm it on Nightly.
I captured a video of this issue, if you need it.
|
Library - Can't create a new folder if places.xhtml is open in content User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
1) open the Library,
2) select any folder in the sidebar,
3) right mouse click "New folder" in the bookmarks panel,
4) nothing happens or only an empty dialog box is showing up.
There's a SUMO report about this issue: https://support.mozilla.org/questions/1279599#answer-1289597 and I can confirm it on Nightly.
I captured a video of this issue, if you need it.
|
P5
|
REOPENED
|
2020-02-13 15:39:21+00:00
|
2024-02-27 15:59:10+00:00
| 169 | 5 |
|
1615370
|
Launching URIs fails when explorer.exe is not running
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.100 Safari/537.36
Steps to reproduce:
Kill Windows explorer and URI launch will stop working.
example URI:
steam://connect/ipaddress
esportal://arg/arg
Actual results:
Nothing happens, the following error is observed in the console:
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIHandlerInfo.launchWithURI] 6 dialog.js:349
onOK chrome://mozapps/content/handling/dialog.js:349
initialize chrome://mozapps/content/handling/dialog.js:147
_fireButtonEvent chrome://global/content/elements/dialog.js:537
_doButtonCommand chrome://global/content/elements/dialog.js:516
_handleButtonCommand chrome://global/content/elements/dialog.js:510
_handleButtonCommand self-hosted:876
(Async: EventListener.handleEvent)
_configureButtons chrome://global/content/elements/dialog.js:382
connectedCallback chrome://global/content/elements/dialog.js:184
<anonym> chrome://global/content/customElements.js:219
(Async: EventListener.handleEvent)
<anonym> chrome://global/content/customElements.js:211
<anonym> chrome://global/content/customElements.js:820
observe resource://gre/modules/CustomElementsListener.jsm:24
Expected results:
The appropriate applications should launch.
|
Launching URIs fails when explorer.exe is not running User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.100 Safari/537.36
Steps to reproduce:
Kill Windows explorer and URI launch will stop working.
example URI:
steam://connect/ipaddress
esportal://arg/arg
Actual results:
Nothing happens, the following error is observed in the console:
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIHandlerInfo.launchWithURI] 6 dialog.js:349
onOK chrome://mozapps/content/handling/dialog.js:349
initialize chrome://mozapps/content/handling/dialog.js:147
_fireButtonEvent chrome://global/content/elements/dialog.js:537
_doButtonCommand chrome://global/content/elements/dialog.js:516
_handleButtonCommand chrome://global/content/elements/dialog.js:510
_handleButtonCommand self-hosted:876
(Async: EventListener.handleEvent)
_configureButtons chrome://global/content/elements/dialog.js:382
connectedCallback chrome://global/content/elements/dialog.js:184
<anonym> chrome://global/content/customElements.js:219
(Async: EventListener.handleEvent)
<anonym> chrome://global/content/customElements.js:211
<anonym> chrome://global/content/customElements.js:820
observe resource://gre/modules/CustomElementsListener.jsm:24
Expected results:
The appropriate applications should launch.
|
P3
|
RESOLVED
|
FIXED
|
2020-02-13 17:29:38+00:00
|
2020-03-12 00:53:21+00:00
| 465 | 3 |
1615415
|
Cookies are not deleted after closing Firefox in Private Mode
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.5 Safari/605.1.15
Steps to reproduce:
I set Firefox to always use private mode and after closing there are always Cookies left, different size, after each session and I always open private windows
So I always have to delete them manually.
Actual results:
The cookie data is not deleted after closing and opening Firefox again.
Expected results:
There should be 0 kByte Cookie Data in Settings
|
Cookies are not deleted after closing Firefox in Private Mode User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.5 Safari/605.1.15
Steps to reproduce:
I set Firefox to always use private mode and after closing there are always Cookies left, different size, after each session and I always open private windows
So I always have to delete them manually.
Actual results:
The cookie data is not deleted after closing and opening Firefox again.
Expected results:
There should be 0 kByte Cookie Data in Settings
|
P1
|
RESOLVED
|
INVALID
|
2020-02-13 19:39:15+00:00
|
2020-03-17 09:01:40+00:00
| 148 | 1 |
1615470
|
Heuristic and private search results aren't properly updated when a one-off search button is selected and you continue typing
|
STR:
1. Type something so that the heuristic result is a "Search with <Engine>" search result (i.e., doesn't trigger autofill and isn't a visit result)
2. Arrow down until a one-off is selected that isn't your default engine
3. Continue typing
The favicon and engine name in the heuristic result (and the private search result) revert back to your default engine. They should remain the selected one-off engine. If you then hit enter, we do a search using the selected one-off engine.
|
Heuristic and private search results aren't properly updated when a one-off search button is selected and you continue typing STR:
1. Type something so that the heuristic result is a "Search with <Engine>" search result (i.e., doesn't trigger autofill and isn't a visit result)
2. Arrow down until a one-off is selected that isn't your default engine
3. Continue typing
The favicon and engine name in the heuristic result (and the private search result) revert back to your default engine. They should remain the selected one-off engine. If you then hit enter, we do a search using the selected one-off engine.
|
P3
|
RESOLVED
|
WORKSFORME
|
2020-02-13 23:28:09+00:00
|
2020-11-04 17:52:12+00:00
| 151 | 3 |
1615560
|
Expose default search engine pref
|
The WNPanel message requires access to the default search engine name. We need to expose this value.
|
Expose default search engine pref The WNPanel message requires access to the default search engine name. We need to expose this value.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-14 10:00:33+00:00
|
2020-02-24 11:50:56+00:00
| 30 | 1 |
1615612
|
about:certificate chain download gives entire encoding on one line
|
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
1. In Certificate Manager UI, "Your Certificates" tab, import a (client) certificate from a P12.
2. In Certificate Manager UI, choose the "View" button.
3. In the about:certificate tab which appears, go to the "Miscellaneous" section and click the "PEM (chain)" link. Download the file which Firefox offers.
Actual results:
The Base64-encoding of the certificate appears on a single, very long, line, viz:
-----BEGIN CERTIFICATE-----
<Base64 further than the eye can see...>
-----END CERTIFICATE-----
Expected results:
The Base64 encoding is wrapped over several lines, just like for the "PEM (cert)" link which is adjacent to the "PEM (chain)" link. Viz:
-----BEGIN CERTIFICATE-----
<Base64>
<More Base64>
<etc etc etc.>
-----END CERTIFICATE-----
|
about:certificate chain download gives entire encoding on one line User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
1. In Certificate Manager UI, "Your Certificates" tab, import a (client) certificate from a P12.
2. In Certificate Manager UI, choose the "View" button.
3. In the about:certificate tab which appears, go to the "Miscellaneous" section and click the "PEM (chain)" link. Download the file which Firefox offers.
Actual results:
The Base64-encoding of the certificate appears on a single, very long, line, viz:
-----BEGIN CERTIFICATE-----
<Base64 further than the eye can see...>
-----END CERTIFICATE-----
Expected results:
The Base64 encoding is wrapped over several lines, just like for the "PEM (cert)" link which is adjacent to the "PEM (chain)" link. Viz:
-----BEGIN CERTIFICATE-----
<Base64>
<More Base64>
<etc etc etc.>
-----END CERTIFICATE-----
|
P3
|
RESOLVED
|
FIXED
|
2020-02-14 14:27:52+00:00
|
2021-03-17 10:03:41+00:00
| 279 | 3 |
1615850
|
Bookmarks window unusable on small/moderate screens with larger fonts
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Opened bookmarks window to try to sync.
(Which succeeded, after I took this screenshot.)
Actual results:
See screenshot.
Expected results:
The actual list should be visible.
To make things more readable, I've reduced resolution to 1152 x 648.
To make things more readable, I've increased font sizes and spacing. Here are relevant parts of userChrome.css:
/* Global UI font */
* { font-family: Andika !important; }
* { font-size: 16pt !important; }
#urlbar { height: 20pt }
/* Bookmarks spacing */
#placeContent treechildren::-moz-tree-row {
min-height: 24pt !important;
maxn-height: 24pt !important;
}
I have trouble reading on any monitor without similar fixes.
|
Bookmarks window unusable on small/moderate screens with larger fonts User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Opened bookmarks window to try to sync.
(Which succeeded, after I took this screenshot.)
Actual results:
See screenshot.
Expected results:
The actual list should be visible.
To make things more readable, I've reduced resolution to 1152 x 648.
To make things more readable, I've increased font sizes and spacing. Here are relevant parts of userChrome.css:
/* Global UI font */
* { font-family: Andika !important; }
* { font-size: 16pt !important; }
#urlbar { height: 20pt }
/* Bookmarks spacing */
#placeContent treechildren::-moz-tree-row {
min-height: 24pt !important;
maxn-height: 24pt !important;
}
I have trouble reading on any monitor without similar fixes.
|
P5
|
NEW
|
2020-02-15 22:22:38+00:00
|
2023-06-02 14:50:05+00:00
| 245 | 5 |
|
1615853
|
Searching for "encoding" points to a setting that doesn't exist anymore
|
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
20200215095617
STR:
1. about:preferences
2. Type `encoding` in the Find box.
AR:
Search result highlights the Advanced⦠button in the Fonts and Colors category. There's no such setting there anymore, because it was removed in bug 1551276.
ER:
No search results.
|
Searching for "encoding" points to a setting that doesn't exist anymore Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
20200215095617
STR:
1. about:preferences
2. Type `encoding` in the Find box.
AR:
Search result highlights the Advanced⦠button in the Fonts and Colors category. There's no such setting there anymore, because it was removed in bug 1551276.
ER:
No search results.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-15 22:43:53+00:00
|
2020-02-25 15:48:42+00:00
| 125 | 1 |
1615901
|
Origin header should not be set on OpenSearch POST
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
1. navigate to https://duckduckgo.com/lite/
2. add as a search engine
3. set as default search engine
4. select text, right-click, "Search DuckDuckGo Lite"
Actual results:
page displays "forbidden"
Expected results:
search results displayed
|
Origin header should not be set on OpenSearch POST User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
1. navigate to https://duckduckgo.com/lite/
2. add as a search engine
3. set as default search engine
4. select text, right-click, "Search DuckDuckGo Lite"
Actual results:
page displays "forbidden"
Expected results:
search results displayed
|
P1
|
VERIFIED
|
FIXED
|
2020-02-16 15:59:02+00:00
|
2020-04-09 08:38:31+00:00
| 120 | 1 |
1615931
|
Sync doesn't upload any bookmarks when one bookmark is invalid
|
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Sync (either Sync Now or wait for it to sync), when one bookmark was an invalid URL and there were other (valid) new bookmarks locally that needed to be uploaded.
The invalid bookmark was https://http%3a%2f%2fwww.forbes.com%2fsites%2fsarahtilton%2f2015%2f01%2f09%2fproblems-with-math-tutoring-app-expands-the-answers%2f/
The local device where I saw the error is a laptop whose OS is Xubuntu 18.04, and the Firefox is Mozilla Firefox for Ubuntu 73.0 (64 bit). I sync it with another partition of that same laptop's hard disk (same OS), and with a OnePlus One phone running Firefox for Android (OS is not stock Android, it's CyanogenOS).
Actual results:
New (valid) local bookmarks did not appear on my two other devices (so I infer they never got uploaded). On the device with the bad bookmark (the laptop), new bookmarks that had been created on another device appeared in Bookmarks (so I infer that downloading is fine). No error message (unless I examine the sync log). Bookmarks I had moved to new folders returned to the folders they had been in before.
Expected results:
The new valid local bookmarks should be uploaded to the server and then appear on other devices. Bookmarks locally moved to other folders should appear in the new folders on other devices.
|
Sync doesn't upload any bookmarks when one bookmark is invalid User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Sync (either Sync Now or wait for it to sync), when one bookmark was an invalid URL and there were other (valid) new bookmarks locally that needed to be uploaded.
The invalid bookmark was https://http%3a%2f%2fwww.forbes.com%2fsites%2fsarahtilton%2f2015%2f01%2f09%2fproblems-with-math-tutoring-app-expands-the-answers%2f/
The local device where I saw the error is a laptop whose OS is Xubuntu 18.04, and the Firefox is Mozilla Firefox for Ubuntu 73.0 (64 bit). I sync it with another partition of that same laptop's hard disk (same OS), and with a OnePlus One phone running Firefox for Android (OS is not stock Android, it's CyanogenOS).
Actual results:
New (valid) local bookmarks did not appear on my two other devices (so I infer they never got uploaded). On the device with the bad bookmark (the laptop), new bookmarks that had been created on another device appeared in Bookmarks (so I infer that downloading is fine). No error message (unless I examine the sync log). Bookmarks I had moved to new folders returned to the folders they had been in before.
Expected results:
The new valid local bookmarks should be uploaded to the server and then appear on other devices. Bookmarks locally moved to other folders should appear in the new folders on other devices.
|
P2
|
RESOLVED
|
FIXED
|
2020-02-17 01:41:47+00:00
|
2020-03-16 02:41:50+00:00
| 416 | 2 |
1615938
|
Thin font-weight on "Created/Last modified/Last used" area
|
Steps to reproduce:
1. Navigate to about:logins
2. Create an entry
3. Look at the "Created/Last modified/Last used" area
What happens:
The text appears too narrow, thin, and has bad smoothing.
Expected result:
Nicer looking text.
|
Thin font-weight on "Created/Last modified/Last used" area Steps to reproduce:
1. Navigate to about:logins
2. Create an entry
3. Look at the "Created/Last modified/Last used" area
What happens:
The text appears too narrow, thin, and has bad smoothing.
Expected result:
Nicer looking text.
|
P2
|
VERIFIED
|
FIXED
|
2020-02-17 02:31:40+00:00
|
2020-04-21 10:21:38+00:00
| 73 | 2 |
1615941
|
The A-Z and Z-A sort should be sorted by eTLD+1
|
The A-Z and Z-A sort should be sorted by eTLD+1. The current sort includes subdomains which means that it is basically impossible to find a login just from scrolling the list. Some logins may have "secure." subdomain prefix for example which ends up ordering them In a non-intuitive place in the list.
|
The A-Z and Z-A sort should be sorted by eTLD+1 The A-Z and Z-A sort should be sorted by eTLD+1. The current sort includes subdomains which means that it is basically impossible to find a login just from scrolling the list. Some logins may have "secure." subdomain prefix for example which ends up ordering them In a non-intuitive place in the list.
|
P3
|
RESOLVED
|
WONTFIX
|
2020-02-17 02:57:00+00:00
|
2020-08-07 20:36:55+00:00
| 92 | 3 |
1616002
|
When default zoom level is changed a β100%β flash is displayed in address bar after restarting Firefox
|
**Affected versions**
* 75.0a1 (2020-02-16)
* 74.0b4
* 73.0
**Affected platforms**
* Windows 10x64
* macOS 10.14
* Ubuntu 18.04x64
**Steps to reproduce**
1. Launch Firefox.
2. Go to about:preferences.
3. Change the default zoom (e.g set it to 90%).
4. Open different sites in new tabs.
5. Restart Firefox.
6. Go to one of the opened tabs in order to load it.
**Expected result**
* No flash with 100% zoom level after restart.
**Actual result**
* A 100% zoom flash is displayed when loading the page after restart.
**Regression range**
* This issue is not a recent regression since I was able to reproduce it on Firefox 73.0. Iβll come with a regression range asap.
**Additional notes**
* Iβll attach a screen recording with the issue.
|
When default zoom level is changed a β100%β flash is displayed in address bar after restarting Firefox **Affected versions**
* 75.0a1 (2020-02-16)
* 74.0b4
* 73.0
**Affected platforms**
* Windows 10x64
* macOS 10.14
* Ubuntu 18.04x64
**Steps to reproduce**
1. Launch Firefox.
2. Go to about:preferences.
3. Change the default zoom (e.g set it to 90%).
4. Open different sites in new tabs.
5. Restart Firefox.
6. Go to one of the opened tabs in order to load it.
**Expected result**
* No flash with 100% zoom level after restart.
**Actual result**
* A 100% zoom flash is displayed when loading the page after restart.
**Regression range**
* This issue is not a recent regression since I was able to reproduce it on Firefox 73.0. Iβll come with a regression range asap.
**Additional notes**
* Iβll attach a screen recording with the issue.
|
P3
|
NEW
|
2020-02-17 10:24:48+00:00
|
2020-07-09 04:30:21+00:00
| 248 | 3 |
|
1616007
|
Policies set via GPO can be bypassed/canceled by using an invalid policies.json file
|
**Affected versions**
* Firefox 75.0a1 (BuildId:20200216210001)
* Firefox 74.0b1 (BuildId:20200210140608)
**Unaffected versions**
* Firefox 73.0 (BuildId:20200207195153)
**Affected platforms**
* Windows 10 64bit.
**Preconditions**
Enable several policies via GPO (ex: Disable Private Browsing and Disable Firefox Screenshots)
**Steps to reproduce**
1. Create a distribution folder inside your Firefox path.
2. Add a policies.json file which contains invalid entries.
3. Launch Firefox.
4. Access the about:policies page.
**Expected result**
* Policies that were previously set via GPO are being successfully displayed inside the about:policies page and they are successfully applied. (In this case Private Browsing and Firefox Screenshots should be disabled).
**Actual result**
* Policies that were previously set via GPO are not applied ( In this case Private Browsing and Firefox Screenshots are enabled)
**Regression Range**
* I think that this may have came with the changes performed in Bug 1552600
**Note**
Example of invalid policies.json file content:
{
"policies": {
"DisableTelemetry": true,
"DisableMasterPasswordCreation": true,
"Locke
}
}
|
Policies set via GPO can be bypassed/canceled by using an invalid policies.json file **Affected versions**
* Firefox 75.0a1 (BuildId:20200216210001)
* Firefox 74.0b1 (BuildId:20200210140608)
**Unaffected versions**
* Firefox 73.0 (BuildId:20200207195153)
**Affected platforms**
* Windows 10 64bit.
**Preconditions**
Enable several policies via GPO (ex: Disable Private Browsing and Disable Firefox Screenshots)
**Steps to reproduce**
1. Create a distribution folder inside your Firefox path.
2. Add a policies.json file which contains invalid entries.
3. Launch Firefox.
4. Access the about:policies page.
**Expected result**
* Policies that were previously set via GPO are being successfully displayed inside the about:policies page and they are successfully applied. (In this case Private Browsing and Firefox Screenshots should be disabled).
**Actual result**
* Policies that were previously set via GPO are not applied ( In this case Private Browsing and Firefox Screenshots are enabled)
**Regression Range**
* I think that this may have came with the changes performed in Bug 1552600
**Note**
Example of invalid policies.json file content:
{
"policies": {
"DisableTelemetry": true,
"DisableMasterPasswordCreation": true,
"Locke
}
}
|
P1
|
RESOLVED
|
DUPLICATE
|
2020-02-17 10:39:16+00:00
|
2021-01-26 18:41:57+00:00
| 342 | 1 |
1616008
|
When using very high (200+%) text-only zoom in the preferences / options, text in dropdowns (menulists), buttons and other UI elements escapes the bounding box / background for the element
|
**Affected versions**
* 75.0a1 (2020-02-16)
* 74.0b4
* 73.0
**Affected platforms**
* Windows 10x64
* macOS 10.14
* Ubuntu 18.04x64
**Steps to reproduce**
1. Launch Firefox.
2. Go to about:preferences.
3. Check the βzoom text onlyβ option
4. Change the default zoom (e.g set it to 200% or higher).
**Expected result**
* The dropdown list is correctly displayed
**Actual result**
* The dropdown list is incorrectly displayed
**Regression range**
* This issue is not a recent regression since I was able to reproduce it on Firefox 73.0. Iβll come with a regression range asap.
**Additional notes**
* Iβll attach a screenshot with the issue.
|
When using very high (200+%) text-only zoom in the preferences / options, text in dropdowns (menulists), buttons and other UI elements escapes the bounding box / background for the element **Affected versions**
* 75.0a1 (2020-02-16)
* 74.0b4
* 73.0
**Affected platforms**
* Windows 10x64
* macOS 10.14
* Ubuntu 18.04x64
**Steps to reproduce**
1. Launch Firefox.
2. Go to about:preferences.
3. Check the βzoom text onlyβ option
4. Change the default zoom (e.g set it to 200% or higher).
**Expected result**
* The dropdown list is correctly displayed
**Actual result**
* The dropdown list is incorrectly displayed
**Regression range**
* This issue is not a recent regression since I was able to reproduce it on Firefox 73.0. Iβll come with a regression range asap.
**Additional notes**
* Iβll attach a screenshot with the issue.
|
P3
|
VERIFIED
|
FIXED
|
2020-02-17 10:43:42+00:00
|
2020-03-02 07:58:55+00:00
| 238 | 3 |
1616058
|
Syntax errors in `SyncedBookmarksMirror.jsm` due to on-disk corruption
|
We're seeing some _really_ interesting errors in telemetryβthings like `ReferenceError: ruper is not defined` (should be `super`) and `XPCOMUtils.defineLazyGlobalGettErs is not a function` (note the case flip), as well as syntax errors in bound params (syntax error in `'unfiled_____root________`) and the SQL strings themselves (syntax errors near `as`, `malformed database schema - unrecognized token: "$"`).
These are all likely caused by `omni.ja` corruption, since we've seen similar issues in bug 1594453, comment 26, bug 1550951 comment 8, and bug 1403348 comment 36.
|
Syntax errors in `SyncedBookmarksMirror.jsm` due to on-disk corruption We're seeing some _really_ interesting errors in telemetryβthings like `ReferenceError: ruper is not defined` (should be `super`) and `XPCOMUtils.defineLazyGlobalGettErs is not a function` (note the case flip), as well as syntax errors in bound params (syntax error in `'unfiled_____root________`) and the SQL strings themselves (syntax errors near `as`, `malformed database schema - unrecognized token: "$"`).
These are all likely caused by `omni.ja` corruption, since we've seen similar issues in bug 1594453, comment 26, bug 1550951 comment 8, and bug 1403348 comment 36.
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-02-17 15:00:56+00:00
|
2020-10-28 05:32:17+00:00
| 196 | 3 |
1616090
|
If the default zoom level is not 100%, about:blank tabs always show zoom indicator [100%] in the address bar
|
Reproducible: always:
Steps to reproduce:
1. Set Home or New tabs to blank
2. Set default zoom level other than 100%
3. Open Home or New tab page or about:blank
Actual Results:
Blank tabs always show zoom indicator [100%] in the address bar
Expected Results:
the zoom indicator should not display
|
If the default zoom level is not 100%, about:blank tabs always show zoom indicator [100%] in the address bar Reproducible: always:
Steps to reproduce:
1. Set Home or New tabs to blank
2. Set default zoom level other than 100%
3. Open Home or New tab page or about:blank
Actual Results:
Blank tabs always show zoom indicator [100%] in the address bar
Expected Results:
the zoom indicator should not display
|
P5
|
RESOLVED
|
FIXED
|
2020-02-17 17:30:31+00:00
|
2020-09-01 09:17:41+00:00
| 98 | 5 |
1616103
|
Bookmarks search - unsorted results order
|
Reproduce: Use the Bookmarks Manager and a SQLite-browser to perform a search in the 'moz_bookmarks'-table that gives more than seven results/matched entries. The results will be initially sorted according to their ID number (rowid), but in the Bookmarks Manager the first and last matches/entries are swapped.
Unsorted bookmarks search:
-sorted by ID number in places.sqlite (moz_bookmarks)
-first and last matches/entries are swapped (with more than 7 results)
-correct order only remains with less than 7 results
While it could make sense to show the most recent/last created entry at top, the first/oldest one shouldn't be placed at the very bottom.
|
Bookmarks search - unsorted results order Reproduce: Use the Bookmarks Manager and a SQLite-browser to perform a search in the 'moz_bookmarks'-table that gives more than seven results/matched entries. The results will be initially sorted according to their ID number (rowid), but in the Bookmarks Manager the first and last matches/entries are swapped.
Unsorted bookmarks search:
-sorted by ID number in places.sqlite (moz_bookmarks)
-first and last matches/entries are swapped (with more than 7 results)
-correct order only remains with less than 7 results
While it could make sense to show the most recent/last created entry at top, the first/oldest one shouldn't be placed at the very bottom.
|
P3
|
NEW
|
2020-02-17 18:30:47+00:00
|
2022-10-11 23:57:54+00:00
| 163 | 3 |
|
1616126
|
DOS based on repeated basic authentication prompt.
|
As requested at https://bugzilla.mozilla.org/show_bug.cgi?id=377496
re-entering the bug here.
Sequence of events is:
1. Bing ad for common term such as "bug report" sends user to
http://shop.frankfurt-airport.store
2. Redirects to attack site.
3. Page in attachment appears. Obvious phishing attack coupled with denial of service attack.
4. Unable to dismiss basic authentication prompt. Unable to stop page. Unable to close browser. Ubuntu Linux 18.04 begins thrashing with heavy disk I/O.
5. Finally was able to open a terminal window, which took many minutes to open, ran "top" to find Firefox process, killed Firefox. System returned to normal.
|
DOS based on repeated basic authentication prompt. As requested at https://bugzilla.mozilla.org/show_bug.cgi?id=377496
re-entering the bug here.
Sequence of events is:
1. Bing ad for common term such as "bug report" sends user to
http://shop.frankfurt-airport.store
2. Redirects to attack site.
3. Page in attachment appears. Obvious phishing attack coupled with denial of service attack.
4. Unable to dismiss basic authentication prompt. Unable to stop page. Unable to close browser. Ubuntu Linux 18.04 begins thrashing with heavy disk I/O.
5. Finally was able to open a terminal window, which took many minutes to open, ran "top" to find Firefox process, killed Firefox. System returned to normal.
|
P2
|
RESOLVED
|
FIXED
|
2020-02-17 21:04:55+00:00
|
2021-02-02 09:07:12+00:00
| 182 | 2 |
1616157
|
PDF.js UI elements are affected by global default zoom
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
1. Set the default zoom preference to 150%
2. Open a PDF in Firefox
Actual results:
The PDF.js UI (toolbar, sidebar) is scaled up to 150%. There's no way to scale it down to 100%, because all ways to zoom in/out are handled specially by PDF.js.
Expected results:
The PDF.js UI should stay scaled to 100%, because the size of other Firefox UI elements is not affected by the default zoom. Other special viewers like the image viewer and the media player also default to 100% regardless of the default zoom.
|
PDF.js UI elements are affected by global default zoom User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
1. Set the default zoom preference to 150%
2. Open a PDF in Firefox
Actual results:
The PDF.js UI (toolbar, sidebar) is scaled up to 150%. There's no way to scale it down to 100%, because all ways to zoom in/out are handled specially by PDF.js.
Expected results:
The PDF.js UI should stay scaled to 100%, because the size of other Firefox UI elements is not affected by the default zoom. Other special viewers like the image viewer and the media player also default to 100% regardless of the default zoom.
|
P2
|
VERIFIED
|
FIXED
|
2020-02-18 01:22:11+00:00
|
2020-03-20 10:01:08+00:00
| 185 | 2 |
1616280
|
Investigate using shadow DOM to hide Remote L10n translations for from local translations
|
Why: we would be able to use HTML markup in our remote translations. For context any messaging surface that uses Remote L10n now cannot support HTML markup.
The global Localization instance does not expect another one (like the Remote L10n one) to exist and will overwrite our translations. We can hide content from it by using custom elements and then [connecting the root](https://searchfox.org/mozilla-central/rev/0439db3a39faddb90197a87cc184c57dcbf0a770/browser/components/aboutlogins/content/components/confirmation-dialog.js#19) to the Remote L10n localization. By default the mutation observer does not check the shadow DOM.
|
Investigate using shadow DOM to hide Remote L10n translations for from local translations Why: we would be able to use HTML markup in our remote translations. For context any messaging surface that uses Remote L10n now cannot support HTML markup.
The global Localization instance does not expect another one (like the Remote L10n one) to exist and will overwrite our translations. We can hide content from it by using custom elements and then [connecting the root](https://searchfox.org/mozilla-central/rev/0439db3a39faddb90197a87cc184c57dcbf0a770/browser/components/aboutlogins/content/components/confirmation-dialog.js#19) to the Remote L10n localization. By default the mutation observer does not check the shadow DOM.
|
P2
|
RESOLVED
|
FIXED
|
2020-02-18 14:45:12+00:00
|
2020-04-21 03:10:22+00:00
| 185 | 2 |
1616296
|
PDF Printing: Unusual Characters Appearing
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Printed a PDF from the PDF view. PDF is from journals-sagepub-com.
Actual results:
Boxes appeared at every space between characters (see attached pdf)
Expected results:
It should have printed normally. This is not the first time I have encountered this exact issue with scholarly journal pdfs. I only experience this issue in Firefox. PDFs printed in Chrome/Chromium-based browsers, Safari, and in Preview (OSX) are all as they appear on the screen.
|
PDF Printing: Unusual Characters Appearing User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Printed a PDF from the PDF view. PDF is from journals-sagepub-com.
Actual results:
Boxes appeared at every space between characters (see attached pdf)
Expected results:
It should have printed normally. This is not the first time I have encountered this exact issue with scholarly journal pdfs. I only experience this issue in Firefox. PDFs printed in Chrome/Chromium-based browsers, Safari, and in Preview (OSX) are all as they appear on the screen.
|
P3
|
RESOLVED
|
INCOMPLETE
|
2020-02-18 16:03:49+00:00
|
2022-03-11 16:37:18+00:00
| 155 | 3 |
1616305
|
Global zoom fails to propagate to existing tabs when site-specific zoom is disabled
|
After landing bug 1603494, the following workflow is possible:
1. Disable site specific zoom in about:config
2. Set a default zoom level in about:preferences
3. Open new tabs for any domain, see your default zoom level reflected
However, the following currently does _not_ work:
1. Disable site specific zoom in about:config
2. Open google.com
3. In a new tab, navigate to about:preferences and set a default zoom level
4. Open twitter.com
Expected:
Twitter and google have adjusted to the default zoom level set in (3)
Actual:
Twitter has adjusted to the default zoom level set in (3) but google has not.
My guess is there are listeners that we disable when site-specific zoom is off, and so even when a tab that existed before the default zoom level was set is made active, it doesn't "hear" the change.
|
Global zoom fails to propagate to existing tabs when site-specific zoom is disabled After landing bug 1603494, the following workflow is possible:
1. Disable site specific zoom in about:config
2. Set a default zoom level in about:preferences
3. Open new tabs for any domain, see your default zoom level reflected
However, the following currently does _not_ work:
1. Disable site specific zoom in about:config
2. Open google.com
3. In a new tab, navigate to about:preferences and set a default zoom level
4. Open twitter.com
Expected:
Twitter and google have adjusted to the default zoom level set in (3)
Actual:
Twitter has adjusted to the default zoom level set in (3) but google has not.
My guess is there are listeners that we disable when site-specific zoom is off, and so even when a tab that existed before the default zoom level was set is made active, it doesn't "hear" the change.
|
P3
|
NEW
|
2020-02-18 16:22:14+00:00
|
2022-10-11 23:58:07+00:00
| 212 | 3 |
|
1616324
|
Add focus ring for sidebar drop down menu and close icon
|
STEPS TO REPRODUCE
1. Open any sidebar (e.g. β-B to open bookmarks sidebar)
2. Select shift-tab to move focus backwards onto close icon
3. Select shift-tab again to move focus backwards again to drop down menu
EXPECTED RESULTS
* Focus rings appear for both 2 and 3 in the same style as about:preferences (see sidebar.gif)
ACTUAL RESULTS
* Focus is invisible
|
Add focus ring for sidebar drop down menu and close icon STEPS TO REPRODUCE
1. Open any sidebar (e.g. β-B to open bookmarks sidebar)
2. Select shift-tab to move focus backwards onto close icon
3. Select shift-tab again to move focus backwards again to drop down menu
EXPECTED RESULTS
* Focus rings appear for both 2 and 3 in the same style as about:preferences (see sidebar.gif)
ACTUAL RESULTS
* Focus is invisible
|
P3
|
VERIFIED
|
FIXED
|
2020-02-18 17:58:34+00:00
|
2021-02-18 09:33:29+00:00
| 100 | 3 |
1616355
|
Attribution postSigningData should be per installation
|
Right now, the `postSigningData` written by an _attributed_ stub installer is written to a [single global location](https://searchfox.org/mozilla-central/rev/df94cd5ba431234bc220ac081def0801fe44b89e/browser/components/attribution/AttributionCode.jsm#43). That means that multiple installers will compete for the global location, and in the event that a second Firefox version is installed an existing profile will report _varying_ attribution, which of course should not be possible. This ticket tracks making `postSigningData` per installation.
|
Attribution postSigningData should be per installation Right now, the `postSigningData` written by an _attributed_ stub installer is written to a [single global location](https://searchfox.org/mozilla-central/rev/df94cd5ba431234bc220ac081def0801fe44b89e/browser/components/attribution/AttributionCode.jsm#43). That means that multiple installers will compete for the global location, and in the event that a second Firefox version is installed an existing profile will report _varying_ attribution, which of course should not be possible. This ticket tracks making `postSigningData` per installation.
|
P3
|
RESOLVED
|
FIXED
|
2020-02-18 19:43:01+00:00
|
2022-05-04 03:43:07+00:00
| 171 | 3 |
1616454
|
Putting Bookmark Toolbar Items next to the address bar can make it too small to use
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
I have a lot of bookmarks in my bookmark toolbar, and 3 buttons on the right side of my address bar.
Actual results:
When I visit sites that make Firefox put extra buttons on the left side of the address bar, like the reader mode or blocked autoplay buttons, it becomes impossible to put my cursor in the address bar.
Expected results:
Firefox should move more bookmarks to the overflow menu of the bookmars toolbar to make room for the address bar.
|
Putting Bookmark Toolbar Items next to the address bar can make it too small to use User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
I have a lot of bookmarks in my bookmark toolbar, and 3 buttons on the right side of my address bar.
Actual results:
When I visit sites that make Firefox put extra buttons on the left side of the address bar, like the reader mode or blocked autoplay buttons, it becomes impossible to put my cursor in the address bar.
Expected results:
Firefox should move more bookmarks to the overflow menu of the bookmars toolbar to make room for the address bar.
|
P5
|
NEW
|
2020-02-19 02:50:02+00:00
|
2020-07-09 04:31:06+00:00
| 171 | 5 |
|
1616460
|
bookmarks tree view can cause bookmarks to be moved even when it's not visible
|
Bug 1605881 worked around the 1 case where we know for sure that unexpected bookmark moves where happening, but the core issue remains and this could theoretically happen in other scenarios due to a fundamental issue in the bookmark tree view. See bug 1605881 comment 10 for a detailed description of what's wrong and what can be done to fix it.
|
bookmarks tree view can cause bookmarks to be moved even when it's not visible Bug 1605881 worked around the 1 case where we know for sure that unexpected bookmark moves where happening, but the core issue remains and this could theoretically happen in other scenarios due to a fundamental issue in the bookmark tree view. See bug 1605881 comment 10 for a detailed description of what's wrong and what can be done to fix it.
|
P1
|
RESOLVED
|
FIXED
|
2020-02-19 04:33:10+00:00
|
2020-03-10 16:10:12+00:00
| 94 | 1 |
1616471
|
Firefox browser has entirely removed the firepath addons
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36
Steps to reproduce:
1.I opened the firefox browser
2.I searched for Firepath addons on Addons Store
3.It has shown the message that it isupport the Firepath addons only upto the 45.0 version
Actual results:
It has disabled the firepath addons after 45.0 version
Expected results:
It should atleast be enabled for the latest version of firefox
|
Firefox browser has entirely removed the firepath addons User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36
Steps to reproduce:
1.I opened the firefox browser
2.I searched for Firepath addons on Addons Store
3.It has shown the message that it isupport the Firepath addons only upto the 45.0 version
Actual results:
It has disabled the firepath addons after 45.0 version
Expected results:
It should atleast be enabled for the latest version of firefox
|
P3
|
RESOLVED
|
INVALID
|
2020-02-19 06:32:06+00:00
|
2020-02-19 08:54:19+00:00
| 156 | 3 |
1616508
|
If in one tab ETP is OFF, the switch moves from OFF position to ON while navigating between two tabs
|
**Affected versions**
* Firefox 73.0
* Firefox 74.0b4
* Nightly 75.0a1
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04 x64
* macOS 10.15
**Steps to reproduce**
1. Open two sites in different tabs.
2. In one of the tab turn off ETP.
3. Without closing the doorhanger, switch to the other tab and open ETP doorhanger.
4. Pay close attention to the button for the ON/OFF switch.
**Expected result**
* The switch is on the ON position.
**Actual result**
* The switch moves from OFF position to ON.
**Regression range**
* If this is a regression it's an older one. I can reproduce the issue on Firefox 73.0, too.
**Additional notes**
* Please look at the attached gif.
|
If in one tab ETP is OFF, the switch moves from OFF position to ON while navigating between two tabs **Affected versions**
* Firefox 73.0
* Firefox 74.0b4
* Nightly 75.0a1
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04 x64
* macOS 10.15
**Steps to reproduce**
1. Open two sites in different tabs.
2. In one of the tab turn off ETP.
3. Without closing the doorhanger, switch to the other tab and open ETP doorhanger.
4. Pay close attention to the button for the ON/OFF switch.
**Expected result**
* The switch is on the ON position.
**Actual result**
* The switch moves from OFF position to ON.
**Regression range**
* If this is a regression it's an older one. I can reproduce the issue on Firefox 73.0, too.
**Additional notes**
* Please look at the attached gif.
|
P3
|
NEW
|
2020-02-19 09:15:59+00:00
|
2022-10-10 19:29:22+00:00
| 228 | 3 |
|
1616517
|
Cards context menu button animation is rendered incorrectly with WebRender enabled
|
**[Affected versions]:**
- Firefox Release 73.0.1 Build ID 20200217142647
- Firefox Beta 74.0b5 Build ID 20200218224219
- Firefox Nightly 75.0a1 Build ID 20200218213359
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[Prerequisites]:**
- Have WebRender graphics compositor enabled.
**[Steps to reproduce]:**
1. Open about:newtab page.
2. Hover over any Top Site/Recommended by Pocket/Highlights card.
3. Observe the context menu button.
**[Expected result]:**
- Context menu button animation is rendered correctly.
**[Actual result]:**
- Context menu button animation is rendered incorrectly.
**[Notes]:**
- Issue is observed better for Highlights cards.
- Not reproducing if Webrender is disabled.
|
Cards context menu button animation is rendered incorrectly with WebRender enabled **[Affected versions]:**
- Firefox Release 73.0.1 Build ID 20200217142647
- Firefox Beta 74.0b5 Build ID 20200218224219
- Firefox Nightly 75.0a1 Build ID 20200218213359
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[Prerequisites]:**
- Have WebRender graphics compositor enabled.
**[Steps to reproduce]:**
1. Open about:newtab page.
2. Hover over any Top Site/Recommended by Pocket/Highlights card.
3. Observe the context menu button.
**[Expected result]:**
- Context menu button animation is rendered correctly.
**[Actual result]:**
- Context menu button animation is rendered incorrectly.
**[Notes]:**
- Issue is observed better for Highlights cards.
- Not reproducing if Webrender is disabled.
|
P3
|
NEW
|
2020-02-19 09:37:32+00:00
|
2022-10-11 23:58:21+00:00
| 233 | 3 |
|
1616531
|
MS RDWebAccess pages shows up as "Unencrypted"
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
1. Open an website to access work resources via RemoteApp and Desktop Connections (RD Web Access).
2. In address bar click on the "Lock" icon in the addressbar.
3. It shows up as "Secured Connection"
4. Click on the arrow to the right and click "More Information"
5. Here it shows up as "Not Secured" and there is no option to display the SSL Certificate.
Actual results:
1. Website shows up as "Unsecured"
Expected results:
1. Website should show up as "Secured" and there should be an "Show Certificate button"
|
MS RDWebAccess pages shows up as "Unencrypted" User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
1. Open an website to access work resources via RemoteApp and Desktop Connections (RD Web Access).
2. In address bar click on the "Lock" icon in the addressbar.
3. It shows up as "Secured Connection"
4. Click on the arrow to the right and click "More Information"
5. Here it shows up as "Not Secured" and there is no option to display the SSL Certificate.
Actual results:
1. Website shows up as "Unsecured"
Expected results:
1. Website should show up as "Secured" and there should be an "Show Certificate button"
|
P3
|
NEW
|
2020-02-19 11:16:31+00:00
|
2024-08-24 19:23:12+00:00
| 188 | 3 |
|
1616600
|
The Firefox process will not shut down after closing the browser if the Camera and Microphone are allowed in different tabs
|
[Affected versions]:
Nightly 75.0a1
[Affected platforms]:
Platforms: all
Steps :
1. Open the Firefox Browser and https://jsfiddle.net/jib1/r60bzmrs/
2. Alow the camera permission prompt.
3. Open the Firefox Browser and https://jsfiddle.net/jib1/r60bzmrs/ in a second tab.
4. Close the Firefox process.
Expected Results :
The Firefox process should close without issues.
Actual Results :
The Firefox process will not shutdown upon closing the browser.
Note: Please note that the same issue occurs with the microphone permission (or both at the same time) (https://jsfiddle.net/jib1/59og5vhn/).
After the user allows the microphone to start in two separate tabs and closing the browser the Firefox process will not shutdown.
This issue only occurs on Windows and Ubuntu, it seems Mac will shutdown the process if you quit the browser with right click > Quit.
I've also performed a Mozregression on this issue and here are the results :
Last known GOOD build:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ea063dbb6c1b5cdfedbf232e234a7f9c492b44af&tochange=cf63a0b7bd7d7110fb917cf158097a6495c65ccd
First known BAD build:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d827ca47ac5bdc005f6854c2534cd0c4bcd37db0&tochange=cf63a0b7bd7d7110fb917cf158097a6495c65ccd
|
The Firefox process will not shut down after closing the browser if the Camera and Microphone are allowed in different tabs [Affected versions]:
Nightly 75.0a1
[Affected platforms]:
Platforms: all
Steps :
1. Open the Firefox Browser and https://jsfiddle.net/jib1/r60bzmrs/
2. Alow the camera permission prompt.
3. Open the Firefox Browser and https://jsfiddle.net/jib1/r60bzmrs/ in a second tab.
4. Close the Firefox process.
Expected Results :
The Firefox process should close without issues.
Actual Results :
The Firefox process will not shutdown upon closing the browser.
Note: Please note that the same issue occurs with the microphone permission (or both at the same time) (https://jsfiddle.net/jib1/59og5vhn/).
After the user allows the microphone to start in two separate tabs and closing the browser the Firefox process will not shutdown.
This issue only occurs on Windows and Ubuntu, it seems Mac will shutdown the process if you quit the browser with right click > Quit.
I've also performed a Mozregression on this issue and here are the results :
Last known GOOD build:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ea063dbb6c1b5cdfedbf232e234a7f9c492b44af&tochange=cf63a0b7bd7d7110fb917cf158097a6495c65ccd
First known BAD build:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d827ca47ac5bdc005f6854c2534cd0c4bcd37db0&tochange=cf63a0b7bd7d7110fb917cf158097a6495c65ccd
|
P2
|
VERIFIED
|
FIXED
|
2020-02-19 16:05:20+00:00
|
2020-02-28 08:41:14+00:00
| 475 | 2 |
1616631
|
move and split browser_search_tips.js
|
The test takes a long time to run, we should move all tips tests into a tips/ subfolder under tests/browser and split this test. We should rename the existing interventions_update folder to tips/ to avoid too deep structures and avoid duplicating head.js
|
move and split browser_search_tips.js The test takes a long time to run, we should move all tips tests into a tips/ subfolder under tests/browser and split this test. We should rename the existing interventions_update folder to tips/ to avoid too deep structures and avoid duplicating head.js
|
P3
|
RESOLVED
|
FIXED
|
2020-02-19 18:10:21+00:00
|
2020-02-29 04:08:10+00:00
| 72 | 3 |
1616639
|
Spacers can get noticably thinner, and even restoring toolbar defaults doesn't fix it
|
STR:
1. Clean profile
2. Open about:preferences#search and select the "Add search bar in toolbar" option
3. Drag the resizer between the urlbar and the search bar to the farthest left (you'll see at this point that the left spacer gets thin)
4. Do the same, now to the farthest right
5. In the same about:preferences page select the "Use the address bar for search and navigation" option
AR:
The spacers now get really thin. Going back to customize mode, the restore defaults button is disabled (i.e. the current state is allegedly already the default). Even if you make changes and restore defaults, the spacers are still thin.
ER:
Normal behaviour of the spacers.
|
Spacers can get noticably thinner, and even restoring toolbar defaults doesn't fix it STR:
1. Clean profile
2. Open about:preferences#search and select the "Add search bar in toolbar" option
3. Drag the resizer between the urlbar and the search bar to the farthest left (you'll see at this point that the left spacer gets thin)
4. Do the same, now to the farthest right
5. In the same about:preferences page select the "Use the address bar for search and navigation" option
AR:
The spacers now get really thin. Going back to customize mode, the restore defaults button is disabled (i.e. the current state is allegedly already the default). Even if you make changes and restore defaults, the spacers are still thin.
ER:
Normal behaviour of the spacers.
|
P3
|
VERIFIED
|
FIXED
|
2020-02-19 18:37:08+00:00
|
2020-05-14 14:37:22+00:00
| 185 | 3 |
1616724
|
The item suddenly moves down one line because the menu("Restart to update Nightly" ) is inserted at the top.
|
This is annoying. it may cause false click.
Reproducible: yes, if you are lucky
Steps to reproduce:
1. Start Nightly
2. Open Hamburger Menu and click an item
Actual Results:
The item suddenly moves down a line. So, I was clicked on an unintended item.
Expected Results:
Items must not move down.
|
The item suddenly moves down one line because the menu("Restart to update Nightly" ) is inserted at the top. This is annoying. it may cause false click.
Reproducible: yes, if you are lucky
Steps to reproduce:
1. Start Nightly
2. Open Hamburger Menu and click an item
Actual Results:
The item suddenly moves down a line. So, I was clicked on an unintended item.
Expected Results:
Items must not move down.
|
P5
|
NEW
|
2020-02-20 00:52:29+00:00
|
2022-10-11 23:58:33+00:00
| 95 | 5 |
|
1616772
|
Re-enable browser/base/content/test/fullscreen/browser_bug1557041.js for Fission
|
I'm going to disable this for Fission. This bug is for re-enabling browser/base/content/test/fullscreen/browser_bug1557041.js for Fission.
|
Re-enable browser/base/content/test/fullscreen/browser_bug1557041.js for Fission I'm going to disable this for Fission. This bug is for re-enabling browser/base/content/test/fullscreen/browser_bug1557041.js for Fission.
|
P3
|
RESOLVED
|
FIXED
|
2020-02-20 09:06:30+00:00
|
2020-05-27 20:17:40+00:00
| 70 | 3 |
1616793
|
Stop hiding top sites if they are disabled in the new tab page
|
Our initial assumption in bug 1608359 was wrong, users hide Top Sites in the New Tab Page for the most various reasons among which starting with a clean slate or the remove-bloat placebo effect.
Those same users are now surprised that we removed the top sites list from the urlbar, and the connection between the two features is totally hidden and undiscoverable.
|
Stop hiding top sites if they are disabled in the new tab page Our initial assumption in bug 1608359 was wrong, users hide Top Sites in the New Tab Page for the most various reasons among which starting with a clean slate or the remove-bloat placebo effect.
Those same users are now surprised that we removed the top sites list from the urlbar, and the connection between the two features is totally hidden and undiscoverable.
|
P1
|
VERIFIED
|
FIXED
|
2020-02-20 10:27:14+00:00
|
2020-02-28 13:19:05+00:00
| 95 | 1 |
1616825
|
Bookmarks should ignore refs/anchors
|
After refreshing a bookmarked Google document, on the address bar it shows that the document is not marked.
Steps to reproduce:
1. Open any bookmarked Google document.
2. Navigate and click anywhere on the page.
3. Refresh the page. Without clicking anywhere, on the address bar it shows that the document is not bookmarked.
4. Click again anywhere on the page and it should appear that the document is bookmarked again.
I've managed to reproduce this issue on Firefox 73.0.1 and Nightly 75.0. I have also tested on a OneDrive document and I could not reproduce the behavior.
|
Bookmarks should ignore refs/anchors After refreshing a bookmarked Google document, on the address bar it shows that the document is not marked.
Steps to reproduce:
1. Open any bookmarked Google document.
2. Navigate and click anywhere on the page.
3. Refresh the page. Without clicking anywhere, on the address bar it shows that the document is not bookmarked.
4. Click again anywhere on the page and it should appear that the document is bookmarked again.
I've managed to reproduce this issue on Firefox 73.0.1 and Nightly 75.0. I have also tested on a OneDrive document and I could not reproduce the behavior.
|
P3
|
NEW
|
2020-02-20 13:05:06+00:00
|
2022-10-11 23:58:41+00:00
| 143 | 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.