instruction
stringclasses 1
value | input
stringlengths 38
33k
⌀ | output
stringclasses 4
values | __index_level_0__
int64 0
3.49k
|
|---|---|---|---|
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9359460
Screenshot of DefaultPrompt and Callout.png
An edge case seen in dev that can be replicated with below steps:
Pre-Req
1. Set Firefox Nightly as not default browser
2. Create a new profile in latest Firefox Nightly and Open Firefox Nightly with new profile
3. Open about:preferences -> General -> Check open previous windows and tabs checkbox
4. Open about:config and set `browser.shopping.experience2023.enabled` as true
Steps
1. Open amazon PDP page and click `Yes try it` in shopping sidebar and exit by clicking x button, shows ‘Get back to review Checker whenever you see the price tag’ feature callout
2. Quit Firefox Nightly
3. Change System date and time to future say 2 days ahead
4. Launch again with the same profile
5. Default prompt and feature callout shows up together
Expected Result
Feature Callout and Default prompt doesn't display together
Actual Result
Feature Callout and Default prompt display together. Clicking on Feature Callout and Default Prompt or anywhere in web page doesn’t dismiss either of the dialog.
Clicking partially visible `Not Now` of Default prompt dismisses default prompt and than let feature Callout dismiss Feature Callout cannot be dismissed when shown with Set Firefox Default Prompt | Firefox | 0 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | ### Preconditions:
- Set the `browser.shopping.experience2023.enabled` - `TRUE`
- Set the `browser.shopping.experience2023.optedIn` - `0`
- Turn on a screen reader (i.e. NVDA on Windows OS)
### Steps to reproduce:
1. While the screen reader is running, reach the following link: https://www.amazon.com/dp/B07V6ZSHF4?th=1
2. Observe the announcement made by a screen reader
### Expected result:
* The user who cannot see the screen is made aware that there is an opt-in message:
* the screen reader announced the text of the opti-in message
* (preferred) and the keyboard focus is placed on the `Yes, try it` control (so pressing `Enter` would activate this control)
### Actual result:
* Screen reader is not announcing the opt-in message and the user who cannot see the sidebar would not be aware that there is, in fact, a new feature sidebar available for them to use (the screen reader would read the sidebar info at the very end of announcing the entire long product page content)
* NVDA user feedback:
> It turns out that it [the sidebar] did appear. I didn't realise it was a sidebar and there was no indication it had appeared, so I had no indication that I needed to focus the sidebar with f6 to access it. We probably need to figure out how to fix that; e.g. role="alert" or something so that it gets reported like doorhanger alerts.
### Recommended solution:
1. Move the programmatic (and visual) focus to the `Yes, try it` button on the sidebar when the sidebar appears for the user and shows the opt-in message. Make sure to keep the `role=alertdialog` ARIA role on the message container so the message is announced by a screen reader when the focus lands on the container's control. The onboarding Shopping sidebar is not easily discoverable with a screen reader | Firefox | 1 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | When the pdfjs feature callout tour is active, if you open a pdf in a new background tab and immediately navigate to it while it is still loading, the feature callout displayes a broken diamond and flashes a couple of times before finally loading appropriately. Feature callout temporarily is hidden and throws an error when immediately navigating to a new PDF tab | Firefox | 2 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9314686
broken_menu.png
Steps to reproduce:
1) Navigate to about:config
2) Set `browser.urlbar.resultMenu` to `true`
3) Navigate to https://github.com/gregorypappas/onDeleteSuggestion
4) Download and unzip the extension
5) Navigate to about:debugging -> This Firefox -> Temporary Extensions
6) Select 'Load Extension' and install the unzipped extension from step 4
7) Type `omni 123` in the address bar
8) Click the result menu button on one of the rows provided by the extension
Actual results:
The menu is empty
Expected results:
The menu is not empty [Omnibox API] Deletable suggestion result menu is broken | Firefox | 3 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9319401
2023-02-23_09h12_00.png
Affected versions:
- Nightly (112.0a1/20230222214030)
- Beta (111.0b4/20230221190142)
Description:
The RTAMO onboarding page design is cut at the bottom and along with it, the “Not Now” button. A small portion of the upper part of the button is still visible and can be clicked to expand the address bar i.e. functionality is not affected.
Steps to reproduce:
1. While using a VM with Windows, launch Edge or Chrome and access https://addons.mozilla.org
2. On AMO, access the page of any add-on and click the “Download Firefox and get the extension” button
3. Once the installer is downloaded, run it to install Firefox (This will install the latest Firefox Release 110.0)
4. After installation Firefox Release will launch and the RTAMO onboarding page will be displayed, the “Not Now” button being fully visible and none of the page contents being cut.
5. Open the installation folder of Firefox Release, locate the “postSigningData” file and copy it to Desktop.
6. Download and install the latest Firefox Nightly 112.0a1 and Firefox Beta 111.0b4
7. Open the installation folders of Nightly and Beta and paste the previously copied “postSigningData” file inside the folders.
8. Launch both Nightly and Beta and access about:welcome on the browsers
9. The RTAMO onboarding page will be displayed on both browsers, but the page design will be cut at the bottom along with the “Not Now” button. The upper part of the button is still visible and can be clicked.
Actual:
RTAMO onboarding page design is cut at the bottom along with the “Not Now” button.
Expected:
The RTAMO onboarding page contents are fully displayed. RTAMO onboarding page design is cut at the bottom along with the “Not Now” button | Firefox | 4 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Steps to reproduce:
Access https://www.jetbrains.com/idea/
Note: I asked my friend to test it. On fedora, with Xorg, it didn't crash, but it used a lot of CPU and lagged the whole computer. With Wayland, everything is fine. I'm using a VMWare VM.
Related crash report: https://crash-stats.mozilla.org/report/index/77169fdf-ddac-4683-ba93-a4fca0221229
It's worth noticing that all crashes happen in VM, specifically VMWare's VM.
Actual results:
The website started loading, and during the rendering, it crashed.
Expected results:
It should load the website normally. Mac and Windows version is fine, no issue at all. WebGL/PDF.js in VMWare VM: Main process crash in gbm_bo_get_fd | Core | 5 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | There's a subtle issue I unintentionally caused in bug 1809722. I haven't investigated the precise cause but I'm guessing the DOM changes or the absolute positioning messed up the dismiss button's transitions. It only fades in/out, it doesn't slide down with the rest of the content. Fix non-split spotlight's dismiss button's transition | Firefox | 6 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | [This string](https://searchfox.org/mozilla-central/rev/0c2945ad4769e2d4428c72e6ddd78d60eb920394/browser/locales/en-US/browser/newtab/asrouter.ftl#247) has double en dashes, but ([per Acorn](https://acorn.firefox.com/latest/content/punctuation.html#section-hyphens-and-dashes-c9)) it should have a single em dash `—`.
This isn't a critical issue and won't block the experiment. The string has already been translated, and translators have done their own thing with the dashes. So there's no need to change the ID to restart translation. We can just change the EN strings in-place, and let it ride the trains for 115 or 116.
The needed changes are very simple:
```diff
diff --git a/browser/locales/en-US/browser/newtab/asrouter.ftl b/browser/locales/en-US/browser/newtab/asrouter.ftl
index 6615a601fa70c..53b6515cec100 100644
--- a/browser/locales/en-US/browser/newtab/asrouter.ftl
+++ b/browser/locales/en-US/browser/newtab/asrouter.ftl
@@ -244,6 +244,6 @@ fxa-sync-cfr-secondary = Remind me later
## Device Migration FxA Spotlight
device-migration-fxa-spotlight-header = Using an older device?
-device-migration-fxa-spotlight-body = Back up your data to make sure you don’t lose important info like bookmarks and passwords –– especially if you switch to a new device.
+device-migration-fxa-spotlight-body = Back up your data to make sure you don’t lose important info like bookmarks and passwords — especially if you switch to a new device.
device-migration-fxa-spotlight-primary-button = How to back up my data
device-migration-fxa-spotlight-link = Remind me later
``` Wrong dashes in Device Migration Spotlight subtitle EN string | Firefox | 7 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9341549
Screen Shot 2023-06-28 at 8.30.10 AM.png
CFR default 'icon_and_message' layout is showing ratings section by default. This breaks all messages live with layout as 'icon_and_message'
https://experimenter.services.mozilla.com/nimbus/device-migration-existing-users-sumo-switch-device-cfr-rollout/summary
https://searchfox.org/mozilla-central/source/browser/components/newtab/lib/OnboardingMessageProvider.jsm#81
This issue seems to happen in same session after a CFR message with layout `addon_recommendation` is shown and is replicable in Fx114 and could be possible fallout of Bug 1825658 fix
STR:
1. Open about:newtab#devtools and [copy message](https://gist.github.com/punamdahiya/4a8d7808a96c0619dbef0a4558cb8c90) with layout 'addon_recommendation' and hit Show
https://experimenter.services.mozilla.com/nimbus/dictionary-addon-all-users/summary
2. Search for CFR message e.g `CFR_FULL_VIDEO_SUPPORT_EN ` with layout as `icon_and_message`. Click Show
Expected Result
Icon and Message shouldn't show ratings section CFR 'icon_and_message' layout broken after `addon_recommendation` CFR is shown | Firefox | 8 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36
Steps to reproduce:
1. Installed the new Nvidia 555 series drivers
2. Used Gnome 46.1 or another compositor with Explicit Sync support (kwin w/ some patches)
3. Run Firefox
Actual results:
Firefox crashes with:
```
$ firefox-nightly/firefox
[GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@59: error 4: No Acquire point provided
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
ExceptionHandler::GenerateDump cloned child 43927
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
```
Expected results:
Firefox runs Firefox crashes on Wayland with Explicit Sync on Nvidia | Core | 9 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | When using both the `no_rdm` and `reverse_split` properties in a spotlight screen with split layout, when responsive mode is entered at 800px the spotlight remains in it's full size (as intended), but the layout is un-reversed. This seems to be due to media queries throughout our CSS not appropriately handling the `no-rdm` property appropriately ([example](https://searchfox.org/mozilla-central/rev/8c3ca2f5a74e0ba59c3d9dddf5468a2ffab13467/browser/components/aboutwelcome/content-src/aboutwelcome.scss#827-837)). We should go through the css and add no-rdm negations to each of these media queries.
Alternatively, we could bypass the need for `no-rdm` negations in each of these media queries by leveraging something like a [MediaQueryList change event listener](https://developer.mozilla.org/en-US/docs/Web/API/MediaQueryList/change_event), and applying an attribute or class in the case of the `no_rdm` property being present in content, and ridding the css of media query no-rdm negations. reverse_split property styles are reverted at widths < 800px when no_rdm property is present | Firefox | 10 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9397896
Screenshot 2024-04-22 at 10.02.54 AM.png
When both a title and subtitle aren't included in a screen's content in the split layout for spotlight, the element that contains them is still rendered, which makes the flex layout behave strangely when there is no title or subtitle. "welcome-text" container is still rendered in the absence of title and subtitle | Firefox | 11 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | In order to address a bug with auto light/dark theming on MacOS we are creating light/dark counterpoints for all wallpapers. The thumbnails for onboarding are in-tree so we need to update those with the new images. Update wallpaper onboarding thumbnail images | Firefox | 12 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9368533
Screenshot 2023-12-13 at 4.53.11 PM.png
**Steps to Reproduce**
1. In `about:config`, set `browser.firefox-view.search.enabled` to `true`.
2. Open Firefox View.
3. If necessary, sign into Mozilla accounts in order to populate tabs from other devices.
4. In the search box, enter a search term that does not match any synced tab.
5. Clear out the search box.
**Expected Result**
The original tab lists are restored.
**Actual Result**
The tab lists are blanked out.
It appears that this has something to do with the new `updatesPaused` property introduced in [fxview-tab-list.mjs](https://searchfox.org/mozilla-central/source/browser/components/firefoxview/fxview-tab-list.mjs#240-247). When `shouldUpdate()` is commented out, the component appears to work as expected in this scenario. In Recent Browsing, entering and clearing a search term wipes out tabs from other devices | Firefox | 13 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9370190
poc.html
#Reproduce
OS:Win10 X64
123.0a1 (2023-12-19) (64-bit)
#Step:
1. python -m http.server 1337
2. python -m ffpuppet firefox.exe -p prefs.js -d -u http://localhost:1337/poc.html
#Analysis
missing boundary checks for `ticks + start, detune + start, end - start`
https://searchfox.org/mozilla-central/source/dom/media/webaudio/OscillatorNode.cpp#300
```
void ProcessBlock(AudioNodeTrack* aTrack, GraphTime aFrom,
const AudioBlock& aInput, AudioBlock* aOutput,
bool* aFinished) override {
MOZ_ASSERT(mSource == aTrack, "Invalid source track");
TRACE("OscillatorNodeEngine::ProcessBlock");
TrackTime ticks = mDestination->GraphTimeToTrackTime(aFrom);
if (mStart == -1) {
ComputeSilence(aOutput);
return;
}
if (ticks + WEBAUDIO_BLOCK_SIZE <= mStart || ticks >= mStop) {
ComputeSilence(aOutput);
} else {
aOutput->AllocateChannels(1);
float* output = aOutput->ChannelFloatsForWrite(0);
uint32_t start, end;
FillBounds(output, ticks, start, end);
float frequency[WEBAUDIO_BLOCK_SIZE];
float detune[WEBAUDIO_BLOCK_SIZE];
if (ParametersMayNeedUpdate()) {
if (mFrequency.HasSimpleValue()) {
std::fill_n(frequency, WEBAUDIO_BLOCK_SIZE, mFrequency.GetValue());
} else {
mFrequency.GetValuesAtTime(ticks + start, frequency + start,
end - start);
}
if (mDetune.HasSimpleValue()) {
std::fill_n(detune, WEBAUDIO_BLOCK_SIZE, mDetune.GetValue());
} else {
mDetune.GetValuesAtTime(ticks + start, detune + start, end - start);
}
}
``` stack-buffer-overflow webaudio/AudioEventTimeline.cpp:510 in AudioEventTimeline::GetValuesAtTimeHelperInternal | Core | 14 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Scope of this bug is to update shopping sidebar default width to 320px instead of 26.67em
See https://bugzilla.mozilla.org/show_bug.cgi?id=1865351#c19 Update Shopping Sidebar default width to use pixel value | Firefox | 15 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9370812
Incorrect date displayed in fr-doorhanger-milestone-heading2
This was mentioned by a German localizer and I was able to reproduce on my machine locally.
The string `cfr-doorhanger-milestone-heading2` should display that X number of trackers were blocked since the user profile began tracking blocked counters, e.g. `Nightly blocked over 1,000 trackers since May 2023!`. Instead, the string is displaying the current month and year (`Nightly blocked over 1,000 trackers since January 2024!`)
Steps to reproduce:
1) Create a new profile and open in Firefox
2) Visit a page with a tracking cookie (recommend `amazon.com`). This will create an entry in `protections.sqlite`
3) Use `about:support` to find the Profile Folder where your `protections.sqlite` file is saved
4) Quit Firefox to ensure `protections.sqlite` is editable
5) Use a sqlite database editor such as `DB Browser for SQLite` to open `protections.sqlite`
6) Find the first entry in the `events` table, edit the `count` column to `1000`, and the `datetime` column to something other than January 2024 (e.g. `2023-11-03`). Write the changes to the database and close your editor.
7) Open Firefox with the profile created in step 1
8) Navigate to `about:config`, create and set a config `browser.contentblocking.cfr-milestone.update-interval` and set the value as a number `10`
9) Navigate to `amazon.com`. Refresh the page until the string is triggered. (Should take around 3 refreshes.)
10) Observe the doorhanger (screenshot attached)
Similar strings (`graph-total-tracker-summary` and `protections-milestone`) show the date of earliest recorded blocked trackers as expected.
I've checked a previous bug (Bug 1687910) in which this string was changed, but was this fixed more than 3 years ago, so something must have changed in the code calling this string. Enhanced Tracking Protection milestone doorhanger shows incorrect date | Firefox | 16 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0
Steps to reproduce:
Users are reporting that Firefox keeps asking them to try Firefox View even after they've removed the toolbar button:
>Get recently closed tabs back with Firefox View
The only options are `Try it` and `Not now`, which confuses users who simply don't want to try it. Don't nag users about Firefox View | Firefox | 18 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Affected versions:
- Nightly (99.0a1/20220306190604)
[Steps to reproduce]:
1. Access AMO Prod on a browser different from Firefox (example: Microsoft Edge) and afterwards the page of a recommended extension/theme.
2. Click on the “Download Firefox and get the extension/theme” blue button
3. A new page opens in the same tab and Firefox Release is automatically downloaded
4. Install the previously downloaded Firefox Release.
Note: After installation is complete, the browser will be automatically launched.
5. Close the browser.
6. Download and install the latest Nightly.
7. Launch Nightly and access about:welcome.
8. Observe that the RTAMO page loads, however the served add-on has it’s name replaced by a placeholder “{$addon-name}”.
[Expected results]:
The RTAMO about:welcome page should properly fetch the extension/theme name.
[Actual results]:
The RTAMO about:welcome page does not fetch the add-on name, instead it displays a placeholder - “{$addon-name}”.
For further details, see the attached screenshots.
NOTE:
I’ve also checked the latest Beta using the same STR as above and it’s not affected – the extension/theme names are properly fetched and displayed. RTAMO onboarding page does not fetch the extension/theme name on Nightly | Firefox | 19 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | More From Mozilla section is missing a hidden attribute , which is causing this newly added section to show up below the fold on about:preferences refresh or accessing via url
STR
1. Click Application Menu -> Settings
2. Open about:preferences with 'More From Mozilla' section below the fold
Fix is to add hidden=true for moreFromMozillaCategory here https://searchfox.org/mozilla-central/source/browser/components/preferences/moreFromMozilla.inc.xhtml#12 More from Mozilla section shows up below the fold when accessing settings/preferences | Firefox | 20 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | During review, mstriemer found that the `Get VPN`/`Get Rally` buttons don't work with the keyboard focus then enter/space. They react to space as if they should work but nothing happens.
Suggested fix: Switch to an <a> most likely, there should be a button-link class or something to style that correctly.
Neither Mark nor I could find any general classes that were available to everyone, but there were lots of bespoke implementations in various modules:
Mark said that it needs to be backported from proclient.
mstriemer:
> So yeah we’d want a different bug; I can file that later and you can just fix it however you’d like. Make "Get VPN" / "Get Rally` buttons keyboard accessibe | Firefox | 21 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | macOS Big Sur 11.2.3, M1 Air
Download a file.
Expand the download menu in the toolbar. Right-click the file, "Show in Finder".
Expected: Finder opens, similar to clicking the magnifying glass icon.
Actual: No effect. "Show in Finder" and other context menu items in the Downloads panel that operate on a single download are nonfunctional. | Firefox | 22 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | I'm not aware of any user-facing breakage caused by this, but it is a theoretical issue that is worth fixing.
Steps to reproduce:
1. Be on macOS, and set `widget.macos.native-context-menus` and `browser.proton.contextmenus.enabled` to true.
2. Use a build which contains the fixes for bug 1700715.
3. Open a menu by right-clicking the toolbar.
4. Right-click the toolbar again, in a different place, so that the same context menu is shown elsewhere.
Expected results:
The popuphiding + popuphidden events for the old menu should be fired before the call to ShowPopup, and ideally also before the contextmenu event starts.
Actual results:
The popuphiding + popuphidden events fire during ShowPopup which is called while handling the contextmenu event. popuphiding / popuphidden events can be dispatched during ShowPopup if the same native context menu is reopened | Core | 23 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Steps to reproduce:
1. In a build with the patch for bug 1700371, go to toolbar customization.
2. In the macOS system accessibility Display preferences, enable Increase contrast.
3. In the macOS system general preferences, set the system to Light Mode.
4. In Firefox in toolbar customization, using the Themes dropdown at the bottom, switch to the dark Firefox theme.
5. Notice how the buttons in the bottom right corner are drawn transparently.
6. Move your mouse over those buttons.
Expected results:
The buttons should pick one look and stick with it.
Actual results:
The buttons redraw with an opaque white background once hovered.
The bug here is that they draw transparently at all - if the system is set to Light Mode, or if `widget.macos.respect-system-appearance` is `false`, they should always be drawn with the Aqua appearance, which has an opaque white background.
It looks like they only draw transparently because they draw just after the window background itself is drawn. When the window background is drawn, since the window is set to the dark appearance, the global NSAppearance.currentAppearance is set to dark, and our native theme drawing seems to be affected by NSAppearance.currentAppearance. Inconsistent native button drawing in windows with overridden appearance | Core | 24 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | When I load `about:studies`, the page is page. I see the following error in the web console:
```
Uncaught TypeError: can't convert undefined to object
render resource://normandy-content/about-studies/about-studies.js:428
_renderValidatedComponentWithoutOwnerOrContext resource://normandy-vendor/ReactDOM.js:18
_renderValidatedComponent resource://normandy-vendor/ReactDOM.js:18
performInitialMount resource://normandy-vendor/ReactDOM.js:18
mountComponent resource://normandy-vendor/ReactDOM.js:18
mountComponent resource://normandy-vendor/ReactDOM.js:5
mountChildren resource://normandy-vendor/ReactDOM.js:18
_createInitialChildren resource://normandy-vendor/ReactDOM.js:18
mountComponent resource://normandy-vendor/ReactDOM.js:18
mountComponent resource://normandy-vendor/ReactDOM.js:5
mountChildren resource://normandy-vendor/ReactDOM.js:18
_createInitialChildren resource://normandy-vendor/ReactDOM.js:18
mountComponent resource://normandy-vendor/ReactDOM.js:18
mountComponent resource://normandy-vendor/ReactDOM.js:5
performInitialMount resource://normandy-vendor/ReactDOM.js:18
mountComponent resource://normandy-vendor/ReactDOM.js:18
mountComponent resource://normandy-vendor/ReactDOM.js:5
mountChildren resource://normandy-vendor/ReactDOM.js:18
_createInitialChildren resource://normandy-vendor/ReactDOM.js:18
mountComponent resource://normandy-vendor/ReactDOM.js:18
mountComponent resource://normandy-vendor/ReactDOM.js:5
_updateRenderedComponent resource://normandy-vendor/ReactDOM.js:18
_performComponentUpdate resource://normandy-vendor/ReactDOM.js:18
updateComponent resource://normandy-vendor/ReactDOM.js:18
performUpdateIfNecessary resource://normandy-vendor/ReactDOM.js:18
performUpdateIfNecessary resource://normandy-vendor/ReactDOM.js:5
i resource://normandy-vendor/ReactDOM.js:5
perform resource://normandy-vendor/ReactDOM.js:5
perform resource://normandy-vendor/ReactDOM.js:5
perform resource://normandy-vendor/ReactDOM.js:5
v resource://normandy-vendor/ReactDOM.js:5
closeAll resource://normandy-vendor/ReactDOM.js:5
perform resource://normandy-vendor/ReactDOM.js:5
batchedUpdates resource://normandy-vendor/ReactDOM.js:18
d resource://normandy-vendor/ReactDOM.js:5
o resource://normandy-vendor/ReactDOM.js:18
enqueueSetState resource://normandy-vendor/ReactDOM.js:18
setState resource://normandy-vendor/React.js:5
handleEvent resource://normandy-content/about-studies/about-studies.js:66
about-studies.js:428:60
```
My about:telemetry Experiment Data says I'm enrolled in the following experiments:
```
rollout-doh-nightly-rollout-to-all-us-desktop-users-nightly-74-80-bug-1613481.branch active
rollout-doh-nightly-rollout-to-all-us-desktop-users-nightly-74-80-bug-1613481.type normandy-prefrollout
rollout-doh-nightly-rollout-to-all-us-desktop-users-nightly-74-80-bug-1613481.enrollmentId f3157ac7-4f39-d64e-b734-07f6dd2b15a8
```
I filed bug 1699761 about a similar "`about:studies` is blank" error and that bug was fixed. Might this bug be a similar compatibilty case that the fix didn't handle? Or a side effect of the fix? about:studies page is blank: Uncaught TypeError: can't convert undefined to object | Firefox | 25 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0
Steps to reproduce:
1. On a system with microphone and webcam attached on a GNOME Wayland session go to https://meet.jit.si and open a meeting.
2. Firefox asks for permission to use the microphone and webcam.
3. Grant permission
Actual results:
A small new Firefox windows appears with the title Firefox - Sharing Indicator. This small window shows that the camera and microphone are in use.
Expected results:
The sharing indicator should appear on top of the desktop (or somewhere else) but preferably not in a new window that sometimes get out if sight behind other windows. In Xorg the indicator is visible at the top of the window or desktop. [Wayland] Sharing indicator is in new window | Core | 27 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | The fill color we end up with is an rgba() value, with 0.7 in the alpha channel. This should be 1 (full opacity). Toolbar icons in dark and light themes have 70% opacity | Firefox | 28 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9220472
signal-2021-05-05-161102.jpeg
User Agent: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.7113.93 Safari/537.36
Steps to reproduce:
Specs:
- Gnome 40 (Garuda Linux)
Steps:
1. Right click anywhere on the page.
Actual results:
The right-click menu has a transparent background.
Expected results:
The right-click menu should have an opaque background.
Mozregression output:
app_name: firefox
build_date: 2021-04-28 00:43:00.344000
build_file: /home/rk/.mozilla/mozregression/persist/48f696159514--autoland--target.tar.bz2
build_type: integration
build_url: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Lj6NbIBfQwyquPh3K2gjMg/runs/0/artifacts/public%2Fbuild%2Ftarget.tar.bz2
changeset: 48f696159514ffbc64ca6cc9c1800efb83184809
pushlog_url: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=91e9b4e787511a09cf76a9499acb18421194ad9a&tochange=48f696159514ffbc64ca6cc9c1800efb83184809
repo_name: autoland
repo_url: https://hg.mozilla.org/integration/autoland
task_id: Lj6NbIBfQwyquPh3K2gjMg
It could have something to do with this bug (Bug 1707992). Transparent context menu background on right click (Linux Gnome 40) | Core | 29 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9213533
Actual vs Expected.png
**Affected versions**
Firefox Nightly 89.0a1
**Preconditions**
browser.proton.enabled= *true*
browser.proton.infobars.enabled= *true*
**Steps to reproduce**
1. Launch Firefox Nightly
2. Navigate to https://permission.site
3. Click on "Protocol Handler"
**Expected Results**
The Protocol handler informational infobar appears properly and has the correct (!) icon
**Actual Results**
The informational infobar's icon is not the correct one Informational infobars have the wrong (i) icon on Proton | Firefox | 31 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Bug 1728853 introduced reverting to previous theme on secondary button of second screen. This waits for the `AddonManager.getAddonsByTypes` promise to resolve before continuing to the next screen. This allows additional clicks to be handled concurrently and that breaks things.
https://searchfox.org/mozilla-central/rev/0998b61022a1ece43afe3c750077e5804c6c6392/browser/base/content/upgradeDialog.js#324-326 Quickly clicking "explore colorways" then "keep previous" twice makes upgrade spotlight stuck | Firefox | 34 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9242971
firefox-out-of-memory.zip
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0
Steps to reproduce:
Firefox 93.0b9 (64-bit) on Windows 10.
Using JS code with set of mixins and defined Reflect properties cause "Uncaught out of memory" console crash with empty call stack.
Setting `javascript.options.baselinejit` to `false` or setting a bigger number for
`javascript.options.baselinejit.threshold` (like `1000`) solves the issue.
The attached JS script shows the problem.
It is a bit synthetic but we face the exact same error in production code for a real project.
```
const
{ getPrototypeOf } = Object,
{ defineProperty } = Reflect,
{ hasOwnProperty } = Object.prototype,
metaSymbol = Symbol('classMetaData'),
Mixin = Target => class extends Target {},
MixinFoo = Target => class extends Target {
get foo() { }
set foo(value) { }
};
class Base {
/*
* An object owned by this class that does not share properties with its super class.
*/
static get $meta() {
const me = this;
let meta = me[metaSymbol];
if (!hasOwnProperty.call(me, metaSymbol)) {
me[metaSymbol] = meta = {
class : me,
super : getPrototypeOf(me).$meta
};
defineProperty(meta.class.prototype, '$meta', {
value : meta
});
}
return meta;
}
}
class MyClass extends (Mixin(Mixin(Mixin(Mixin(Mixin(Mixin(Mixin(Mixin(Mixin(Mixin(Mixin(MixinFoo(Base))))))))))))) {}
const
instance = new MyClass(),
arr = [...Array(1000).keys()].map(() => {
return instance.foo || MyClass.$meta.foo;
});
console.log(`OK. ${arr.length}`);
```
Actual results:
Crash with "Uncaught out of memory" in console.
Expected results:
Expected no error to happen.
Output `OK. 1000` in console. Uncaught out of memory (OOM) crash with Baseline JIT enabled | Core | 35 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9243986
screenshot
The outline of the focused find bar is clipped on the left side. This is a regression from bug 1728368 in Firefox 92.0.1 - Firefox 92.0 was not affected. Firefox Nightly is still affected. The issue could be reproduced in the Firefox support by users with Windows 10, Windows 7 and macOS (other platforms were not tested). focused find bar outline is clipped on the left side | Toolkit | 36 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9244333
Tab border on Windows 10 at 150% UI scale
As the attachment shows the border around a tab is thicker on the bottom and right, and thinner on the top and left side.
This shows on Windows 10 if UI is scaled to 150% - which is Windows default for my display. _(Not sure how frequent that is the case across all Windows devices - I don't think we have telemetry on that scale)_
This issue does not show on 100% or 200% UI scale, nor does it show on Mac no matter what scale is used there. In all those instances the border has the same thickness all around. Tab border thicker on 2 sides then on the other 2 | Firefox | 37 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | After deprecating .enabled in experimenter, we discovered messaging system is still using the old property. We should update it to use `feature.variables.enabled` Messaging system should use feature.variables.enabled, not feature.enabled | Firefox | 38 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9241220
image.png
Google Docs appears to have started pushing canvas backed google docs by default for some documents. See an example here (Most Mozilla accounts seem to be getting canvas backed GDocs on this doc):
https://docs.google.com/document/d/1-DkkjJ069KD8mJOcl5MW6jJkfbRV_kNbx1aTb6mngcY/edit#
We're seeing very poor Glyph rendering (kerning/hinting and AA/gamma). See attached image. As far as we can tell this is happening everywhere where we're using Windows an D2D canvas, and this may be somewhat worse when using DPI scaling. GDocs has very poor glyph rendering with D2D canvas | Core | 39 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | The "Save To Pocket" button sits in an overflow panel in the main toolbar. It is now completely empty for me on a M1 Macbook Air.
This does not reproduce on a clean profile.
Bisecting gets to the following range, at which point all builds start crashing on startup:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c11d60ea8989f78f258f4e30a968a779af737436&tochange=06d659a9bb93bf87ed51070d6a861e6e60bff6d7
This contains: https://bugzilla.mozilla.org/show_bug.cgi?id=1693582
Which seems highly relevant. "Save To Pocket" panel is empty when launched from overflow menu | Firefox | 40 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | per :ayeddi -
- "The dialog does not follow the HCM styling for controls on hover: Close and Next/Got it! should have their colors reversed on hover, but the Close icon disappears on Win and is almost invisible on mac."
- "Next does not follow Windows HCM colors for buttons: expected to use ButtonText and ButtonFace, but the outline is using text color (white on WinOS 11 Night Sky HCM, as an example, while yellow is expected)"
See featureCallout.mjs for feature callout code.
See [here](https://searchfox.org/mozilla-central/source/browser/components/newtab/content-src/aboutwelcome/components/MultiStageProtonScreen.jsx) in AboutWelcome for screen content code. Ensure Feature Callout messages are accessible in HCM (High Contrast Mode) | Firefox | 41 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | STR:
1) Enable PDF.js editing by setting pdfjs.annotationEditorEnabled to true
2) Draw something somewhere
3) Select what you drew
4) Press CTRL+C
5) Press CTRL+V
When pasting, sometimes the pasted content is empty or has artifacts.
It is easily reproducible if you press CTRL+V, then CTRL+Z to cancel the paste, then CTRL+V again in a loop. Pasted objects in pdf.js editor are sometimes empty or show rendering artifacts | Core | 42 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Perfherder has detected a build_metrics performance regression from push [f26005b20a7e23bdf825abe98bb039fa632f9f0f](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=f26005b20a7e23bdf825abe98bb039fa632f9f0f). As author of one of the patches included in that push, we need your help to address this regression.
### Regressions:
| **Ratio** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**|
|--|--|--|--|--|
| [0.16%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,1921012,1,2) | installer size | osx-shippable | nightly | 84,201,100.96 -> 84,337,887.50 |
| [0.10%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,2259234,1,2) | installer size | osx-shippable | instrumented | 120,508,702.79 -> 120,624,789.33 |
| [0.06%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,1921012,1,2) | installer size | osx-shippable | nightly | 84,242,426.17 -> 84,292,952.67 |
Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=35165), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) may be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/).
For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ). 0.16 - 0.06% installer size / installer size + 1 more (OSX) regression on Tue August 16 2022 | Firefox | 43 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | [Central-as-beta simulation](https://treeherder.mozilla.org/jobs?repo=try&group_state=expanded&selectedTaskRun=L3l-oJUPSG-lTOLaBilZAg.0&resultStatus=testfailed%2Cbusted%2Cexception&fromchange=118b9eece81ec02330f49a485a7b9ae492d6c709&tochange=118b9eece81ec02330f49a485a7b9ae492d6c709&searchStr=x)
[How to run these simulations](https://wiki.mozilla.org/Sheriffing/How_To/Beta_simulations#TRUNK_AS_EARLY_BETA)
[Failure log:](https://treeherder.mozilla.org/logviewer?job_id=387958866&repo=try&lineNumber=4102)
```
[task 2022-08-20T14:04:55.739Z] 14:04:55 INFO - TEST-START | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js
[task 2022-08-20T14:04:56.190Z] 14:04:56 WARNING - TEST-UNEXPECTED-FAIL | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | xpcshell return code: 0
[task 2022-08-20T14:04:56.190Z] 14:04:56 INFO - TEST-INFO took 450ms
[task 2022-08-20T14:04:56.190Z] 14:04:56 INFO - >>>>>>>
[task 2022-08-20T14:04:56.191Z] 14:04:56 INFO - PID 25592 | [Parent 25592, Main Thread] WARNING: Couldn't get the user appdata directory. Crash events may not be produced.: file /builds/worker/checkouts/gecko/toolkit/crashreporter/nsExceptionHandler.cpp:2914
[task 2022-08-20T14:04:56.192Z] 14:04:56 INFO - (xpcshell/head.js) | test MAIN run_test pending (1)
[task 2022-08-20T14:04:56.192Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 0 pending (2)
[task 2022-08-20T14:04:56.192Z] 14:04:56 INFO - (xpcshell/head.js) | test MAIN run_test finished (2)
[task 2022-08-20T14:04:56.192Z] 14:04:56 INFO - running event loop
[task 2022-08-20T14:04:56.200Z] 14:04:56 INFO - browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | Starting test_OnboardingMessageProvider_getUpgradeMessage_no_pin
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getUpgradeMessage_no_pin pending (2)
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 0 finished (2)
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - TEST-PASS | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | test_OnboardingMessageProvider_getUpgradeMessage_no_pin - [test_OnboardingMessageProvider_getUpgradeMessage_no_pin : 15] Screen has pin screen id - "UPGRADE_PIN_FIREFOX" == "UPGRADE_PIN_FIREFOX"
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - TEST-PASS | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | test_OnboardingMessageProvider_getUpgradeMessage_no_pin - [test_OnboardingMessageProvider_getUpgradeMessage_no_pin : 20] Primary button has pin action type - "PIN_FIREFOX_TO_TASKBAR" == "PIN_FIREFOX_TO_TASKBAR"
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 1 pending (2)
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getUpgradeMessage_no_pin finished (2)
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | Starting test_OnboardingMessageProvider_getUpgradeMessage_pin_no_default
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getUpgradeMessage_pin_no_default pending (2)
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 1 finished (2)
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - TEST-PASS | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | test_OnboardingMessageProvider_getUpgradeMessage_pin_no_default - [test_OnboardingMessageProvider_getUpgradeMessage_pin_no_default : 38] Screen has make default screen id - "UPGRADE_ONLY_DEFAULT" == "UPGRADE_ONLY_DEFAULT"
[task 2022-08-20T14:04:56.201Z] 14:04:56 INFO - TEST-PASS | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | test_OnboardingMessageProvider_getUpgradeMessage_pin_no_default - [test_OnboardingMessageProvider_getUpgradeMessage_pin_no_default : 43] Primary button has make default action - "SET_DEFAULT_BROWSER" == "SET_DEFAULT_BROWSER"
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 2 pending (2)
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getUpgradeMessage_pin_no_default finished (2)
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | Starting test_OnboardingMessageProvider_getUpgradeMessage_pin_and_default
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getUpgradeMessage_pin_and_default pending (2)
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 2 finished (2)
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - TEST-PASS | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | test_OnboardingMessageProvider_getUpgradeMessage_pin_and_default - [test_OnboardingMessageProvider_getUpgradeMessage_pin_and_default : 61] Screen has get started screen id - "UPGRADE_GET_STARTED" == "UPGRADE_GET_STARTED"
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - TEST-PASS | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | test_OnboardingMessageProvider_getUpgradeMessage_pin_and_default - [test_OnboardingMessageProvider_getUpgradeMessage_pin_and_default : 66] Primary button has no action type - true == true
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 3 pending (2)
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getUpgradeMessage_pin_and_default finished (2)
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | Starting test_OnboardingMessageProvider_getNoImport_default
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getNoImport_default pending (2)
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 3 finished (2)
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - TEST-PASS | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | test_OnboardingMessageProvider_getNoImport_default - [test_OnboardingMessageProvider_getNoImport_default : 82] Screen has no import screen id - "UPGRADE_MOBILE_DOWNLOAD" != "UPGRADE_IMPORT_SETTINGS"
[task 2022-08-20T14:04:56.202Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 4 pending (2)
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getNoImport_default finished (2)
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | Starting test_OnboardingMessageProvider_getImport_nodefault
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getImport_nodefault pending (2)
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 4 finished (2)
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - TEST-PASS | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | test_OnboardingMessageProvider_getImport_nodefault - [test_OnboardingMessageProvider_getImport_nodefault : 102] Screen has import screen id - "UPGRADE_IMPORT_SETTINGS" == "UPGRADE_IMPORT_SETTINGS"
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 5 pending (2)
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getImport_nodefault finished (2)
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | Starting test_OnboardingMessageProvider_getPinPrivateWindow_noPrivatePin
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - (xpcshell/head.js) | test test_OnboardingMessageProvider_getPinPrivateWindow_noPrivatePin pending (2)
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - (xpcshell/head.js) | test run_next_test 5 finished (2)
[task 2022-08-20T14:04:56.203Z] 14:04:56 WARNING - TEST-UNEXPECTED-FAIL | browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | test_OnboardingMessageProvider_getPinPrivateWindow_noPrivatePin - [test_OnboardingMessageProvider_getPinPrivateWindow_noPrivatePin : 128] Screen has pin private window screen id - "UPGRADE_GRATITUDE" == "UPGRADE_PIN_PRIVATE_WINDOW"
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - /builds/worker/workspace/build/tests/xpcshell/tests/browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js:test_OnboardingMessageProvider_getPinPrivateWindow_noPrivatePin:128
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - /builds/worker/workspace/build/tests/xpcshell/head.js:_do_main:238
[task 2022-08-20T14:04:56.203Z] 14:04:56 INFO - /builds/worker/workspace/build/tests/xpcshell/head.js:_execute_test:595
[task 2022-08-20T14:04:56.204Z] 14:04:56 INFO - -e:null:1
[task 2022-08-20T14:04:56.204Z] 14:04:56 INFO - exiting test
[task 2022-08-20T14:04:56.204Z] 14:04:56 INFO - Unexpected exception NS_ERROR_ABORT:
[task 2022-08-20T14:04:56.204Z] 14:04:56 INFO - _abort_failed_test@/builds/worker/workspace/build/tests/xpcshell/head.js:866:20
[task 2022-08-20T14:04:56.204Z] 14:04:56 INFO - do_report_result@/builds/worker/workspace/build/tests/xpcshell/head.js:967:5
[task 2022-08-20T14:04:56.204Z] 14:04:56 INFO - Assert<@/builds/worker/workspace/build/tests/xpcshell/head.js:73:21
[task 2022-08-20T14:04:56.204Z] 14:04:56 INFO - proto.report@resource://testing-common/Assert.jsm:228:10
[task 2022-08-20T14:04:56.204Z] 14:04:56 INFO - equal@resource://testing-common/Assert.jsm:270:8
[task 2022-08-20T14:04:56.204Z] 14:04:56 INFO - test_OnboardingMessageProvider_getPinPrivateWindow_noPrivatePin@/builds/worker/workspace/build/tests/xpcshell/tests/browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js:128:12
[task 2022-08-20T14:04:56.204Z] 14:04:56 INFO - _do_main@/builds/worker/workspace/build/tests/xpcshell/head.js:238:6
[task 2022-08-20T14:04:56.205Z] 14:04:56 INFO - _execute_test@/builds/worker/workspace/build/tests/xpcshell/head.js:595:5
[task 2022-08-20T14:04:56.205Z] 14:04:56 INFO - @-e:1:1
[task 2022-08-20T14:04:56.206Z] 14:04:56 INFO - exiting test
[task 2022-08-20T14:04:56.207Z] 14:04:56 INFO - PID 25592 | [Parent 25592, Main Thread] WARNING: Extra shutdown CC: 'i < NORMAL_SHUTDOWN_COLLECTIONS', file /builds/worker/checkouts/gecko/xpcom/base/nsCycleCollector.cpp:3359
[task 2022-08-20T14:04:56.207Z] 14:04:56 INFO - PID 25592 | [Parent 25592, Main Thread] WARNING: OOPDeinit() without successful OOPInit(): file /builds/worker/checkouts/gecko/toolkit/crashreporter/nsExceptionHandler.cpp:3371
[task 2022-08-20T14:04:56.208Z] 14:04:56 INFO - PID 25592 | [Parent 25592, Main Thread] WARNING: NS_ENSURE_TRUE(Preferences::InitStaticMembers()) failed: file /builds/worker/checkouts/gecko/modules/libpref/Preferences.cpp:4604
[task 2022-08-20T14:04:56.209Z] 14:04:56 INFO - PID 25592 | [Parent 25592, Main Thread] WARNING: XPCOM object PerThreadData destroyed from static ctor/dtor: file /builds/worker/checkouts/gecko/xpcom/base/nsTraceRefcnt.cpp:206
[task 2022-08-20T14:04:56.212Z] 14:04:56 INFO - PID 25592 | [Parent 25592, Main Thread] WARNING: XPCOM object SourceList destroyed from static ctor/dtor: file /builds/worker/checkouts/gecko/xpcom/base/nsTraceRefcnt.cpp:206
[task 2022-08-20T14:04:56.212Z] 14:04:56 INFO - <<<<<<<
[task 2022-08-20T14:04:56.212Z] 14:04:56 INFO - TEST-START | toolkit/crashreporter/test/unit_ipc/test_content_memory_list.js
```
Hello Punam, could you take a look at this failure? It seems to be regressed by Bug 1783751. Perma early beta browser/components/newtab/test/xpcshell/test_OnboardingMessageProvider.js | single tracking bug when Gecko 105 merges to Beta on 2022-08-22 | Firefox | 44 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9235627
navbar.gif
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
I updated to version 91.
Actual results:
The text of the tabs cannot be read, nor is the separation between them distinguished.
Expected results:
The different tabs must be readable and distinguishable.
This defect appeared in version 90, until now it had been solved by disabling proton but apparently they removed that option and did not fix the problem. [Windows 8] The text of the tabs cannot be read when using the dark theme | Firefox | 45 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Enrollments don't have a `featureIds` property. The fix in bug 1714449 needs to be changed to use the branch feature information. Use enrollment branch information for startup onUpdate notifications | Firefox | 46 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:98.0) Gecko/20100101 Firefox/98.0
Steps to reproduce:
1. Go to https://holodex.net/
2a. Try using control click on a Video's Title section.
2b. Try using control click on a channel name inside any Video Card.
Actual results:
2a: observe that 2 tabs were opened of the video.
2b: observe that 3 tabs were opened of that channel.
Tested on Firefox 98.
(Users report they also observed this behavior on Firefox 99, and 100)
Expected results:
2a: one tab opens of the video.
2b: one tab opens of the channel.
(Note: Chrome and Safari exhibits this correct behavior, users report that Firefox 97 also behaves correctly.) Event bubbling behaves inconsistent to Chrome and Safari, Creates Multiple Tabs when Control Clicking | Core | 47 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | [Beta-as-release simulation](https://treeherder.mozilla.org/jobs?repo=try&selectedTaskRun=WVTfLYdBQge8QAY8Y7PK8A.0&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry&revision=0b89b78309c9171bc7bccc8df434fa40b5ea8fd4)
[How to run these simulations](https://wiki.mozilla.org/Sheriffing/How_To/Beta_simulations)
[Failure log:](https://treeherder.mozilla.org/logviewer?job_id=372189600&repo=try&lineNumber=7131)
```
[task 2022-03-24T13:29:28.316Z] 13:29:28 INFO - TEST-START | toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js
[task 2022-03-24T13:29:28.395Z] 13:29:28 INFO - adb launch_application: am startservice -W -n 'org.mozilla.geckoview.test_runner/org.mozilla.geckoview.test_runner.XpcshellTestRunnerService$i0' -a android.intent.action.MAIN --es env0 XPCOM_DEBUG_BREAK=stack-and-abort --es env1 MOZ_CRASHREPORTER=1 --es env2 MOZ_CRASHREPORTER_NO_REPORT=1 --es env3 MOZ_DISABLE_NONLOCAL_CONNECTIONS=1 --es env4 MOZ_DEVELOPER_REPO_DIR=/builds/worker/checkouts/gecko --es env5 MOZ_DISABLE_CONTENT_SANDBOX=1 --es env6 MOZ_FETCHES_DIR=/builds/worker/fetches --es env7 MOZ_DISABLE_SOCKET_PROCESS=1 --es env8 LD_LIBRARY_PATH=/data/local/tmp/test_root/xpcb --es env9 MOZ_LINKER_CACHE=/data/local/tmp/test_root/xpcb --es env10 GRE_HOME=/data/local/tmp/test_root/xpcb --es env11 XPCSHELL_TEST_PROFILE_DIR=/data/local/tmp/test_root/xpc/p/5aeccd2f-467a-436e-8586-b1ceac933ccf --es env12 HOME=/data/local/tmp/test_root/xpc/p --es env13 XPCSHELL_TEST_TEMP_DIR=/data/local/tmp/test_root/xpc/tmp/0b1e08b3-3234-4891-92be-a90d2a1e7e84 --es env14 MOZ_ANDROID_DATA_DIR=/data/local/tmp/test_root/xpcb --es env15 MOZ_IN_AUTOMATION=1 --es env16 MOZ_ANDROID_CPU_ABI=x86_64 --es env17 MOZHTTP2_PORT=33841 --es env18 MOZNODE_EXEC_PORT=42703 --es env19 TMPDIR=/data/local/tmp/test_root/xpc/p/5aeccd2f-467a-436e-8586-b1ceac933ccf --es env20 XPCSHELL_MINIDUMP_DIR=/data/local/tmp/test_root/xpc/minidumps/5aeccd2f-467a-436e-8586-b1ceac933ccf --es arg0 -g --es arg1 /data/local/tmp/test_root/xpcb --es arg2 --greomni --es arg3 /data/local/tmp/test_root/xpcb/geckoview-test_runner.apk --es arg4 -m --es arg5 -e --es arg6 'const _HEAD_JS_PATH = "/data/local/tmp/test_root/xpc/head.js";' --es arg7 -e --es arg8 'const _MOZINFO_JS_PATH = "/data/local/tmp/test_root/xpc/p/5aeccd2f-467a-436e-8586-b1ceac933ccf/mozinfo.json";' --es arg9 -e --es arg10 'const _PREFS_FILE = "/data/local/tmp/test_root/xpc/user.js";' --es arg11 -e --es arg12 'const _TESTING_MODULES_DIR = "/data/local/tmp/test_root/xpc/m";' --es arg13 -f --es arg14 /data/local/tmp/test_root/xpc/head.js --es arg15 -e --es arg16 'const _HEAD_FILES = ["/data/local/tmp/test_root/xpc/toolkit/components/glean/tests/xpcshell/head.js"];' --es arg17 -e --es arg18 'const _JSDEBUGGER_PORT = 0;' --es arg19 -e --es arg20 'const _TEST_CWD = "/data/local/tmp/test_root/xpc/toolkit/components/glean/tests/xpcshell";' --es arg21 -e --es arg22 'const _TEST_FILE = ["test_GIFFTIPC.js"];' --es arg23 -e --es arg24 'const _TEST_NAME = "toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js";' --es arg25 -e --es arg26 '_execute_test(); quit(0);' --ez use_multiprocess True --es out_file /data/local/tmp/test_root/xpc/logs/xpcshell-b8d875c7-3f00-41e8-a73d-2ed4952877c4.log
[task 2022-03-24T13:29:28.659Z] 13:29:28 INFO - remotexpcshelltests.py | toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js | 27044 | Launched Test App
[task 2022-03-24T13:29:36.615Z] 13:29:36 INFO - remotexpcshelltests.py | toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js | 27044 | Application ran for: 0:00:08.298078
[task 2022-03-24T13:29:36.705Z] 13:29:36 WARNING - TEST-UNEXPECTED-FAIL | toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js | xpcshell return code: 0
[task 2022-03-24T13:29:36.705Z] 13:29:36 INFO - TEST-INFO took 8388ms
[task 2022-03-24T13:29:36.705Z] 13:29:36 INFO - >>>>>>>
[task 2022-03-24T13:29:36.706Z] 13:29:36 INFO - (xpcshell/head.js) | test MAIN run_test pending (1)
[task 2022-03-24T13:29:36.706Z] 13:29:36 INFO - (xpcshell/head.js) | test run_next_test 0 pending (2)
[task 2022-03-24T13:29:36.706Z] 13:29:36 INFO - (xpcshell/head.js) | test MAIN run_test finished (2)
[task 2022-03-24T13:29:36.706Z] 13:29:36 INFO - running event loop
[task 2022-03-24T13:29:36.706Z] 13:29:36 INFO - toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js | Starting test_setup
[task 2022-03-24T13:29:36.706Z] 13:29:36 INFO - (xpcshell/head.js) | test test_setup pending (2)
[task 2022-03-24T13:29:36.706Z] 13:29:36 INFO - (xpcshell/head.js) | test run_next_test 0 finished (2)
[task 2022-03-24T13:29:36.707Z] 13:29:36 INFO - (xpcshell/head.js) | test run_next_test 1 pending (2)
[task 2022-03-24T13:29:36.707Z] 13:29:36 INFO - (xpcshell/head.js) | test test_setup finished (2)
[task 2022-03-24T13:29:36.707Z] 13:29:36 INFO - toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js | Starting run_child_stuff
[task 2022-03-24T13:29:36.707Z] 13:29:36 INFO - (xpcshell/head.js) | test run_child_stuff pending (2)
[task 2022-03-24T13:29:36.707Z] 13:29:36 INFO - TEST-SKIP | toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js | run_child_stuff - run_child_stuff skipped because the following conditions were met: (runningInParent)
[task 2022-03-24T13:29:36.707Z] 13:29:36 INFO - (xpcshell/head.js) | test run_next_test pending (3)
[task 2022-03-24T13:29:36.708Z] 13:29:36 INFO - (xpcshell/head.js) | test run_next_test 1 finished (3)
[task 2022-03-24T13:29:36.708Z] 13:29:36 INFO - (xpcshell/head.js) | test run_next_test 2 pending (3)
[task 2022-03-24T13:29:36.708Z] 13:29:36 INFO - (xpcshell/head.js) | test run_child_stuff finished (3)
[task 2022-03-24T13:29:36.708Z] 13:29:36 INFO - (xpcshell/head.js) | test run_next_test finished (2)
[task 2022-03-24T13:29:36.708Z] 13:29:36 INFO - toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js | Starting test_child_metrics
[task 2022-03-24T13:29:36.708Z] 13:29:36 INFO - (xpcshell/head.js) | test test_child_metrics pending (2)
[task 2022-03-24T13:29:36.709Z] 13:29:36 INFO - (xpcshell/head.js) | test run in child pending (3)
[task 2022-03-24T13:29:36.709Z] 13:29:36 INFO - (xpcshell/head.js) | test run_next_test 2 finished (3)
[task 2022-03-24T13:29:36.709Z] 13:29:36 INFO - "CONSOLE_MESSAGE: (warn) [JavaScript Warning: "Use of nsIFile in content process is deprecated." {file: "/data/local/tmp/test_root/xpc/head.js" line: 372}]"
[task 2022-03-24T13:29:36.709Z] 13:29:36 INFO - (xpcshell/head.js) | test finished (2)
[task 2022-03-24T13:29:36.709Z] 13:29:36 INFO - Unexpected exception undefined - timed out after 50 tries.
[task 2022-03-24T13:29:36.709Z] 13:29:36 INFO - undefined
[task 2022-03-24T13:29:36.709Z] 13:29:36 INFO - exiting test
[task 2022-03-24T13:29:36.709Z] 13:29:36 INFO - <<<<<<<
[task 2022-03-24T13:29:36.819Z] 13:29:36 INFO - Cleaning up profile for /builds/worker/workspace/build/tests/xpcshell/tests/toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js folder: /data/local/tmp/test_root/xpc/p/5aeccd2f-467a-436e-8586-b1ceac933ccf
[task 2022-03-24T13:29:37.129Z] 13:29:37 INFO - INFO | Result summary:
[task 2022-03-24T13:29:37.130Z] 13:29:37 INFO - INFO | Passed: 833
[task 2022-03-24T13:29:37.130Z] 13:29:37 WARNING - INFO | Failed: 1
[task 2022-03-24T13:29:37.130Z] 13:29:37 WARNING - One or more unittests failed.
[task 2022-03-24T13:29:37.130Z] 13:29:37 INFO - INFO | Todo: 6
[task 2022-03-24T13:29:37.130Z] 13:29:37 INFO - INFO | Retried: 1
[task 2022-03-24T13:29:37.130Z] 13:29:37 INFO - SUITE-END | took 588s
[task 2022-03-24T13:29:37.131Z] 13:29:37 INFO - Node moz-http2 server shutting down ...
[task 2022-03-24T13:29:37.180Z] 13:29:37 ERROR - Return code: 1
``` Perma toolkit/components/glean/tests/xpcshell/test_GIFFTIPC.js | xpcshell return code: 0 when Gecko 99 merges to release on 2022-03-28 | Toolkit | 48 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9271151
example artifacts with dark
[Tracking Requested - why for this release]: Firefox 100 upgrade spotlight image doesn't look good on dark
The asset that landed in bug 1762270 is a 115x94 gif with light theme background mostly replaced with transparent and rendered as 90x73, so there's some artifacts that show up for dark theme. It was originally used in a remote ECO message and resized to 70x57 in bug 1759680.
We could optimize the image with video codecs like vp9 to get both quality and file size, but that would require changing from setting the image as a background-image: url().
For an asset-only change, we can use a different animated image format that supports actual color transparency. Improve heart animation image asset for dark mode | Firefox | 49 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Opening any of the popups from the URL bar (like clicking the privacy icon) then clicking it again doesn't restore the state, the toolbar icon remains as if it was open.
Local bisection says this was due to bug 1760276. [wayland] Popup icons don't change state when closed | Core | 50 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | [Tracking Requested - why for this release]:
@ Kate, I think this bug is a regression from Nimbus event bug 1656568. I bisected this problem (using my daily profile) to this pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=316fdd5817ae62591d1c63f983ab608765096ce7&tochange=24b91deee352b75f7e1a387d5cf4f0a939a90bee
In my daily profile, my `about:studies` page is blank. View Source shows that the page's HTML is loaded, but nothing is rendered. I can't reproduce in a clean profile, so the problem seems to a side effect of some experiment I've been enrolled in.
My `about:telemetry` Experiment Data says I'm enrolled in the following experiments:
```
rollout-doh-nightly-rollout-to-all-us-desktop-users-nightly-74-80-bug-1613481.branch active
rollout-doh-nightly-rollout-to-all-us-desktop-users-nightly-74-80-bug-1613481.type normandy-prefrollout
rollout-doh-nightly-rollout-to-all-us-desktop-users-nightly-74-80-bug-1613481.enrollmentId f3157ac7-4f39-d64e-b734-07f6dd2b15a8
bug-1686593-pref-http3-on-nightly-nightly-86-88.branch http3-enabled-treatment
bug-1686593-pref-http3-on-nightly-nightly-86-88.type normandy-exp
bug-1686593-pref-http3-on-nightly-nightly-86-88.enrollmentId 5443457b-ee29-ec4a-ad1b-45a2e855846c
```
In the browser console, I see the following error every time I load `about:studies`:
`debuggee 'resource://devtools/shared/base-loader.js:289' would run 2 builtin-modules.js:196:11` about:studies page is blank | Firefox | 53 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Steps to reproduce:
1. Be on macOS, and set `widget.macos.native-context-menus` and `browser.proton.contextmenus.enabled` to true.
2. Right click somewhere on this page to open a content area context menu.
3. Dismiss the menu by clicking somewhere else on this page, outside the menu.
4. Move your mouse over a toolbar button in the toolbar at the top.
5. Click a toolbar button, for example the hamburger button.
Expected results:
In step 4, hover effects should work. In step 5, the click should work.
Actual results:
Neither hover effects nor the click work. But once you've clicked somewhere, they start to work again.
Hover effects and clicks inside tab content still work.
This bug does not happen if the right click in step 2 happens in the chrome, or if the menu is dismissed by clicking a draggable part of the window in step 3. After opening a native context menu in tab content, the first click in the browser chrome is ignored (and mouseover effects don't work) | Core | 54 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Steps to reproduce:
1. Be on macOS, and set `widget.macos.native-context-menus` and `browser.proton.contextmenus.enabled` to true.
2. Open the bookmarks menu from its toolbar button. Alternatively, open a bookmarks folder panel in the bookmarks toolbar.
3. Right click on one of the bookmarks.
Expected results:
A context menu should appear on top of the other menu/panel.
Actual results:
The open menu/panel is dismissed and no context menu opens. With native context menus enabled, right-clicking a bookmark in a bookmarks panel (bookmarks toolbar folder popup or library panel) does not work | Core | 55 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9211326
example screenshot
Steps to reproduce:
1. Be on macOS, and set `widget.macos.native-context-menus` and `browser.proton.contextmenus.enabled` to true.
2. Make sure the bookmarks toolbar is shown.
3. Right-click on a bookmark or a bookmarks folder in the bookmarks toolbar.
Expected results:
The context menu should contain the items you would expect, and the right items should be enabled.
Actual results:
The menu has odd contents.
Note: If you set one of the prefs to false, open the non-native context menu, and then set them to true again, the native context menu will now contain the correct contents. In that case you can open a new window to reproduce this bug again. With native context menus enabled, the context menu of the bookmarks toolbar has strange contents (too many items, or duplicate items, or empty items, or all items disabled) | Core | 56 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Due to a change in the way we initialize `SharedDataMap` it looks like experiments are now being read from `undefined.json` – I think this could potentially unenroll a bunch of users across 85/86, so we probably need an uplift for this. File path is undefined for ExperimentStore | Firefox | 57 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Spec: https://www.figma.com/file/hGOaTi5ufs2Ese6agbUN4G/New-New-Tab?node-id=985%3A10147 Top sites font size if off by 1px when newNewtabExperience is enabled | Firefox | 58 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9204306
pip-unclickable.png
Steps to reproduce:
1. On a web site with a video, enter Picture-in-Picture mode.
2. Switch to a different tab.
3. Try to switch back to the original tab by clicking it.
Expected results:
The tab should be easy to click.
Actual results:
Clicking the upper half of the tab hits the "PICTURE-IN-PICTURE" text and doesn't do anything. It feels like the browser is not responding to the click. The tab hover effect is still shown in this state, making it look like the tab is clickable at that position. With the Proton tab bar, switching to a background tab is harder if contains a PiP video because part of the tab shape is unresponsive to clicks | Firefox | 59 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0
Steps to reproduce:
Build on Solaris SPARC failed with (i386 was fine):
```
4:03.40 In file included from Unified_cpp_dom_media_platforms0.cpp:11:
4:03.40 /builds2/psumbera/mozilla-central-build/dom/media/platforms/PDMFactory.cpp: In static member function ?static bool mozilla::PDMFactory::AllDecodersAreRemote()?:
4:03.40 /builds2/psumbera/mozilla-central-build/dom/media/platforms/PDMFactory.cpp:755:23: error: ?media_rdd_ffvpx_enabled? is not a member of ?mozilla::StaticPrefs?; did you mean ?media_rdd_vpx_enabled??
4:03.41 755 | StaticPrefs::media_rdd_ffvpx_enabled() &&
4:03.41 | ^~~~~~~~~~~~~~~~~~~~~~~
4:03.41 | media_rdd_vpx_enabled
```
he first bad revision is:
changeset: 568768:6b30d87e0b90
user: Bob Owen <bobowencode@gmail.com>
date: Thu Feb 25 07:10:58 2021 -0800
description:
Bug 1692894 p2: Don't create devices for decoding when all decoders are remote. r=mattwoodrow
Differential Revision: https://phabricator.services.mozilla.com/D105631 dom/media/platforms/PDMFactory.cpp:755:23: error: ?media_rdd_ffvpx_enabled? is not a member of ?mozilla::StaticPrefs?; did you mean ?media_rdd_vpx_enabled?? | Core | 60 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Spec: https://www.figma.com/file/hGOaTi5ufs2Ese6agbUN4G/New-New-Tab?node-id=1227%3A12445 Search bar focus ring does not exist when newNewtabExperience is enabled and search handoff enabled | Firefox | 61 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | When resizing the screen, sometimes the search bar and the personalize button overlap. We need some more work here to make the button properly responsive. New Tab: personlize button overlaps search bar at certain screen sizes | Firefox | 62 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | ## Steps to reproduce
0. Install the official Linux flatpak of Firefox from Flathub: https://flathub.org/apps/details/org.mozilla.firefox
1. Go to any website, press Ctrl+P/select to print.
2. It now opens the system dialog for printing (likely because it uses a portal or so it cannot show Firefox's own dialog)
3. Choose "Print".
You see a progress bar as usual (it is quite fast, but sending a printing job may be fast). You also see a notification about a finished printing job.
However, it does not print it. Also no print job is shown in the printer settings.
What does work, however, is everything else: If I print something else, it even shows the current state in the printing dialog – maybe, because that's just a system component.
## System
Firefox 84.0.2
Fedora 33 Silverblue
GNOME here
Reproduced with:
* two different systems (devices)
* two different printers (Canon and HP)
* two different printer connections (USB, WiFi)
When I print the website into a PDF file (which works in the dialog) and then use another app (Evince e.g.) to print the PDF, it does work, however. So it's not a system error.
Also, in the non-Flatpak versions it also seems to work. Use print portal under flatpak | Core | 63 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Google reported to us that download protection requests made from Firefox do not set the API key correctly.
The current request is:
https://sb-ssl.google.com/safebrowsing/clientreport/download?key=%GOOGLE_SAFEBROWSING_API_KEY%
The right one should look like:
https://sb-ssl.google.com/safebrowsing/clientreport/download?key=AIzaSyC7jspt...
From a quick look, this seems to be related to the fix in Bug 1237103, so this bug might have been here since Firefox 44. This bug didn’t affect the functionality of the download protection because Google didn’t drop requests without the API key previously. However, they are migrating the backends onto a newer infrastructure (1% of traffic at this point), which will drop requests without the correct API key set. This means users will not be protected by download protection.
We should fix this issue as soon as possible. For the older version of Firefox, we are still discussing if there is any possible workaround for this issue. Download protection requests don't set API key | Toolkit | 64 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | As brought up by @prathiksha and @JulianWels , there is no focus styling that is visible when tabbing to a highlighted tiles right under the search area. The pocket tiles still seem to have the styling. This is not the case without the newnew tab pref so it seems like a recent regression. Highlighted tiles in the new tab no longer have focus styling. | Firefox | 65 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:85.0) Gecko/20100101 Firefox/85.0
Steps to reproduce:
1. Open a zoom invite link
2. Click "Launch meeting"
Actual results:
Nothing launched.
Expected results:
In version 84 and below, the flatpak zoom client would always launch.
It also doesn't work with the Zoom .rpm. Cannot launch Flatpak or rpm Zoom client from Flatpak Firefox 85 | Core | 66 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0
Steps to reproduce:
Open a new window.
Actual results:
Firefox stopped to respond to commands and sometimes there are rendering glitches.
I run mozregression first with a new profile and then with webrender enabled but nothing was wrong. I tried it with my usual profile and the problematic commit is this one: https://hg.mozilla.org/integration/autoland/rev/9b17e776c11765d83ef5f1b0a6288a0c688cd1e1.
Right I know I can't try other flags but I still want to help. What is the best way to share my config? [wayland] Firefox hangs when a second window is opened (with software rendering) | Core | 67 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | This bug is for crash report bp-5e8bc895-b8da-4ccc-acaf-9f96c0200608.
Top 10 frames of crashing thread:
```
0 xul.dll static mozilla::ContentBlocking::OnAllowAccessFor toolkit/components/antitracking/ContentBlocking.cpp:563
1 xul.dll mozilla::ContentBlocking::CompleteAllowAccessFor::<unnamed-tag>::operator const toolkit/components/antitracking/ContentBlocking.cpp:467
2 xul.dll mozilla::MozPromise<int, bool, 1>::ThenValue<`lambda at /builds/worker/checkouts/gecko/toolkit/components/antitracking/ContentBlocking.cpp:532:9'>::DoResolveOrRejectInternal xpcom/threads/MozPromise.h:839
3 xul.dll mozilla::MozPromise<bool, mozilla::ipc::ResponseRejectReason, 1>::ThenValueBase::ResolveOrRejectRunnable::Run xpcom/threads/MozPromise.h:410
4 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1211
5 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
6 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308
7 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
8 xul.dll nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
9 xul.dll nsAppShell::Run widget/windows/nsAppShell.cpp:430
```
these content crashes have started cross-platform in 77 nightly and now seem to hit the beta audience in 78.0b too. Crash in [@ mozilla::ContentBlocking::OnAllowAccessFor] | Core | 68 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | null | Core | 69 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9167053
about_welcome_00.gif
* Opened on request on [bug 1653315](https://bugzilla.mozilla.org/show_bug.cgi?id=1653315#c9)
*Affected versions*
* 81.0a1 (20200729213824)
*Affected platforms*
* Windows 10x64
* Ubuntu 18.04
*Steps to reproduce*
1. Open Firefox and go to about:welcome.
2. Navigate through the welcome screens to the "Choose A Look" screen.
3. Select any random theme and then change it to another one.
*Expected result*
* Themes are changed as expected.
*Actual result*
* Themes section/ Save Theme/ Not now buttons are moved when changing the selection.
*Regression range*
* https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3894c97b6b9479a3f189424d52c74281ecb5d17b&tochange=aafd087ec6adaf20816250dc410be7138dc5099f
*Notes*
* Attached a screen recording.
* This happens when focusing/ defocusing the themes.
* On macOS 10.12 the items are moving only when using the TAB key to select them and they are not moving when clicked.
**Suggested Severity: S3** Items from about:welcome Choose a look section are moving when selected | Firefox | 71 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Steps to reproduce:
1. Visit the product page on Etsy
https://www.etsy.com/listing/799631062/soft-organic-cotton-crew-socks-short?ref=shop_home_active_20
2. Put 1 pair of socks to the shopping cart
3. Proceed to Guest Checkout
4. Fill in the shipping information
5. Proceed to review order
Expected results:
1. Save card doorhanger dropped
2. Choose save and have a complete card profile in autofill
Actual results:
1. Save card doorhanger dropped
2. Choose save but the "name on card" and "card type" were not saved Fields are not saved after choosing to save the credit card from the doorhanger | Toolkit | 72 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Since enabling Fission, I ran into a problem today with navigation. In this one tab, I have a file:// URL page open. If I type an https:// URL into the address bar and press Enter, the spinner starts, and I see the hostname in the status bar at the bottom of the window, but the navigation never succeeds. In the browser console, I see this exception:
```
TypeError: can't access property "legacySHistory", history is null [SessionHistory.jsm:109:1]
collect resource://gre/modules/sessionstore/SessionHistory.jsm:109
collect resource://gre/modules/sessionstore/SessionHistory.jsm:39
collectFrom resource:///modules/sessionstore/ContentSessionStore.jsm:200
send resource:///modules/sessionstore/ContentSessionStore.jsm:469
flush resource:///modules/sessionstore/ContentSessionStore.jsm:800
receiveMessage resource:///modules/sessionstore/ContentSessionStore.jsm:616
```
If I try to visit a different file:// URL in that tab, it works. And navigating to an https:// URL from another tab that has a file:// URL document shown it works too, so something's gone wrong with this tab / process in particular. can't navigate away from file:// URL | Firefox | 73 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9152944
Screenshot
I’ve noticed the button “Manage Breaches” in the Monitor card of the Protections Dashboard has layout issues in French “Manage Breaches” button in Protections Dashboard has layout issues | Firefox | 74 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | The font-family telemetry added by bug 1619349 is broken for Windows because of a copy/paste error in the DirectWrite impl of GetVisibilityForFamily -- it never returns the LangPack value. :( Font visibility is not set correctly for language-pack fonts on Windows | Core | 75 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | This bug is for crash report bp-a18b3a1d-63f9-4bfb-bb97-f422c0200503.
```
Top 10 frames of crashing thread:
0 xul.dll nsGlobalWindowInner::StorageAccessGranted dom/base/nsGlobalWindowInner.cpp:7202
1 xul.dll static mozilla::ContentBlocking::OnAllowAccessFor toolkit/components/antitracking/ContentBlocking.cpp:567
2 xul.dll mozilla::ContentBlocking::AllowAccessFor::<unnamed-tag>::operator const toolkit/components/antitracking/ContentBlocking.cpp:363
3 xul.dll mozilla::MozPromise<mozilla::Maybe<mozilla::ContentBlocking::StorageAccessPromptChoices>, mozilla::ipc::ResponseRejectReason, 1>::ThenValue<`lambda at /builds/worker/checkouts/gecko/toolkit/components/antitracking/ContentBlocking.cpp:354:14'>::DoResolveOrRejectInternal xpcom/threads/MozPromise.h:798
4 xul.dll mozilla::MozPromise<CopyableTArray<bool>, nsresult, 0>::ThenValueBase::ResolveOrRejectRunnable::Run xpcom/threads/MozPromise.h:405
5 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1200
6 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:481
7 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
8 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308
9 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
```
This looks like a a dereference of a `NULL` `this` pointer. The oldest buildid for this crash is 20200429215539. Tentatively filing under Core > Privacy: Anti-Tracking because most of the changes around this code seem to be happening in this component. Please move to the right component if this is wrong. Crash in [@ nsGlobalWindowInner::StorageAccessGranted] | Core | 77 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | STR: Start new profile of Firefox in the UK, engine list will look like
Google
Amazon.com
DuckDuckGo
Bing
Twitter
Wikipedia
eBay
Amazon.co.uk
Then restart, engine order looks like:
eBay
Amazon.co.uk
Bing
DuckDuckGo
Google
Twitter
Wikipedia Engines are in wrong order after restart | Firefox | 78 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | ## Step to Reproduce
1. Open Firefox Nightly and go to youtube
2. Open any video #1
- Now the metadata shown on Notification bar meets the info on youtube
3. Open another video #2 via another tab, or click other videos on same page
- The metadata shown on Notification bar isn't updated
## Expect Result
The metadata shown on Notification bar is updated to the info of video #2
## Expect Result
The metadata shown on Notification bar stays unchanged. It's still the info of video #1
I am on Ubuntu 18.04 [MediaControl-Linux] Metadata isn't updated after it's set in Ubuntu | Core | 79 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9142257
Screen Shot 2020-04-21 at 11.58.41 PM.png
Steps to reproduce:
1. Enable dark mode in macOS (I am using Catalina)
2. Enable separate search box
3. Type anything into search box
What happens:
The search suggestions panel background color is a gray that has bad contrast.
Expected result:
As previous.
18:05.50 INFO: Narrowed inbound regression window from [b87c6162, e7f852ba] (3 builds) to [b87c6162, 6c312e49] (2 builds) (~1 steps left)
18:05.50 INFO: No more inbound revisions, bisection finished.
18:05.50 INFO: Last good revision: b87c616243ab9b9b5210ba23317cc0668bb5a27b
18:05.50 INFO: First bad revision: 6c312e49ee094e66684abedc5ee314dfa595bfa1
18:05.50 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b87c616243ab9b9b5210ba23317cc0668bb5a27b&tochange=6c312e49ee094e66684abedc5ee314dfa595bfa1 Gray/discolored background in search bar in macOS dark mode | Toolkit | 81 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Steps to reproduce:
Download the testcase and run: `python3 -m http.server`
Open the developer tools (Network) and navigate to http://localhost:8000/testcase.html
This will send a XHR request to the same origin on a page where Referrer-Policy: no-referrer is applied.
What happened:
Request headers include:
```
Origin: null
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
```
Expected results:
The request header should be this (matches Firefox 75.0):
```
Origin: http://localhost:8000
```
Additional information:
This change was bisected to https://hg.mozilla.org/integration/autoland/rev/a925b80f029e3f2107a91bde02e9799fb9821eb3 (application_buildid: 20200420201907)
It breaks search functionality on a Confluence wiki page where this referrer-policy is set. Origin is null for an XHR request to the same origin when Referrer-Policy is no-referrer | Core | 82 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9140124
example.png
On 77 Nightly, most of the sharing icons in the macOS are not displaying for me. This creates visual imbalance, and also makes it challenging to scan the list and find which option you're looking to choose. macOS Share menu icons are missing | Core | 83 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | This is a blocker to turning on this feature.
During the cache load processes there is a new object that is setup but doesn't tear down the old worker.
This new object then goes and sets up a new worker.
Pretty sure this is a memory leak of sorts.
The fix should be easy, either make sure, if there is a provider already available, use it and not make a new one.
Or teardown the old one.
I prefer the option to use the old one. v2 personalization can trigger multiple instances of PersonalityProviderWorker.js | Firefox | 84 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | **Problem description**
When typing text in a plain old textarea in the latest build of Fenix, Talkback speaks too much information. For each letter I type, Talkback announces "Editing. [all the text I've entered ] Entry. [the label for the textarea] Edit options available. Use swipe up then right to view." when it probably should just speak the letter I typed.
**Steps to reproduce**
Load a page with this content:
`<label for="message">Good Times:</label><textarea id="message" name="message"></textarea>`
https://codepen.io/asadotzler/pen/bGVVevY
Now focus the textarea and double tap to bring up the keyboard.
Type the word "fun"
**Results**
Talback announces "Editing. Fun. Entry. Good Times. Edit options available. Use swipe up then right to view."
**Expected results**
Talkback announces each letter as I type it and nothing else. typing text in a textarea in Fenix (geckoview) is cumbersome because it's so verbose | Core | 85 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | This bug is for crash report bp-3d1796a9-b704-4049-abed-1ff470200413.
```
Top 10 frames of crashing thread:
0 XUL RustMozCrash mozglue/static/rust/wrappers.cpp:17
1 XUL mozglue_static::panic_hook mozglue/static/rust/lib.rs:89
2 XUL core::ops::function::Fn::call src/libcore/ops/function.rs:72
3 XUL std::panicking::rust_panic_with_hook src/libstd/panicking.rs:475
4 XUL rust_begin_unwind src/libstd/panicking.rs:375
5 XUL core::panicking::panic_fmt src/libcore/panicking.rs:84
6 XUL core::panicking::panic src/libcore/panicking.rs:51
7 XUL cubeb_coreaudio::backend::buffer_manager::BufferManager::push_silent_data third_party/rust/cubeb-coreaudio/src/backend/buffer_manager.rs
8 XUL cubeb_coreaudio::backend::audiounit_output_callback third_party/rust/cubeb-coreaudio/src/backend/mod.rs:615
9 CoreAudio CoreAudio@0xca1e
``` Crash in [@ cubeb_coreaudio::backend::buffer_manager::BufferManager::push_silent_data] | Core | 86 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | If we re initialize a personality provider using cache, it's not properly passing the previous cached score into the new insistence, causing it to make them fresh which is not really ideal. Personality Provider isn't properly rehydrating itself with cached values | Firefox | 87 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | I've many sync pings for my personal account which have, say:
```
"devices": [
{
"id": "00000000000000000000000000000000",
"type": "desktop",
"os": "Darwin",
"version": "77.0a1"
},
{
"id": "00000000000000000000000000000000",
"type": "desktop"
}
],
...
"uid": "2b...",
```
The ping reports a sync did happen (so we should have a token) and given we report the uid, we should be able to report the device IDs.
This is true for all recent pings, then they start appearing (on May 2). Without digging deeper and without real evidence, I'm suspecting bug 1604844 Many sync pings are missing device IDs | Firefox | 88 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36
Steps to reproduce:
1.Go to firefox version Firefox 83.0
2. Login to facebook account using credentials Testgsn4@gmail.com/t3st@123
3. Open our game https://apps.facebook.com/mesmogames/
4. Open console logs before opening game.
Actual results:
In console provided error is seen XDR encoding failure in file https://cdn.trackjs.com/agent/v3/latest/t.js 13 : 288. Because of this, app is not loading for certain players in firefox.
Note: This issue is seen only in firefox and in particular versions Firefox 83.0 and Firefox 80.0. In no other browser issue is seen.
Expected results:
This console error should not been seen and game should have loaded properly Console error: XDR encoding failure from Nov 13th | Core | 89 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | On new profiles - in Pocket locales - there is a brief moment on the New Tab page where the Firefox logo will show, then when the user's location is determined, it will hide and Pocket will load.
This can be fixed by not showing the logo until the location is determined. Conversely this will cause a slight stutter on non pocket locales, where the logo will load slightly later. But loading a moment later is better than showing and being removed. Fix stutter on new profiles due to Firefox logo | Firefox | 90 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0
Steps to reproduce:
Fix for Bug 1656155 caused on Solaris build failure:
```
gmake[3]: Entering directory '/builds/psumbera/FIREFOX/obj-x86_64-pc-solaris2.11/memory/replace/logalloc'
memory/replace/logalloc/FdPrintf.o
/builds/psumbera/FIREFOX/epoll/g++ -std=gnu++17 -o FdPrintf.o -c -I/builds/psumbera/FIREFOX/obj-x86_64-pc-solaris2.11/dist/system_wrappers -include /builds/psumbera/FIREFOX/config/gcc_hidden.h -fstack-protector-strong -DDEBUG=1 -DMOZ_REPLACE_MALLOC_PREFIX=logalloc -DMOZ_NO_MOZALLOC -DMOZ_HAS_MOZGLUE -DIMPL_MFBT -I/builds/psumbera/FIREFOX/memory/replace/logalloc -I/builds/psumbera/FIREFOX/obj-x86_64-pc-solaris2.11/memory/replace/logalloc -I/builds/psumbera/FIREFOX/memory/build -I/builds/psumbera/FIREFOX/obj-x86_64-pc-solaris2.11/dist/include -I/builds/psumbera/FIREFOX/obj-x86_64-pc-solaris2.11/dist/include/nspr -I/builds/psumbera/FIREFOX/obj-x86_64-pc-solaris2.11/dist/include/nss -fPIC -DMOZILLA_CLIENT -include /builds/psumbera/FIREFOX/obj-x86_64-pc-solaris2.11/mozilla-config.h -Wall -Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code -Wwrite-strings -Wno-invalid-offsetof -Wduplicated-cond -Wimplicit-fallthrough -Wunused-function -Wunused-variable -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wno-error=coverage-mismatch -Wno-error=free-nonheap-object -Wno-multistatement-macros -Wno-error=class-memaccess -Wno-error=deprecated-copy -Wformat -Wformat-overflow=2 -Werror=implicit-function-declaration -Wno-psabi -fno-sized-deallocation -fno-aligned-new -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -pthread -pipe -g -fno-omit-frame-pointer -funwind-tables -MD -MP -MF .deps/FdPrintf.o.pp /builds/psumbera/FIREFOX/memory/replace/logalloc/FdPrintf.cpp
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++
/builds/psumbera/FIREFOX/memory/replace/logalloc/FdPrintf.cpp: In instantiation of ‘unsigned int NumDigits(T) [with T = long unsigned int]’:
/builds/psumbera/FIREFOX/memory/replace/logalloc/FdPrintf.cpp:123:46: required from here
/builds/psumbera/FIREFOX/memory/replace/logalloc/FdPrintf.cpp:70:19: error: call of overloaded ‘log10(long unsigned int&)’ is ambiguous
70 | double l = log10(n);
| ~~~~~^~~
In file included from /usr/gcc/9/lib/gcc/x86_64-pc-solaris2.11/9.3.0/include-fixed/math.h:24,
from /usr/gcc/9/include/c++/9.3.0/cmath:45,
from /builds/psumbera/FIREFOX/obj-x86_64-pc-solaris2.11/dist/system_wrappers/cmath:3,
from /builds/psumbera/FIREFOX/memory/replace/logalloc/FdPrintf.cpp:14:
/usr/gcc/9/lib/gcc/x86_64-pc-solaris2.11/9.3.0/include-fixed/iso/math_iso.h:209:21: note: candidate: ‘long double std::log10(long double)’
209 | inline long double log10(long double __X) { return __log10l(__X); }
| ^~~~~
/usr/gcc/9/lib/gcc/x86_64-pc-solaris2.11/9.3.0/include-fixed/iso/math_iso.h:170:15: note: candidate: ‘float std::log10(float)’
170 | inline float log10(float __X) { return __log10f(__X); }
| ^~~~~
/usr/gcc/9/lib/gcc/x86_64-pc-solaris2.11/9.3.0/include-fixed/iso/math_iso.h:70:15: note: candidate: ‘double std::log10(double)’
70 | extern double log10 __P((double));
| ^~~~~
gmake[3]: *** [/builds/psumbera/FIREFOX/config/rules.mk:725: FdPrintf.o] Error 1
``` FdPrintf.cpp:70:19: error: call of overloaded ‘log10(long unsigned int&)’ is ambiguous | Core | 91 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9182135
install.log
On a Windows 8.1 machine, installing Firefox 82.0 RC 2 and 83.0a1 into a new folder requires a reboot to complete. The issue does not reproduce on a Windows 10 machine.
The full .exe installers are used (en-US) versions, both 32-bit and 64-bit reproduce the issue.
The installation dialog shows "A Little Housekeeping…" for several seconds.
The installation folder is outside C:\Program Files
After the install and before the reboot, there is a firefox.exe.moz-upgrade file in the install folder which is gone after the reboot. Firefox requests 'Reboot Now' to complete install on some systems | Firefox | 92 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0
Steps to reproduce:
I try to print receipt to Star TSP 100 & TSP650II model printers. I set headers & footers blank, and margins to zero. Then print.
Receipt printing works with Firefox 81.0.2
Actual results:
Printer prints a 1,5cm blank slice. Print preview is also blank.
Expected results:
Receipt should have printed corectly. Printing to Star Micronics receipt printer broken since v82 (output and print preview are blank) | Core | 94 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9183057
Screen Shot 2020-10-21 at 2.08.01 PM.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:82.0) Gecko/20100101 Firefox/82.0
Steps to reproduce:
*My FF version is not using the Chromium print prompt.
*macOS Catalina (10.15.7)
1) Open example PDF: https://food-guide.canada.ca/static/assets/pdf/HEPs-Guide-nw-en.pdf
2) Click printer icon.
3) Set Paper size to "Letter". Set scale to 100%.
4) Print OR Open with Preview.
Actual results:
There appear to be extra margins at the top and left sides, pushing some content off the printed document. Please see screenshot attached.
Expected results:
The printed document should match the onscreen PDF, since paper size is the same and scale is 100%. When printing, PDFs are misaligned and clipped in v82 due to extra margins | Core | 95 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | STR the crash:
1. Open https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_iframe with new print UI
2. Highlight "The iframe element" on right side of page
3. "Print selection" using context menu
4. Tab Crashes
STR the error:
1. Open https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_iframe with new print UI
2. Highlight anything on the left side of page
3. "Print selection" using context menu
4. Notice print preview error
The error is being caught from `await previewBrowser.frameLoader.printPreview(settings, sourceWinId));` is `UnknownError("Print preview failed", (void 0))`.
Here are the warnings I see:
```
[Parent 59430, Main Thread] WARNING: 'nsContentUtils::GetCommonBrowserParentAncestor( remote, oldRemote) != remote', file /Users/emmamalysz/Desktop/firefox-source/dom/events/EventStateManager.cpp:1367
[Child 59437, Main Thread] WARNING: '!endContent', file /Users/emmamalysz/Desktop/firefox-source/dom/base/Selection.cpp:1511
[Child 59437, Main Thread] WARNING: '!mPrt->mPrintObject->mPresContext', file /Users/emmamalysz/Desktop/firefox-source/layout/printing/nsPrintJob.cpp:1239
[Child 59437, Main Thread] WARNING: nsPrintJob::ResumePrintAfterResourcesLoaded failed: 'rv == NS_ERROR_ABORT', file /Users/emmamalysz/Desktop/firefox-source/layout/printing/nsPrintJob.cpp:1545
```
I'm not sure if this should be split into two separate bugs. This blocks the work I'm doing in Bug 1670122 because adding this option directly into the settings UI makes it much easier for a user to encounter this error. Printing selected text can cause "Print preview failed" error and crashes | Core | 96 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | With the pref:
browser.newtabpage.activity-stream.newNewtabExperience.enabled=true
or
browser.newtabpage.activity-stream.customizationMenu.enabled=true
When opening the customize menu, sometimes it jumps and stutters. We should fix this and uplioft to 85 for testing. Customize menu animation is not smooth | Firefox | 97 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | This only affects Firefox 85.0b1 so far. It's frequent.
Crash report: https://crash-stats.mozilla.org/report/index/13e1daf2-1669-48ff-9114-90f0f0201215
MOZ_CRASH Reason: ```Global Glean object not initialized```
Top 10 frames of crashing thread:
```
0 xul.dll RustMozCrash mozglue/static/rust/wrappers.cpp:16
1 xul.dll mozglue_static::panic_hook mozglue/static/rust/lib.rs:89
2 xul.dll core::ops::function::Fn::call<fn ../7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227
3 xul.dll std::panicking::rust_panic_with_hook ../7eac88abb2e57e752f3302f02be5f3ce3d7adfb4//library/std/src/panicking.rs:581
4 xul.dll std::panicking::begin_panic_handler::{{closure}} ../7eac88abb2e57e752f3302f02be5f3ce3d7adfb4//library/std/src/panicking.rs:484
5 xul.dll std::sys_common::backtrace::__rust_end_short_backtrace<closure-0, !> ../7eac88abb2e57e752f3302f02be5f3ce3d7adfb4//library/std/src/sys_common/backtrace.rs:153
6 xul.dll std::panicking::begin_panic_handler ../7eac88abb2e57e752f3302f02be5f3ce3d7adfb4//library/std/src/panicking.rs:483
7 xul.dll core::panicking::panic_fmt ../7eac88abb2e57e752f3302f02be5f3ce3d7adfb4//library/core/src/panicking.rs:85
8 xul.dll core::option::expect_failed ../7eac88abb2e57e752f3302f02be5f3ce3d7adfb4//library/core/src/option.rs:1226
9 xul.dll core::ops::function::FnOnce::call_once<closure-0, tuple<>> ../7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227
``` Frequent Beta Crash in [@ core::option::expect_failed | core::ops::function::FnOnce::call_once<T>] | Toolkit | 98 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Remove extra added space with newtab update 1 on top of search. It's pushing Pocket down. Remove extra added space above the search bar/logo on newtab page | Firefox | 99 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9183628
firefox-debug_0e74_2020-10-24_17-24-01-965.log
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36
Steps to reproduce:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-10-24T13:08:22.372506800Z" />
<EventRecordID>19589</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-FQ35S98</Computer>
<Security />
</System>
- <EventData>
<Data>firefox.exe</Data>
<Data>84.0.0.7602</Data>
<Data>5f940f9b</Data>
<Data>ntdll.dll</Data>
<Data>10.0.14393.3986</Data>
<Data>5f77fd0d</Data>
<Data>c0000005</Data>
<Data>000000000003469c</Data>
<Data>824</Data>
<Data>01d6aa06c00a6e80</Data>
<Data>C:\Program Files\Firefox Nightly\firefox.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>9f952e82-7c06-430e-acb3-db4ea80f36b3</Data>
<Data />
<Data />
</EventData>
</Event>
I try to use windbg and mozregression.
Tested autoland build: 2a46f29c (verdict: g)
app_name: firefox
build_date: 2020-10-21 00:08:25.137000
build_file: C:\Users\amix\.mozilla\mozregression\persist\2a46f29c8cdd--autoland--target.zip
build_type: integration
build_url: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/cMjDIhv6QXumrBVi86wxhQ/runs/0/artifacts/public%2Fbuild%2Ftarget.zip
changeset: 2a46f29c8cdd6f6269483e86c6e21e649ffa7127
pushlog_url: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2a46f29c8cdd6f6269483e86c6e21e649ffa7127&tochange=e88986658685538d5ab62d66c31e183b43e813ce
repo_name: autoland
repo_url: https://hg.mozilla.org/integration/autoland
task_id: cMjDIhv6QXumrBVi86wxhQ
Tested autoland build: 4c3e6fb9 (verdict: b)
app_name: firefox
build_date: 2020-10-21 00:24:50.430000
build_file: C:\Users\amix\.mozilla\mozregression\persist\4c3e6fb95aa6-pgo--autoland--target.zip
build_type: integration
build_url: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Okfv9Gf6T-GgBvUhGNEU1g/runs/0/artifacts/public%2Fbuild%2Ftarget.zip
changeset: 4c3e6fb95aa6184651f215d466e702ff7d1660d3
pushlog_url: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2a46f29c8cdd6f6269483e86c6e21e649ffa7127&tochange=4c3e6fb95aa6184651f215d466e702ff7d1660d3
repo_name: autoland
repo_url: https://hg.mozilla.org/integration/autoland
task_id: Okfv9Gf6T-GgBvUhGNEU1g
Differential Revision: https://phabricator.services.mozilla.com/D93709
Actual results:
Windows event log full of app errors since 22.10.2020. Startup crash on ntdll.dll | Core | 100 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | about:ion watches for add-on changes, but it is not comparing the cached vs. the add-on listener event correctly. about:ion does not update when add-ons status changes | Firefox | 101 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Crash report: https://crash-stats.mozilla.org/report/index/582e27ee-8961-46a8-b750-c0cc40201109
Reason: ```EXCEPTION_ACCESS_VIOLATION_READ```
Top 10 frames of crashing thread:
```
0 xul.dll mozilla::gfx::DrawTargetRecording::DrawTargetRecording gfx/2d/DrawTargetRecording.cpp:185
1 xul.dll mozilla::layers::CanvasChild::CreateDrawTarget gfx/layers/ipc/CanvasChild.cpp:252
2 xul.dll mozilla::layers::RecordedTextureData::Lock gfx/layers/client/TextureRecorded.cpp:47
3 xul.dll mozilla::layers::TextureClient::Lock gfx/layers/client/TextureClient.cpp:700
4 xul.dll mozilla::layers::ShareableCanvasRenderer::UpdateCompositableClient gfx/layers/ShareableCanvasRenderer.cpp:213
5 xul.dll nsDisplayCanvas::CreateWebRenderCommands layout/generic/nsHTMLCanvasFrame.cpp:136
6 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommands gfx/layers/wr/WebRenderCommandBuilder.cpp:1653
7 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList gfx/layers/wr/WebRenderCommandBuilder.cpp:1758
8 xul.dll nsDisplayOwnLayer::CreateWebRenderCommands layout/painting/nsDisplayList.cpp:6416
9 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommands gfx/layers/wr/WebRenderCommandBuilder.cpp:1653
``` Crash in [@ mozilla::gfx::DrawTargetRecording::DrawTargetRecording] | Core | 102 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | When using the dispatcher from RLB in FOG from bug 1662868, [TSAN started complaining](https://treeherder.mozilla.org/jobs?repo=autoland&fromchange=1e6b3c1288586627d5905d6ce87764daf4f7bc2c&searchStr=linux%2C18.04%2Cx64%2Ctsan%2Copt%2Cxpcshell%2Ctests%2Ctest-linux1804-64-tsan%2Fopt-xpcshell-e10&tochange=18db050b9f5606ba641067039e1182d262b137f9&group_state=expanded&selectedTaskRun=TzfhvhleQFOtjKGPjxZoPA.0).
Following the steps [here](https://firefox-source-docs.mozilla.org/tools/sanitizer/tsan.html) I was able to reproduce the issue locally, but still not able to understand what's going on, since the dispatcher shutdown procedure is correctly being called.
This bug should be take right after bug 1662868 to either confirm the suppression or fix the underlying issue. Investigate the TSAN error in the FOG/Glean Dispatcher | Toolkit | 103 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9173937
PrintToPdf.gif
**Affected versions**
* 82.0a1 (BuildId:20200903151816)
* 81.0b6 (BuildId:20200903205131)
**Affected platforms**
* Windows 10 64bit
* Ubuntu 18.04 64bit
* macOS 10.14
**Steps to reproduce**
1. Launch Firefox.
2. Access any webpage.
3. Hit Ctrl + P
4. Select the Save to Pdf, Microsoft Print to PDF or the Microsoft XPS document destination.
5. Click Print/Save
6. Cancel the Save As window modal.
**Expected result**
* The UI remains intractable and displayed since the print action was canceled by the user.
**Actual result**
* The UI options are locked and the user has to close the UI by pressing the esc keyboard button.
**Regression Window**
* This is a regression.
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=284e3c053bf57ee8f331b21a90751936ee604482&tochange=0de10c26da552953484a56f0fbdb3ab70196988e
* Possible Regressor: Bug 1659624
**Additional Information**
* For further information regarding this issue please observe the attached screencast.
* [Suggested Severity] S2 Canceling the “Save as” modal while printing to file (Save to Pdf, Microsoft Print to PDF & Microsoft XPS document destinations) locks the new UI | Toolkit | 104 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9173960
pdfJS.gif
**Affected versions**
* 82.0a1 (BuildId:20200903151816)
* 81.0b6 (BuildId:20200903205131)
**Affected platforms**
* Windows 10 64bit
* Ubuntu 18.04 64bit
* macOS 10.14
**Steps to reproduce**
1. Launch Firefox
2. Access the following [link](http://www.dbsparks.com/research/html/SNRN02.pdf)
3. Click the print button.
**Expected result**
* The print preview successfully displays the pdf file.
**Actual result**
* The print preview displays a blank pdf and it cannot be printed.
**Regression Window**
* This seems to be a regression but I can’t reproduce this issue using mozregression (odd..) I’ll try to search for a manual regression as soon as time permits.
**Additional Information**
* For further information regarding this issue please observe the attached screencast. Print preview displays blank pages for pdf documents | Core | 105 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | In bug 1657220 I added new telemetry probes, but mistakenly set them to `record_in_processes: 'content'`. They need to be recorded in the main process. The new print preview UI telemetry probes are registered for the wrong process | Core | 106 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Currently we badge the Pioneer icon if the `pioneer-study-addons` collection changes, but we switched this to `pioneer-study-addons-v1`. We could work around it on the server, but it'd be much cleaner to just have this in the client. Watch proper RS collection name for badge highlighting | Firefox | 107 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | STR;
1 Open https://www.irs.gov/pub/irs-pdf/f1040.pdf
2 Click the print icon button in the pdf viewer Print preview progress dialog appears when window.print is called if print.show_print_progress is true. | Core | 108 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9172445
Screencast from 08-27-2020 09:43:40 AM.webm
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0
Steps to reproduce:
When right clicking in the bottom right corner of the screen, the last entry of the context menu is automatically selected when releasing the right click.
Happens only under wayland; when using xwayland the context menu shows as expected.
Reproduced with firefox 80.0 and firefox nightly 82.0a1 on Fedora 32.
Actual results:
The screenshot tool show up on right click (see attached video).
Expected results:
The context menu should show up. [Wayland] context menu automatically selects last entry on right click | Core | 109 |
Categorize the news article into one of the 4 categories:
Core
Firefox
SeaMonkey
Toolkit | Created attachment 9173482
consent_modal.html
Attached is the text for the privacy notice acceptance modal that all users must accept (in the modal) in order to first enroll in Pioneer.
I was given two URLs for the Manifesto and for the overall Mozilla Privacy Policy that do not have localization paths in them. Please check to ensure these are correct. Land Privacy Notice Text for Pioneer panel enrollment modal | Firefox | 110 |