Dataset Viewer
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
|
|---|---|---|---|---|---|---|---|---|---|---|
1606631
|
Inefficient z-ordering of elements in the browser UI, causes large layers with current WebRender heuristics
|
Steps to reproduce:
1. Be on macOS.
2. Enable the prefs `gfx.webrender.all`, `gfx.webrender.compositor` (requires restart), and `gfx.core-animation.tint-opaque` (restartless).
3. Pay attention to the amount of redness on the screen.
Expected results:
The active tab and the back button should be drawn into the same red layer as the rest of the chrome.
Actual results:
The active tab and the back button are drawn into another red layer that goes on top of the rest of the chrome. When the statusbar appears (when a link is moused over), there's a big red layer that covers the majority of the browser window.
Most of the browser chrome is "behind" the content area, in z-order. Elements that are "in front" of the content area, in z-order, go into a separate layer. (The fact that these elements don't overlap the content area is not taken into account by WebRender, and we should keep it that way.)
We should apply some z-index declarations in browser CSS, so that we have the following order:
1. Bottom layer: The window background and all elements in the browser chrome that do not overlap the content area. This should include the active tab and the back button.
2. Middle layer: The `<browser>` for the tab contents
3. Top layer: Elements from the browser chrome that can overlap the tab contents, such as the focused URL bar and the URL bar autocomplete dropdown.
|
Inefficient z-ordering of elements in the browser UI, causes large layers with current WebRender heuristics Steps to reproduce:
1. Be on macOS.
2. Enable the prefs `gfx.webrender.all`, `gfx.webrender.compositor` (requires restart), and `gfx.core-animation.tint-opaque` (restartless).
3. Pay attention to the amount of redness on the screen.
Expected results:
The active tab and the back button should be drawn into the same red layer as the rest of the chrome.
Actual results:
The active tab and the back button are drawn into another red layer that goes on top of the rest of the chrome. When the statusbar appears (when a link is moused over), there's a big red layer that covers the majority of the browser window.
Most of the browser chrome is "behind" the content area, in z-order. Elements that are "in front" of the content area, in z-order, go into a separate layer. (The fact that these elements don't overlap the content area is not taken into account by WebRender, and we should keep it that way.)
We should apply some z-index declarations in browser CSS, so that we have the following order:
1. Bottom layer: The window background and all elements in the browser chrome that do not overlap the content area. This should include the active tab and the back button.
2. Middle layer: The `<browser>` for the tab contents
3. Top layer: Elements from the browser chrome that can overlap the tab contents, such as the focused URL bar and the URL bar autocomplete dropdown.
|
P3
|
RESOLVED
|
INCOMPLETE
|
2020-01-02 13:46:45+00:00
|
2024-06-28 09:36:11+00:00
| 373 | 3 |
1606644
|
pages with unsaved data should not be closed by middle click on their tab
|
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
I am using Linux
1. Type some text into a page text box.
2. Click once on the page tab. A dialog box appears "This page is asking you to confirm that you want to leave - data you have entered may not be saved.".
3. Click once more on the tab and the page closes.
Actual results:
On the second click, the page closed ignoring the apparently blocking dialog and loosing the information I typed into the text box.
For my particular use cases, I use middle click to remove a collection of consecutive unused pages. To do this, I rapidly middle click on the tabs. With the current behavior, I close pages that have un-sumitted text.
Expected results:
Middle clicking on a tab that has a dialog box "This page is asking you to confirm that you want to leave - data you have entered may not be saved." should do nothing.
|
pages with unsaved data should not be closed by middle click on their tab User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
I am using Linux
1. Type some text into a page text box.
2. Click once on the page tab. A dialog box appears "This page is asking you to confirm that you want to leave - data you have entered may not be saved.".
3. Click once more on the tab and the page closes.
Actual results:
On the second click, the page closed ignoring the apparently blocking dialog and loosing the information I typed into the text box.
For my particular use cases, I use middle click to remove a collection of consecutive unused pages. To do this, I rapidly middle click on the tabs. With the current behavior, I close pages that have un-sumitted text.
Expected results:
Middle clicking on a tab that has a dialog box "This page is asking you to confirm that you want to leave - data you have entered may not be saved." should do nothing.
|
P5
|
NEW
|
2020-01-02 14:46:03+00:00
|
2023-03-13 14:15:22+00:00
| 253 | 5 |
|
1606677
|
Dragging a folder shortcut on the toolbar duplicates the shortcut
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I had sync on, so my mobile bookmarks synced into PC firefox.
The mobile bookmarks is listed under "other bookmarks" in the PC.
So i dragged and moved it into the "bookmark toolbar" to re-arrange the bookmarks.
But i had too many bookmarks in the toolbar, so some are truncated (inside the arrow).
I dragged the folder from arrow subsection to toolbar again to bring it in front, and send other bookmark (whichever bookmark in last, before arrow) into that section (truncated section).
But instead of putting the mobile bookmark folder in the toolbar front, the folder got replicated.
Actual results:
The bookmark folder got replicated instead of getting moved (re-arranged).
Expected results:
The bookmark folder should have re-arranged.
|
Dragging a folder shortcut on the toolbar duplicates the shortcut User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I had sync on, so my mobile bookmarks synced into PC firefox.
The mobile bookmarks is listed under "other bookmarks" in the PC.
So i dragged and moved it into the "bookmark toolbar" to re-arrange the bookmarks.
But i had too many bookmarks in the toolbar, so some are truncated (inside the arrow).
I dragged the folder from arrow subsection to toolbar again to bring it in front, and send other bookmark (whichever bookmark in last, before arrow) into that section (truncated section).
But instead of putting the mobile bookmark folder in the toolbar front, the folder got replicated.
Actual results:
The bookmark folder got replicated instead of getting moved (re-arranged).
Expected results:
The bookmark folder should have re-arranged.
|
P3
|
NEW
|
2020-01-02 16:54:34+00:00
|
2022-10-11 23:48:04+00:00
| 235 | 3 |
|
1606731
|
Searching for a page in the address bar or history sidebar should ignore diacritics
|
Steps to reproduce:
1. Visit https://ca.wikipedia.org/
2. Type "viquipedia" in the address bar
Expected results: https://ca.wikipedia.org/ should appear
Actual results: https://ca.wikipedia.org/ does not appear
|
Searching for a page in the address bar or history sidebar should ignore diacritics Steps to reproduce:
1. Visit https://ca.wikipedia.org/
2. Type "viquipedia" in the address bar
Expected results: https://ca.wikipedia.org/ should appear
Actual results: https://ca.wikipedia.org/ does not appear
|
P3
|
RESOLVED
|
FIXED
|
2020-01-02 21:37:42+00:00
|
2020-02-28 09:18:15+00:00
| 81 | 3 |
1606789
|
First run page suggests signing in when you already are, and accounts.firefox.com doesn't indicate you already are logged in
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
1. I reinstalled Firefox because it crashed every time I tried to open it
2. Firefox asked me to have a "fresh start" so I clicked it
3. Firefox asked me to login to Firefox so I clicked it
4. Then I added Lastpass to Firefox because I didn't know the password to my Firefox account
5. Lastpass didin't seem to wok so I closed Firefox
6. And was loged in when I started Firefox again
Expected results:
I expected to not be loged in after restart of Firefox. Maybe this has something to do with the old data after reinstalling Firefox?
|
First run page suggests signing in when you already are, and accounts.firefox.com doesn't indicate you already are logged in User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
1. I reinstalled Firefox because it crashed every time I tried to open it
2. Firefox asked me to have a "fresh start" so I clicked it
3. Firefox asked me to login to Firefox so I clicked it
4. Then I added Lastpass to Firefox because I didn't know the password to my Firefox account
5. Lastpass didin't seem to wok so I closed Firefox
6. And was loged in when I started Firefox again
Expected results:
I expected to not be loged in after restart of Firefox. Maybe this has something to do with the old data after reinstalling Firefox?
|
P2
|
RESOLVED
|
MOVED
|
2020-01-03 09:06:53+00:00
|
2020-09-10 01:51:03+00:00
| 224 | 2 |
1606797
|
Do not allow more than one simultaneous "open external protocol" dialog to appear per originating tab
|
**Affected versions**
- Firefox 68.4.0esr
- Firefox 70.0.1
- Firefox 72.0b11
- Firefox 73.0a1
**Affected platforms**
- Windows 10 & 7
- macOS 10.15
**Steps to reproduce**
1. Open the following [link](https://outlook.live.com/people/0/) and login with valid credentials
2. If not available, create a new contact and add a phone number to it
3. On the newly created contact, click on the phone number
**Expected result**
- An external application window requesting the user to choose is shown
**Actual result**
- Two windows will appear, requesting the same action
**Regression range**
- I will see for a regression, if there is one.
**Additional notes**
- The actual issue can be seen in the attachment.
- On Ubuntu 18, a request to launch an external application will not appear, instead a page stating that "The address was not understood" will appear.
|
Do not allow more than one simultaneous "open external protocol" dialog to appear per originating tab **Affected versions**
- Firefox 68.4.0esr
- Firefox 70.0.1
- Firefox 72.0b11
- Firefox 73.0a1
**Affected platforms**
- Windows 10 & 7
- macOS 10.15
**Steps to reproduce**
1. Open the following [link](https://outlook.live.com/people/0/) and login with valid credentials
2. If not available, create a new contact and add a phone number to it
3. On the newly created contact, click on the phone number
**Expected result**
- An external application window requesting the user to choose is shown
**Actual result**
- Two windows will appear, requesting the same action
**Regression range**
- I will see for a regression, if there is one.
**Additional notes**
- The actual issue can be seen in the attachment.
- On Ubuntu 18, a request to launch an external application will not appear, instead a page stating that "The address was not understood" will appear.
|
P3
|
RESOLVED
|
FIXED
|
2020-01-03 10:17:01+00:00
|
2021-01-06 02:04:04+00:00
| 252 | 3 |
1606809
|
Right-clicking on edges of the expanded MegaBar gets the toolbar contextual menu, not the address bar one
|
STR
1. Turn on the bookmarks toolbar.
2. Click on the address bar to focus it and cause it to expand.
3. Decide you're going to paste something, but in the meantime you've moved the mouse down slightly but not off the expanded bar.
4. Right-click and go to select paste.
Actual Results
The toolbar bar context menu was shown and the bookmarks toolbar got disabled (because I did it too quick to realise).
Expected Results
The address bar context menu should have been shown and paste should have been selected.
This also occurs on the top and side edges.
|
Right-clicking on edges of the expanded MegaBar gets the toolbar contextual menu, not the address bar one STR
1. Turn on the bookmarks toolbar.
2. Click on the address bar to focus it and cause it to expand.
3. Decide you're going to paste something, but in the meantime you've moved the mouse down slightly but not off the expanded bar.
4. Right-click and go to select paste.
Actual Results
The toolbar bar context menu was shown and the bookmarks toolbar got disabled (because I did it too quick to realise).
Expected Results
The address bar context menu should have been shown and paste should have been selected.
This also occurs on the top and side edges.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-03 12:19:39+00:00
|
2020-03-19 14:59:34+00:00
| 151 | 1 |
1606893
|
JavaScript error: resource://gre/modules/PushDB.jsm, line 414: Error: Record ? does not exist
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
- Re-install Firefox Nightly
- Configure Sync
- See Errors
```
JavaScript error: resource://gre/modules/PushDB.jsm, line 414: Error: Record 0fc4cbcc-cb21-4f8b-b19a-da3bce18b8d7 does not exist
```
Actual results:
Errors:
```
1578068234448 Sync.AddonsReconciler INFO Registering as Add-on Manager listener.
1578068234448 Sync.AddonsReconciler DEBUG Adding change listener.
1578068234450 FirefoxAccounts TRACE not checking freshness of profile as it remains recent
JavaScript error: resource://gre/modules/PushDB.jsm, line 414: Error: Record 0fc4cbcc-cb21-4f8b-b19a-da3bce18b8d7 does not exist
JavaScript error: resource://gre/modules/PushDB.jsm, line 414: Error: Record 0fc4cbcc-cb21-4f8b-b19a-da3bce18b8d7 does not exist
{}
1578068239451 Sync.Service DEBUG User-Agent: Firefox/73.0a1 (Linux x86_64) FxSync/1.75.0.20191217161753.desktop
1578068239451 Sync.Service INFO Starting sync at 2020-01-03 13:17:19 in browser session 06Tm6orSJVql
1578068239451 Sync.Service DEBUG In sync: should login.
1578068239452 Sync.Service INFO User logged in successfully - verifying login.
```
Expected results:
No errors. Thanks!
|
JavaScript error: resource://gre/modules/PushDB.jsm, line 414: Error: Record ? does not exist User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
- Re-install Firefox Nightly
- Configure Sync
- See Errors
```
JavaScript error: resource://gre/modules/PushDB.jsm, line 414: Error: Record 0fc4cbcc-cb21-4f8b-b19a-da3bce18b8d7 does not exist
```
Actual results:
Errors:
```
1578068234448 Sync.AddonsReconciler INFO Registering as Add-on Manager listener.
1578068234448 Sync.AddonsReconciler DEBUG Adding change listener.
1578068234450 FirefoxAccounts TRACE not checking freshness of profile as it remains recent
JavaScript error: resource://gre/modules/PushDB.jsm, line 414: Error: Record 0fc4cbcc-cb21-4f8b-b19a-da3bce18b8d7 does not exist
JavaScript error: resource://gre/modules/PushDB.jsm, line 414: Error: Record 0fc4cbcc-cb21-4f8b-b19a-da3bce18b8d7 does not exist
{}
1578068239451 Sync.Service DEBUG User-Agent: Firefox/73.0a1 (Linux x86_64) FxSync/1.75.0.20191217161753.desktop
1578068239451 Sync.Service INFO Starting sync at 2020-01-03 13:17:19 in browser session 06Tm6orSJVql
1578068239451 Sync.Service DEBUG In sync: should login.
1578068239452 Sync.Service INFO User logged in successfully - verifying login.
```
Expected results:
No errors. Thanks!
|
P3
|
RESOLVED
|
INCOMPLETE
|
2020-01-03 19:35:41+00:00
|
2020-10-09 03:10:06+00:00
| 487 | 3 |
1607016
|
Cannot select existing tags when saving to pocket list
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
Click "Save to Pocket" arrow icon in address bar. Enter text in field "Add tags".
Actual results:
I can type in a new tag normally....however....what if the tag already exists?
Expected results:
In previous versions of Firefox, when entering text in field, the application would locate previously created tags and allow you to select the tag (thereby avoiding duplicate tag creation). This function is no longer working. When i type in a tag name, Firefox no longer presents a list possible matches from existing tags
|
Cannot select existing tags when saving to pocket list User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
Click "Save to Pocket" arrow icon in address bar. Enter text in field "Add tags".
Actual results:
I can type in a new tag normally....however....what if the tag already exists?
Expected results:
In previous versions of Firefox, when entering text in field, the application would locate previously created tags and allow you to select the tag (thereby avoiding duplicate tag creation). This function is no longer working. When i type in a tag name, Firefox no longer presents a list possible matches from existing tags
|
P2
|
RESOLVED
|
WONTFIX
|
2020-01-04 15:17:13+00:00
|
2021-04-05 15:22:23+00:00
| 172 | 2 |
1607022
|
Extension recommendation on YouTube despite the fact that I disabled these recommendations
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Extension recommendations appear sometimes (once a day?) on YouTube despite the fact that I disabled these recommendations.
Actual results:
I saw extension recommendation.
Expected results:
There have to be no extension recommendations.
|
Extension recommendation on YouTube despite the fact that I disabled these recommendations User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Extension recommendations appear sometimes (once a day?) on YouTube despite the fact that I disabled these recommendations.
Actual results:
I saw extension recommendation.
Expected results:
There have to be no extension recommendations.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-04 16:19:44+00:00
|
2020-01-14 13:14:01+00:00
| 100 | 1 |
1607028
|
tab-crash page needs Submit button or label
|
In Firefox 71.0, I visited a certain Web page. In a few seconds, the page crashed the tab, although not the whole browser. The tab replaced the downloaded page with a page saying, near the top, "Gah. Your tab just crashed."/"We can help!" and titled (in the tab and the tab's tooltip) "Tab crash reporter". I wanted to report the crash. The only two buttons FF offered said "Restore This Tab" and "Close Tab". It's not clear which button reports the crash; both are plausible. While "Send an automated crash report so we can fix issues like this." when checkmarked (which it is by default) would seem to mean that either button would send the report, because it says "automated" whereas clicking the button implies manually rather than automatically, it seems that the checkmark applies only to future crashes. I clicked to restore, which did not confirm a submission or its receipt, so I still don't know if Mozilla got the report. (I suppose I could have revisited the page, gotten another crash, and then clicked the other button and then I could assume that Mozilla got the report one way or the other, but the reason for a crash may lead us to hesitate to visit a page too often given a risk, e.g., if hosting malware.)
(Note: The page that caused the crash in FF 71.0 on Fedora 31 did not cause it with FF 71.0 on Ubuntu 18.04.3 LTS and the owner of the page said they set up Fedora and FF on a virtual machine and had no problem, so I'm not pointing to the page causing the crash on one machine (although on different networks) (probably not reproducible by most other people) but to FF's response.)
FF's page did not have its own URL. The URL was that of the page producing the crash.
Suggestion: Edit the label on whichever button we should use to add "and Submit" or add a dedicated Submit button (preferably with confirmation but even just the button would be useful).
|
tab-crash page needs Submit button or label In Firefox 71.0, I visited a certain Web page. In a few seconds, the page crashed the tab, although not the whole browser. The tab replaced the downloaded page with a page saying, near the top, "Gah. Your tab just crashed."/"We can help!" and titled (in the tab and the tab's tooltip) "Tab crash reporter". I wanted to report the crash. The only two buttons FF offered said "Restore This Tab" and "Close Tab". It's not clear which button reports the crash; both are plausible. While "Send an automated crash report so we can fix issues like this." when checkmarked (which it is by default) would seem to mean that either button would send the report, because it says "automated" whereas clicking the button implies manually rather than automatically, it seems that the checkmark applies only to future crashes. I clicked to restore, which did not confirm a submission or its receipt, so I still don't know if Mozilla got the report. (I suppose I could have revisited the page, gotten another crash, and then clicked the other button and then I could assume that Mozilla got the report one way or the other, but the reason for a crash may lead us to hesitate to visit a page too often given a risk, e.g., if hosting malware.)
(Note: The page that caused the crash in FF 71.0 on Fedora 31 did not cause it with FF 71.0 on Ubuntu 18.04.3 LTS and the owner of the page said they set up Fedora and FF on a virtual machine and had no problem, so I'm not pointing to the page causing the crash on one machine (although on different networks) (probably not reproducible by most other people) but to FF's response.)
FF's page did not have its own URL. The URL was that of the page producing the crash.
Suggestion: Edit the label on whichever button we should use to add "and Submit" or add a dedicated Submit button (preferably with confirmation but even just the button would be useful).
|
P5
|
UNCONFIRMED
|
2020-01-04 18:33:19+00:00
|
2023-03-06 23:02:10+00:00
| 466 | 5 |
|
1607160
|
Maximizing window after bookmarking causes address bar to consume toolbar and trigger overflow
|
STR:
1. Click the bookmark star button.
2. With the bookmark panel still open, maximize the window.
The address bar fills the toolbar and the toolbar items overflow. Happens when the window is resized during the bookmarking animation which starts immediately after the bookmark panel being closed. The library icon may also float in an odd location until the bookmarking animation is finished.
After animation completes the address bar can be corrected by re-maximizing or resizing the window larger than the original size when the problem occurred.
Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ac5fc1e491a2bb5481d47247bea3c2b22318001c&tochange=517c9efa9592ad0c103ec2542e4bc7fcaf06c505
Regressed by Bug 1580538.
|
Maximizing window after bookmarking causes address bar to consume toolbar and trigger overflow STR:
1. Click the bookmark star button.
2. With the bookmark panel still open, maximize the window.
The address bar fills the toolbar and the toolbar items overflow. Happens when the window is resized during the bookmarking animation which starts immediately after the bookmark panel being closed. The library icon may also float in an odd location until the bookmarking animation is finished.
After animation completes the address bar can be corrected by re-maximizing or resizing the window larger than the original size when the problem occurred.
Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ac5fc1e491a2bb5481d47247bea3c2b22318001c&tochange=517c9efa9592ad0c103ec2542e4bc7fcaf06c505
Regressed by Bug 1580538.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-06 10:17:08+00:00
|
2020-01-23 08:46:31+00:00
| 232 | 1 |
1607185
|
The card context menus from the "Recommended by Pocket" and "Highlights" sections are not fully visible if the browser is horizontally resized
|
**[Affected versions]:**
- Firefox Nightly 73.0a1 - Build ID: 20200106092427
**[Affected Platforms]:**
- Windows 10 x64
- Mac 10.15.2
- Ubuntu 18.04 x64
**[Prerequisites]:**
- Have a Firefox profile with the "browser.search.region" pref set to "US" in the "about:config" page.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab and hover the "Recommended by Pocket" card displayed in the third position.
3. Click the menu button displayed in the top-right part of the card.
4. Resize the browser horizontally to 75% and observe the displayed context menu.
**[Expected result]:**
- All the context menu elements are correctly displayed and fully visible.
**[Actual result]:**
- The context menu is not fully visible.
**[Notes]:**
- This issue is reproducible with any card from the "Recommended by Pocket" section.
- This issue is also reproducible with the card context menus from the "Highlights" section.
- Attached a screen recording of the issue.
|
The card context menus from the "Recommended by Pocket" and "Highlights" sections are not fully visible if the browser is horizontally resized **[Affected versions]:**
- Firefox Nightly 73.0a1 - Build ID: 20200106092427
**[Affected Platforms]:**
- Windows 10 x64
- Mac 10.15.2
- Ubuntu 18.04 x64
**[Prerequisites]:**
- Have a Firefox profile with the "browser.search.region" pref set to "US" in the "about:config" page.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab and hover the "Recommended by Pocket" card displayed in the third position.
3. Click the menu button displayed in the top-right part of the card.
4. Resize the browser horizontally to 75% and observe the displayed context menu.
**[Expected result]:**
- All the context menu elements are correctly displayed and fully visible.
**[Actual result]:**
- The context menu is not fully visible.
**[Notes]:**
- This issue is reproducible with any card from the "Recommended by Pocket" section.
- This issue is also reproducible with the card context menus from the "Highlights" section.
- Attached a screen recording of the issue.
|
P3
|
NEW
|
2020-01-06 12:48:50+00:00
|
2024-02-26 12:20:47+00:00
| 312 | 3 |
|
1607387
|
Session is not restored
|
I'm consistently seeing a trivial (but annoying) issue on a mac machine: session doesn't get restored, FF always start with a new fresh session. That, despite the "Resource previous session" clearly enabled.
|
Session is not restored I'm consistently seeing a trivial (but annoying) issue on a mac machine: session doesn't get restored, FF always start with a new fresh session. That, despite the "Resource previous session" clearly enabled.
|
P3
|
RESOLVED
|
WORKSFORME
|
2020-01-07 03:35:28+00:00
|
2024-01-25 12:33:00+00:00
| 51 | 3 |
1607410
|
Re-enable tracking protection messages
|
Need to bring back the TP messages disabled by bug 1603483.
The trigger rename bug 1604563 did not make it to 72 so the messages might only be re-enabled for 73+ depending on how the profiler data looks like for 72.
|
Re-enable tracking protection messages Need to bring back the TP messages disabled by bug 1603483.
The trigger rename bug 1604563 did not make it to 72 so the messages might only be re-enabled for 73+ depending on how the profiler data looks like for 72.
|
P1
|
RESOLVED
|
FIXED
|
2020-01-07 09:14:34+00:00
|
2020-02-18 11:02:05+00:00
| 61 | 1 |
1607441
|
Pinned tabs order are reversed every time Nightly is restarted
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Build ID: 20200107095722
### Steps to reproduce
1. In a new profile, pin 2 or more tabs, preferably with different favicons to differentiate them easier.
2. Restart, or close & reopen Nightly.
### Actual result
Order for pinned tabs are reversed.
### Expected result
Order remains unchanged.
This is regressed by bug 1242912. Is bug 1606633 related?
|
Pinned tabs order are reversed every time Nightly is restarted User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Build ID: 20200107095722
### Steps to reproduce
1. In a new profile, pin 2 or more tabs, preferably with different favicons to differentiate them easier.
2. Restart, or close & reopen Nightly.
### Actual result
Order for pinned tabs are reversed.
### Expected result
Order remains unchanged.
This is regressed by bug 1242912. Is bug 1606633 related?
|
P1
|
VERIFIED
|
FIXED
|
2020-01-07 13:33:51+00:00
|
2020-02-18 15:40:30+00:00
| 147 | 1 |
1607617
|
Session Restore Buttons are Misaligned
|
To reproduce, go to about:sessionrestore in trunk.
The buttons for restore/start new are aligned to the far left, and vertically stacked. The issue is purely aesthetic.
|
Session Restore Buttons are Misaligned To reproduce, go to about:sessionrestore in trunk.
The buttons for restore/start new are aligned to the far left, and vertically stacked. The issue is purely aesthetic.
|
P2
|
RESOLVED
|
DUPLICATE
|
2020-01-07 23:28:59+00:00
|
2020-01-14 19:35:18+00:00
| 46 | 2 |
1607630
|
pdf.js occasionally shows incorrect symbols until page is refreshed
|
I don't have easy steps to reliably reproduce this but I probably see it on average after about 2-3 hours of PDF reading. The issue is that some symbols (I believe it is "some fonts") display incorrectly in the document I'm reading. Reloading the page immediately fixes the symbols. I've attached a screen shot of a page, before and after reloading the page. Check, for example, the second line, where Prt(A) was incorrectly rendered as \eta\phi(A). Some potentially useful points (I haven't confirmed if they are important):
1. I am reading this document from a file on my hard drive, not the web.
2. The document in the images is freely available here [1].
3. I am currently on the 01-05-20 nightly build on Windows.
4. I read a lot of PDFs. I'd say that this popped up, roughly, sometime in the last month.
5. I have gfx.canvas.remote set to true. I don't know if this still on in nightly by default or not. This is part of Bob Owen's project to move 2D canvas operations out of the content process. I set that to true many months ago but, again, just recently started seeing this.
6. Reloading the page seems to fix it every time. Other things, like changing tabs or switching window focus, seem to have no effect on the bug.
7. I haven't seen the issue when just opening a document, but this may be a coincidence. I have always come across it after scrolling through the document.
[1] http://math.mit.edu/~dspivak/teaching/sp18/7Sketches.pdf
|
pdf.js occasionally shows incorrect symbols until page is refreshed I don't have easy steps to reliably reproduce this but I probably see it on average after about 2-3 hours of PDF reading. The issue is that some symbols (I believe it is "some fonts") display incorrectly in the document I'm reading. Reloading the page immediately fixes the symbols. I've attached a screen shot of a page, before and after reloading the page. Check, for example, the second line, where Prt(A) was incorrectly rendered as \eta\phi(A). Some potentially useful points (I haven't confirmed if they are important):
1. I am reading this document from a file on my hard drive, not the web.
2. The document in the images is freely available here [1].
3. I am currently on the 01-05-20 nightly build on Windows.
4. I read a lot of PDFs. I'd say that this popped up, roughly, sometime in the last month.
5. I have gfx.canvas.remote set to true. I don't know if this still on in nightly by default or not. This is part of Bob Owen's project to move 2D canvas operations out of the content process. I set that to true many months ago but, again, just recently started seeing this.
6. Reloading the page seems to fix it every time. Other things, like changing tabs or switching window focus, seem to have no effect on the bug.
7. I haven't seen the issue when just opening a document, but this may be a coincidence. I have always come across it after scrolling through the document.
[1] http://math.mit.edu/~dspivak/teaching/sp18/7Sketches.pdf
|
P1
|
RESOLVED
|
FIXED
|
2020-01-08 00:23:49+00:00
|
2020-05-20 12:25:15+00:00
| 391 | 1 |
1607677
|
Black square appears on first window Hamburger’s Menu when a drop down is presented on the second window
|
*Affected versions*
* 74.0a1 (20200107215758)
* 73.0b2 (20200107212705)
* 72.0.1 (20200107212822)
* 68.4.1esr (20200107212959)
*Affected platforms*
* Windows 10x64
* Ubuntu 18.04
* macOS 10.15
*Steps to reproduce*
1. Open Firefox and open a new window.
2. Go to about:addons and add a random extension from Recommended Extensions.
3. Observe the hamburger menu from the first window as long as the Manage your addons dropdown menu is active.
*Expected result*
* No visual glitches presented on the first Window.
*Actual result*
* Black (or white depending on the theme) square appears on the hamburger menu as long as a drop-down is active on the second one.
*Regression Range*
* Reproducible with Firefox 71.0a1 (20191009213914). I will search for one ASAP.
*Notes*
* Attached a screen recording with the issue.
* The issue is reproducible on the first window as long as a dropdown from the hamburger menu is presented on the second one.
|
Black square appears on first window Hamburger’s Menu when a drop down is presented on the second window *Affected versions*
* 74.0a1 (20200107215758)
* 73.0b2 (20200107212705)
* 72.0.1 (20200107212822)
* 68.4.1esr (20200107212959)
*Affected platforms*
* Windows 10x64
* Ubuntu 18.04
* macOS 10.15
*Steps to reproduce*
1. Open Firefox and open a new window.
2. Go to about:addons and add a random extension from Recommended Extensions.
3. Observe the hamburger menu from the first window as long as the Manage your addons dropdown menu is active.
*Expected result*
* No visual glitches presented on the first Window.
*Actual result*
* Black (or white depending on the theme) square appears on the hamburger menu as long as a drop-down is active on the second one.
*Regression Range*
* Reproducible with Firefox 71.0a1 (20191009213914). I will search for one ASAP.
*Notes*
* Attached a screen recording with the issue.
* The issue is reproducible on the first window as long as a dropdown from the hamburger menu is presented on the second one.
|
P3
|
NEW
|
2020-01-08 08:54:08+00:00
|
2022-10-10 19:29:16+00:00
| 292 | 3 |
|
1607732
|
about:certificate should be delisted from about:about and URL suggestions
|
As I recall in the past for about: pages which are useless when visited directly we've delisted them from about:about (and removed them from URL suggestions). One example being about:reader which is only useful when handed a URL.
We should do this with about:certificate
|
about:certificate should be delisted from about:about and URL suggestions As I recall in the past for about: pages which are useless when visited directly we've delisted them from about:about (and removed them from URL suggestions). One example being about:reader which is only useful when handed a URL.
We should do this with about:certificate
|
P5
|
RESOLVED
|
WORKSFORME
|
2020-01-08 12:55:36+00:00
|
2020-12-04 10:17:01+00:00
| 79 | 5 |
1607797
|
Behaviour of multiple restricting providers is undefined
|
When Search Tips land, we'll have two restricting providers in conflict: Top Sites and Search Tips. We need to figure out how these two should interact, allowing them both to be shown at the appropriate times.
|
Behaviour of multiple restricting providers is undefined When Search Tips land, we'll have two restricting providers in conflict: Top Sites and Search Tips. We need to figure out how these two should interact, allowing them both to be shown at the appropriate times.
|
P2
|
RESOLVED
|
WONTFIX
|
2020-01-08 15:41:09+00:00
|
2020-01-22 22:54:33+00:00
| 53 | 2 |
1607810
|
Drag & drop a link onto Bookmarks menu/Bookmarks widget broken after exiting DOM fullscreen
|
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Firefox 72.0 and 71 bookmarks save problem.
Actual results:
The full screen resets everything as in: https://bugzilla.mozilla.org/show_bug.cgi?id=1601706
As in this case.
Expected results:
Everything works when Firefox restarts. No error except scroll problems.
Until we get into full screen.
Everything is shown in the video.
I tried on 2 computers.
|
Drag & drop a link onto Bookmarks menu/Bookmarks widget broken after exiting DOM fullscreen User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Firefox 72.0 and 71 bookmarks save problem.
Actual results:
The full screen resets everything as in: https://bugzilla.mozilla.org/show_bug.cgi?id=1601706
As in this case.
Expected results:
Everything works when Firefox restarts. No error except scroll problems.
Until we get into full screen.
Everything is shown in the video.
I tried on 2 computers.
|
P2
|
RESOLVED
|
FIXED
|
2020-01-08 16:10:32+00:00
|
2020-02-03 18:52:47+00:00
| 163 | 2 |
1607889
|
Intermittent TV toolkit/components/normandy/test/browser/browser_RecipeRunner.js | only recipes with compatible capabilities should be executed - [] deepEqual [[{"name":"match","filter_expression":"true","capabilities":["compatible"]}]] - JS frame :: chro
|
**Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=284052222&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Kt-WOaowRAqhWBHyJCAQvw/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Kt-WOaowRAqhWBHyJCAQvw/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
---
|
Intermittent TV toolkit/components/normandy/test/browser/browser_RecipeRunner.js | only recipes with compatible capabilities should be executed - [] deepEqual [[{"name":"match","filter_expression":"true","capabilities":["compatible"]}]] - JS frame :: chro **Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=284052222&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Kt-WOaowRAqhWBHyJCAQvw/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Kt-WOaowRAqhWBHyJCAQvw/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
---
|
P5
|
RESOLVED
|
INCOMPLETE
|
2020-01-08 19:59:57+00:00
|
2020-02-04 17:02:58+00:00
| 337 | 5 |
1607892
|
Intermittent TV browser/components/customizableui/test/browser_lwt_telemetry.js | Get more opened AMO - Got about:blank, expected about:blank#getMoreThemes
|
**Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=284062889&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GVzNx9m2Qw-mNK7okcoQzQ/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GVzNx9m2Qw-mNK7okcoQzQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
---
|
Intermittent TV browser/components/customizableui/test/browser_lwt_telemetry.js | Get more opened AMO - Got about:blank, expected about:blank#getMoreThemes **Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=284062889&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GVzNx9m2Qw-mNK7okcoQzQ/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GVzNx9m2Qw-mNK7okcoQzQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
---
|
P5
|
RESOLVED
|
INCOMPLETE
|
2020-01-08 20:01:05+00:00
|
2020-02-04 17:03:01+00:00
| 311 | 5 |
1607894
|
Intermittent normandy/test/browser/browser_RecipeRunner.js | recipes/all recipes with matching should have their signature verified - [] deepEqual [[{"name":"match","action":"matchAction","filter_expression":"true"},{"signature":"abc"},"
|
**Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=284050452&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Gky4q57EQbeyVZivuqTkwg/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Gky4q57EQbeyVZivuqTkwg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
---
|
Intermittent normandy/test/browser/browser_RecipeRunner.js | recipes/all recipes with matching should have their signature verified - [] deepEqual [[{"name":"match","action":"matchAction","filter_expression":"true"},{"signature":"abc"}," **Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=284050452&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Gky4q57EQbeyVZivuqTkwg/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Gky4q57EQbeyVZivuqTkwg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
---
|
P5
|
RESOLVED
|
INCOMPLETE
|
2020-01-08 20:04:14+00:00
|
2024-10-08 05:11:28+00:00
| 334 | 5 |
1607925
|
{protections Report] Manage Protections button is incorrectly visible
|
The manage Protections button in the ETP card should only be visible when a user is in custom and has turned off all protections.
|
{protections Report] Manage Protections button is incorrectly visible The manage Protections button in the ETP card should only be visible when a user is in custom and has turned off all protections.
|
P1
|
RESOLVED
|
FIXED
|
2020-01-08 21:59:11+00:00
|
2020-02-12 15:42:33+00:00
| 38 | 1 |
1607937
|
ExtensionSettings Policy's blocked_install_message does not always display
|
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
1. Configure the ExtensionSettings policiy by way of the policies.json file in the C:\Program Files\Mozilla Firefox\distribution\ folder so that all extensions are blocked by default.
"ExtensionSettings": {
"*": {
"blocked_install_message": "Custom Message Still Needs to Go Here...",
"install_sources": ["https://addons.mozilla.org/"],
"installation_mode": "blocked",
"allowed_types": ["extension", "theme", "dictionary", "langpack"]
}
2. Open about:addons and attempt to install an extension such Facebook Container.
Actual results:
Error message "Firefox prevented this site from asking you to install software on your computer." received. The installation was blocked, but our custom message was not displayed to alert the employee who blocked the installation and why.
Expected results:
Error message should have been the custom one that was specified in the policy. If attempting the installation from https://addons.mozilla.org/en-US/firefox/addon/facebook-container/?src=search, I receive the message I was expecting.
"Facebook Container (@contain-facebook) is blocked by your system administrator. Custom Message Still Needs to Go Here...".
|
ExtensionSettings Policy's blocked_install_message does not always display User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
1. Configure the ExtensionSettings policiy by way of the policies.json file in the C:\Program Files\Mozilla Firefox\distribution\ folder so that all extensions are blocked by default.
"ExtensionSettings": {
"*": {
"blocked_install_message": "Custom Message Still Needs to Go Here...",
"install_sources": ["https://addons.mozilla.org/"],
"installation_mode": "blocked",
"allowed_types": ["extension", "theme", "dictionary", "langpack"]
}
2. Open about:addons and attempt to install an extension such Facebook Container.
Actual results:
Error message "Firefox prevented this site from asking you to install software on your computer." received. The installation was blocked, but our custom message was not displayed to alert the employee who blocked the installation and why.
Expected results:
Error message should have been the custom one that was specified in the policy. If attempting the installation from https://addons.mozilla.org/en-US/firefox/addon/facebook-container/?src=search, I receive the message I was expecting.
"Facebook Container (@contain-facebook) is blocked by your system administrator. Custom Message Still Needs to Go Here...".
|
P1
|
VERIFIED
|
FIXED
|
2020-01-08 22:31:50+00:00
|
2020-01-28 13:39:03+00:00
| 365 | 1 |
1607941
|
Intermittent ccov toolkit/components/normandy/test/browser/browser_RecipeRunner.js | run() does not run again from timer - Got 3, expected 2
|
**Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=284091996&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CctXUP1MRFan_fQwMr578A/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CctXUP1MRFan_fQwMr578A/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
---
|
Intermittent ccov toolkit/components/normandy/test/browser/browser_RecipeRunner.js | run() does not run again from timer - Got 3, expected 2 **Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=284091996&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CctXUP1MRFan_fQwMr578A/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CctXUP1MRFan_fQwMr578A/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
---
|
P5
|
RESOLVED
|
INCOMPLETE
|
2020-01-08 22:47:00+00:00
|
2020-02-18 17:00:14+00:00
| 298 | 5 |
1607977
|
Intermittent TV toolkit/components/normandy/test/browser/browser_RecipeRunner.js | RecipeRunner should report uptake telemetry - [["success"],["sign_error"]] deepEqual [["sign_error"]] - JS frame :: chrome://mochitests/content/browser/toolkit/components/
|
**Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=284115980&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/We-mddM-Q12r4tI5GCvVsQ/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/We-mddM-Q12r4tI5GCvVsQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
---
|
Intermittent TV toolkit/components/normandy/test/browser/browser_RecipeRunner.js | RecipeRunner should report uptake telemetry - [["success"],["sign_error"]] deepEqual [["sign_error"]] - JS frame :: chrome://mochitests/content/browser/toolkit/components/ **Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=284115980&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/We-mddM-Q12r4tI5GCvVsQ/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/We-mddM-Q12r4tI5GCvVsQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
---
|
P5
|
RESOLVED
|
INCOMPLETE
|
2020-01-09 00:51:59+00:00
|
2020-02-18 17:00:16+00:00
| 337 | 5 |
1608011
|
Sync telemetry isn't reporting the syncNodeType
|
Because I neglected to extract it from the tokenserver response :(
[Tracking Requested - why for this release]:
We really want telemetry which indicates what if a user is on the "new" sync storage node.
|
Sync telemetry isn't reporting the syncNodeType Because I neglected to extract it from the tokenserver response :(
[Tracking Requested - why for this release]:
We really want telemetry which indicates what if a user is on the "new" sync storage node.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-09 05:53:24+00:00
|
2020-01-14 02:57:17+00:00
| 61 | 1 |
1608036
|
Loss of all pinned tabs except one
|
STR:
Restart firefox. Observe all pinned tabs are gone except one.
Very likely a regression from bug 1607441 which tried to fix the order reversal.
|
Loss of all pinned tabs except one STR:
Restart firefox. Observe all pinned tabs are gone except one.
Very likely a regression from bug 1607441 which tried to fix the order reversal.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-09 08:43:44+00:00
|
2020-02-19 07:27:53+00:00
| 46 | 1 |
1608106
|
[macOS] Disabled drag space label (ie when title bar is enabled) inside Customize page is barely visible with dark OS theme
|
[Affected versions]:
- 72.0.1
- 73.0b2
- 74.0a1 (2020-01-07)
[Affected platforms]:
- macOS 10.14
- macOS 10.15
[Steps to reproduce]:
1. Open the Customize page (Menu - Customize)
2. Check the Title Bar options
[Expected result]:
- Drag Space options turns inactive, no visual issue can be observed
[Actual result]:
- Drag Space options turns inactive, but it is hardly visible
[Regression range]:
- I will provide one asap
[Additional notes]:
- Issue not reproducible with dark mode on Windows
|
[macOS] Disabled drag space label (ie when title bar is enabled) inside Customize page is barely visible with dark OS theme [Affected versions]:
- 72.0.1
- 73.0b2
- 74.0a1 (2020-01-07)
[Affected platforms]:
- macOS 10.14
- macOS 10.15
[Steps to reproduce]:
1. Open the Customize page (Menu - Customize)
2. Check the Title Bar options
[Expected result]:
- Drag Space options turns inactive, no visual issue can be observed
[Actual result]:
- Drag Space options turns inactive, but it is hardly visible
[Regression range]:
- I will provide one asap
[Additional notes]:
- Issue not reproducible with dark mode on Windows
|
P3
|
VERIFIED
|
FIXED
|
2020-01-09 14:13:08+00:00
|
2020-01-17 15:46:40+00:00
| 164 | 3 |
1608147
|
New windows no longer created with dark page when set to blank in dark mode.
|
STR:
1. Set "Homepage and new windows" and "New tabs" to "Blank Page" or alternatively set the following:
`browser.newtabpage.enabled = false`
`browser.startup.homepage = about:blank`
2. Enable OS dark more or set `ui.systemUsesDarkTheme = 1`.
3. Create a new window.
Expected:
Page content is dark.
Actual:
Page content is white.
Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e3e2c1d7478e450e2b32c85c416ccf70f9de56d3&tochange=379a82fe25d90e023c9bbe1f3437d82c6c2914ff
Regressed by Bug 1599544.
|
New windows no longer created with dark page when set to blank in dark mode. STR:
1. Set "Homepage and new windows" and "New tabs" to "Blank Page" or alternatively set the following:
`browser.newtabpage.enabled = false`
`browser.startup.homepage = about:blank`
2. Enable OS dark more or set `ui.systemUsesDarkTheme = 1`.
3. Create a new window.
Expected:
Page content is dark.
Actual:
Page content is white.
Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e3e2c1d7478e450e2b32c85c416ccf70f9de56d3&tochange=379a82fe25d90e023c9bbe1f3437d82c6c2914ff
Regressed by Bug 1599544.
|
P3
|
NEW
|
2020-01-09 16:04:16+00:00
|
2022-10-11 23:49:29+00:00
| 216 | 3 |
|
1608169
|
Investigate megabar expansion animation sluggishness
|
Verdi and I recently noticed that the megabar visibly shrinks a bit before it expands. This seems to have looked better some time ago so this is possibly a regression.
|
Investigate megabar expansion animation sluggishness Verdi and I recently noticed that the megabar visibly shrinks a bit before it expands. This seems to have looked better some time ago so this is possibly a regression.
|
P2
|
VERIFIED
|
FIXED
|
2020-01-09 16:59:28+00:00
|
2021-12-30 05:55:22+00:00
| 45 | 2 |
1608230
|
Status Bar spoofing using URL encoding and `@`
|
Hello,
When we move mouse on a link, its href(of that anchor tag) is shown in status bar which is used for anti-phishing. But we can spoof that status bar and can redirect vicitm to an external malicious website instead of shown website. This behavior may lead to phishing attacks.
Steps to reproduce:
1. Use following as href of an anchor tag:
https://www.facebook.com%2Flogin%3Ftestx=ZW5o%26dummy2=amJuaDZhbU42ZUc1cWRtdHVlbXA0YTJwMmJtcDRlbXR1ZG1wcmVuaHFhMjUyYW10NGJucHJkbTVxYTNodWFuWnJibnA0YW10MmJtdHVlR3R1ZG10dWVtcHJkbTVyYm5oNmRtdHVhM2g2Ym5acmJtcHJlbmh1ZG5wNGRucDRZMjU0ZW1wamVuaHVhblpyYm5wcWVHdHFkbTVxZUhwcmJuWnFhM3A0YW10dWRtcHJlRzU2YTNadWFtd[@example.com/]bZW5oamJuaDZhbU42ZUc1cWRtdHVlbXA0YTJwMmJtcDRlbmhqYm5oNmFtTjZlRzVxZG10dWVtcDRhMnAyYm1wNGVtdHVkbXByZW5ocWEyNTJhbXQ0Ym5wcmRtNXFhM2h1YW5acmJucDRhbXQyYm10dWVHdHVkbXR1ZW1wcmRtNXJibmg2ZG10dWEzaDZiblpyYm1wcmVuaHVkbnA0ZWc9PQ==
2. Move mouse on that link
3. In status bar, https://www.facebook.com/login?testx=... is shown but click on that link
4. You will be redirected to https://example.com without any warning
5. Done
I have attached a PoC HTML file. `example.com` is not shown anywhere in status bar.
Suggested Fix:
As url redirects to example.com so status bar should show `example.com/...`
Firefox version : 72.0.1
OS : Windows 10 (64 bit)
|
Status Bar spoofing using URL encoding and `@` Hello,
When we move mouse on a link, its href(of that anchor tag) is shown in status bar which is used for anti-phishing. But we can spoof that status bar and can redirect vicitm to an external malicious website instead of shown website. This behavior may lead to phishing attacks.
Steps to reproduce:
1. Use following as href of an anchor tag:
https://www.facebook.com%2Flogin%3Ftestx=ZW5o%26dummy2=amJuaDZhbU42ZUc1cWRtdHVlbXA0YTJwMmJtcDRlbXR1ZG1wcmVuaHFhMjUyYW10NGJucHJkbTVxYTNodWFuWnJibnA0YW10MmJtdHVlR3R1ZG10dWVtcHJkbTVyYm5oNmRtdHVhM2g2Ym5acmJtcHJlbmh1ZG5wNGRucDRZMjU0ZW1wamVuaHVhblpyYm5wcWVHdHFkbTVxZUhwcmJuWnFhM3A0YW10dWRtcHJlRzU2YTNadWFtd[@example.com/]bZW5oamJuaDZhbU42ZUc1cWRtdHVlbXA0YTJwMmJtcDRlbmhqYm5oNmFtTjZlRzVxZG10dWVtcDRhMnAyYm1wNGVtdHVkbXByZW5ocWEyNTJhbXQ0Ym5wcmRtNXFhM2h1YW5acmJucDRhbXQyYm10dWVHdHVkbXR1ZW1wcmRtNXJibmg2ZG10dWEzaDZiblpyYm1wcmVuaHVkbnA0ZWc9PQ==
2. Move mouse on that link
3. In status bar, https://www.facebook.com/login?testx=... is shown but click on that link
4. You will be redirected to https://example.com without any warning
5. Done
I have attached a PoC HTML file. `example.com` is not shown anywhere in status bar.
Suggested Fix:
As url redirects to example.com so status bar should show `example.com/...`
Firefox version : 72.0.1
OS : Windows 10 (64 bit)
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-01-09 19:20:06+00:00
|
2024-05-30 17:06:14+00:00
| 268 | 3 |
1608348
|
Default Zoom Text Only option set in about:preferences does not work
|
#### Affected versions:
Nightly 74.0a1 (2020-01-10), Beta 73.0b3
#### Affected platforms:
ALL
#### Steps:
1. Launch Firefox with a new profile and go to about:preferences.
2. Under General, go to Zoom section, check the "Zoom text only" checkbox and select any value from the "Default zoom" dropdown.
3. Access any website that contains text strings and photos.
#### Actual result:
The default zoom level is applied to entire content of the page.
#### Expected result:
Default zoom level should be applied just for text only.
|
Default Zoom Text Only option set in about:preferences does not work #### Affected versions:
Nightly 74.0a1 (2020-01-10), Beta 73.0b3
#### Affected platforms:
ALL
#### Steps:
1. Launch Firefox with a new profile and go to about:preferences.
2. Under General, go to Zoom section, check the "Zoom text only" checkbox and select any value from the "Default zoom" dropdown.
3. Access any website that contains text strings and photos.
#### Actual result:
The default zoom level is applied to entire content of the page.
#### Expected result:
Default zoom level should be applied just for text only.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-10 08:06:01+00:00
|
2022-09-28 10:07:07+00:00
| 154 | 1 |
1608545
|
Opening a new tab in the same container doesn't work
|
In the last couple of days when I am in a non default container and I open a new tab using Cmd-Click on the new tab button (+) the tab gets the correct container indicator, but the page opens with the credentials in my default container. My typical use case is with GDocs, but I notice it with other sites, too.
|
Opening a new tab in the same container doesn't work In the last couple of days when I am in a non default container and I open a new tab using Cmd-Click on the new tab button (+) the tab gets the correct container indicator, but the page opens with the credentials in my default container. My typical use case is with GDocs, but I notice it with other sites, too.
|
P2
|
RESOLVED
|
FIXED
|
2020-01-10 20:46:58+00:00
|
2020-01-19 18:03:08+00:00
| 87 | 2 |
1608554
|
Firefox: Unable to initially Access on-screen Controls with the Keyboard after Changing Search Bar Settings from within a New Profile
|
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
To reproduce - this assumes that a fresh Firefox profile is being used and that NVDA 2019.2.1 is running:
1. Open Firefox, and navigate to Tools/Options - ensure that NVDA's Focus Mode is enabled at this point
2. Open the "Search" panel, and either tab or shift + tab out of the Options in this panel and to the other visible controls on the screen - including the address bar and other tab-able items. The idea here is to prove that NVDA is able to navigate to these at this stage
3. Navigate back to the available options from within the Search panel, and in the selection of radio buttons that controls how the search box is selected, change this selection to "Add search bar in toolbar"
4. Finally, as before, either tab or shift + tab out of the Search settings, and into the on-screen controls
Actual results:
After changing this setting to force the Search Bar to appear separately to the Address Bar, on-screen controls should still be tab-able - which isn't initially the case after changing the above setting. It's worth noting that if Firefox is then closed and the same profile re-opened, these controls can then be tabbed to as expected. It's also worth mentioning that this isn't a new bug as such, and has been present since at least Firefox 71.
Expected results:
N/A
|
Firefox: Unable to initially Access on-screen Controls with the Keyboard after Changing Search Bar Settings from within a New Profile User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
To reproduce - this assumes that a fresh Firefox profile is being used and that NVDA 2019.2.1 is running:
1. Open Firefox, and navigate to Tools/Options - ensure that NVDA's Focus Mode is enabled at this point
2. Open the "Search" panel, and either tab or shift + tab out of the Options in this panel and to the other visible controls on the screen - including the address bar and other tab-able items. The idea here is to prove that NVDA is able to navigate to these at this stage
3. Navigate back to the available options from within the Search panel, and in the selection of radio buttons that controls how the search box is selected, change this selection to "Add search bar in toolbar"
4. Finally, as before, either tab or shift + tab out of the Search settings, and into the on-screen controls
Actual results:
After changing this setting to force the Search Bar to appear separately to the Address Bar, on-screen controls should still be tab-able - which isn't initially the case after changing the above setting. It's worth noting that if Firefox is then closed and the same profile re-opened, these controls can then be tabbed to as expected. It's also worth mentioning that this isn't a new bug as such, and has been present since at least Firefox 71.
Expected results:
N/A
|
P1
|
RESOLVED
|
FIXED
|
2020-01-10 21:07:49+00:00
|
2020-03-17 07:05:43+00:00
| 371 | 1 |
1608597
|
[Nudges] Top sites will conflict with the nudges/tips experiment on 74
|
Top sites and quantumbar update1 are scheduled to ship on release in 74, if I'm not mistaken. 74 is also the final release where the nudges/tips experiment will run: https://experimenter.services.mozilla.com/experiments/search-tips-aka-nudges/
That's a problem because both top sites and nudges use restricting providers, and right now we only support one restricting provider at a time. The result is that when the experiment opens the quantumbar view to show a tip on 74, the top sites are also shown (at best) or only the top sites are shown, with no tip at all (at worst).
So we need to fix this for 74 somehow. We might fix it by fixing bug 1607797, and if so, this bug is just a dupe of that bug. I can also imagine a wallpaper/quick fix that isn't blocked on fixing that larger bug.
|
[Nudges] Top sites will conflict with the nudges/tips experiment on 74 Top sites and quantumbar update1 are scheduled to ship on release in 74, if I'm not mistaken. 74 is also the final release where the nudges/tips experiment will run: https://experimenter.services.mozilla.com/experiments/search-tips-aka-nudges/
That's a problem because both top sites and nudges use restricting providers, and right now we only support one restricting provider at a time. The result is that when the experiment opens the quantumbar view to show a tip on 74, the top sites are also shown (at best) or only the top sites are shown, with no tip at all (at worst).
So we need to fix this for 74 somehow. We might fix it by fixing bug 1607797, and if so, this bug is just a dupe of that bug. I can also imagine a wallpaper/quick fix that isn't blocked on fixing that larger bug.
|
P1
|
RESOLVED
|
FIXED
|
2020-01-11 00:38:37+00:00
|
2020-02-21 02:25:33+00:00
| 224 | 1 |
1608601
|
[Nudges] Urlbar input isn't cleared after clicking the redirect tip's "Okay, Got It" button
|
This is a last-minute nudges/tips bug that Harry found today. It's a problem on 72 and later versions. I don't think it's a show stopper -- we could ship the extension with it -- but I also think we should fix it. We should able to do it entirely from the add-on without landing any production code in m-c, but it will require an experiment API addition.
When the redirect tip is shown (for example on google.com), the input correctly is empty, but when you then click the tip's "Okay, Got It" button, the input's value is set to the page's URL. So you have to clear the input before you can search. It should remain empty when you click the button.
Harry found this while porting the extension in bug 1606909. The value is set to the URL by the handleRevert call here: https://searchfox.org/mozilla-central/rev/d4d6f81e0ab479cde192453bae83d5e3edfb39d6/browser/components/urlbar/UrlbarInput.jsm#615
The stack is:
_setValue (UrlbarInput.jsm#1076)
value (UrlbarInput.jsm#941)
URLBarSetURI (browser.js#3390)
handleRevert (UrlbarInput.jsm#434)
pickElement (UrlbarInput.jsm#615)
_on_mouseup (UrlbarView.jsm#1424)
handleEvent (UrlbarView.jsm#499)
|
[Nudges] Urlbar input isn't cleared after clicking the redirect tip's "Okay, Got It" button This is a last-minute nudges/tips bug that Harry found today. It's a problem on 72 and later versions. I don't think it's a show stopper -- we could ship the extension with it -- but I also think we should fix it. We should able to do it entirely from the add-on without landing any production code in m-c, but it will require an experiment API addition.
When the redirect tip is shown (for example on google.com), the input correctly is empty, but when you then click the tip's "Okay, Got It" button, the input's value is set to the page's URL. So you have to clear the input before you can search. It should remain empty when you click the button.
Harry found this while porting the extension in bug 1606909. The value is set to the URL by the handleRevert call here: https://searchfox.org/mozilla-central/rev/d4d6f81e0ab479cde192453bae83d5e3edfb39d6/browser/components/urlbar/UrlbarInput.jsm#615
The stack is:
_setValue (UrlbarInput.jsm#1076)
value (UrlbarInput.jsm#941)
URLBarSetURI (browser.js#3390)
handleRevert (UrlbarInput.jsm#434)
pickElement (UrlbarInput.jsm#615)
_on_mouseup (UrlbarView.jsm#1424)
handleEvent (UrlbarView.jsm#499)
|
P1
|
RESOLVED
|
FIXED
|
2020-01-11 01:22:18+00:00
|
2020-01-15 02:11:22+00:00
| 410 | 1 |
1608606
|
Multi-select tabs: closing tab with X button should only affect the target tab.
|
As stated by Jared [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1578131#c2), clicking on the X button of a multi-selected tab should only close that one tab to maintain parity with Chrome.
Note:
Triggering Ctrl-W should still remove the whole selection.
|
Multi-select tabs: closing tab with X button should only affect the target tab. As stated by Jared [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1578131#c2), clicking on the X button of a multi-selected tab should only close that one tab to maintain parity with Chrome.
Note:
Triggering Ctrl-W should still remove the whole selection.
|
P2
|
NEW
|
2020-01-11 02:23:00+00:00
|
2023-12-20 08:05:37+00:00
| 97 | 2 |
|
1608656
|
pocket has only one row on new pageand no option to change
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
update from firefox 71.0 to 72.0.1
Actual results:
pocket has only one row on new page and the option to change it disappered.
the value browser.newtabpage.activity-stream.topSitesRows=4 is still present in about:config
Expected results:
pocket has four rows on new page
|
pocket has only one row on new pageand no option to change User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
update from firefox 71.0 to 72.0.1
Actual results:
pocket has only one row on new page and the option to change it disappered.
the value browser.newtabpage.activity-stream.topSitesRows=4 is still present in about:config
Expected results:
pocket has four rows on new page
|
P3
|
UNCONFIRMED
|
2020-01-11 19:48:55+00:00
|
2024-01-18 22:40:59+00:00
| 134 | 3 |
|
1608687
|
Master password prompt gives the appearance of a security check, but can be bypassed once it was already unlocked
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
1. Start Firefox (with a set up Master Password)
2. User enters the master password because he is forced by Firefox to enter it once initially at start
3. User uses his browser as usual
4. Attacker opens 'about:logins' and can reveal all saved passwords
Actual results:
The prompt for masterpassword makes the appearance that the passwords within 'about:logins' are somekind of protected.
But you can without entering the masterpassword and by not clicking on the "View Password"-Buttons do the following things:
- You can search for passwords with the search field.
- You can access the javascript object from Developer Console.
- You can change type=password to type=text with Inspector to reveal plain-text passwords.
Expected results:
The prompt for master password when clicking on "Show password" gives the appearance of a security check that is obviously easy to bypass. I would have expected a different level of protection or at least not one that gives the appearance of being one.
|
Master password prompt gives the appearance of a security check, but can be bypassed once it was already unlocked User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
1. Start Firefox (with a set up Master Password)
2. User enters the master password because he is forced by Firefox to enter it once initially at start
3. User uses his browser as usual
4. Attacker opens 'about:logins' and can reveal all saved passwords
Actual results:
The prompt for masterpassword makes the appearance that the passwords within 'about:logins' are somekind of protected.
But you can without entering the masterpassword and by not clicking on the "View Password"-Buttons do the following things:
- You can search for passwords with the search field.
- You can access the javascript object from Developer Console.
- You can change type=password to type=text with Inspector to reveal plain-text passwords.
Expected results:
The prompt for master password when clicking on "Show password" gives the appearance of a security check that is obviously easy to bypass. I would have expected a different level of protection or at least not one that gives the appearance of being one.
|
P5
|
NEW
|
2020-01-12 12:40:23+00:00
|
2024-05-30 17:06:19+00:00
| 278 | 5 |
|
1608696
|
Layout for Icons of One-Click Search Engines Sometimes become messed up
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I browsed internet like a normal person.
Actual results:
It just become like this after some time of use. You can fix it by changing the engines in setting and everything goes back to normal, but after a while it become messed up again. I do not know what trigger it.
Expected results:
It should not be messed up.
|
Layout for Icons of One-Click Search Engines Sometimes become messed up User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I browsed internet like a normal person.
Actual results:
It just become like this after some time of use. You can fix it by changing the engines in setting and everything goes back to normal, but after a while it become messed up again. I do not know what trigger it.
Expected results:
It should not be messed up.
|
P3
|
NEW
|
2020-01-12 15:54:57+00:00
|
2022-10-11 23:50:05+00:00
| 129 | 3 |
|
1608739
|
Google.com keep appear in suggestion
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Type g in the location url
Actual results:
Show google.com in first place
Expected results:
Show bookmark starting with g, but not google.com !
Since i've removed google.com from search engine, since i completely disabled browsing history, why google.com keep being appear in first place when i type the g letter ?
He not come from browsing history (private mode by default) or bookmark, so, where does he come from ?
|
Google.com keep appear in suggestion User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Type g in the location url
Actual results:
Show google.com in first place
Expected results:
Show bookmark starting with g, but not google.com !
Since i've removed google.com from search engine, since i completely disabled browsing history, why google.com keep being appear in first place when i type the g letter ?
He not come from browsing history (private mode by default) or bookmark, so, where does he come from ?
|
P5
|
RESOLVED
|
INCOMPLETE
|
2020-01-13 03:07:01+00:00
|
2020-07-07 05:27:16+00:00
| 147 | 5 |
1608766
|
openViewOnFocus breaks most common pattern for quickly navigating toolbars with the keyboard
|
Bug 1603778 enabled browser.urlbar.openViewOnFocus by default in Nightly. Unfortunately, this breaks the most common (and [officially documented on Mozilla support](https://support.mozilla.org/en-US/kb/access-toolbar-functions-using-keyboard)) pattern for quickly navigating toolbars with the keyboard:
1. Users press alt+d or control+l.
2. They would then generally press tab or shift+tab to begin navigating to other toolbar controls.
With openViewOnFocus enabled, pressing tab or shift+tab (step 2) moves through address bar suggestions instead of moving to the next or previous toolbar control.
The tricky issue here is that this behaviour appears to be by design. I don't know what the product goal is, but we clearly want users to see the suggestion list when they focus the address bar. If that's what we want for mouse users, it follows that it's also what we want for keyboard users... but currently, that's in direct conflict with toolbar keyboard navigation.
There are three possible solutions:
1. Don't do openViewOnFocus for keyboard users. But that means keyboard users get a different UX.
2. Stop tab/shift+tab from navigating suggestions, either always or only if openViewOnFocus triggered. There's bug 1437524 for getting rid of this always, but there's a lot of controversy concerning that.
3. Add another keystroke to focus the toolbar for quick toolbar keyboard navigation which doesn't trigger openViewOnFocus. That means we have to come up with yet another keyboard command and means users have to re-train something they do reflexively (and potentially hundreds/thousands of times a day).
|
openViewOnFocus breaks most common pattern for quickly navigating toolbars with the keyboard Bug 1603778 enabled browser.urlbar.openViewOnFocus by default in Nightly. Unfortunately, this breaks the most common (and [officially documented on Mozilla support](https://support.mozilla.org/en-US/kb/access-toolbar-functions-using-keyboard)) pattern for quickly navigating toolbars with the keyboard:
1. Users press alt+d or control+l.
2. They would then generally press tab or shift+tab to begin navigating to other toolbar controls.
With openViewOnFocus enabled, pressing tab or shift+tab (step 2) moves through address bar suggestions instead of moving to the next or previous toolbar control.
The tricky issue here is that this behaviour appears to be by design. I don't know what the product goal is, but we clearly want users to see the suggestion list when they focus the address bar. If that's what we want for mouse users, it follows that it's also what we want for keyboard users... but currently, that's in direct conflict with toolbar keyboard navigation.
There are three possible solutions:
1. Don't do openViewOnFocus for keyboard users. But that means keyboard users get a different UX.
2. Stop tab/shift+tab from navigating suggestions, either always or only if openViewOnFocus triggered. There's bug 1437524 for getting rid of this always, but there's a lot of controversy concerning that.
3. Add another keystroke to focus the toolbar for quick toolbar keyboard navigation which doesn't trigger openViewOnFocus. That means we have to come up with yet another keyboard command and means users have to re-train something they do reflexively (and potentially hundreds/thousands of times a day).
|
P2
|
VERIFIED
|
FIXED
|
2020-01-13 09:01:47+00:00
|
2020-03-06 16:12:58+00:00
| 409 | 2 |
1608802
|
Text in permission management list in about:preferences is spread across 2 lines instead of 1
|
STR:
1. Open about:preferences#privacy
2. Scroll to the Permissions section, see the permission name is in a new line after its icon
3. Same goes to the "Allow Nightly to send technical and interaction data to Mozilla" checkbox in the Data Collection section
Regressed by bug 1606130.
|
Text in permission management list in about:preferences is spread across 2 lines instead of 1 STR:
1. Open about:preferences#privacy
2. Scroll to the Permissions section, see the permission name is in a new line after its icon
3. Same goes to the "Allow Nightly to send technical and interaction data to Mozilla" checkbox in the Data Collection section
Regressed by bug 1606130.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-13 12:27:14+00:00
|
2020-02-12 16:09:06+00:00
| 87 | 1 |
1608829
|
"Learn more" link in the Data Collection section on about:preferences is in a second line instead of the same line
|
+++ This bug was initially created as a clone of Bug #1608802 +++
STR:
1. Open about:preferences#privacy
2. Scroll to the Data Collection section, see the "Allow Nightly to send technical and interaction data to Mozilla" checkbox
AR:
"Learn More" link in a new line
ER:
Should be in the same line.
Regressed by bug 1606130.
|
"Learn more" link in the Data Collection section on about:preferences is in a second line instead of the same line +++ This bug was initially created as a clone of Bug #1608802 +++
STR:
1. Open about:preferences#privacy
2. Scroll to the Data Collection section, see the "Allow Nightly to send technical and interaction data to Mozilla" checkbox
AR:
"Learn More" link in a new line
ER:
Should be in the same line.
Regressed by bug 1606130.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-13 14:49:43+00:00
|
2020-01-16 21:47:09+00:00
| 114 | 1 |
1608855
|
url bar suggesting an url alphabetically, not sorted by most visited
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
have youtube.com and y2mate.com as bookmarks. Then open new tab, enter "y
Actual results:
it will ALWAYS suggest y2mate.com instead of youtube.com, even though I super regularly visit youtube, and barely y2mate.com
Expected results:
youtube.com should be on top as top suggestion
|
url bar suggesting an url alphabetically, not sorted by most visited User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
have youtube.com and y2mate.com as bookmarks. Then open new tab, enter "y
Actual results:
it will ALWAYS suggest y2mate.com instead of youtube.com, even though I super regularly visit youtube, and barely y2mate.com
Expected results:
youtube.com should be on top as top suggestion
|
P5
|
NEW
|
2020-01-13 16:03:23+00:00
|
2020-07-07 05:29:31+00:00
| 131 | 5 |
|
1608899
|
Improve styling of data collection erasure notification box in preferences and adjust addon notification bar font size
|
STR:
1. Set `ui.systemUsesDarkTheme` to `1`
2. Open about:preferences#privacy
3. Untick the "Allow Firefox to send technical and interaction data to Mozilla" checkbox
4. See the notification box
AR:
1. The notification box is not suited for in-content dark mode
2. The "Learn More" text is not horizontally centered
3. The text size is not the consistent with the very-similar notification box from about:addons
|
Improve styling of data collection erasure notification box in preferences and adjust addon notification bar font size STR:
1. Set `ui.systemUsesDarkTheme` to `1`
2. Open about:preferences#privacy
3. Untick the "Allow Firefox to send technical and interaction data to Mozilla" checkbox
4. See the notification box
AR:
1. The notification box is not suited for in-content dark mode
2. The "Learn More" text is not horizontally centered
3. The text size is not the consistent with the very-similar notification box from about:addons
|
P3
|
NEW
|
2020-01-13 18:36:39+00:00
|
2022-10-11 23:50:17+00:00
| 127 | 3 |
|
1608910
|
Bottom buttons disappear when resizing subdialogs
|
Reproduced in firefox nightly version 74.0a1 (2020-01-13) (64-bit) in Ubuntu 18.04.3 LTS
Build ID 20200113093823
Steps to reproduce:
1- go to about:preferences
2- reach Language and Appearance section
3- click "choose" within language option
4- resize window and close it
5- repeat step 3
6- window size is back to original size before step 4 (**attachment: size goes back to original.webm** )
7- now go to privacy and security section
8- in Cookies and Site Data section, click Manage Data button
9- Rezise the window (only its widtch no the length)
10- close and repeat step 8
11- resize the window to be smaller, and notice that remove selected/all buttons are cut, and cancel and save changes button are no longer visible. ( **attachment resize remains so buttons get corrupted or disappear.webm**)
Expected results:
** Buttons should always be visible
** same behaviour should be triggered in every submenu ( there is a max/min size that user can resize, and when resizing window and closing and reopening, size should be the same)
Any of these would work
Actual results:
Buttons are not visible when resizing
|
Bottom buttons disappear when resizing subdialogs Reproduced in firefox nightly version 74.0a1 (2020-01-13) (64-bit) in Ubuntu 18.04.3 LTS
Build ID 20200113093823
Steps to reproduce:
1- go to about:preferences
2- reach Language and Appearance section
3- click "choose" within language option
4- resize window and close it
5- repeat step 3
6- window size is back to original size before step 4 (**attachment: size goes back to original.webm** )
7- now go to privacy and security section
8- in Cookies and Site Data section, click Manage Data button
9- Rezise the window (only its widtch no the length)
10- close and repeat step 8
11- resize the window to be smaller, and notice that remove selected/all buttons are cut, and cancel and save changes button are no longer visible. ( **attachment resize remains so buttons get corrupted or disappear.webm**)
Expected results:
** Buttons should always be visible
** same behaviour should be triggered in every submenu ( there is a max/min size that user can resize, and when resizing window and closing and reopening, size should be the same)
Any of these would work
Actual results:
Buttons are not visible when resizing
|
P3
|
NEW
|
2020-01-13 19:35:59+00:00
|
2022-10-11 23:50:19+00:00
| 290 | 3 |
|
1608970
|
Increase telemetry detail for moz-extension scripts loaded in the parent process
|
Per zombie, moz-extension scripts that are loaded in the parent process are unexpected are we should treat them as a security issue. We'd like to collect additional telemetry about when this happens.
At this point, we only have the (full) url that is being loaded. From Telemetry we also know what extensions the user has installed. It's not possible (or at least I don't see how) to map an Extension UUID to Extension Name from C++ but if we collect the path and filename that should be enough to figure out which extension it is - especially if we have enough reports for extension overlap.
Note that this only applies when the WebExtension process is *enabled*.
Presently we know *something* is going on here, we have 3,421 distinct windows clients reporting 33K events on Nightly. We don't know what is causing it, or how many extensions.
|
Increase telemetry detail for moz-extension scripts loaded in the parent process Per zombie, moz-extension scripts that are loaded in the parent process are unexpected are we should treat them as a security issue. We'd like to collect additional telemetry about when this happens.
At this point, we only have the (full) url that is being loaded. From Telemetry we also know what extensions the user has installed. It's not possible (or at least I don't see how) to map an Extension UUID to Extension Name from C++ but if we collect the path and filename that should be enough to figure out which extension it is - especially if we have enough reports for extension overlap.
Note that this only applies when the WebExtension process is *enabled*.
Presently we know *something* is going on here, we have 3,421 distinct windows clients reporting 33K events on Nightly. We don't know what is causing it, or how many extensions.
|
P1
|
RESOLVED
|
FIXED
|
2020-01-13 22:10:17+00:00
|
2020-03-21 12:00:22+00:00
| 209 | 1 |
1609034
|
Device registration not updated when user's password is reset
|
The device registration includes the encryption key for the URL etc. If a user resets their password, this key should be updated - but best I can tell, the device is not re-registered in this case. In theory, no registration change should be necessary for a *change*, only for a reset, but we should verify that.
Our [existing mechanism](https://searchfox.org/mozilla-central/rev/9e45d74b956be046e5021a746b0c8912f1c27318/services/fxaccounts/FxAccountsDevice.jsm#176) for detecting whether a device re-registration is needed also doesn't really handle this case - it will say no registration is needed even if the key contents have changed. We probably need to arrange to unconditionally re-register in this case.
Bug 1296328 was filed a few years ago, and will typically handle the case where the password was changed/reset on *this* device, but doesn't handle it on subsequent devices. It's possible we should revert that if the mechanism we end up with handles that case too.
Found this via bug 1601446, which isn't going to fix this - although it might help - it re-registers on verification, so we probably need to ensure some observer is notified in all these cases - ON_ACCOUNT_STATE_CHANGE_NOTIFICATION seems the obvious candidate.
|
Device registration not updated when user's password is reset The device registration includes the encryption key for the URL etc. If a user resets their password, this key should be updated - but best I can tell, the device is not re-registered in this case. In theory, no registration change should be necessary for a *change*, only for a reset, but we should verify that.
Our [existing mechanism](https://searchfox.org/mozilla-central/rev/9e45d74b956be046e5021a746b0c8912f1c27318/services/fxaccounts/FxAccountsDevice.jsm#176) for detecting whether a device re-registration is needed also doesn't really handle this case - it will say no registration is needed even if the key contents have changed. We probably need to arrange to unconditionally re-register in this case.
Bug 1296328 was filed a few years ago, and will typically handle the case where the password was changed/reset on *this* device, but doesn't handle it on subsequent devices. It's possible we should revert that if the mechanism we end up with handles that case too.
Found this via bug 1601446, which isn't going to fix this - although it might help - it re-registers on verification, so we probably need to ensure some observer is notified in all these cases - ON_ACCOUNT_STATE_CHANGE_NOTIFICATION seems the obvious candidate.
|
P2
|
NEW
|
2020-01-14 05:03:33+00:00
|
2022-10-11 23:50:25+00:00
| 330 | 2 |
|
1609166
|
Firefox Sync login does not become verified, despite entering correct verification code
|
STEPS TO REPRODUCE
1. In a fresh profile from the toolbar menu, select Sign in to Firefox (Turn on Sync)
2. Create a new account but do not verify
3. Notice that browser enters "verification required" state
4. Enter verification code
EXPECTED RESULTS
* Sync becomes verified and starts working
ACTUAL RESULTS
* Remains in "verification required" state until user selects "Resend Verification" in sync prefs
|
Firefox Sync login does not become verified, despite entering correct verification code STEPS TO REPRODUCE
1. In a fresh profile from the toolbar menu, select Sign in to Firefox (Turn on Sync)
2. Create a new account but do not verify
3. Notice that browser enters "verification required" state
4. Enter verification code
EXPECTED RESULTS
* Sync becomes verified and starts working
ACTUAL RESULTS
* Remains in "verification required" state until user selects "Resend Verification" in sync prefs
|
P1
|
RESOLVED
|
FIXED
|
2020-01-14 16:11:32+00:00
|
2020-04-08 21:40:59+00:00
| 102 | 1 |
1609225
|
Get browser.cache.disk.parent_directory working
|
We added this via policy but it's not working.
It's set too late.
It works for users because it's set as a user pref so it just gets read on the next reboot.
|
Get browser.cache.disk.parent_directory working We added this via policy but it's not working.
It's set too late.
It works for users because it's set as a user pref so it just gets read on the next reboot.
|
P3
|
RESOLVED
|
WORKSFORME
|
2020-01-14 19:42:43+00:00
|
2020-09-21 20:00:18+00:00
| 57 | 3 |
1609287
|
about:protections private browsing message is not dark theme friendly
|
https://searchfox.org/mozilla-central/rev/9b4b41b95cbcda63f565bdc24411e15248f91d83/browser/components/protections/content/protections.css#262-270
These hardcoded colors should be replaced with variables from common.css.
|
about:protections private browsing message is not dark theme friendly https://searchfox.org/mozilla-central/rev/9b4b41b95cbcda63f565bdc24411e15248f91d83/browser/components/protections/content/protections.css#262-270
These hardcoded colors should be replaced with variables from common.css.
|
P2
|
VERIFIED
|
FIXED
|
2020-01-15 00:30:56+00:00
|
2020-01-19 16:15:22+00:00
| 96 | 2 |
1609321
|
URL autofill sometimes flickers when typing the wrong case
|
1. Type "bugzilla.mozilla.org/s" to autofill a URL like bugzilla.mozilla.org/show_bug.cgi?id=123456
2. Press backspace to delete the selected part
3. Press backspace again to delete the "s"
4. Type an uppercase "S" and then start typing the rest of "how_bug". The case doesn't matter for the "how_bug" part.
Most of the time you try this, the rest of the "how_bug" etc. part -- which is selected -- flickers and then disappears. Step 1 seems to be necessary.
I'm guessing that it's autofilling the placeholder, and then when the search is done, it's correctly removing the autofilled part because it doesn't actually match due to the difference in case. So I would guess that the placeholder logic is incorrectly doing a case-insensitive comparison, but I haven't debugged this yet.
|
URL autofill sometimes flickers when typing the wrong case 1. Type "bugzilla.mozilla.org/s" to autofill a URL like bugzilla.mozilla.org/show_bug.cgi?id=123456
2. Press backspace to delete the selected part
3. Press backspace again to delete the "s"
4. Type an uppercase "S" and then start typing the rest of "how_bug". The case doesn't matter for the "how_bug" part.
Most of the time you try this, the rest of the "how_bug" etc. part -- which is selected -- flickers and then disappears. Step 1 seems to be necessary.
I'm guessing that it's autofilling the placeholder, and then when the search is done, it's correctly removing the autofilled part because it doesn't actually match due to the difference in case. So I would guess that the placeholder logic is incorrectly doing a case-insensitive comparison, but I haven't debugged this yet.
|
P3
|
NEW
|
2020-01-15 03:26:53+00:00
|
2020-07-07 05:30:07+00:00
| 240 | 3 |
|
1609534
|
When the address manager subdialog is scrollable, it overlaps the scrollbar for the <select> element
|
STR:
1. Navigate to "about:preferences"
2. Search for "addresses"
3. Click the button that reads "Saved Addresses..."
4. Add addresses so that there are at least 8 total.
5. Observe that there is now a scroll bar on the <select> element that displays the addresses.
6. Close the address manager subdialog.
7. Resize the Firefox window so that it is quite small
8. Click "Saved Addresses..." again
Expected Results:
Both the scrollbar for the dialog and the scrollbar for the <select> element should be visible
Actual Results:
The scrollbar for the <select> element is not visible because it is hidden under the scrollbar for the dialog. There isn't even a horizontal scrollbar we could use to bring it into frame.
A couple of notes about this:
- I discovered this while fixing Bug 1608246, which was preventing the subdialog from being shown at all when the Firefox window was too small. You may need to wait for that patch to merge to be able to reproduce this. I did, however, double check with a build from before Bug 1608246 was introduced to verify that this bug was preexisting behavior rather than something I caused.
- I discovered this on Windows. I know that macOS scrollbars are, by default, a bit unusual and like to hide, so I have no idea whether this issue appears there or how it presents.
|
When the address manager subdialog is scrollable, it overlaps the scrollbar for the <select> element STR:
1. Navigate to "about:preferences"
2. Search for "addresses"
3. Click the button that reads "Saved Addresses..."
4. Add addresses so that there are at least 8 total.
5. Observe that there is now a scroll bar on the <select> element that displays the addresses.
6. Close the address manager subdialog.
7. Resize the Firefox window so that it is quite small
8. Click "Saved Addresses..." again
Expected Results:
Both the scrollbar for the dialog and the scrollbar for the <select> element should be visible
Actual Results:
The scrollbar for the <select> element is not visible because it is hidden under the scrollbar for the dialog. There isn't even a horizontal scrollbar we could use to bring it into frame.
A couple of notes about this:
- I discovered this while fixing Bug 1608246, which was preventing the subdialog from being shown at all when the Firefox window was too small. You may need to wait for that patch to merge to be able to reproduce this. I did, however, double check with a build from before Bug 1608246 was introduced to verify that this bug was preexisting behavior rather than something I caused.
- I discovered this on Windows. I know that macOS scrollbars are, by default, a bit unusual and like to hide, so I have no idea whether this issue appears there or how it presents.
|
P3
|
NEW
|
2020-01-15 21:07:17+00:00
|
2022-10-11 23:50:56+00:00
| 335 | 3 |
|
1609578
|
Users shouldn't have to "Block" future permissions to back out of *changing* camera or mic
|
A page may call `getUserMedia` many times requesting different devices. Hitting "Deny" on _any_ of these prompts temporarily blocks all further gUM permissions on that page. That seems overly severe.
A common use flow is in-content device selection where a user switches camera or microphone:
**STR (requires 2 cameras, or use a phone):** (Remove persistent permissions first):
1. Open https://whereby.com/room12345 and "Request permission"
2. Hit "Allow" in Firefox's gUM prompt
3. (You realize you wanted to use a different camera and) click the ⚙️ gear icon to change to the other camera (or flip ↻ front/back on phone)
4. Pick your other camera. A Firefox gUM prompt for that device appears.
5. (You change your mind and) hit "Deny" in this second gUM prompt
**Expected result:**
* The first camera is still chosen and working, and repeating steps 4-5 works (at least on a third camera).
**Actual result:**
* "Cam and mic are blocked" & the user is stuck until they refresh the page (see image).
**Side-bug:**
* As the image shows, the page-info drop-down has icons showing permission is blocked, but the text still says "Allowed Temporarily". The text appears to be a refresh bug, as the permission actually appears blocked. In fact, dragging the live tab into its own window causes the text to refresh to show "Blocked Temporarily").
**Proposed solution**
* Only add temporary blocks from "Deny" in *first* prompt (but `☑ Remember this decision` + "Deny" still adds permanent block even in subsequent ones).
* The definition of "first" may need hashing out. I think it's:
* The page has not been granted gUM previously in this session, or since the user last revoked permission manually in this session.
|
Users shouldn't have to "Block" future permissions to back out of *changing* camera or mic A page may call `getUserMedia` many times requesting different devices. Hitting "Deny" on _any_ of these prompts temporarily blocks all further gUM permissions on that page. That seems overly severe.
A common use flow is in-content device selection where a user switches camera or microphone:
**STR (requires 2 cameras, or use a phone):** (Remove persistent permissions first):
1. Open https://whereby.com/room12345 and "Request permission"
2. Hit "Allow" in Firefox's gUM prompt
3. (You realize you wanted to use a different camera and) click the ⚙️ gear icon to change to the other camera (or flip ↻ front/back on phone)
4. Pick your other camera. A Firefox gUM prompt for that device appears.
5. (You change your mind and) hit "Deny" in this second gUM prompt
**Expected result:**
* The first camera is still chosen and working, and repeating steps 4-5 works (at least on a third camera).
**Actual result:**
* "Cam and mic are blocked" & the user is stuck until they refresh the page (see image).
**Side-bug:**
* As the image shows, the page-info drop-down has icons showing permission is blocked, but the text still says "Allowed Temporarily". The text appears to be a refresh bug, as the permission actually appears blocked. In fact, dragging the live tab into its own window causes the text to refresh to show "Blocked Temporarily").
**Proposed solution**
* Only add temporary blocks from "Deny" in *first* prompt (but `☑ Remember this decision` + "Deny" still adds permanent block even in subsequent ones).
* The definition of "first" may need hashing out. I think it's:
* The page has not been granted gUM previously in this session, or since the user last revoked permission manually in this session.
|
P2
|
RESOLVED
|
FIXED
|
2020-01-16 01:54:30+00:00
|
2022-08-24 01:24:07+00:00
| 445 | 2 |
1609635
|
Snippets broken in Nightly 74
|
#### Affected versions:
Nightly 74.0a1 (2020-01-16)
#### Affected platforms:
ALL
#### Preconditions:
Have the "browser.newtabpage.activity-stream.asrouter.devtoolsEnabled" pref set to "true" in the "about:config" page.
#### Steps:
1. Navigate to the "about:newtab#asrouter" page and select the "snippets_local_testing" from the "Messages" section's dropdown menu.
2. Click the "Show" button from the "SIMPLE_TEST_1" section.
#### Actual result:
The "SIMPLE_TEST_1" snippet is displayed in the bottom part of the browser but there is no hyperlink.
#### Expected result:
The body text of the snippet should contain a hyperlink in the right part of the firefox icon.
Please see also the following bug, might be related to this issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1601880
#### Regression range:
Last good revision: 72bc4f39b6598b06925c9a3372a5076f5e6f78ab
First bad revision: 01fde39940c3d8baa41dc747bf4454cf312be78c
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=72bc4f39b6598b06925c9a3372a5076f5e6f78ab&tochange=01fde39940c3d8baa41dc747bf4454cf312be78c
|
Snippets broken in Nightly 74 #### Affected versions:
Nightly 74.0a1 (2020-01-16)
#### Affected platforms:
ALL
#### Preconditions:
Have the "browser.newtabpage.activity-stream.asrouter.devtoolsEnabled" pref set to "true" in the "about:config" page.
#### Steps:
1. Navigate to the "about:newtab#asrouter" page and select the "snippets_local_testing" from the "Messages" section's dropdown menu.
2. Click the "Show" button from the "SIMPLE_TEST_1" section.
#### Actual result:
The "SIMPLE_TEST_1" snippet is displayed in the bottom part of the browser but there is no hyperlink.
#### Expected result:
The body text of the snippet should contain a hyperlink in the right part of the firefox icon.
Please see also the following bug, might be related to this issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1601880
#### Regression range:
Last good revision: 72bc4f39b6598b06925c9a3372a5076f5e6f78ab
First bad revision: 01fde39940c3d8baa41dc747bf4454cf312be78c
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=72bc4f39b6598b06925c9a3372a5076f5e6f78ab&tochange=01fde39940c3d8baa41dc747bf4454cf312be78c
|
P1
|
VERIFIED
|
FIXED
|
2020-01-16 09:58:49+00:00
|
2020-02-07 07:49:31+00:00
| 424 | 1 |
1609657
|
Firefox does not generate an accessibility tree for PDFs
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36
Steps to reproduce:
Run NVDA on Windows 10
Visit https://www.pdfa.org/wp-content/uploads/2019/09/PDF-Association-flyer-A4.pdf in Firefox - this PDF file is known to be tagged for accessibility.
Use the standard keyboard input controls for browsing the document (e.g. H for headings) or inspect the Accessibility tree in the dev tools
Actual results:
Document semantics, aria roles, accessible names and descriptions are ignored. Dev tools > Accessibility reports the existence of a document, but not much else. It appears that Firefox is not generating an accessibility tree for PDF content, even when the PDF is tagged.
Expected results:
Should be able to navigate the document via its semantics (landmarks, headings etc.) exactly as you can with Adobe Acrobat (using the exact same PDF). Dev tools accessibility should map these semantics as a tree, exactly as it would with a correctly-made HTML or SVG file.
|
Firefox does not generate an accessibility tree for PDFs User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36
Steps to reproduce:
Run NVDA on Windows 10
Visit https://www.pdfa.org/wp-content/uploads/2019/09/PDF-Association-flyer-A4.pdf in Firefox - this PDF file is known to be tagged for accessibility.
Use the standard keyboard input controls for browsing the document (e.g. H for headings) or inspect the Accessibility tree in the dev tools
Actual results:
Document semantics, aria roles, accessible names and descriptions are ignored. Dev tools > Accessibility reports the existence of a document, but not much else. It appears that Firefox is not generating an accessibility tree for PDF content, even when the PDF is tagged.
Expected results:
Should be able to navigate the document via its semantics (landmarks, headings etc.) exactly as you can with Adobe Acrobat (using the exact same PDF). Dev tools accessibility should map these semantics as a tree, exactly as it would with a correctly-made HTML or SVG file.
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-01-16 12:28:40+00:00
|
2022-07-28 21:41:08+00:00
| 282 | 3 |
1609740
|
Redhat Linux EL 6.10 Firefox v68, Set as Desktop Background not working - Dialog appears and allows but image not actually set
|
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
run Firefox, searched for desktop backgrounds, pulled up the page with an image I liked, right clicked on image and selected Set as Desktop Background. The dialog pops up where you can set the position and color. Clicked on Set as Desktop Background button on the dialog.
Actual results:
Nothing, the dialog goes away and the desktop background is not set.
Expected results:
The image should have been set as the background image for the desktop.
|
Redhat Linux EL 6.10 Firefox v68, Set as Desktop Background not working - Dialog appears and allows but image not actually set User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
run Firefox, searched for desktop backgrounds, pulled up the page with an image I liked, right clicked on image and selected Set as Desktop Background. The dialog pops up where you can set the position and color. Clicked on Set as Desktop Background button on the dialog.
Actual results:
Nothing, the dialog goes away and the desktop background is not set.
Expected results:
The image should have been set as the background image for the desktop.
|
P3
|
UNCONFIRMED
|
2020-01-16 18:32:32+00:00
|
2022-10-11 23:51:12+00:00
| 170 | 3 |
|
1609880
|
No indication why global/default zoom does not work with privacy.resistFingerprinting enabled
|
STR:
1. Enable `privacy.resistFingerprinting`.
2. Go to `about:preferences` and change the "Default zoom" setting (introduced in 73) to something other than 100%.
Expected:
Default zoom works or some explanation why it doesn't.
Actual:
Default zoom fails without explanation.
|
No indication why global/default zoom does not work with privacy.resistFingerprinting enabled STR:
1. Enable `privacy.resistFingerprinting`.
2. Go to `about:preferences` and change the "Default zoom" setting (introduced in 73) to something other than 100%.
Expected:
Default zoom works or some explanation why it doesn't.
Actual:
Default zoom fails without explanation.
|
P5
|
RESOLVED
|
FIXED
|
2020-01-17 09:46:28+00:00
|
2022-07-07 18:23:22+00:00
| 86 | 5 |
1609906
|
Add automated test that exercises about:downloads
|
We completely broke about:downloads and didn't notice. We should fix that.
|
Add automated test that exercises about:downloads We completely broke about:downloads and didn't notice. We should fix that.
|
P1
|
RESOLVED
|
FIXED
|
2020-01-17 11:47:59+00:00
|
2020-02-19 22:54:50+00:00
| 27 | 1 |
1609922
|
Add mochitest for end to end snippets rendering test
|
Follow up of bug 1609635, we need mochitests that catch snippets rendering regressions.
|
Add mochitest for end to end snippets rendering test Follow up of bug 1609635, we need mochitests that catch snippets rendering regressions.
|
P1
|
RESOLVED
|
FIXED
|
2020-01-17 13:00:44+00:00
|
2020-02-11 09:13:47+00:00
| 40 | 1 |
1610024
|
The "Redirect" tip is not triggered in the next session if you previously dismiss it temporarily and perform a search in another tab
|
+++ This bug was initially created as a clone of Bug #1605738 +++
We wontfixed bug 1605738 for the tips experiment, but we may want to fix it for the tips implementation in the product. Or maybe not, but I just wanted to file this bug so we don't forget to consider it.
Relevant parts of the original bug below. See also the discussion there.
-----
[Steps to reproduce]:
1. Open Firefox with the profile from prerequisites.
2. In an already opened tab navigate to https://www.google.com/ page.
3. Click anywhere on the page in order to dismiss the tip.
4. In another opened tab, perform a search using the address bar.
5. Restart the browser.
6. In an already opened tab navigate to https://www.google.com/ page.
7. Observe what happens next.
[Expected result]:
- The “Redirect” tip is displayed.
[Actual result]:
- The “Redirect” tip is not displayed.
[Notes]:
- This issue is also reproducible with the other supported search engines: Bing and DucDuckGo.
- This issue is not reproducible if, at step 4, you delete the existing URL, unfocus the address bar and only after that you perform a search.
- Attached a screen recording with the issue.
|
The "Redirect" tip is not triggered in the next session if you previously dismiss it temporarily and perform a search in another tab +++ This bug was initially created as a clone of Bug #1605738 +++
We wontfixed bug 1605738 for the tips experiment, but we may want to fix it for the tips implementation in the product. Or maybe not, but I just wanted to file this bug so we don't forget to consider it.
Relevant parts of the original bug below. See also the discussion there.
-----
[Steps to reproduce]:
1. Open Firefox with the profile from prerequisites.
2. In an already opened tab navigate to https://www.google.com/ page.
3. Click anywhere on the page in order to dismiss the tip.
4. In another opened tab, perform a search using the address bar.
5. Restart the browser.
6. In an already opened tab navigate to https://www.google.com/ page.
7. Observe what happens next.
[Expected result]:
- The “Redirect” tip is displayed.
[Actual result]:
- The “Redirect” tip is not displayed.
[Notes]:
- This issue is also reproducible with the other supported search engines: Bing and DucDuckGo.
- This issue is not reproducible if, at step 4, you delete the existing URL, unfocus the address bar and only after that you perform a search.
- Attached a screen recording with the issue.
|
P2
|
VERIFIED
|
FIXED
|
2020-01-17 21:19:54+00:00
|
2020-03-04 16:05:02+00:00
| 329 | 2 |
1610081
|
The non-scrolling sidebar in about:addons and about:preferences is a potential migraine trigger
|
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Used about:addons
Actual results:
It has a sidebar which does no scroll with the rest of the page.
It's not as bad as most pages with this layout, but it's still a potential migraine trigger and/or aggravator.
Right now, the non-scrolling sidebar and scrolling add-on list are next to each other on the left side of the window. Maybe it would work better if they were on opposite sides of the window, space permitting.
|
The non-scrolling sidebar in about:addons and about:preferences is a potential migraine trigger User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Used about:addons
Actual results:
It has a sidebar which does no scroll with the rest of the page.
It's not as bad as most pages with this layout, but it's still a potential migraine trigger and/or aggravator.
Right now, the non-scrolling sidebar and scrolling add-on list are next to each other on the left side of the window. Maybe it would work better if they were on opposite sides of the window, space permitting.
|
P3
|
VERIFIED
|
FIXED
|
2020-01-18 02:32:50+00:00
|
2023-06-02 14:49:37+00:00
| 168 | 3 |
1610200
|
Address bar does not autohide after navigating to a new page in fullscreen
|
From https://www.reddit.com/r/firefox/comments/eqy7wf/firefox_fullscreen_f11_does_not_auto_hide/
Steps to reproduce:
1. Open Firefox.
2. Open a web page
3. Enter full screen (F11)
4. Use Ctrl-l to open address bar, navigate to any URL
What happens:
The addressbar does not autohide.
Expected result:
The address bar should autohide.
12:55.13 INFO: No more inbound revisions, bisection finished.
12:55.13 INFO: Last good revision: 12d4df6de36eaae416b024531d12eb8ee802835c
12:55.13 INFO: First bad revision: 2e388d4237d0473f6e14f4218290d54857be84d6
12:55.13 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=12d4df6de36eaae416b024531d12eb8ee802835c&tochange=2e388d4237d0473f6e14f4218290d54857be84d6
|
Address bar does not autohide after navigating to a new page in fullscreen From https://www.reddit.com/r/firefox/comments/eqy7wf/firefox_fullscreen_f11_does_not_auto_hide/
Steps to reproduce:
1. Open Firefox.
2. Open a web page
3. Enter full screen (F11)
4. Use Ctrl-l to open address bar, navigate to any URL
What happens:
The addressbar does not autohide.
Expected result:
The address bar should autohide.
12:55.13 INFO: No more inbound revisions, bisection finished.
12:55.13 INFO: Last good revision: 12d4df6de36eaae416b024531d12eb8ee802835c
12:55.13 INFO: First bad revision: 2e388d4237d0473f6e14f4218290d54857be84d6
12:55.13 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=12d4df6de36eaae416b024531d12eb8ee802835c&tochange=2e388d4237d0473f6e14f4218290d54857be84d6
|
P1
|
VERIFIED
|
FIXED
|
2020-01-19 20:50:42+00:00
|
2020-02-19 08:02:37+00:00
| 317 | 1 |
1610250
|
Zoom level badge is displayed in the address bar for default zoom level set to 110%
|
#### Affected versions:
Nightly 74.0a1 (2020-01-20), Beta 73.0b7
#### 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 110% value from the "Default zoom" dropdown.
#### Actual result:
The zoom level badge is displayed next to the url bar.
#### Expected result:
The zoom level badge should be not displayed in the URL bar for default zoom level. It is displayed only when the default zoom is set to 110%. For any other value the badge is not displayed.
|
Zoom level badge is displayed in the address bar for default zoom level set to 110% #### Affected versions:
Nightly 74.0a1 (2020-01-20), Beta 73.0b7
#### 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 110% value from the "Default zoom" dropdown.
#### Actual result:
The zoom level badge is displayed next to the url bar.
#### Expected result:
The zoom level badge should be not displayed in the URL bar for default zoom level. It is displayed only when the default zoom is set to 110%. For any other value the badge is not displayed.
|
P3
|
VERIFIED
|
FIXED
|
2020-01-20 08:39:27+00:00
|
2020-01-23 08:09:48+00:00
| 168 | 3 |
1610298
|
Preview messages don't belong to a provider
|
The preview flow is:
1. Add preview provider
2. Update all providers (fetch messages).
* this removes the preview provider at the end
3. Fetch messages that match `message.provider === 'preview'`
* this would check for `provider.excludes...` but the preview provider was already removed
|
Preview messages don't belong to a provider The preview flow is:
1. Add preview provider
2. Update all providers (fetch messages).
* this removes the preview provider at the end
3. Fetch messages that match `message.provider === 'preview'`
* this would check for `provider.excludes...` but the preview provider was already removed
|
P1
|
RESOLVED
|
FIXED
|
2020-01-20 14:47:39+00:00
|
2020-02-04 02:11:45+00:00
| 78 | 1 |
1610318
|
Preferences/Options being opened with subcategories have a "useless" back button entry added (e.g. The Manage Settings button from about:protections and the privacy protection entry in the hamburger menu)
|
**Affected versions**
* 74.0a1
* 73.0b7
* 72.0.2
**Affected platforms**
* Windows 10x64
* macOS 10.15
* Ubuntu 16.04x64
**Steps to reproduce**
1. Go to reddit.com
2. Go to the url bar and click on the shield.
3. Go to Show Report option.
4. Click on Manage Settings
**Expected result**
* A new tab is opened with about:preferences#privacy and the "Back" is not enabled.
**Actual result**
* A new tab is opened with about:preferences#privacy and the "back" buttons is enabled.
**Regression range**
* will return with a regression ASAP.
**Additional notes**
* The "back" button should not be activated , since the section has opened in a new tab. The back button simply refreshes the page and does not redirect to anything.
|
Preferences/Options being opened with subcategories have a "useless" back button entry added (e.g. The Manage Settings button from about:protections and the privacy protection entry in the hamburger menu) **Affected versions**
* 74.0a1
* 73.0b7
* 72.0.2
**Affected platforms**
* Windows 10x64
* macOS 10.15
* Ubuntu 16.04x64
**Steps to reproduce**
1. Go to reddit.com
2. Go to the url bar and click on the shield.
3. Go to Show Report option.
4. Click on Manage Settings
**Expected result**
* A new tab is opened with about:preferences#privacy and the "Back" is not enabled.
**Actual result**
* A new tab is opened with about:preferences#privacy and the "back" buttons is enabled.
**Regression range**
* will return with a regression ASAP.
**Additional notes**
* The "back" button should not be activated , since the section has opened in a new tab. The back button simply refreshes the page and does not redirect to anything.
|
P5
|
RESOLVED
|
DUPLICATE
|
2020-01-20 15:52:03+00:00
|
2024-03-26 15:45:16+00:00
| 251 | 5 |
1610397
|
Double clicking multiple words in separate search box selects all text instead of the word being double clicked
|
From: https://www.reddit.com/r/firefox/comments/erf08d/7201_i_can_no_longer_drag_links_from_the_address/ff3dg9i/
Steps to reproduce:
1. Enable separate search box
2. type two or more words in search box, like "example example"
3. Double-click the first "example"
What happens:
Both words are selected.
Expected result:
Only the first word is selected.
21:33.97 INFO: No more inbound revisions, bisection finished.
21:33.97 INFO: Last good revision: 37fd68a3d10d0ec85350177152ab9af8425f0d3c
21:33.97 INFO: First bad revision: d57c700859fbd63684386e0bf063331460753bc4
21:33.97 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=37fd68a3d10d0ec85350177152ab9af8425f0d3c&tochange=d57c700859fbd63684386e0bf063331460753bc4
|
Double clicking multiple words in separate search box selects all text instead of the word being double clicked From: https://www.reddit.com/r/firefox/comments/erf08d/7201_i_can_no_longer_drag_links_from_the_address/ff3dg9i/
Steps to reproduce:
1. Enable separate search box
2. type two or more words in search box, like "example example"
3. Double-click the first "example"
What happens:
Both words are selected.
Expected result:
Only the first word is selected.
21:33.97 INFO: No more inbound revisions, bisection finished.
21:33.97 INFO: Last good revision: 37fd68a3d10d0ec85350177152ab9af8425f0d3c
21:33.97 INFO: First bad revision: d57c700859fbd63684386e0bf063331460753bc4
21:33.97 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=37fd68a3d10d0ec85350177152ab9af8425f0d3c&tochange=d57c700859fbd63684386e0bf063331460753bc4
|
P3
|
VERIFIED
|
FIXED
|
2020-01-20 23:39:41+00:00
|
2020-03-16 09:57:28+00:00
| 321 | 3 |
1610421
|
Wrong context menu after rearranging tab
|
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I moved a tab to the left
I then quickly right clicked it because I intended to close All Tabs To The Right
Actual results:
I got a limited context menu instead of the full one (See attached file).
Expected results:
I expected the full context menu to perform my actions.
|
Wrong context menu after rearranging tab User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I moved a tab to the left
I then quickly right clicked it because I intended to close All Tabs To The Right
Actual results:
I got a limited context menu instead of the full one (See attached file).
Expected results:
I expected the full context menu to perform my actions.
|
P3
|
NEW
|
2020-01-21 03:26:02+00:00
|
2022-10-11 23:51:58+00:00
| 116 | 3 |
|
1610423
|
"Also use this proxy for FTP and HTTPS" grays out SOCKS proxy settings
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
1. Go to "Preferences" > "Network Settings" > "Settings..."
2. Check "Also use this proxy for FTP and HTTPS"
Actual results:
"SOCKS Host" line is grayed out, with the previous settings filled in.
Expected results:
"SOCKS Host" line is not grayed out.
|
"Also use this proxy for FTP and HTTPS" grays out SOCKS proxy settings User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
1. Go to "Preferences" > "Network Settings" > "Settings..."
2. Check "Also use this proxy for FTP and HTTPS"
Actual results:
"SOCKS Host" line is grayed out, with the previous settings filled in.
Expected results:
"SOCKS Host" line is not grayed out.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-21 04:12:38+00:00
|
2020-02-07 09:42:26+00:00
| 129 | 1 |
1610430
|
URL Autosuggestion does not give suggestions until I have typed in "https://"
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I have been accustomed to the URL suggesting pages in the following manner
If I have visited the site "https://www.dr.dk" then when typing in "d" in the adress bar, it would suggest the page.
Actual results:
When I type in "d" there is no suggestions. Instead it only starts suggesting the page after I have prefixed with "https://"
Then I can write
"https://d" and it suggests the expecting page.
Expected results:
I should be able to only type in "d" in the address bar and then get a suggestion.
Note that this happens for all suggestions and not just for the page "https://www.dr.dk", it was just used as an example. I am not sure, however, if it has to do with settings on my machine, but I have not been able to find any documentation that could lead me in the right direction as to a fix that I can implement.
|
URL Autosuggestion does not give suggestions until I have typed in "https://" User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
I have been accustomed to the URL suggesting pages in the following manner
If I have visited the site "https://www.dr.dk" then when typing in "d" in the adress bar, it would suggest the page.
Actual results:
When I type in "d" there is no suggestions. Instead it only starts suggesting the page after I have prefixed with "https://"
Then I can write
"https://d" and it suggests the expecting page.
Expected results:
I should be able to only type in "d" in the address bar and then get a suggestion.
Note that this happens for all suggestions and not just for the page "https://www.dr.dk", it was just used as an example. I am not sure, however, if it has to do with settings on my machine, but I have not been able to find any documentation that could lead me in the right direction as to a fix that I can implement.
|
P5
|
RESOLVED
|
INCOMPLETE
|
2020-01-21 07:12:50+00:00
|
2020-05-13 13:24:18+00:00
| 276 | 5 |
1610497
|
Address bar can not be selected by mouse if the browser has the minimum width
|
**Affected versions**
* Fx 74.0a1
* Fx 73.0b7
* Fx 72.0.2
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04 LTS
* macOS 10.14
**Steps to reproduce**
1. Launch Firefox.
2. Go to "https://www.mozilla.org/en-US/contribute/stories/" .
3. Change the browser width to the minimum.
4. Attempt to select the address bar with the mouse cursor.
**Expected result**
* The address bar is selected.
**Actual result**
* The address bar can not be selected.
**Regression range**
* First bad: 20-09-2020
* Last good: 19-09-2020
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b46946d6e446cf50fc2c3fcc62e2cb8ec84c4064&tochange=517c9efa9592ad0c103ec2542e4bc7fcaf06c505
* Potential regressor: 1580538
**Additional notes**
* Builds that have the permanent search icon in front of the megabar are not affected (https://bugzil.la/1589836).
* This issue is not reproducible if the address bar is set in focus using the keyboard ( Ctrl/Cmd + L).
|
Address bar can not be selected by mouse if the browser has the minimum width **Affected versions**
* Fx 74.0a1
* Fx 73.0b7
* Fx 72.0.2
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04 LTS
* macOS 10.14
**Steps to reproduce**
1. Launch Firefox.
2. Go to "https://www.mozilla.org/en-US/contribute/stories/" .
3. Change the browser width to the minimum.
4. Attempt to select the address bar with the mouse cursor.
**Expected result**
* The address bar is selected.
**Actual result**
* The address bar can not be selected.
**Regression range**
* First bad: 20-09-2020
* Last good: 19-09-2020
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b46946d6e446cf50fc2c3fcc62e2cb8ec84c4064&tochange=517c9efa9592ad0c103ec2542e4bc7fcaf06c505
* Potential regressor: 1580538
**Additional notes**
* Builds that have the permanent search icon in front of the megabar are not affected (https://bugzil.la/1589836).
* This issue is not reproducible if the address bar is set in focus using the keyboard ( Ctrl/Cmd + L).
|
P2
|
VERIFIED
|
FIXED
|
2020-01-21 13:09:09+00:00
|
2021-01-18 15:53:23+00:00
| 360 | 2 |
1610523
|
Cannot easily reattempt navigating to a URL that returned status 204 No Content using reload button (and URL is not remembered in session restore)
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
- Open new tab
- Open network console
- Navigate to a page with status 204 (No Content), for example http://httpstat.us/204
- Try to reload the page with the button near the address bar or F5 or Ctrl+R
Actual results:
Nothing. Reload button is disabled.
Expected results:
Firefox should send a new HTTP request.
The 204 status is special, but I think if the user explicitly entered the address in the address bar, the browser should navigate to that page and make it possible to reload it. This is a common task (and HTTP status) for developers of web services.
|
Cannot easily reattempt navigating to a URL that returned status 204 No Content using reload button (and URL is not remembered in session restore) User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
- Open new tab
- Open network console
- Navigate to a page with status 204 (No Content), for example http://httpstat.us/204
- Try to reload the page with the button near the address bar or F5 or Ctrl+R
Actual results:
Nothing. Reload button is disabled.
Expected results:
Firefox should send a new HTTP request.
The 204 status is special, but I think if the user explicitly entered the address in the address bar, the browser should navigate to that page and make it possible to reload it. This is a common task (and HTTP status) for developers of web services.
|
P5
|
UNCONFIRMED
|
2020-01-21 14:31:59+00:00
|
2022-10-11 23:52:06+00:00
| 214 | 5 |
|
1610623
|
DisplayMenuBar isn't working via GPO with Firefox 72
|
With the changes in bug 1587492, the GPO for the menubar isn't working anymore.
This is because the GPO uses 1/0 instead of booleans (implementation detail), so the schema validator change isn't kicking in.
This is a corner case where we moved a bool to a string enum, so I'm going to put in a workaround.
|
DisplayMenuBar isn't working via GPO with Firefox 72 With the changes in bug 1587492, the GPO for the menubar isn't working anymore.
This is because the GPO uses 1/0 instead of booleans (implementation detail), so the schema validator change isn't kicking in.
This is a corner case where we moved a bool to a string enum, so I'm going to put in a workaround.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-21 20:03:42+00:00
|
2020-01-27 10:01:00+00:00
| 103 | 1 |
1610681
|
UrlbarView needs to select the heuristic result when it's not the first result added
|
In helping to port interventions, I'm seeing that we end up with an unselected heuristic result. The first result added to the view is the intervention tip, which has a suggestedIndex=1 and is not the heuristic. Later, UnifiedComplete's heuristic result is added. The two results appear in the correct positions, and the first result's `heuristic` property is true. The problem is that the view only selects the heuristic when it is the first result added [1]. That's not the case here, as just described.
[1] https://searchfox.org/mozilla-central/rev/cfd1cc461f1efe0d66c2fdc17c024a203d5a2fd8/browser/components/urlbar/UrlbarView.jsm#427
|
UrlbarView needs to select the heuristic result when it's not the first result added In helping to port interventions, I'm seeing that we end up with an unselected heuristic result. The first result added to the view is the intervention tip, which has a suggestedIndex=1 and is not the heuristic. Later, UnifiedComplete's heuristic result is added. The two results appear in the correct positions, and the first result's `heuristic` property is true. The problem is that the view only selects the heuristic when it is the first result added [1]. That's not the case here, as just described.
[1] https://searchfox.org/mozilla-central/rev/cfd1cc461f1efe0d66c2fdc17c024a203d5a2fd8/browser/components/urlbar/UrlbarView.jsm#427
|
P1
|
RESOLVED
|
FIXED
|
2020-01-21 23:55:41+00:00
|
2020-01-30 02:43:42+00:00
| 219 | 1 |
1610812
|
Context menu is displayed wrong (on the right side) for the last Highlight from a row again
|
**Affected versions**
* 73.0b8, 74.0a1 (2020-01-21)
**Affected platforms**
* Windows 10, macOS 10.13, Ubuntu 18.04;
**Steps to reproduce**
1. Navigate to this link https://getpocket.cdn.mozilla.net/explore/trending?src=ff_new_tab and open ~25-30 different pages each in a new tab, in order to populate the Highlights section.
2. Restart the browser.
3. Click the "..." button for one of the Highlights on the last tile from a row.
**Expected result**
* context menu is opened on the left side;
**Actual result**
* context menu is opened on the right side, forcing the scrollbar to appear;
**Regression range**
* last good build_date: 2019-12-18;
* first bad build_date: 2019-12-19;
* pushlog [URL](https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f870bccd07eeedcde5f5e0ee290d6b2158934105&tochange=8e1b11b00157269f1f781753efc241e005efeaf1)
**Additional notes**
* 72.0.2 not affected;
* issue surfaced before as bug 1485633;
* best way to reproduce this is resizing the window to ~ half width of the screen.
|
Context menu is displayed wrong (on the right side) for the last Highlight from a row again **Affected versions**
* 73.0b8, 74.0a1 (2020-01-21)
**Affected platforms**
* Windows 10, macOS 10.13, Ubuntu 18.04;
**Steps to reproduce**
1. Navigate to this link https://getpocket.cdn.mozilla.net/explore/trending?src=ff_new_tab and open ~25-30 different pages each in a new tab, in order to populate the Highlights section.
2. Restart the browser.
3. Click the "..." button for one of the Highlights on the last tile from a row.
**Expected result**
* context menu is opened on the left side;
**Actual result**
* context menu is opened on the right side, forcing the scrollbar to appear;
**Regression range**
* last good build_date: 2019-12-18;
* first bad build_date: 2019-12-19;
* pushlog [URL](https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f870bccd07eeedcde5f5e0ee290d6b2158934105&tochange=8e1b11b00157269f1f781753efc241e005efeaf1)
**Additional notes**
* 72.0.2 not affected;
* issue surfaced before as bug 1485633;
* best way to reproduce this is resizing the window to ~ half width of the screen.
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-01-22 13:37:45+00:00
|
2020-02-25 20:50:43+00:00
| 378 | 3 |
1610865
|
"1/2.3 B" in urlbar shouldn't suggest "Visit http://0.0.0.1/2.3 B"
|
Can "1/2.3 B" be a valid URL? I think that typing/pasting it in urlbar and pressing enter should load results in default search engine instead of trying to load http://0.0.0.1/2.3 B as Firefox currently does.
|
"1/2.3 B" in urlbar shouldn't suggest "Visit http://0.0.0.1/2.3 B" Can "1/2.3 B" be a valid URL? I think that typing/pasting it in urlbar and pressing enter should load results in default search engine instead of trying to load http://0.0.0.1/2.3 B as Firefox currently does.
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-01-22 16:34:13+00:00
|
2020-02-21 04:07:22+00:00
| 102 | 3 |
1610923
|
Point npm run testmc to use mach to avoid error with linting
|
From inside /browser/components/newtab
If you try to run `npm run testmc`
You get and error:
```
Error: Cannot read config file: /home/scott/mozilla-central/.eslintrc.js
Error: ENOENT: no such file or directory, open 'tools/rewriting/ThirdPartyPaths.txt'
at Object.openSync (fs.js:443:3)
at Object.readFileSync (fs.js:343:35)
at Object.<anonymous> (/home/scott/mozilla-central/.eslintrc.js:37:9)
at Module._compile (/home/scott/mozilla-central/browser/components/newtab/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:690:17)
at require (/home/scott/mozilla-central/browser/components/newtab/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
Failed to parse JSON:
Unexpected end of JSON input
```
I ran a bisect and found https://bugzilla.mozilla.org/show_bug.cgi?id=1607172 to be the first instance of this issue.
|
Point npm run testmc to use mach to avoid error with linting From inside /browser/components/newtab
If you try to run `npm run testmc`
You get and error:
```
Error: Cannot read config file: /home/scott/mozilla-central/.eslintrc.js
Error: ENOENT: no such file or directory, open 'tools/rewriting/ThirdPartyPaths.txt'
at Object.openSync (fs.js:443:3)
at Object.readFileSync (fs.js:343:35)
at Object.<anonymous> (/home/scott/mozilla-central/.eslintrc.js:37:9)
at Module._compile (/home/scott/mozilla-central/browser/components/newtab/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:690:17)
at require (/home/scott/mozilla-central/browser/components/newtab/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
Failed to parse JSON:
Unexpected end of JSON input
```
I ran a bisect and found https://bugzilla.mozilla.org/show_bug.cgi?id=1607172 to be the first instance of this issue.
|
P1
|
RESOLVED
|
FIXED
|
2020-01-22 19:36:56+00:00
|
2020-02-04 01:50:29+00:00
| 451 | 1 |
1610932
|
Address bar stays in focus after clicking bookmark folder in bookmark toolbar
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
Have bookmarks toolbar visible under view > toolbars, and have a bookmark folder visible in the bookmark toolbar, such that it is not directly below the address bar
Click within the URL area of the address bar
Click on the bookmark folder in the bookmark toolbar. Also happens when you click the "more" dropdown button at the far right of the bookmark toolbar.
74.0a1 (2020-01-22) (64-bit)
Actual results:
The "popout" frame remains around the address bar, partially obstructing the bookmarks toolbar (see attached screenshot)
Expected results:
The address bar should return to its "out of focus" state as it would have been before clicking on the URL in the steps above.
|
Address bar stays in focus after clicking bookmark folder in bookmark toolbar User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
Have bookmarks toolbar visible under view > toolbars, and have a bookmark folder visible in the bookmark toolbar, such that it is not directly below the address bar
Click within the URL area of the address bar
Click on the bookmark folder in the bookmark toolbar. Also happens when you click the "more" dropdown button at the far right of the bookmark toolbar.
74.0a1 (2020-01-22) (64-bit)
Actual results:
The "popout" frame remains around the address bar, partially obstructing the bookmarks toolbar (see attached screenshot)
Expected results:
The address bar should return to its "out of focus" state as it would have been before clicking on the URL in the steps above.
|
P2
|
RESOLVED
|
INVALID
|
2020-01-22 20:11:33+00:00
|
2020-02-21 04:01:56+00:00
| 225 | 2 |
1610985
|
Hide the Microsoft Edge Legacy migrator when the browser isn't accessible to users
|
(Quoting Matthew N. [:MattN] from bug 1608513 comment #4)
> There's not an easy way to support all the possible configurations (Legacy Edge, side-by-side [SxS], and new Edge) on all Windows versions we support. I think the simplest path is to rename the legacy migrator to "Microsoft Edge Legacy" on all Windows versions. This may cause some confusion for users who are still migrating from it and don't have the Chromium Edge but I'm not sure addressing that is worth the complexity/time.
>
> One thing that probably wouldn't be hard to implement would be hiding the legacy migrator when the application is hidden from the user. Unfortunately the registry key mentioned at https://docs.microsoft.com/en-us/deployedge/microsoft-edge-sysupdate-access-old-edge#how-operating-system-os-changes-are-triggered (`SOFTWARE\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}\BrowserReplacement`) doesn't exactly match the one set on my Windows 10 VM (`HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}\BrowserReplacement`) so I think we should ask Microsoft how best to detect when Microsoft Edge Legacy should be hidden.
Mike, should I join the Microsoft-Mozilla mailing list or would you prefer to send an email asking how to detect when the old Microsoft Edge is hidden (due to the new Edge being installed without SxS mode) on Windows 7 - 10? Thanks
|
Hide the Microsoft Edge Legacy migrator when the browser isn't accessible to users (Quoting Matthew N. [:MattN] from bug 1608513 comment #4)
> There's not an easy way to support all the possible configurations (Legacy Edge, side-by-side [SxS], and new Edge) on all Windows versions we support. I think the simplest path is to rename the legacy migrator to "Microsoft Edge Legacy" on all Windows versions. This may cause some confusion for users who are still migrating from it and don't have the Chromium Edge but I'm not sure addressing that is worth the complexity/time.
>
> One thing that probably wouldn't be hard to implement would be hiding the legacy migrator when the application is hidden from the user. Unfortunately the registry key mentioned at https://docs.microsoft.com/en-us/deployedge/microsoft-edge-sysupdate-access-old-edge#how-operating-system-os-changes-are-triggered (`SOFTWARE\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}\BrowserReplacement`) doesn't exactly match the one set on my Windows 10 VM (`HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}\BrowserReplacement`) so I think we should ask Microsoft how best to detect when Microsoft Edge Legacy should be hidden.
Mike, should I join the Microsoft-Mozilla mailing list or would you prefer to send an email asking how to detect when the old Microsoft Edge is hidden (due to the new Edge being installed without SxS mode) on Windows 7 - 10? Thanks
|
P2
|
NEW
|
2020-01-22 22:42:44+00:00
|
2022-10-11 23:52:31+00:00
| 424 | 2 |
|
1611058
|
Rethink how send-tab falls back to the sync-based sendtab mechanism
|
If there's some intermittent server error sending a tab to Fenix, we fall back to the old sync command based mechanism - however, Fenix doesn't support this mechanism. Things like our VR products are probably in the same bucket.
It's probably time to consider if we should kill that fallback.
|
Rethink how send-tab falls back to the sync-based sendtab mechanism If there's some intermittent server error sending a tab to Fenix, we fall back to the old sync command based mechanism - however, Fenix doesn't support this mechanism. Things like our VR products are probably in the same bucket.
It's probably time to consider if we should kill that fallback.
|
P3
|
RESOLVED
|
FIXED
|
2020-01-23 04:18:05+00:00
|
2020-06-12 03:13:13+00:00
| 84 | 3 |
1611093
|
Proxy credentials show the "Discard" dialog for saving changes
|
**Affected versions**
Nightly 74.0a1 74.0a1 (2020-01-21) (64-bit)
Beta 73.0b8 (64-bit)
Release 72.0.2 (64-bit)
**Affected platforms**
Windows 10 x64
MacOS 10.15
**Steps to reproduce**
1. Launch Firefox
2. Set up manual Proxy configuration
3. Go to a site on the same tab to toggle the auth dialog
4. Enter valid credentials and save them
5. Go to about:logins
6. Edit the password and click on "Save Changes"
**Expected result**
The changes should be saved
**Actual Result**
The "Discard unsaved changes" dialog appears.
Clicking "Discard" will discard the changes
Clicking "Cancel" will **save** the changes
*This only happens to Proxy credentials, http, ftp and other credentials don't have this issue*
**Note**
Last good build was 71.0a1 (2019-09-17)
**Regression-Range**
Mozregression found Bug 1579184.
|
Proxy credentials show the "Discard" dialog for saving changes **Affected versions**
Nightly 74.0a1 74.0a1 (2020-01-21) (64-bit)
Beta 73.0b8 (64-bit)
Release 72.0.2 (64-bit)
**Affected platforms**
Windows 10 x64
MacOS 10.15
**Steps to reproduce**
1. Launch Firefox
2. Set up manual Proxy configuration
3. Go to a site on the same tab to toggle the auth dialog
4. Enter valid credentials and save them
5. Go to about:logins
6. Edit the password and click on "Save Changes"
**Expected result**
The changes should be saved
**Actual Result**
The "Discard unsaved changes" dialog appears.
Clicking "Discard" will discard the changes
Clicking "Cancel" will **save** the changes
*This only happens to Proxy credentials, http, ftp and other credentials don't have this issue*
**Note**
Last good build was 71.0a1 (2019-09-17)
**Regression-Range**
Mozregression found Bug 1579184.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-23 09:11:12+00:00
|
2022-09-19 06:06:08+00:00
| 258 | 1 |
1611161
|
Format numbers in the font size drop-down using mozIntl.NumberFormat
|
#### Affected versions:
ALL
#### Affected platforms:
ALL
#### Preconditions:
Install an AR build.
#### Steps:
1. Launch Firefox with a new profile using the AR build and go to about:preferences.
2. Scroll down to Language and Appearance section.
#### Actual result:
Font size drop-down displays western numerals. Default zoom drop-down displays eastern arabic numerals I think.
#### Expected result:
All drop-downs should display the numbers in the same format.
|
Format numbers in the font size drop-down using mozIntl.NumberFormat #### Affected versions:
ALL
#### Affected platforms:
ALL
#### Preconditions:
Install an AR build.
#### Steps:
1. Launch Firefox with a new profile using the AR build and go to about:preferences.
2. Scroll down to Language and Appearance section.
#### Actual result:
Font size drop-down displays western numerals. Default zoom drop-down displays eastern arabic numerals I think.
#### Expected result:
All drop-downs should display the numbers in the same format.
|
P3
|
NEW
|
2020-01-23 14:47:57+00:00
|
2022-10-11 23:52:42+00:00
| 138 | 3 |
|
1611179
|
Firefox Home - First Highlights tile does not immediately reflect correct bookmark name
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
1. Download the latest FF nightly. (No existing user data or bookmarks.)
2. Visit Wikipedia.org or any other site.
3. Bookmark the page via the star icon in the address bar. Give the bookmark a new name other than the title of the page, such as "WikipediaCustomName".
4. Navigate to Firefox Home via the home button and scroll to the Highlights section.
Actual results:
The name on the first Highlights tile is the default name, not the new name (e.g. "Wikipedia", not "WikipediaCustomName").
This only affects the first tile. Repeating the process with another website moves the first bookmark (Wikipedia) to a second tile, and that name updates to the correct name. However, the new first tile will have an incorrect name.
Refreshing the page has no effect. However, on restarting Firefox, the first tile's name updates to the correct name.
I'm not sure how this issue relates to "non-bookmark" Highlights tiles such as those for frequently visited sites.
Expected results:
As for all such tiles, the name on the first Highlights bookmark tile should always be the current bookmark name, not the default name.
|
Firefox Home - First Highlights tile does not immediately reflect correct bookmark name User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
1. Download the latest FF nightly. (No existing user data or bookmarks.)
2. Visit Wikipedia.org or any other site.
3. Bookmark the page via the star icon in the address bar. Give the bookmark a new name other than the title of the page, such as "WikipediaCustomName".
4. Navigate to Firefox Home via the home button and scroll to the Highlights section.
Actual results:
The name on the first Highlights tile is the default name, not the new name (e.g. "Wikipedia", not "WikipediaCustomName").
This only affects the first tile. Repeating the process with another website moves the first bookmark (Wikipedia) to a second tile, and that name updates to the correct name. However, the new first tile will have an incorrect name.
Refreshing the page has no effect. However, on restarting Firefox, the first tile's name updates to the correct name.
I'm not sure how this issue relates to "non-bookmark" Highlights tiles such as those for frequently visited sites.
Expected results:
As for all such tiles, the name on the first Highlights bookmark tile should always be the current bookmark name, not the default name.
|
P3
|
NEW
|
2020-01-23 15:57:26+00:00
|
2022-10-11 23:52:43+00:00
| 321 | 3 |
|
1611215
|
Length of items in address bar changes when I hit CMD for no clear reason
|
See video. I find this behaviour distracting every time I notice it!
|
Length of items in address bar changes when I hit CMD for no clear reason See video. I find this behaviour distracting every time I notice it!
|
P3
|
NEW
|
2020-01-23 17:39:04+00:00
|
2020-07-09 02:41:09+00:00
| 32 | 3 |
|
1611271
|
macOS Urlbar border is hard to make out
|
Bug 1606930 comment 6 points out that our macOS Urlbar border is not the right colour. This is because we're using `-moz-mac-focusring` for the colour, which is transparent. This doesn't look good with the new 1px border, especially on dark theme.
|
macOS Urlbar border is hard to make out Bug 1606930 comment 6 points out that our macOS Urlbar border is not the right colour. This is because we're using `-moz-mac-focusring` for the colour, which is transparent. This doesn't look good with the new 1px border, especially on dark theme.
|
P1
|
VERIFIED
|
FIXED
|
2020-01-23 20:53:04+00:00
|
2020-03-30 12:06:25+00:00
| 80 | 1 |
1611308
|
Some context menu items that modify values should be disabled for disabled form controls
|
The following menu items (which isn't an exhaustive list) should IMO be disabled on disabled form fields e.g. <input>:
* Cut
* Paste
* Fill Login/Password
* Use generated password…
* Spelling suggestions
Perhaps [`onEditable`](https://searchfox.org/mozilla-central/rev/e878e5b81bb319c141900ce9cfcde732df5c8449/browser/actors/ContextMenuChild.jsm#1046) should be false for `@disabled` fields like it is for `@readOnly`… but then that makes me think perhaps `SpellCheckHelper.EDITABLE` should also be `false` in this case…
Perhaps the spell checker underline should also be removed in this case?
|
Some context menu items that modify values should be disabled for disabled form controls The following menu items (which isn't an exhaustive list) should IMO be disabled on disabled form fields e.g. <input>:
* Cut
* Paste
* Fill Login/Password
* Use generated password…
* Spelling suggestions
Perhaps [`onEditable`](https://searchfox.org/mozilla-central/rev/e878e5b81bb319c141900ce9cfcde732df5c8449/browser/actors/ContextMenuChild.jsm#1046) should be false for `@disabled` fields like it is for `@readOnly`… but then that makes me think perhaps `SpellCheckHelper.EDITABLE` should also be `false` in this case…
Perhaps the spell checker underline should also be removed in this case?
|
P3
|
NEW
|
2020-01-23 23:27:35+00:00
|
2022-10-11 23:52:50+00:00
| 199 | 3 |
|
1611395
|
Start page/address bar search does not accept foreign coding
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Firefox starting search page and address bar (set to default) does not process special chars/letters for language selected in Mozilla. In this example Polish Language.
All special letters existing in Polish are not interpreted correctly when typed in and searched. Default browser search set to https://duckduckgo.com in this example.
Actual results:
I search for polish wording 'Piękne łąki' (trans. beautiful fields) from the address bar or Mozilla starting search page and then duckduckgo page opens automatically and shows search results for 'Piękne łąki'.
All special letters have been changed to ASCI number I believe.
Expected results:
The exact wording as typed should be sent to the website in this example 'Piękne łąki'.
|
Start page/address bar search does not accept foreign coding User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Firefox starting search page and address bar (set to default) does not process special chars/letters for language selected in Mozilla. In this example Polish Language.
All special letters existing in Polish are not interpreted correctly when typed in and searched. Default browser search set to https://duckduckgo.com in this example.
Actual results:
I search for polish wording 'Piękne łąki' (trans. beautiful fields) from the address bar or Mozilla starting search page and then duckduckgo page opens automatically and shows search results for 'Piękne łąki'.
All special letters have been changed to ASCI number I believe.
Expected results:
The exact wording as typed should be sent to the website in this example 'Piękne łąki'.
|
P5
|
RESOLVED
|
WORKSFORME
|
2020-01-24 10:24:06+00:00
|
2020-01-28 21:31:46+00:00
| 235 | 5 |
1611514
|
New-tab pocket recommendation thumbnails have visual artifacts introduced by our PNG-->JPEG post-processing
|
It seems the Pocket-powered recommendations on the New Tab Page are taking PNG images, downscaling & reencoding them as JPEG images, and using that lossy/visual-artifact-laden result for the thumbnail.
For photos this may be fine, but for simpler graphics, it looks pretty gross. See attached screenshot, which shows weird "halo"/"ghost" JPEG artifacts in a thumbnail for a simplisafe sponsored article.
If I right-click the image to get its URL, I can see that it is the following (which also shows the artifacts if I load it directly):
https://img-getpocket.cdn.mozilla.net/296x148/filters:format(jpeg):quality(60):no_upscale():strip_exif()/https%3A%2F%2Fs.zkcdn.net%2FAdvertisers%2F1d95cdbde5a74b448a6c7525cd7341ec.png
If I snip out and url-decode the last ~third of that URL, I can get the source image which is:
https://s.zkcdn.net/Advertisers/1d95cdbde5a74b448a6c7525cd7341ec.png
...which does not have any such artifacts.
|
New-tab pocket recommendation thumbnails have visual artifacts introduced by our PNG-->JPEG post-processing It seems the Pocket-powered recommendations on the New Tab Page are taking PNG images, downscaling & reencoding them as JPEG images, and using that lossy/visual-artifact-laden result for the thumbnail.
For photos this may be fine, but for simpler graphics, it looks pretty gross. See attached screenshot, which shows weird "halo"/"ghost" JPEG artifacts in a thumbnail for a simplisafe sponsored article.
If I right-click the image to get its URL, I can see that it is the following (which also shows the artifacts if I load it directly):
https://img-getpocket.cdn.mozilla.net/296x148/filters:format(jpeg):quality(60):no_upscale():strip_exif()/https%3A%2F%2Fs.zkcdn.net%2FAdvertisers%2F1d95cdbde5a74b448a6c7525cd7341ec.png
If I snip out and url-decode the last ~third of that URL, I can get the source image which is:
https://s.zkcdn.net/Advertisers/1d95cdbde5a74b448a6c7525cd7341ec.png
...which does not have any such artifacts.
|
P3
|
NEW
|
2020-01-24 21:06:14+00:00
|
2022-10-11 23:53:03+00:00
| 348 | 3 |
|
1611559
|
Cross-site and social trackers show up as "Allowed" in the Protections Panel with DFPI
|
STR:
1. Set `network.cookie.cookieBehavior` to 5.
2. Navigate to https://www.theatlantic.com/science/archive/2020/01/betelgeuse-supernova/605251/.
3. Open the Protections Panel.
Social media and cross-site trackers show up as Allowed instead of Blocked. This may confuse people who are testing DFPI and make them believe cookie blocking isn't working correctly...
|
Cross-site and social trackers show up as "Allowed" in the Protections Panel with DFPI STR:
1. Set `network.cookie.cookieBehavior` to 5.
2. Navigate to https://www.theatlantic.com/science/archive/2020/01/betelgeuse-supernova/605251/.
3. Open the Protections Panel.
Social media and cross-site trackers show up as Allowed instead of Blocked. This may confuse people who are testing DFPI and make them believe cookie blocking isn't working correctly...
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-01-25 01:33:33+00:00
|
2020-02-04 10:44:38+00:00
| 128 | 3 |
1611587
|
Bookmarks with no title might be reordered.
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Each time Firefox Sync syncs my data, all the bookmarks in my Bookmarks Toolbar, which are within separate folders, get mixed up.
Actual results:
All bookmarks in separate folders are all in ONE folder, the other folders then are empty + the position of the folders are mixed up as well.
Expected results:
No rearrangement of the bookmark folders an the bookmarks within the folders in the Bookmarks Toolbar.
|
Bookmarks with no title might be reordered. User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Each time Firefox Sync syncs my data, all the bookmarks in my Bookmarks Toolbar, which are within separate folders, get mixed up.
Actual results:
All bookmarks in separate folders are all in ONE folder, the other folders then are empty + the position of the folders are mixed up as well.
Expected results:
No rearrangement of the bookmark folders an the bookmarks within the folders in the Bookmarks Toolbar.
|
P3
|
UNCONFIRMED
|
2020-01-25 11:07:35+00:00
|
2022-10-11 23:53:12+00:00
| 156 | 3 |
|
1611598
|
Unable to change the start page to custom url if blank page is set via policy
|
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Set the start page via Policy (tested with GPO) to blank page.
Start Firefox and change start page from blank to custom URL.
Restart Firefox.
Actual results:
Firefox starts with blank page.
Expected results:
Firefox should start with custom URL.
|
Unable to change the start page to custom url if blank page is set via policy User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Set the start page via Policy (tested with GPO) to blank page.
Start Firefox and change start page from blank to custom URL.
Restart Firefox.
Actual results:
Firefox starts with blank page.
Expected results:
Firefox should start with custom URL.
|
P3
|
RESOLVED
|
DUPLICATE
|
2020-01-25 13:27:04+00:00
|
2020-05-07 19:16:46+00:00
| 125 | 3 |
1611605
|
Tabs did not get restored from previous session
|
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36 OPR/64.0.3417.92
Steps to reproduce:
Had several tabs open. Browser window open all night (8+ hours). Restore previous session is set to on in preferences.
output of uname -a
Linux brittney-HP-Notebook 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Actual results:
Woke up to find Firefox had closed. Restarted Firefox and it opened to start page https://start.ubuntu-mate.org/
No tabs were restored. Under History -> Recently closed tabs contains no info
Expected results:
Tabs from previously session should have been remembered and restored
|
Tabs did not get restored from previous session User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36 OPR/64.0.3417.92
Steps to reproduce:
Had several tabs open. Browser window open all night (8+ hours). Restore previous session is set to on in preferences.
output of uname -a
Linux brittney-HP-Notebook 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Actual results:
Woke up to find Firefox had closed. Restarted Firefox and it opened to start page https://start.ubuntu-mate.org/
No tabs were restored. Under History -> Recently closed tabs contains no info
Expected results:
Tabs from previously session should have been remembered and restored
|
P3
|
NEW
|
2020-01-25 14:06:09+00:00
|
2022-05-25 12:24:18+00:00
| 234 | 3 |
|
1611641
|
[regression] Opening a new tab should not override PRIMARY paste content
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
On a Linux system, select some short text.
Open a new tab.
Middle-click on empty URL-bar.
Actual results:
The current URL of the previous focused tab is pasted.
Expected results:
The short text you had selected should be pasted.
|
[regression] Opening a new tab should not override PRIMARY paste content User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
On a Linux system, select some short text.
Open a new tab.
Middle-click on empty URL-bar.
Actual results:
The current URL of the previous focused tab is pasted.
Expected results:
The short text you had selected should be pasted.
|
P5
|
RESOLVED
|
WORKSFORME
|
2020-01-25 20:45:18+00:00
|
2020-10-13 18:52:08+00:00
| 114 | 5 |
1611645
|
"Mozilla Firefox (Private Browsing)" tooltip appears when hovering over browser chrome in private windows, for example over urlbar search suggestions
|
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Open a private window.
Type "Firefox" in the UrlBar.
Hover over the search suggestions.
Actual results:
A "Mozilla Firefox (Private Browsing)" tooltip shows up.
Expected results:
This tooltip is distracting. Do not show it.
|
"Mozilla Firefox (Private Browsing)" tooltip appears when hovering over browser chrome in private windows, for example over urlbar search suggestions User Agent: Mozilla/5.0 (Windows NT 6.1; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Open a private window.
Type "Firefox" in the UrlBar.
Hover over the search suggestions.
Actual results:
A "Mozilla Firefox (Private Browsing)" tooltip shows up.
Expected results:
This tooltip is distracting. Do not show it.
|
P3
|
VERIFIED
|
FIXED
|
2020-01-25 22:01:48+00:00
|
2020-06-15 10:55:29+00:00
| 135 | 3 |
1611649
|
[regression] Middle-clicking in URL-bar should only paste PRIMARY buffer, even if clickSelectsAll is True
|
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
On a Linux system, ensure your `browser.urlbar.clickSelectsAll` option is set to True.
Select some short text.
Middle-click in your URL-bar.
Actual results:
The full current URL is pasted where you have clicked.
I.e., if you were on `http://example.url/my-page` an you have middle-clicked just after the last slash /, the new URL is now `http://example.url/http://example.url/my-pagemy-page`
Expected results:
The selected short text should be pasted where you have middle-clicked (as Firefox do when `browser.urlbar.clickSelectsAll` option is set to False).
Alternatively, the selected text could replace the current URL-bar content.
|
[regression] Middle-clicking in URL-bar should only paste PRIMARY buffer, even if clickSelectsAll is True User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
On a Linux system, ensure your `browser.urlbar.clickSelectsAll` option is set to True.
Select some short text.
Middle-click in your URL-bar.
Actual results:
The full current URL is pasted where you have clicked.
I.e., if you were on `http://example.url/my-page` an you have middle-clicked just after the last slash /, the new URL is now `http://example.url/http://example.url/my-pagemy-page`
Expected results:
The selected short text should be pasted where you have middle-clicked (as Firefox do when `browser.urlbar.clickSelectsAll` option is set to False).
Alternatively, the selected text could replace the current URL-bar content.
|
P5
|
RESOLVED
|
WORKSFORME
|
2020-01-25 22:59:36+00:00
|
2021-07-22 12:59:59+00:00
| 252 | 5 |
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 95