Bug ID
int64 961
1.91M
| Comment ID
int64 3.98k
17.1M
| Author
stringlengths 8
48
| Comment Text
stringlengths 1
64.3k
⌀ |
|---|---|---|---|
1,860,528 | 16,634,271 |
Created attachment 9359781
With `browser.urlbar.trimHttps`
Steps to reproduce:
1. Enable `browser.urlbar.trimHttps`
2. Visit https://googlesamples.github.io/web-fundamentals/fundamentals/security/prevent-mixed-content/active-mixed-content.html
3. Click Site Identity Button/Padlock > Connection secure > Disable protections for now
You can see that a line appears in front of the URL, which has previously striked through the https:// scheme, but now seems out of place.
|
|
1,860,791 | 16,636,172 |
Created attachment 9360009
non sponsored result cannot be dismissed.mp4
**[Notes]**
- The following error is displayed in the browser console: "TypeError: result.payload.sponsoredAdvertiser is undefined".
- The "Block" telemetry is correctly registered, but the non-sponsored result is not dismissed and also can be triggered again.
- If Rust is disabled the non-sponsored results from Remote Settings can be successfully dismissed.
**[Affected versions]**
- Firefox Beta 120.0b1 (Build ID: 20231023135443)
- Firefox Nightly 121.0a1 (Build ID: 20231023215318)
**[Affected platforms]**
- Windows 10 x64
- macOS 13.5
- Ubuntu 22.04
**[Prerequisites]**
Have the following prefs set:
- browser.search.region set to "US"
- browser.urlbar.quicksuggest.rustEnabled set to true.
**[Steps to reproduce]**
1. Open the Firefox build with the prefs mentioned in the prerequisites.
2. Type a keyword that would trigger a non-sponsored suggestion (wikipedia), eg: "music".
3. Hover the non-sponsored result.
4. Click the "..." menu button.
5. Click the "Dismiss this suggestion" button.
6. Observe the behavior.
**[Expected results]**
- The non-sponsored result is dismissed and is no longer triggered.
**[Actual results]**
- The non-sponsored result is not dismissed.
**[Additional Notes]**
- Attached is a screen recording of the issue.
|
|
1,860,885 | 16,636,850 |
Created attachment 9360091
tb119.console.log
Steps to reproduce:
Upgraded from 118b6 to 119. (b3, b4, and b6 all the same so far)
Actual results:
Nothing appears inside the folder and message panes, no calendar entries show (local or Google), even in Troubleshooting Mode. The only hint that the profile is actually loading is the Calendars are all listed, without the entries. Downgrading to 118 with the profile downgrade switch restores full functionality.
I've attached a console log and screenshots, in case that helps.
Expected results:
Everything appears as normal.
|
|
1,860,977 | 16,637,393 |
Created attachment 9360189
pics.zip
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0
Steps to reproduce:
Send 2 E-Mails to myself.
E-Mail A with no encryption
E-Mail B with PGP encryption and 5 MB
Open E-Mail B
While Thunderbird is loading/decrypting click to open E-Mail A
Actual results:
After E-Mail B is encrypted the subject of E-Mail A is permanently changed to the subject of E-Mail B, restarting Thunderbird does not resolve this bug.
Expected results:
Subject of E-Mail A should not change.
|
|
1,861,988 | 16,645,459 |
Created attachment 9360999
Video of the issue.mp4
**[Prerequisites]:**
- A new profile is used.
**[Steps to reproduce]:**
1. Set “app.normandy.user_id” to “4d03162f-ae8c-42ad-8620-ef1bb65cfea5”;
2. Set “messaging-system.rsexperimentloader.collection_id” to “nimbus-preview”;
3. Set “browser.search.region” to “US”;
4. Restart the browser;
5. Navigate to “about:studies”;
6. Observe the list of active experiments.
**[Expected result]:**
- User should be enrolled in either the “Fox Doodle” or “Review Checker” experiment, but not both.
**[Actual result]:**
- User is enrolled in both experiments.
**[Notes]:**
- This happens because [“Fox Doodle”](https://experimenter.services.mozilla.com/nimbus/fox-doodle-set-to-default-early-day-user/summary) was the first one to be received by the browser and at that moment the condition that the user is not enrolled in the [“Review Checker 119 new profiles”](https://experimenter.services.mozilla.com/nimbus/review-checker-119-new-profiles/summary) experiment was true.
- If both experiments are enrolling at the same time this is a situation that can occur for users that never interacted with either experiment. In order to avoid this situation, both experiments should exclude each other.
|
|
1,862,074 | 16,646,183 |
Firefox for Android
Steps to reproduce:
I installed Firefox 118.1.1 on my Android phone (HTC Desire 22 Pro, Android 12, arm64-v8a). I downloaded a file from any website. The app doesn't crash, the full phone crashes and goes directly to the boot screen animation, so a full automatic reboot.
Actual results:
Since I installed Firefox 118.1.1 on my Android phone via the Play Store, my phone crashes when I download any file from any website. My phone doesn't show any dialog with information that the app crashed, it directly goes to the boot screen and bootanimation. This problem occurs on 118.1.1, 118.2.0, 119.0.
When I downgrade to 118.1.0 everything works as expected.
Expected results:
The file should be stored in the Downloads folder and the phone shouldn't crash
|
|
1,862,089 | 16,646,284 |
The test case is:
```
gczeal(10);
var ins = new WebAssembly.Instance(new WebAssembly.Module(wasmTextToBinary(`
(module
(type $t (func (param i64 funcref)))
(func (export "test") (param i64 funcref) (result i64)
local.get 0
local.get 1
local.get 1
ref.cast (ref $t)
call_ref $t
local.get 0
)
)`)));
var vis = ins.exports.test;
while (1) {
const visFn = new WebAssembly.Function({
parameters: ["i64", "funcref"],
results: []
}, ()=>{});
vis(1n, visFn);
}
```
and crashes with
```
Assertion failure: this->flags() == 0, at /Users/yury/Work/mozilla-unified/js/src/gc/Cell.h:832
#01: JSObject::getClass() const[/Users/yury/Work/mozilla-unified/obj-aarch64-apple-darwin22.5.0/dist/bin/js +0x1a8dc]
#02: bool ToJSValue_funcref<js::wasm::NoDebug>(JSContext*, void*, JS::MutableHandle<JS::Value>)[/Users/yury/Work/mozilla-unified/obj-aarch64-apple-darwin22.5.0/dist/bin/js +0x138ce10]
#03: bool js::wasm::ToJSValue<js::wasm::NoDebug>(JSContext*, void const*, js::wasm::PackedType<js::wasm::FieldTypeTraits>, JS::MutableHandle<JS::Value>, js::wasm::CoercionLevel)[/Users/yury/Work/mozilla-unified/obj-aarch64-apple-darwin22.5.0/dist/bin/js +0x138b678]
#04: js::wasm::Instance::callImport(JSContext*, unsigned int, unsigned int, unsigned long long*)[/Users/yury/Work/mozilla-unified/obj-aarch64-apple-darwin22.5.0/dist/bin/js +0x128f6f4]
#05: js::wasm::Instance::callImport_general(js::wasm::Instance*, int, int, unsigned long long*)[/Users/yury/Work/mozilla-unified/obj-aarch64-apple-darwin22.5.0/dist/bin/js +0x1290cc0]
zsh: segmentation fault ~/Work/mozilla-unified/obj-aarch64-apple-darwin22.5.0/dist/bin/js 5.js
```
Looking at rr session (different/non-reduces test though): earlier, `Instance::callImport` https://searchfox.org/mozilla-central/source/js/src/wasm/WasmInstance.cpp#253 starts GC and relocates the function object.
The test is reduced from failures at bug 1861981 and 1854714
|
|
1,856,959 | 16,607,016 |
Created attachment 9356615
Screenrecorder-2023-10-04-16-29-20-243.mp4
### Preconditions
Make sure you have VPN connected to US.
Make sure you have developer's option enabled, and the "Shopping experience" toggle is ON.
Enroll in the Fakespot shopping experience.
### Steps to reproduce
1. Go to a gift card, streaming video, music or games product detailed page from amazon.com, bestbuy.com, or walmart.com.
2. Tap the price tag icon in the URL.
3. Observe the bottom sheet.
### Expected behavior
The "We can't check these reviews" error message is displayed for these types of products.
### Actual behavior
The user is prompted to start the analysis, after which the "No info available" error message is displayed.
### Device information
* Firefox version: Nightly 120.0a1 from 10/04
* Android device: any device
### Any additional information?
After analyzing the product once and closing the bottom sheet, the next time the bottom sheet is opened, the error message would persists (the user is not prompted to analyze the product again).
This issue could be related to https://bugzilla.mozilla.org/show_bug.cgi?id=1856797, however, we receive the same incorrect error message on older Nightly builds as well.
|
|
1,856,972 | 16,607,111 |
Steps to reproduce:
We try to load the CPS PKCS#11 library manually :
1°) Open firefox 114 beta 4
2°) Go to Settings > Privacy & Security
3°) In the 'Security' section, click the button 'Security devices'
4° ) In the security modules dialog, click the button 'Load module'
5°) In the 'Load module' dialog, browse to location where resides the CPS PKCS#11 module (cps3_pkcs11_osx.dylib) in /usr/local/lib
6°) Validate the 'Load module' dialog
=================================
The same library is loaded without any problem in Firefox 118 release.
Actual results:
An error message is displayed saying that the module couldn't be loaded
Expected results:
The CPS module should have been loaded without any error messages
The CPS module should have been listed in the security modules dialog as a new module
|
|
1,857,118 | 16,607,912 |
STR:
- Open 1113 tabs
- Switch Firefox View to the Open Tabs view
- Close one of the tabs
- The browser hangs for about 2 seconds
Here's the profile: https://share.firefox.dev/3ROuzdw
|
|
1,857,430 | 16,609,850 |
Created attachment 9357003
video_2023-10-06_15-08-06.mp4
i found a vulnerability where user can fall for clickjacking to allow location permission
I tested on Firefox version 118.0.1 (64-bit)
steps to reproduce:
1. Open lock2-1-firefox.html
2. fastly move to the "do many clicks here" button.
3. Quickly click the "do many clicks here" button 6-7 times without moving the mouse then the location permission will be allowed
references : https://bugzilla.mozilla.org/show_bug.cgi?id=1826116
|
|
1,857,450 | 16,610,057 |
Steps to reproduce:
Yesterday I upgraded thunderbird from 102ESR to 115.3.1-1~deb12u1 from Debian bookworm (stable) repository.
Actual results:
Today I noticed mess in a NNTP newsgroup. It looks like concurrent writes to the offline cache file:
`News/news.gmane.org/gmane.emacs.orgmode` (actually currently the server is news.gmane.io)
```
From - Thu Oct 5 23:49:55 2023
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
From - Thu Oct 5 23:49:55 2023
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <[email protected]>
Newsgroups: gmane.emacs.orgmode,gmane.emacs.devel
Subject: Re: Completion of links to man pages
Date: Thu, 05 Oct 2023 18:52:36 +0300
Approved: [email protected]
Message-ID: <[email protected]>
References: <[email protected]> <87sf6pi9fn.fsf@localhost>
```
You see that it is a cross-post and before I notice these jammed messages in gmane.emacs.orgmode having offline cache enabled, I noticed no issues with same messages in gmane.emacs.devel where I have not enabled offline cache.
Expected results:
Messages are written to cache strictly sequentially.
In this particular newsgroup I enabled offline storage due to other thunderbird bugs related to opening messages read earlier and to mitigate lags due to intermittent network issues.
|
|
1,857,903 | 16,614,676 |
Created attachment 9357388
Video of the issue.mp4
**[Prerequisites]:**
- “browser.search.region” config is set to any of the following regions: "as,at,be,ch,es,fi,gg,ie,im,io,it,je,mp,nl,pr,se,uk,um,vg,vi".
**[Steps to reproduce]:**
1. Open the browser;
2. Navigate to “about:preferences#moreFromMozilla”;
3. Observe the behavior.
**[Expected result]:**
- Mozilla VPN should be recommended to users and be displayed in the More from Mozilla section since the regions from prerequisites all have Mozilla VPN available as a service.
**[Actual result]:**
- Mozilla VPN product promo is not displayed. Only other products such as Firefox Mobile and Firefox Relay are present.
**[Notes]:**
- Issue does not reproduce for the following regions: "us,ca,nz,sg,my,gb,de,fr" and Mozilla VPN is correctly being displayed in More from Mozilla. Due to this we believe that [this](https://searchfox.org/mozilla-central/rev/3d0b07f5a3c7b8d9955fb8e8acaaf582b1e33bb6/toolkit/modules/BrowserUtils.sys.mjs#505) list of regions is being used instead of the intended one, which should be [this](https://searchfox.org/mozilla-central/source/browser/app/profile/firefox.js#2040) one. As it can be seen, the full list of regions contains the ones that are currently functional, but it also contains the ones from prerequisites that are not working.
|
|
1,858,144 | 16,616,535 |
**Found in**
* Nightly 120.0a1
**Affected versions**
* Nightly 120.0a1
**Tested platforms**
* Affected platforms: macOS 12, Ubuntu 22.04, Windows 11
**Steps to reproduce**
1. Launch a private window.
2. Browse various websites.
3. Delete the session by clicking on the "End Private Session" button.
4. Press the Ctrl+Shift+T keys.
**Expected result**
* After deleting the session data the closed tabs should not be restored.
**Actual result**
* All tabs opened during step 2 are restored even after ending the private session.
**Regression range**
Not a regression.
**Additional notes**
* Setting the severity of this issue to S2 - as it should not be possible to recover deleted browsing history after ending the private session.
|
|
1,858,183 | 16,616,749 |
**Found in**
* Nightly 120.0a1
**Affected versions**
* Nightly 120.0a1
**Tested platforms**
* Affected platforms: macOS 11.7, Ubuntu 22.04 x64, Windows 10 x64.
**Preconditions**
* Open the Screenreader before opening Firefox:
- on Windows 10 - NVDA
- on macOS - Voice Over
- on Ubuntu - integrated screen reader.
**Steps to reproduce**
1. Open a private window.
2. Use the screen reader to reach the "End Private Session" button and open the Confirmation panel.
**Expected result**
* The button and the information from the Confirmation panel (including the check box and buttons) should be read by the screen reader.
**Actual result**
* While the screen reader successfully reads the "Always ask me" checkbox and the buttons, it does not read the text within the Confirmation dialog: "End your private session? Close all private tabs and delete history, cookies, and all other site data."
**Regression range**
* Not a regression.
**Additional notes**
* When using VoiceOver on Mac OS, I could access the text, but it was part of a different group, necessitating navigation through the Extensions and Open App Menu buttons before reaching the text, which might be confusing for the users.
|
|
1,858,371 | 16,617,827 |
**[Affected versions]:**
- Firefox Release 115.0 and above
**[Affected Platforms]:**
- Windows 10 x64
- macOS 13.4.1
- Ubuntu 22.04 x64
**[Steps to reproduce]:**
1. Navigate to the "https://experimenter.services.mozilla.com/nimbus/vpn-moments-page-october-new-users/summary" experiment.
2. Scroll down to the "Audience" section and observe the "Full targeting expression".
**[Expected result]:**
- According to the received [documentation](https://docs.google.com/document/d/1OvWvJ6azwOoSmMqAKqDj1mn8_UsoZa_M53_PNROb0-c/edit#heading=h.hwmok2nif0hz) the "VPN moments page October (New Users)" experiment should target profiles younger than 28 days.
**[Actual result]:**
- The "(currentDate|date - profileAgeCreated|date) / 86400000 >= 28" targeting expression is displayed.
**[Notes]:**
- Based on the actual targeting users with Firefox profiles younger than 28 days will not be enrolled in the experiment.
|
|
1,849,685 | 16,547,396 |
Created attachment 9349840
FakespotIconAddressBar.mp4
**Found in**
* Nightly 118.0a1 (2023-08-22)
**Affected versions**
* Nightly 118.0a1 (2023-08-22)
**Affected platforms**
* ALL
**Preconditions:**
Set the browser.shopping.experience2023.enabled - TRUE
Set the browser.shopping.experience2023.optedIn - 1
**Steps to reproduce**
1. Reach amazon.com
2. Search for Standing desk.
3. Use the Mouse wheel to open a product in a new tab. (Right click open in a new tab also works.)
**Expected result**
* The Fakespot shopping address bar icon should not be displayed on the search results page.
**Actual result**
* The Fakespot address bar icon shows up if the user opens a product details page in a separate tab
**Regression range**
Not Applicable
|
|
1,849,958 | 16,549,211 |
Perfherder has detected a browsertime performance regression from push [29c39113c4bfbf17193d9ca9a756482de04da3af](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=29c39113c4bfbf17193d9ca9a756482de04da3af). 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)** | **Performance Profiles** |
|--|--|--|--|--|--|
| [18%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,3913745,1,13) | [welcome](https://firefox-source-docs.mozilla.org/testing/perfdocs/raptor.html#welcome-c) fcp | windows10-64-shippable-qr | fission warm webrender | [41.50](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ADqWbgZZSf-U2LLAgTrXrw/runs/0/artifacts/public/test_info/browsertime-results.tgz) -> [48.89](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/LQ6k1BmETECNjK-SpzK3AQ/runs/0/artifacts/public/test_info/browsertime-results.tgz) | [Before](https://profiler.firefox.com/from-url/https%3A%2F%2Ffirefox-ci-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2FADqWbgZZSf-U2LLAgTrXrw%2Fruns%2F0%2Fartifacts%2Fpublic%2Ftest_info%2Fprofile_welcome.zip)/[After](https://profiler.firefox.com/from-url/https%3A%2F%2Ffirefox-ci-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2FLQ6k1BmETECNjK-SpzK3AQ%2Fruns%2F0%2Fartifacts%2Fpublic%2Ftest_info%2Fprofile_welcome.zip) |
| [13%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,3913745,1,13) | [welcome](https://firefox-source-docs.mozilla.org/testing/perfdocs/raptor.html#welcome-c) fcp | windows10-64-shippable-qr | fission warm webrender | 41.75 -> 47.27 | |
Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=39377), 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/).
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.
For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
|
|
1,850,337 | 16,553,314 |
**[Affected versions]:**
- Firefox RC 117.0, en-US locale (Build ID: 20230824132758)
**[Affected Platforms]:**
- Windows 10 x64
- macOS 13.1
- Linux Mint 20.2
**[Prerequisites]:**
- Have the Firefox browser installed on your computer.
- Have this “times.json” file downloaded to your computer.
**[Steps to reproduce]:**
1. Create a new profile but do not open it.
2. Paste the “times.json” file to the Profile Folder.
3. Open the Firefox profile newly created.
4. Navigate to the “about:config” page
5. Set the “nimbus.debug” pref to true and the “browser.search.region” set to AT/BE/CA/CH/DE/GB/IE/IN/US.
6. Navigate to "about:studies?optin_slug=newtab-csat-microsurvey&optin_branch=treatment-a&optin_collection=nimbus-preview" to enroll in the Treatment branch of the experiment.
7. Open a new tab and observe the behavior.
**[Expected result]:**
- The “Help Firefox improve this page” microsurvey is correctly displayed according to the [documentation](https://docs.google.com/document/d/1OtvgLfqstCxOUNYXzNKG_98W1R59jPmBU6jaUMqWCs0/edit).
**[Actual result]:**
- The [Microsurvey](https://docs.google.com/document/d/1j6AMusH8XD2MLBnLtpgkzufgwDGxRbQKiADSrlAElZQ/edit) from the Treatment A of the "Microsurvey MVP" experiment is displayed instead.
**[Notes]:**
- Attaching a screen recording of the issue [here](https://drive.google.com/file/d/135FrCb9ZQlz_mSL1TUm3D88ff54OilWA/view?usp=sharing).
|
|
1,850,524 | 16,554,716 |
**[Affected versions]:**
- Firefox RC 117.0 - Build ID: 20230824132758
**[Affected Platforms]:**
- Windows 10 x64
- macOS 13.4.1
- Ubuntu 22.04 x64
**[Prerequisites]:**
- Have the following [User.js](https://drive.google.com/file/d/1p-Ojr-ub3YRzymgnAyEECxXvz6f6sADs/view?usp=sharing) saved to your PC.
- Have a Firefox profile older than 28 days with 21 days of activity.
**[Steps to reproduce]:**
1. Navigate to the profile folder from the prerequisites and paste the "user.js" file.
2. Open the browser using the profile from prerequisites.
3. Navigate the the "about:studies" page and observe the displayed studies.
**[Expected result]:**
- The "Newtab Pocket Topics Microsurvey" experiment is not displayed in the "about:studies" page.
**[Actual result]:**
- The "Newtab Pocket Topics Microsurvey" experiment is displayed as active.
**[Notes]:**
- The [received documentation](https://docs.google.com/document/d/1j6AMusH8XD2MLBnLtpgkzufgwDGxRbQKiADSrlAElZQ/edit#heading=h.gzh3ljgkgxch) states in the "Target Audience Details" section that user should have at least 28 days of activity in order to enroll in the study.
|
|
1,850,732 | 16,556,253 |
Created attachment 9350850
baebb25c-94f2-4c06-a307-1ca5092cb635.ics
Steps to reproduce:
Opened the Calendar window -> Menu -> Open From File -> Calendar -> here I choose the attached .ics file.
Actual results:
The Calendar (and Thunderbird) is not responding and the only thing one can do is forcing close of the program.
Using Thunderbird now becomes impossible since opening it once again results in a immediately freezed program.
Expected results:
The calendar should be imported.
|
|
1,850,938 | 16,557,367 |
6 crashes from 3 installations of Firefox 118.0 Nightly and Developer Edition (diagnostic assert). Same signature had been fixed in bug 1414762 several years ago.
Crash report: https://crash-stats.mozilla.org/report/index/94d17df9-1d8c-4e86-8d2e-e73360230830
MOZ_CRASH Reason: ```MOZ_DIAGNOSTIC_ASSERT(!inUnsafeRegion) ([AutoAssertNoGC] possible GC in GC-unsafe region)```
Top 10 frames of crashing thread:
```
0 XUL JSContext::verifyIsSafeToGC js/src/vm/JSContext.h:518
0 XUL js::RunScript js/src/vm/Interpreter.cpp:419
0 XUL js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:612
0 XUL InternalCall js/src/vm/Interpreter.cpp:647
0 XUL js::Call js/src/vm/Interpreter.cpp:679
1 XUL JS_CallFunctionValue js/src/vm/CallAndConstruct.cpp:55
1 XUL nsXPCWrappedJS::CallMethod js/xpconnect/src/XPCWrappedJSClass.cpp:918
2 XUL PrepareAndDispatch xpcom/reflect/xptcall/md/unix/xptcstubs_x86_64_darwin.cpp:117
3 XUL SharedStub
4 ? @0x000000012705135f
```
|
|
1,851,468 | 16,562,635 |
Steps to reproduce:
1. Go on https://www.bandlab.com/
2. In the console:
(new AudioContext()).audioWorklet.addModule('https://www.bandlab.com/web-app/common/workers/libaudioengine-837fbc5d51.js')
Actual results:
CompileError: at offset 7983: exceptions not enabled
Expected results:
I expect the WASM module to be initialized without any error.
The error started to occur over the weekend, with many BandLab users reporting the same problem. I have switched back to a WASM module compiled without the support for exceptions for now.
I re-installed Firefox 116 on macOS, and it seems to work fine using that version. Is there any changes related to WASM and WASM exception in Firefox 117 that could cause this problem?
|
|
1,851,594 | 16,563,597 |
### Preconditions
- Have the [nimbus-cli](https://experimenter.info/nimbus-cli/install/) tool installed.
- Have [adb](https://developer.android.com/tools/releases/platform-tools) (cli) installed on your device.
- Have an Android 13 device with USB or Wifi debugging enabled and connected to the device on which you installed nimbus-cli.
### Steps to reproduce
1. Install the [latest Firefox Beta](https://github.com/mozilla-mobile/firefox-android/releases/tag/fenix-v118.0b4) on an Android 13 device.
2. Open a terminal window on your workstation.
3. Enter the following command in the terminal window `nimbus-cli -a fenix -c beta enroll release-android-onboarding-redesign-treatment-a-rollout --branch treatment-a`
4. Skip the first onboarding card.
5. Sign into Sync using any method on the second card.
6. Tap the `Turn on notifications` button on the third card and observe the behavior.
### Expected behaviour
- A system dialog is triggered prompting the user to Allow or Not Allow the app to send notifications.
### Actual behaviour
- No system dialog is triggered and notifications are disabled.
### Additional information
- I've used a Samsung Galaxy A32 with Android 13 to reproduce the issue.
- The issue is reproducible on the following fenix versions:
- 117.0b9
- 117.0
- 118.0b4
- The issue is not reproducible on 116.2.0 or 115.2.0.
- The issue is not reproducible if the users skips the Sign In card.
- Attached a screen recording:
- [Link](https://drive.google.com/file/d/1ZVlzyhVil04h3NCVDiejvcvxzjLcT4Om/view?usp=sharing)
@Rahul, could you please take a look at this issue?
|
|
1,851,599 | 16,563,647 |
Steps to reproduce:
On git commit 3279ccb472284368de49190d73acb13926a757ec I observed an assertion violation in the js-shell. Unfortunately, reproduction this assertion is a bit convoluted.
The 6 input files are provided via the reprl/fuzzing interface, hence the attached python script instead of a simple js file.
Furthermore, reproduction works in 10% of trials only. The script's `SPIDERMONKEY` must be adapted to point to the js-shell.
Precautiously marking as s-s.
I uploaded a pernosco session here but the source seems to missing, not sure what I did wrong there.
https://pernos.co/debug/5z_QVrXs3ZkRL1NaiXTQfg/index.html
```
#0 js::jit::AttachBaselineCacheIRStub (cx=cx@entry=0x7ffff662e100, writer=..., kind=<optimized out>,
outerScript=0x382c863a1330, icScript=icScript@entry=0x7ffff549e400, stub=stub@entry=0x7ffff549ea70,
name=0x555555a30c8a "GetProp.TypedElement")
at js/src/jit/BaselineCacheIRCompiler.cpp:2602
#1 0x0000555557cdd497 in js::jit::TryAttachStub<js::jit::GetPropIRGenerator, js::jit::CacheKind, JS::Handle<JS::Value>&, JS::Handle<JS::Value>&> (name=0x5555559d70d6 "GetElem", cx=cx@entry=0x7ffff662e100, frame=<optimized out>,
stub=stub@entry=0x7ffff549ea70, args=..., args=..., args=...)
at js/src/jit/BaselineIC.cpp:497
#2 0x0000555557cdca6b in js::jit::DoGetElemFallback (cx=0x7ffff662e100, frame=0x7fffffffbea0,
stub=0x7ffff549ea70, lhs=..., rhs=..., res=...) at js/src/jit/BaselineIC.cpp:708
#3 0x000035c7531ab627 in ?? ()
#4 0x0000000000000101 in ?? ()
#5 0x00007fffffffbb18 in ?? ()
#6 0x0000000000000000 in ?? ()
```
|
|
1,865,617 | 16,675,191 |
Crash report: https://crash-stats.mozilla.org/report/index/1dd7f326-9819-4295-89c9-302200231120
Java stack trace:
```
java.lang.OutOfMemoryError
```
It seems to be `jni::ByteBuffer::New` causes OOM exception. This method can return error, so we need to consider fallible version of `jni::ByteBuffer::New` .
|
|
1,865,620 | 16,675,308 |
Created attachment 9364460
Error of 'export RNP_LOG_CONSOLE=1'
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 OPR/104.0.0.0
Steps to reproduce:
- create a PGP key in thunderbird < 115 (exact version: 115.4.3)
- used this key with another product to send an encrypted message to my mailbox
- opened the message in thunderbird
Actual results:
The message cannot be opened because 'There are unkonwn problems with this encrypted message'.
Expected results:
The message should have been decrypted and displayed like it was done before the upgrade to 115.
|
|
1,865,625 | 16,675,377 |
Created attachment 9364469
Video showing the issue
**Found in**
* Nightly 121.0a1
**Affected versions**
* Nightly 121.0a1
**Tested platforms**
* Affected platforms: macOS 13.6 and macOS 14
* Unaffected platforms: Windows 10 and Ubuntu 22.04
**Preconditions**
* Have a valid google account
**Steps to reproduce**
1. Login to google account
2. Go to Manage your Google Account > Security
3. Click `Passkey` and then Click on `Create a passkey`
4. Click on `Continue` or use another device and select `Use security key`
**Expected result**
* A new passkey is successfully created
**Actual result**
* Something went wrong dialog is displayed and the passkey is not created
**Regression range**
* Not a regression since this is a new feature and it also reproduces in the same day the feature was added in Nightly 121.
**Additional notes**
* Passkeys can be added to the google account using Safari browser but not Firefox.
* Marking this as S2 severity because users who use Google will not be able to use this feature in Firefox.
* I only get an error inside the Web Console when choosing the `Use security key` option. This is the output from the console:
```c
Uncaught (in promise)
Object { stack: "_.ja@https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.AccountSettingsStrongauthUi.en.ehny_KKREzE.es5.O/am=EEa2_ZJF1gJCAIAI/d=1/excm=_b,_tp,passkeysview/ed=1/dg=0/wt=2/ujg=1/rs=AOaEmlH7sKxUqOaguTfj5eRa-82QnclLAg/m=_b,_tp:26:361\n_.se@https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.AccountSettingsStrongauthUi.en.ehny_KKREzE.es5.O/am=EEa2_ZJF1gJCAIAI/d=1/excm=_b,_tp,passkeysview/ed=1/dg=0/wt=2/ujg=1/rs=AOaEmlH7sKxUqOaguTfj5eRa-82QnclLAg/m=_b,_tp:280:337\n_.YR.prototype.Aa@https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.AccountSettingsStrongauthUi.en.ehny_KKREzE.es5.O/ck=boq-identity.AccountSettingsStrongauthUi.0kGCf5wlYQw.L.F4.O/am=EEa2_ZJF1gJCAIAI/d=1/exm=LEikZe,_b,_tp,byfTOb,lsjVmc/excm=_b,_tp,passkeysview/ed=1/wt=2/ujg=1/rs=AOaEmlHsWfdhqombindHKhvWC95hStGyDA/ee=BcQPH:zw1Icf;EVNhjf:pw70Gc;EmZ2Bf:zr1jrb;Erl4fe:FloWmf;JsbNhc:Xd8iUd;LBgRLc:SdcwHb;Me32dd:MEeYgc;NPKaK:SdcwHb;NSEoX:lazG7b;Oj465e:KG2eXe;Pjplud:EEDORb;QGR0gd:Mlhmy;SMDL4c:qfTGrb;SNUn3:Zw…", ha: false, status: {…} }
```
|
|
1,865,747 | 16,676,174 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/119.0
Steps to reproduce:
I'm running the latest version of Firefox on Linux (Arch), with the Hyprland tiling manager, and trying to access https://www.google.com/maps.
Actual results:
Firefox crashes. If I comment out the "env = GBM_BACKEND,nvidia-drm" line in the config (as suggested here https://wiki.hyprland.org/Nvidia/) it fixes it.
However, my understanding is that by commenting the line I'm basically blocking Firefox from using the GPU (Nvidia), which in turn makes sites such as chess.com sluggish for some reason.
Expected results:
Google Maps should load with no issue, as it does (for example) on Chromium.
|
|
1,865,914 | 16,677,517 |
Created attachment 9364822
test.html
By combining techniques from https://bugzilla.mozilla.org/show_bug.cgi?id=1839073 and https://bugzilla.mozilla.org/show_bug.cgi?id=1857430, possible to bypass fullscreen.
STR
0. For better verification, increase security.notification_enable_delay in about:config to 1000.
1. Open test.html
2. Hover over button and spam click.
3. The prompt is accepted instantaneously after a fullscreen transition without enablement delay of 1000ms
Hypothesis: In this patch we reset the timeShown of https://hg.mozilla.org/mozilla-central/rev/75b8d8d5ea21 when window containing prompt gains focus. Therefore, I think any modifications to the timeShown variable in the fullscreen patch can be reset though this.
|
|
1,865,973 | 16,677,851 |
Created attachment 9364876
Untitled.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0
Steps to reproduce:
1. use firefox with build id 20231121045833
2. goto https://bitbucket.org/fargo3d/public/src/ae0fcdc67bb7c83aed85fc9a4d4a2d5061324597/Makefile
Actual results:
in Makefile code font not render correctly
Expected results:
font should render correctly.
after update it work properly i think it already backout in new version.
but i want to let you known
|
|
1,866,006 | 16,678,019 |
The attached testcase crashes on mozilla-central revision 20231122-ef0b50d89a7f (build with (metadatabuildFlags not available)).
For detailed crash information, see attachment.
To reproduce the issue, perform the following steps:
1. Download the attached testcase, save as "test.bin".
2a. Build with `--enable-fuzzing` (requires Clang and ASan, also build gtests using `./mach gtest dontruntests`).
2b. Alternatively you can download builds from TC using `python -mfuzzfetch -a --fuzzing --target firefox gtest` (see https://github.com/MozillaSecurity/fuzzfetch).
3. Run `FUZZER=NetworkHttp objdir/dist/bin/firefox test.bin`
|
|
1,866,025 | 16,678,367 |
Created attachment 9364941
firefox.strace
Steps to reproduce:
Running on ArchLinux ARM (in case it's a packaging issue) on Sway 1.8.1 + wlroots 0.16.2 (in case it's a Wayland issue), I got the upgrade from `firefox-119.0.1-1-aarch64` to `firefox-120.0-1-aarch64`; upon restarting Firefox, I got met with a segfault (see strace attached) right at startup, before any window opens. Downgrading back to 119.0.1 fixes the issue (but I have now lost access to my normal profile since Firefox has a new check preventing downgrades; I understand why that check was added, but it's still annoying...)
On the environment side, I have `MOZ_DBUS_REMOTE=1` & `MOZ_ENABLE_WAYLAND=1` (not sure if it's relevant, I'll try changing these once I've posted this issue since I can't run both versions in parallel. I don't need the dbus one anymore, it was for back when I was still running X sometimes, and I'll try removing the wayland one in case running through xwayland fixes the issue, as that would narrow down the problem.
Actual results:
Segfault (see strace attached)
Expected results:
Firefox starts :)
|
|
1,866,230 | 16,680,172 |
Created attachment 9365134
multiple impressions registered.mp4
**[Affected versions]:**
- Firefox Beta 121.0b2 - Build ID: 20231122091904
- Firefox Nightly 122.0a1 - Build ID: 20231121183118
**[Affected Platforms]:**
- Windows 10 x64
- Ubuntu 22.04 x64
- macOS 13.1
**[Prerequisites]:**
- Have a Firefox 121 or 122 en* build installed.
- Have the following prefs in the "about:config" page:
- browser.search.region set to US;
- browser.urlbar.quicksuggest.contextualOptIn set to true
- browser.urlbar.quicksuggest.contextualOptIn.topPosition set to false
- Have [Glean telemetry](https://testrail.stage.mozaws.net/index.php?/cases/view/2323256) configured.
**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Click on the Address Bar.
3. Click any of the displayed results while the Opt-In section is displayed.
4. Navigate to "about:glean" and click on the "Apply settings and submit ping".
4. Navigate to the Glean debug page: https://debug-ping-preview.firebaseapp.com/.
5. Select your tag and verify the last event registered.
**[Expected result]:**
- Only one impression for "quick_suggest_contextual_opt_in" is registered.
**[Actual result]:**
- Three impression telemetry are registered for "quick_suggest_contextual_opt_in".
**[Notes]:**
- The issue is NOT reproducible for the Opt-In section displayed at the top, only one impression is registered.
- This issue can affect the data collected for the experiment when it will be launched. Considering this I will mark this issue as an S2.
- Attached is a screen recording of the issue.
|
|
1,866,396 | 16,681,145 |
While investigating Bug 1866025 I ran into content process crashes on Linux on Apple Silicon. I don't have a backtrace yet.
|
|
1,866,545 | 16,681,869 |
The following testcase crashes on mozilla-central revision 20231124-dbd1a6aef0a7 (debug build, run with --fuzzing-safe --ion-offthread-compile=off):
See attachment.
Backtrace:
received signal SIGILL, Illegal instruction.
#0 0x33514063 in ?? ()
#1 0x335141e3 in ?? ()
#2 0xf3400708 in ?? ()
eax 0x0 0
ebx 0x0 0
ecx 0xf3400708 -213907704
edx 0x0 0
esi 0xf6ef8750 -152074416
edi 0xdeadbeef -559038737
ebp 0xffffbfa8 4294950824
esp 0xffffbf90 4294950800
eip 0x33514063 860962915
=> 0x33514063: ud2
0x33514065: mov 0x10(%ecx),%edx
This only reproduces on 32-bit.
|
|
1,866,614 | 16,682,357 |
2023-11-24T16:26:53.178000: DEBUG : Found commit message:
Bug 1858799 - expose an nsIWebAuthnService on Windows. r=keeler
Differential Revision: https://phabricator.services.mozilla.com/D190978
2023-11-24T16:26:53.178000: DEBUG : Did not find a branch, checking all integration branches
2023-11-24T16:26:53.182000: INFO : The bisection is done.
2023-11-24T16:26:53.185000: INFO : Stopped
|
|
1,867,006 | 16,687,081 |
It seems using HTTP2 websockets with a HTTP2 proxy can sometimes cause WS to not work, or even crashes.
We should disable this until we can fix it and get CI to test this exact scenario to avoid regressions.
|
|
1,867,057 | 16,687,370 |
Created attachment 9365862
2023-11-28_16h56_04.png
**Found in**
* Nightly 122.0a1 (2023-11-27)
**Affected versions**
* Nightly 122.0a1 (2023-11-27)
**Affected platforms**
* ALL
**Preconditions:**
browser.shopping.experience2023.enabled - true
browser.shopping.experience2023.optedIn = 0
**Steps to reproduce**
1. Reach https://www.amazon.de/Amazon-brand-Movian-computer-drawers/product-reviews/B07GFRCZWY/ref=cm_cr_arp_d_paging_btm_next_2?ie=UTF8&reviewerType=all_reviews&pageNumber=2
**Expected result**
* We should not get a product_id for unknown products : https://searchfox.org/mozilla-central/rev/9bc264fbc5d6e618d8f3b9677a8f5e8550b94dbc/browser/components/shopping/content/shopping-container.mjs#217,224-225
**Actual result**
* The Product page showed an unanalyzed card, after which the Not enough reviews message was displayed and finally after refresh the Adjusted card is displayed with 0 stars.
**Regression range**
Not Applicable
This is a new Feature that brings Shopping support to amazon.fr and amazon.de.
|
|
1,862,473 | 16,649,126 |
Created attachment 9361461
poc1101.js
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36
Steps to reproduce:
The vulnerability exists in the WASM compiler of JS engine. The configuration for building is as follows:
ac_add_options --enable-project=js
ac_add_options --disable-optimize
ac_add_options --disable-unified-build
ac_add_options --disable-debug
ac_add_options --enable-debug-symbols
ac_add_options --disable-jemalloc
ac_add_options --disable-tests
Actual results:
This is the full crash log:
```
gdb-peda$ bt
#0 0x000018a9cbba41c0 in ()
#1 0x000048840f012840 in ()
#2 0x0000555558c3cb50 in ()
#3 0x00007fffffff7360 in ()
#4 0x000018a9cbba418f in ()
#5 0x0000555558c3cb50 in ()
#6 0x00005555575c60e5 in mozilla::detail::MaybeStorageBase<js::wasm::TrapData, true>::MaybeStorageBase() (this=0x5555575c60e5 <mozilla::detail::MaybeStorageBase<js::wasm::TrapData, true>::MaybeStorageBase()+21>) at obj-x86_64-pc-linux-gnu/dist/include/mozilla/MaybeStorageBase.h:78
#7 0x000018a9cbba46a9 in ()
#8 0x0000555558c3cb50 in ()
#9 0x0000555558bec588 in ()
#10 0x00007fffffff7658 in ()
#11 0x00007fffffff7658 in ()
#12 0x00007fffffff7400 in ()
#13 0x00005555575c3454 in js::jit::JitActivation::JitActivation(JSContext*)
(this=0x7fffffff7400, cx=0x7fffffff7658)
at js/src/vm/JitActivation.cpp:42
#14 0x0000555558314fab in js::wasm::Instance::callExport(JSContext*, unsigned int, JS::CallArgs, js::wasm::CoercionLevel)
(this=0x555558c3cb50, cx=0x555558bec4a0, funcIndex=0x0, args=..., level=js::wasm::CoercionLevel::Spec) at js/src/wasm/WasmInstance.cpp:2851
#15 0x000055555836de24 in WasmCall(JSContext*, unsigned int, JS::Value*)
(cx=0x555558bec4a0, argc=0x0, vp=0x555558d05670)
at js/src/wasm/WasmJS.cpp:1808
#16 0x000055555713748c in CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), js::CallReason, JS::CallArgs const&)
(cx=0x555558bec4a0, native=0x55555836dd00 <WasmCall(JSContext*, unsigned int, JS::Value*)>, reason=js::CallReason::Call, args=...) at js/src/vm/Interpreter.cpp:472
#17 js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason)
(cx=0x555558bec4a0, args=..., construct=js::NO_CONSTRUCT, reason=js::CallReason::Call)
at js/src/vm/Interpreter.cpp:566
#18 0x0000555557137b0a in InternalCall(JSContext*, js::AnyInvokeArgs const&, js::CallReason)
(cx=0x555558bec4a0, args=..., reason=js::CallReason::Call)
at js/src/vm/Interpreter.cpp:633
#19 0x0000555557137ad3 in js::CallFromStack(JSContext*, JS::CallArgs const&, js::CallReason)
(cx=0x555558bec4a0, args=..., reason=js::CallReason::Call)
at js/src/vm/Interpreter.cpp:638
#20 0x000055555714baa3 in js::Interpret(JSContext*, js::RunState&) (cx=0x555558bec4a0, state=...)
at js/src/vm/Interpreter.cpp:3053
#21 0x000055555713676d in MaybeEnterInterpreterTrampoline(JSContext*, js::RunState&)
(cx=0x555558bec4a0, state=...) at js/src/vm/Interpreter.cpp:386
#22 js::RunScript(JSContext*, js::RunState&) (cx=0x555558bec4a0, state=...)
at js/src/vm/Interpreter.cpp:444
#23 0x0000555557138f3e in js::ExecuteKernel(JSContext*, JS::Handle<JSScript*>, JS::Handle<JSObject*>, js::AbstractFramePtr, JS::MutableHandle<JS::Value>)
(cx=0x555558bec4a0, script=0x31f9a964060, envChainArg=(JSObject * const) 0x31f9a93e038 [object LexicalEnvironment], evalInFrame=AbstractFramePtr ((js::InterpreterFrame *) 0x0) = {...}, result=$JS::UndefinedValue()) at js/src/vm/Interpreter.cpp:831
#24 0x0000555557139152 in js::Execute(JSContext*, JS::Handle<JSScript*>, JS::Handle<JSObject*>, JS::MutableHandle<JS::Value>)
(cx=0x555558bec4a0, script=0x31f9a964060, envChain=(JSObject * const) 0x31f9a93e038 [object LexicalEnvironment], rval=$JS::UndefinedValue()) at js/src/vm/Interpreter.cpp:863
#25 0x0000555557423d6f in ExecuteScript(JSContext*, JS::Handle<JSObject*>, JS::Handle<JSScript*>, JS::MutableHandle<JS::Value>)
(cx=0x555558bec4a0, envChain=(JSObject * const) 0x31f9a93e038 [object LexicalEnvironment], script=0x31f9a964060, rval=$JS::UndefinedValue())
at js/src/vm/CompilationAndEvaluation.cpp:494
#26 0x0000555557423e5f in JS_ExecuteScript(JSContext*, JS::Handle<JSScript*>)
(cx=0x555558bec4a0, scriptArg=0x31f9a964060)
at js/src/vm/CompilationAndEvaluation.cpp:518
#27 0x000055555701cb6b in RunFile(JSContext*, char const*, _IO_FILE*, CompileUtf8, bool, bool)
(cx=0x555558bec4a0, filename=0x555558d01a10 "../AFL-WASM-v2/Workspace-SPM/test.js", file=0x555558d01bb0, compileMethod=CompileUtf8::DontInflate, compileOnly=0x0, fullParse=0x0)
at js/src/shell/js.cpp:1217
#28 0x000055555701c4af in Process(JSContext*, char const*, bool, FileKind)
(cx=0x555558bec4a0, filename=0x555558d01a10 "../AFL-WASM-v2/Workspace-SPM/test.js", forceTTY=0x0, kind=FileScript) at js/src/shell/js.cpp:1797
#29 0x0000555556ff975f in ProcessArgs(JSContext*, js::cli::OptionParser*)
(cx=0x555558bec4a0, op=0x7fffffffdfa0) at js/src/shell/js.cpp:10871
#30 0x0000555556ff37b2 in Shell(JSContext*, js::cli::OptionParser*)
(cx=0x555558bec4a0, op=0x7fffffffdfa0) at js/src/shell/js.cpp:11133
#31 0x0000555556feec17 in main(int, char**) (argc=0x3, argv=0x7fffffffe1b8)
at js/src/shell/js.cpp:11537
#32 0x00007ffff7a48083 in __libc_start_main () at /lib/x86_64-linux-gnu/libc.so.6
#33 0x0000555556fc9d39 in _start ()
```
```
gdb-peda$ i registers
rax 0x555558cea5d0 0x555558cea5d0
rbx 0x48840f012840 0x48840f012840
rcx 0xd0574928 0xd0574928
rdx 0x3cd53d2c 0x3cd53d2c
rsi 0xc27f2164 0xc27f2164
rdi 0x5ebae657 0x5ebae657
rbp 0x7fffffff7360 0x7fffffff7360
rsp 0x7fffffff7330 0x7fffffff7330
r8 0xb3f6cad3 0xb3f6cad3
r9 0x9fac1b66 0x9fac1b66
r10 0x555558cea5d0 0x555558cea5d0
r11 0x7ffff7c10be0 0x7ffff7c10be0
r12 0x5555575c60e5 0x5555575c60e5
r13 0x7fffffffe1b0 0x7fffffffe1b0
r14 0x48840f012840 0x48840f012840
r15 0x7ffeedff0000 0x7ffeedff0000
rip 0x18a9cbba41c0 0x18a9cbba41c0
eflags 0x10202 [ IF RF ]
cs 0x33 0x33
ss 0x2b 0x2b
ds 0x0 0x0
es 0x0 0x0
fs 0x0 0x0
gs 0x0 0x0
gdb-peda$ x/20i 0x18a9cbba41c0-0x50
0x18a9cbba4170: xchg edi,eax
0x18a9cbba4171: lods al,BYTE PTR ds:[rsi]
0x18a9cbba4172: mov ecx,0xd0574928
0x18a9cbba4177: mov r8d,0xb3f6cad3
0x18a9cbba417d: mov r9d,0x9fac1b66
0x18a9cbba4183: mov rsi,QWORD PTR [rbp-0x8]
0x18a9cbba4187: mov rdx,rsi
0x18a9cbba418a: call 0x18a9cbba4520
0x18a9cbba418f: lea rsp,[rbp-0x30]
0x18a9cbba4193: mov edi,0x5ebae657
0x18a9cbba4198: mov esi,0xc27f2164
0x18a9cbba419d: mov edx,0x3cd53d2c
0x18a9cbba41a2: mov r12,QWORD PTR [rbp-0x8]
0x18a9cbba41a6: mov rbx,QWORD PTR [r12+0x40]
0x18a9cbba41ab: cmp r14,rbx
0x18a9cbba41ae: je 0x18a9cbba41f9
0x18a9cbba41b4: mov QWORD PTR [rsp+0x8],r14
0x18a9cbba41b9: mov r14,rbx
0x18a9cbba41bc: mov QWORD PTR [rsp],r14
=> 0x18a9cbba41c0: mov r15,QWORD PTR [r14]
gdb-peda$
0x18a9cbba41c3: mov rax,QWORD PTR [r14+0x20]
0x18a9cbba41c7: mov rbx,QWORD PTR [r14+0x18]
0x18a9cbba41cb: mov QWORD PTR [rax+0xb0],rbx
0x18a9cbba41d2: mov rax,QWORD PTR [r12+0x38]
0x18a9cbba41d7: call rax
0x18a9cbba41d9: or r14,0x0
0x18a9cbba41dd: mov r14,QWORD PTR [rsp+0x8]
0x18a9cbba41e2: mov r15,QWORD PTR [r14]
0x18a9cbba41e5: mov r10,QWORD PTR [r14+0x20]
0x18a9cbba41e9: mov r12,QWORD PTR [r14+0x18]
0x18a9cbba41ed: mov QWORD PTR [r10+0xb0],r12
0x18a9cbba41f4: jmp 0x18a9cbba4200
0x18a9cbba41f9: mov rax,QWORD PTR [r12+0x38]
0x18a9cbba41fe: call rax
0x18a9cbba4200: lea rsp,[rbp-0x30]
0x18a9cbba4204: mov eax,eax
0x18a9cbba4206: mov esi,0xc8f3826d
0x18a9cbba420b: mov edx,0x4fdc6d2c
0x18a9cbba4210: mov edi,eax
0x18a9cbba4212: call 0x18a9cbba4030
```
The reason seems to be that the assembly code, compiled from the wasm module, caused a crash during its execution. The root cause is not clear now, but this OOB bug resulted in registers pollution and a direct overwrite of the call stack, making it exploitable.
For example, the critical part of this assembly block is r14 which is used as a pointer to access certain memory locations. If we can control the r14 register to an arbitrary value, there are several potential attacks we might be able to perform:
1. Arbitrary Read: From the instruction mov r15,QWORD PTR [r14], we can see that r14 is used as a pointer to read a value from memory. If we can control r14 to any arbitrary value, this potentially allows us to read data from any memory location in the process's address space.
2. Arbitrary Write: Similar to the previous point, the code contains the instruction mov QWORD PTR [rax+0xb0],rbx where rax is loaded from [r14+0x20]. If we can control r14 to point to a location of our choice, we can change the value of rax and thus control the destination of the write operation (i.e., rax+0xb0), leading to an arbitrary write vulnerability.
3. Arbitrary Function Call: The instruction call rax, where rax is loaded from [r12+0x38], implies that an arbitrary function pointed to by rax can be called. If we control r14 to a controlled memory location where we have written a crafted r12 structure, we can induce the program to call an arbitrary function, potentially leading to code execution.
This issue can be reproduced on the gecko-dev at the GIT commit 11d085b63cf74b using the --wasm-tail-calls running flag. It's worth noting that this flag is enabled by default in the Nightly version of Firefox(121.0a1 2023-11-01).
|
|
1,862,983 | 16,651,637 |
**[Affected versions]:**
- Firefox Release 119.0 (Build ID: 20231019122658)
- Firefox Beta 120.0b5 (Build ID: 20231101092803)
- Firefox Nightly 121.0a1 (Build ID: 20231103093836)
**[Affected Platforms]:**
- Windows 10 x64
- macOS Ventura 13.5.1
- Linux Mint 21.1
**[Prerequisites]:**
- Have a Nimbus experiment with the “feltPrivacy” feature configuration set (e.g.: [Feature Configuration Testing for "feltPrivacy" experiment](https://stage.experimenter.nonprod.dataops.mozgcp.net/nimbus/feature-configuration-testing-for-feltprivacy/summary)).
- Have the following syntax pasted in the Command Prompt Window: set MOZ_REMOTE_SETTINGS_DEVTOOLS=1.
- Have created a new Firefox profile.
- Have this ["user.js"](https://drive.google.com/file/d/1EJM8H7un4rCUaum7QU62wfaGQJBEj2sH/view?usp=sharing) file saved to you computer.
**[Steps to reproduce]:**
1. Create a new profile but do not open it.
2. Paste the "user.js" file into the Profile Folder.
3. Open the Firefox profile newly created.
4. Open a new Private Browsing window.
5. Navigate to the "about:telemetry#events-tab" and search for the "expose" event.
**[Expected result]:**
- An "expose" event related to the experiment is displayed on the "about:telemetry#events-tab" page.
**[Actual result]:**
- No "expose" event related to the experiment is displayed on the "about:telemetry#events-tab" page.
**[Notes]:**
- According to the [“Feature Manifest”](https://searchfox.org/mozilla-central/source/toolkit/components/nimbus/FeatureManifest.yaml#1910) file there should be an exposure event after a Private Window is opened.
- Attaching a screen recording of the issue [here](https://drive.google.com/file/d/1J2vA9kDxv5abEIjO-73KsBe0hSZQoMB4/view?usp=sharing)
|
|
1,863,083 | 16,652,218 |
Created attachment 9361956
bandicam 2023-11-04 04-40-56-944.mp4
i found a vulnerability where user can fall for clickjacking to allow permission
I tested on Firefox version 120.0b4 (64-bit)
steps to reproduce:
1. open clickjacknew.html then click open button
2. Click the "click 3 fastly" button fastly.
|
|
1,863,491 | 16,657,164 |
Created attachment 9362301
about.support.txt
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0
Steps to reproduce:
Browsing Twitter (any of my accounts in their container).
Actual results:
Within a few minutes on the last few Nightly updates Twitter grinds to a halt. Everything loads glacially, including likeing or retweeting. After scrolling clicking on tweet loads the wrong tweet, presumably the scroll hasn't caught up. Happens after disabling Ublock Origin, even in troubleshooting mode. Other websites however seem to be unaffected.
Expected results:
Should be at least as fast as before. Downgrading to Nightly 2023-10-30-16-49-30 (the only old version I tried) restores the usable performance.
|
|
1,863,863 | 16,659,815 |
Created attachment 9362754
bandicam 2023-11-09 10-07-43-779.mp4
i found a vulnerability where user can fall for clickjacking to allow permission
I tested on Firefox dev version 120.0b3 (64-bit)
steps to reproduce:
1. open clickjack0.html then click open button
2. Click the "click 5 fastly" button fastly.
|
|
1,864,123 | 16,661,428 |
EncryptingOutputStream can write random contents of memory to its base stream. This can happen when original data is smaller than 4K. The stream encrypts only actual payload, but data is written to the base stream in whole 4K blocks. EncryptingOutputStream is used by IndexedDB and CacheAPI to store data on disk for private browsing, so the base stream in that case is quota::FileOutputStream, so random contents of memory can end up being stored on disk.
We have a fix for this which fills unused payload with random values.
We suggest to treat this as sec-other since Cache API in private browsing is still gated by a pref and it' still disabled by default. The issue is more serious in the Cache API case, because files stored on disk are fundamental part of the implementation. IndexedDB stores data in separate files only to support storing of DOM Blobs/Files which is not used so often.
IndexedDB in private browsing shipped in FF 115, so the fix might need to be uplifted even to ESR 115.
|
|
1,864,350 | 16,662,718 |
Steps to reproduce:
1. Revoke the camera and microphone permission for Firefox
2. Visit links that have a upload button such as:
https://vocaroo.com/upload
https://postimages.org
and tap the button
3. Deny both permission requests
Actual results:
Nothing
Expected results:
System file picker should pop out because it does not require any permission. This is also what happens on Chrome.
|
|
1,864,478 | 16,665,506 |
Created attachment 9363306
Comparison with the Search icon on the black theme vs white theme
**Found in**
* Nightly 121.0a1
**Affected versions**
* Firefox 120 beta
* Nightly 121.0a1
**Tested platforms**
* Affected platforms: Windows 10
* Unaffected platforms: Ubuntu 22.04, macOS 11.7
**Preconditions**
* In about:config, set "browser.privatebrowsing.felt-privacy-v1" to true
* Enable High Contrast Mode - set the High Contrast Black Theme.
**Steps to reproduce**
1. Open a private window.
2. Observe the in-content Search field.
**Expected result**
* A generic search icon should be displayed on the left side of the "Search with Google or enter address" text.
**Actual result**
* On Windows 10 with a black theme selected, the generic search icon is not visible.
**Regression range**
* Not a regression.
**Additional notes**
* The old search icon is visible with a high contrast black theme when the pref "browser.privatebrowsing.felt-privacy-v1" is set to false.
* This issue is not reproducible on macOS X or Ubuntu when high contrast + black themes are enabled.
|
|
1,864,972 | 16,669,494 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/119.0
Steps to reproduce:
Login using the Danish national eID ("MitID") using the FIDO U2F chip as 2. factor.
This functions correctly on Win10/11 with all versions (at least from v82) to 118.02.
It also works correctly on Google Chrome.
The government agency has been contacted, but was not interested in looking into the matter - referred to using Google Chrome from now on.
Actual results:
Everything in the process works up until the key on the U2F key has been pressed. But then the following error message is displayed:
An error has occurred (my translation of the DA header)
{"timestamp":1700043870123,"correlationId":"dcd2197d-25dd-4654-ac5e-7bddd769ab45","errorId":"AUTHU2F0004","error":{"headers":{"normalizedNames":{},"lazyUpdate":null},"status":500,"statusText":"Internal Server Error","url":"https://www.mitid.dk/mitid-u2f-auth/v1/authenticator-sessions/3efc7c1e-db56-4f85-98a2-5ebf5e02d21e/assertion-response","ok":false,"name":"HttpErrorResponse","message":"Http failure response for https://www.mitid.dk/mitid-u2f-auth/v1/authenticator-sessions/3efc7c1e-db56-4f85-98a2-5ebf5e02d21e/assertion-response: 500 Internal Server Error","error":{"errorCode":"auth.u2f.technical_error","message":"Data could not be converted to json","path":"/v1/authenticator-sessions/3efc7c1e-db56-4f85-98a2-5ebf5e02d21e/assertion-response","timestamp":"2023-11-15T10:18:06.703262Z"}}}
Expected results:
Completion of the login as for all previous versions of Firefox.
Unfortunately I do not know whether this is a bug in Firefox 119.01 or a new intended security feature that is not supported by the Danish eID MitID
The problem has been repeated on 3 different PCs, one of which with a clean install of Firefox 119.01
|
|
1,852,749 | 16,573,918 |
Created attachment 9352676
clusterfuzz-testcase-minimized-advanced_api_fuzzer-4854691663839232
Filing this to track https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62136
|
|
1,852,812 | 16,574,400 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0
Steps to reproduce:
1. Login into my pypi.org account and go to 2FA configuration
2. Try to add a nitrokey 3 mini or nitrokey 3a security USB key as 2FA mecanism
Actual results:
The website raise the following error: `Unsupported credential public key type "OKP"`
Expected results:
The key can be registered without any issue as it does with Chromium.
Notes:
0. It works with Chromium Version 117.0.5938.48 (Official Build) Arch Linux (64-bit). I haven't tested other browsers.
1. After the key is registered from Chromium, I'm able to login using 2FA and the security key with Firefox.
2. The security key works without problem with Firefox on Github, Google or Microsoft accounts.
3. I've also filled a bug on PyPi: https://github.com/pypi/warehouse/issues/14520 and the PyPi team filled an issue on py_webauthn library (used by pypi to auth with security keys): https://github.com/duo-labs/py_webauthn/issues/175
|
|
1,852,948 | 16,575,761 |
Created attachment 9352882
blank_sidebar.gif
**Found in**
* 119.0a1 (2023-09-12)
**Affected versions**
* 119.0a1 (2023-09-12)
**Tested platforms**
* Affected platforms: Ubuntu 20, macOS 12, Windows 10x64
* Unaffected platforms: none
**Preconditions**
* browser.shopping.experience2023.enabled:true
* browser.shopping.experience2023.optedIn:1
**Steps to reproduce**
1. Open multiple Amazon products in different tabs.
2. Close the sidebar by clicking the `X` button or the URL icon button.
3. Switch to other tabs.
**Expected result**
* No sidebar transition is displayed.
**Actual result**
* A blank sidebar is displayed for a split second when switching to other tabs.
**Regression**
* Not a regression.
**Additional notes**
* Attached a screen recording.
|
|
1,852,982 | 16,575,964 |
While going through the telemetry data with Erik, we found a few clients that had spurious es -> es translations. We dug into it, and it was all related to a combination of using the auto-translation feature, changing language packs, and removing your web content languages. I don't have a precise STR for it.
The fix for it is to treat the stored preferences for auto translate as an untrusted list of languages, and validating them during the `maybeOfferTranslate`.
As a bonus, I'll add logic to ensure when we call `TranslationParent.translate` we will check that valid language pairs are received in case there are other regressions in the future.
|
|
1,853,428 | 16,579,418 |
Created attachment 9353446
Screenshot 2023-09-13 205115.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36
Steps to reproduce:
Install 115 (and 116b) from 112. Trying clean install.
Actual results:
Everything looks okay, all folder are displayed, but on the right side no emails appear. Error:
Uncaught TypeError: gFolder is undefined
_onContextMenu chrome://messenger/content/about3Pane.js:2549
handleEvent chrome://messenger/content/about3Pane.js:1512
|
|
1,853,908 | 16,584,519 |
Created attachment 9353882
In this zip file there are 2 png images. One is called conf_interval_plot_median_before_K_generation and the other conf_interval_plot_median_K_generation
Steps to reproduce:
My team and I have tested NSS and we found that it is vulnerable to the Minerva attack and we have now identified the first piece of code that contributes to the side channel.
The test scenario is that we are signing random messages using the SEC_SignData API and then using the private key to extract the K value from the signatures. Then based on the bit size of the extracted nonce we compare full-sized nonces to smaller ones and use the statistical tests to compare the signature times.
Actual results:
Now we have executed the test to verify that all the code from SEC_SignData up to line https://github.com/nss-dev/nss/blob/master/lib/freebl/ec.c#L978 is not leaky and then we have verified that the code in lines https://github.com/nss-dev/nss/blob/master/lib/freebl/ec.c#L979-L986 does leak. We suspect that the side channel is caused by the fact that K is an MPI object, and thus subject to normalization (automatic memory management based on bit size). You can see the results of the analysis below.
For testing, we built nss statically from hg and used the master checkout from 2023-09-14 for both nss and nspr.
The result in the attachment namedconf_interval_plot_median_before_K_generation.png represents code from SEC_SignData up to line 978 of file lib/freebl/ec.c and as you can see in this code there is no leak found. The sample tested has 102,723,896 observations.
The result in the attachment named conf_interval_plot_median_K_generation.png represents code from line 979 to line 986 in file lib/freebl/ec.c and we can clearly see that there is a leak: there is a clear dependency between the bit size of K and the size of the side channel. The sample tested has 129,438,263 observations.
Because we have identified this piece of code as leaky we won't be able to exclude the possibility of a side-channel in the subsequent code. We will need to run the test again after the leaking piece of code is fixed to be able to verify that NSS is not valuable to Minerva anymore (overall we have found a side-channel of ~50 ns and in the k-generating piece of code is only ~45 ns, although the extra 5 ns could be the effect of this piece of code not being side-channel free on the subsequent signature code).
Expected results:
The code should have no side-channels.
|
|
1,854,064 | 16,585,573 |
Created attachment 9354050
Captura de la consola de errores al hacer click en la opcion
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36
Steps to reproduce:
Opción Ver > carpetas > todas las carpetas
Actual results:
Cuando activo la opción esta se vuelve a desactivar sola
Expected results:
Debería de mostrarse toda la lista de correos que tengo instalada y estas no aparecen.
|
|
1,854,068 | 16,585,598 |
The following testcase crashes on mozilla-central revision 20230920-f90822eea608 (debug build, run with --fuzzing-safe --cpu-count=2 --ion-offthread-compile=off --ion-warmup-threshold=10 --baseline-eager):
gczeal(19, 1);
function wasmEvalText(str, imports) {
let binary = wasmTextToBinary(str);
try {
m = new WebAssembly.Module(binary);
} catch(e) {}
return new WebAssembly.Instance(m, imports);
}
let WasmNonAnyrefValues = [];
let {ifNull} = wasmEvalText(`(module
(func (export "ifNull") (param externref externref) (result externref)
local.get 0
)
)`).exports;
evaluate(`
for (let i = 0; i < 10; ++i)
ifNull(()=>{})
`);
Backtrace:
received signal SIGSEGV, Segmentation fault.
#0 0x000012e4e25dc5ba in ?? ()
#1 0x00007ffff3898180 in ?? ()
#2 0xfff9800000000000 in ?? ()
#3 0x0000000000000008 in ?? ()
#4 0x00007fffffffc010 in ?? ()
#5 0x000012e4e25dc4e9 in ?? ()
#6 0x0000000000000000 in ?? ()
rax 0x3aa13de00048 64464202235976
rbx 0xfffe2f2f2f2f2f2f -511070251831505
rcx 0xfffe3aa13de00048 -498485751185336
rdx 0x2622dccea040 41931175272512
rsi 0x3aa13de00018 64464202235928
rdi 0x3aa13de00048 64464202235976
rbp 0x7fffffffbfd8 140737488338904
rsp 0x7fffffffbfc0 140737488338880
r8 0x7fffffffbfc0 140737488338880
r9 0x0 0
r10 0x0 0
r11 0x7ffff3e0dfb8 140737284988856
r12 0x0 0
r13 0x0 0
r14 0x7ffff3898180 140737279263104
r15 0x0 0
rip 0x12e4e25dc5ba 20774259639738
=> 0x12e4e25dc5ba: mov (%rbx),%rbx
0x12e4e25dc5bd: mov (%rbx),%rbx
Marking s-s due to poison values involved.
|
|
1,889,341 | 16,873,867 |
Created attachment 9394723
image_2024_04_03T09_00_29_332Z.png
**[Affected versions]:**
- Firefox Beta, 125.0b7, BUILD ID: 20240401091600
- Firefox Release, 124.0.2, BUILD ID: 20240401114208
**[Affected Platforms]:**
- Windows 11 x64
- Windows 10 x64
**[Prerequisites]:**
- Have the [“user.js”](https://drive.google.com/file/d/1zJJUXs2r1yA8-iCyGBML4aCBqRvnWRgs/view?usp=sharing) downloaded on your computer.
- Have a Firefox IT locale installed.
- Have a Firefox profile younger than 28 days.
**[Steps to reproduce]:**
1. Navigate to the profile folder and paste the user.js from the prerequisites.
2. Open Firefox using the profile from the prerequisites.
3. Open a new tab.
4. Observe the “CSAT Microsurvey” cards in the bottom right part of the page.
**[Expected results]:**
- The title of the “CSAT Microsurvey” cards is not cut by the “X” button.
**[Actual results]:**
- The title of the “CSAT Microsurvey” cards is cut by the “X” button on the “IT” locale.
**[Notes]:**
- This issue is also reproducible on the Treatment B branch of the experiment.
- When hovering over the “X” button the missing text is displayed.
- This issue is also reproducible on the second card of the “CSAT Microsurvey”.
- This issue is not reproducible on the MacOS 14.3 and Ubuntu 22.04 platforms.
- Attached a screenshot of the issue.
|
|
1,889,360 | 16,874,038 |
Created attachment 9394753
image_2024_04_03T09_11_55_340Z.png
**[Notes]:**
- On Windows 11 x64 the text on the “Thank you” card is not correctly displayed, and the elements on the survey are not aligned.
**[Affected versions]:**
- Firefox Beta, 125.0b7, BUILD ID: 20240401091600
- Firefox Release, 124.0.2, BUILD ID: 20240401114208
- Firefox Release 123.0.1, BUILD ID: 20240304104836
**[Affected Platforms]:**
- Windows 11 x64
- Windows 10 x64
- MacOS 14.3
- Ubuntu 22.04
**[Prerequisites]:**
- Have the [“user.js”](https://drive.google.com/file/d/1zJJUXs2r1yA8-iCyGBML4aCBqRvnWRgs/view?usp=sharing) downloaded on your computer.
- Have a Firefox IT locale installed.
- Have a Firefox profile younger than 28 days.
**[Steps to reproduce]:**
1. Navigate to the profile folder and paste the user.js from the prerequisites.
2. Open Firefox using the profile from the prerequisites.
3. Open a new tab.
4. Navigate through the “CSAT Microsurvey” until the “Thank you” card is displayed.
**[Expected results]:**
- The text on the “Thank you” card is not cut by the “X” button and the elements displayed on the survey are aligned.
**[Actual results]:**
- The text on the “Thank you” card is cut by the “X” button and the survey elements are not aligned.
**[Additional Notes]:**
- This issue is also reproducible on the Treatment B branch of the experiment.
- When hovering over the “X” button the missing text is displayed.
- Attached a screenshot of the issue.
|
|
1,890,367 | 16,882,299 |
STR:
- open a pdf;
- click on the ink button (button with the pen icon);
- draw something without release the mouse button;
- release the button;
- draw something else.
The second draw isn't possible.
This is a regression from bug 1866850 and especially from:
https://github.com/mozilla/pdf.js/pull/17823
|
|
1,890,764 | 16,885,112 |
**Found in**
* Beta/RC 125
**Affected versions**
* macOS
**Tested platforms**
* Affected platforms: all macOS
* Unaffected platforms: Windows, Ubuntu
**Steps to reproduce**
1. Install a .pkg beta version from 125 of Firefox (e.g 125.0b1)
2. Start Firefox and visit About Firefox to trigger the update & restart the browser
3. Select Restart Firefox from macOS prompt and input the password
4. Firefox is restarted and prompts to manually download the newest build
**Expected result**
* Firefox should be updated to latest 125 RC version
**Actual result**
* Firefox is not updated, and will ask the user to manually download the newest build
**Additional notes**
* The issue can be seen in the [following attachment](https://drive.google.com/file/d/1bmWo83JI3F1H5FhWE2cyRSnDNOEGWzi1/view?usp=sharing)
* Downloading the update again will result in a successful update
|
|
1,891,322 | 16,888,528 |
Created attachment 9396501
testcase.html
Found while fuzzing m-c 20240412-be4463b26a49 (--enable-debug --enable-fuzzing)
To reproduce via Grizzly Replay:
```
$ pip install fuzzfetch grizzly-framework
$ python -m fuzzfetch -d --fuzzing -n firefox
$ python -m grizzly.replay.bugzilla ./firefox/firefox <bugid>
```
Hit MOZ_CRASH(assertion failed: !(first.offset > last.offset)) at gfx/wr/webrender_api/src/gradient_builder.rs:137
```
#0 0x719780833d85 in MOZ_Crash /builds/worker/workspace/obj-build/dist/include/mozilla/Assertions.h:317:3
#1 0x719780833d85 in RustMozCrash /builds/worker/checkouts/gecko/mozglue/static/rust/wrappers.cpp:18:3
#2 0x71978083323d in mozglue_static::panic_hook::h43eaefe9eb9c21c7 /builds/worker/checkouts/gecko/mozglue/static/rust/lib.rs:98:9
#3 0x71978083323d in core::ops::function::Fn::call::h428b5e23b1db83db /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:79:5
#4 0x7197819211a5 in _$LT$alloc..boxed..Box$LT$F$C$A$GT$$u20$as$u20$core..ops..function..Fn$LT$Args$GT$$GT$::call::h4dd5cc3b5605ae1a /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/alloc/src/boxed.rs:2029:9
#5 0x7197819211a5 in std::panicking::rust_panic_with_hook::hb164d19c0c1e71d4 /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:785:13
#6 0x719781920eb8 in std::panicking::begin_panic_handler::_$u7b$$u7b$closure$u7d$$u7d$::h0369088c533c20e9 /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:651:13
#7 0x71978191e3e5 in std::sys_common::backtrace::__rust_end_short_backtrace::hc11d910daf35ac2e /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/sys_common/backtrace.rs:171:18
#8 0x719781920c43 in rust_begin_unwind /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:647:5
#9 0x71978196ce54 in core::panicking::panic_fmt::ha6effc2775a0749c /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panicking.rs:72:14
#10 0x71978196cf12 in core::panicking::panic::h44790a89027c670f /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/panicking.rs:144:5
#11 0x719780558fe3 in webrender_api::gradient_builder::GradientBuilder::normalize::he7c6ad6d8268af6f /builds/worker/checkouts/gecko/gfx/wr/webrender_api/src/gradient_builder.rs:137:9
#12 0x719780558962 in webrender_api::gradient_builder::GradientBuilder::radial_gradient::h574f1573485c8162 /builds/worker/checkouts/gecko/gfx/wr/webrender_api/src/gradient_builder.rs:91:13
#13 0x719780552cc3 in webrender_api::display_list::DisplayListBuilder::create_radial_gradient::h117d937a913e316d /builds/worker/checkouts/gecko/gfx/wr/webrender_api/src/display_list.rs:1524:24
#14 0x71978007b056 in wr_dp_push_radial_gradient /builds/worker/checkouts/gecko/gfx/webrender_bindings/src/bindings.rs:3702:20
#15 0x71977c45ad52 in mozilla::nsCSSGradientRenderer::BuildWebRenderDisplayItems(mozilla::wr::DisplayListBuilder&, mozilla::layers::StackingContextHelper const&, nsRect const&, nsRect const&, nsSize const&, mozilla::gfx::IntRectTyped<mozilla::CSSPixel> const&, bool, float) /builds/worker/checkouts/gecko/layout/painting/nsCSSRenderingGradients.cpp:1360:14
#16 0x71977c48936a in mozilla::nsImageRenderer::BuildWebRenderDisplayItems(nsPresContext*, mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, mozilla::layers::StackingContextHelper const&, mozilla::layers::RenderRootStateManager*, mozilla::nsDisplayItem*, nsRect const&, nsRect const&, nsRect const&, nsPoint const&, nsSize const&, mozilla::gfx::IntRectTyped<mozilla::CSSPixel> const&, float) /builds/worker/checkouts/gecko/layout/painting/nsImageRenderer.cpp:584:16
#17 0x71977c4460c3 in mozilla::nsImageRenderer::BuildWebRenderDisplayItemsForLayer(nsPresContext*, mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, mozilla::layers::StackingContextHelper const&, mozilla::layers::RenderRootStateManager*, mozilla::nsDisplayItem*, nsRect const&, nsRect const&, nsPoint const&, nsRect const&, nsSize const&, float) /builds/worker/checkouts/gecko/layout/painting/nsImageRenderer.cpp:775:10
#18 0x71977c443677 in nsCSSRendering::BuildWebRenderDisplayItemsForStyleImageLayerWithSC(nsCSSRendering::PaintBGParams const&, mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, mozilla::layers::StackingContextHelper const&, mozilla::layers::RenderRootStateManager*, mozilla::nsDisplayItem*, mozilla::ComputedStyle*, nsStyleBorder const&) /builds/worker/checkouts/gecko/layout/painting/nsCSSRendering.cpp:2729:36
#19 0x71977c4431ef in nsCSSRendering::BuildWebRenderDisplayItemsForStyleImageLayer(nsCSSRendering::PaintBGParams const&, mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, mozilla::layers::StackingContextHelper const&, mozilla::layers::RenderRootStateManager*, mozilla::nsDisplayItem*) /builds/worker/checkouts/gecko/layout/painting/nsCSSRendering.cpp:1958:10
#20 0x71977c469c55 in mozilla::nsDisplayBackgroundImage::CreateWebRenderCommands(mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, mozilla::layers::StackingContextHelper const&, mozilla::layers::RenderRootStateManager*, mozilla::nsDisplayListBuilder*) /builds/worker/checkouts/gecko/layout/painting/nsDisplayList.cpp:3413:7
#21 0x719777b34ac6 in mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommands(mozilla::nsDisplayItem*, mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, mozilla::layers::StackingContextHelper const&, mozilla::nsDisplayListBuilder*) /builds/worker/checkouts/gecko/gfx/layers/wr/WebRenderCommandBuilder.cpp:1864:41
#22 0x719777b33282 in mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList(mozilla::nsDisplayList*, mozilla::nsDisplayItem*, mozilla::nsDisplayListBuilder*, mozilla::layers::StackingContextHelper const&, mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, bool) /builds/worker/checkouts/gecko/gfx/layers/wr/WebRenderCommandBuilder.cpp:2130:7
#23 0x71977c4744b2 in CreateWebRenderCommandsNewClipListOption /builds/worker/checkouts/gecko/layout/painting/nsDisplayList.cpp:4620:30
#24 0x71977c4744b2 in CreateWebRenderCommands /builds/worker/checkouts/gecko/layout/painting/nsDisplayList.h:4959:12
#25 0x71977c4744b2 in mozilla::nsDisplayOwnLayer::CreateWebRenderCommands(mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, mozilla::layers::StackingContextHelper const&, mozilla::layers::RenderRootStateManager*, mozilla::nsDisplayListBuilder*) /builds/worker/checkouts/gecko/layout/painting/nsDisplayList.cpp:5246:22
#26 0x719777b34ac6 in mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommands(mozilla::nsDisplayItem*, mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, mozilla::layers::StackingContextHelper const&, mozilla::nsDisplayListBuilder*) /builds/worker/checkouts/gecko/gfx/layers/wr/WebRenderCommandBuilder.cpp:1864:41
#27 0x719777b33282 in mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList(mozilla::nsDisplayList*, mozilla::nsDisplayItem*, mozilla::nsDisplayListBuilder*, mozilla::layers::StackingContextHelper const&, mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, bool) /builds/worker/checkouts/gecko/gfx/layers/wr/WebRenderCommandBuilder.cpp:2130:7
#28 0x719777b3180a in mozilla::layers::WebRenderCommandBuilder::BuildWebRenderCommands(mozilla::wr::DisplayListBuilder&, mozilla::wr::IpcResourceUpdateQueue&, mozilla::nsDisplayList*, mozilla::nsDisplayListBuilder*, mozilla::layers::WebRenderScrollData&, WrFiltersHolder&&) /builds/worker/checkouts/gecko/gfx/layers/wr/WebRenderCommandBuilder.cpp:1785:5
#29 0x719777b474b8 in mozilla::layers::WebRenderLayerManager::EndTransactionWithoutLayer(mozilla::nsDisplayList*, mozilla::nsDisplayListBuilder*, WrFiltersHolder&&, mozilla::layers::WebRenderBackgroundData*, double) /builds/worker/checkouts/gecko/gfx/layers/wr/WebRenderLayerManager.cpp:365:30
#30 0x71977c462f87 in mozilla::nsDisplayList::PaintRoot(mozilla::nsDisplayListBuilder*, gfxContext*, unsigned int, mozilla::Maybe<double>) /builds/worker/checkouts/gecko/layout/painting/nsDisplayList.cpp:2305:18
#31 0x71977c0d3761 in nsLayoutUtils::PaintFrame(gfxContext*, nsIFrame*, nsRegion const&, unsigned int, mozilla::nsDisplayListBuilderMode, nsLayoutUtils::PaintFrameFlags) /builds/worker/checkouts/gecko/layout/base/nsLayoutUtils.cpp:3312:9
#32 0x71977c03ce9f in mozilla::PresShell::PaintInternal(nsView*, mozilla::PaintInternalFlags) /builds/worker/checkouts/gecko/layout/base/PresShell.cpp:6578:5
#33 0x71977bbb6d62 in nsViewManager::ProcessPendingUpdatesPaint(nsIWidget*) /builds/worker/checkouts/gecko/view/nsViewManager.cpp:408:18
#34 0x71977bbb67ee in nsViewManager::ProcessPendingUpdatesForView(nsView*, bool) /builds/worker/checkouts/gecko/view/nsViewManager.cpp:343:22
#35 0x71977bbb7e4d in nsViewManager::ProcessPendingUpdates() /builds/worker/checkouts/gecko/view/nsViewManager.cpp:916:5
#36 0x71977bff11e5 in nsRefreshDriver::Tick(mozilla::layers::BaseTransactionId<mozilla::VsyncIdType>, mozilla::TimeStamp, nsRefreshDriver::IsExtraTick) /builds/worker/checkouts/gecko/layout/base/nsRefreshDriver.cpp:2841:11
#37 0x71977bffa621 in TickDriver /builds/worker/checkouts/gecko/layout/base/nsRefreshDriver.cpp:367:13
#38 0x71977bffa621 in mozilla::RefreshDriverTimer::TickRefreshDrivers(mozilla::layers::BaseTransactionId<mozilla::VsyncIdType>, mozilla::TimeStamp, nsTArray<RefPtr<nsRefreshDriver>>&) /builds/worker/checkouts/gecko/layout/base/nsRefreshDriver.cpp:345:7
#39 0x71977bffa520 in mozilla::RefreshDriverTimer::Tick(mozilla::layers::BaseTransactionId<mozilla::VsyncIdType>, mozilla::TimeStamp) /builds/worker/checkouts/gecko/layout/base/nsRefreshDriver.cpp:361:5
#40 0x71977bffa3bd in mozilla::VsyncRefreshDriverTimer::RunRefreshDrivers(mozilla::layers::BaseTransactionId<mozilla::VsyncIdType>, mozilla::TimeStamp) /builds/worker/checkouts/gecko/layout/base/nsRefreshDriver.cpp:951:5
#41 0x71977bff965c in mozilla::VsyncRefreshDriverTimer::TickRefreshDriver(mozilla::layers::BaseTransactionId<mozilla::VsyncIdType>, mozilla::TimeStamp) /builds/worker/checkouts/gecko/layout/base/nsRefreshDriver.cpp:861:5
#42 0x71977bff88c9 in mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::NotifyVsyncTimerOnMainThread() /builds/worker/checkouts/gecko/layout/base/nsRefreshDriver.cpp:592:14
#43 0x71977b3090fb in mozilla::dom::VsyncMainChild::RecvNotify(mozilla::VsyncEvent const&, float const&) /builds/worker/checkouts/gecko/dom/ipc/VsyncMainChild.cpp:66:15
#44 0x71977b5fb905 in mozilla::dom::PVsyncChild::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/obj-build/ipc/ipdl/PVsyncChild.cpp:237:78
#45 0x71977b4e3ae0 in mozilla::dom::PContentChild::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/obj-build/ipc/ipdl/PContentChild.cpp:8282:32
#46 0x719777250bbf in mozilla::ipc::MessageChannel::DispatchAsyncMessage(mozilla::ipc::ActorLifecycleProxy*, IPC::Message const&) /builds/worker/checkouts/gecko/ipc/glue/MessageChannel.cpp:1818:25
#47 0x71977724d912 in mozilla::ipc::MessageChannel::DispatchMessage(mozilla::ipc::ActorLifecycleProxy*, mozilla::UniquePtr<IPC::Message, mozilla::DefaultDelete<IPC::Message>>) /builds/worker/checkouts/gecko/ipc/glue/MessageChannel.cpp:1737:9
#48 0x71977724e592 in mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::ActorLifecycleProxy*, mozilla::ipc::MessageChannel::MessageTask&) /builds/worker/checkouts/gecko/ipc/glue/MessageChannel.cpp:1530:3
#49 0x71977724f6df in mozilla::ipc::MessageChannel::MessageTask::Run() /builds/worker/checkouts/gecko/ipc/glue/MessageChannel.cpp:1628:14
#50 0x71977652e097 in mozilla::RunnableTask::Run() /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:578:16
#51 0x719776523706 in mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal(mozilla::detail::BaseAutoLock<mozilla::Mutex&> const&) /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:905:26
#52 0x719776521ee7 in mozilla::TaskController::ExecuteNextTaskOnlyMainThreadInternal(mozilla::detail::BaseAutoLock<mozilla::Mutex&> const&) /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:728:15
#53 0x719776522365 in mozilla::TaskController::ProcessPendingMTTask(bool) /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:514:36
#54 0x719776532036 in operator() /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:232:37
#55 0x719776532036 in mozilla::detail::RunnableFunction<mozilla::TaskController::TaskController()::$_0>::Run() /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.h:548:5
#56 0x719776547362 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/checkouts/gecko/xpcom/threads/nsThread.cpp:1199:16
#57 0x71977654e4ad in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/checkouts/gecko/xpcom/threads/nsThreadUtils.cpp:480:10
#58 0x719777256b05 in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/checkouts/gecko/ipc/glue/MessagePump.cpp:85:21
#59 0x71977716ca61 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:363:3
#60 0x71977716ca61 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:345:3
#61 0x71977bc22168 in nsBaseAppShell::Run() /builds/worker/checkouts/gecko/widget/nsBaseAppShell.cpp:148:27
#62 0x71977bce5e18 in nsAppShell::Run() /builds/worker/checkouts/gecko/widget/gtk/nsAppShell.cpp:470:33
#63 0x71977db31c8b in XRE_RunAppShell() /builds/worker/checkouts/gecko/toolkit/xre/nsEmbedFunctions.cpp:712:20
#64 0x7197772579e6 in mozilla::ipc::MessagePumpForChildProcess::Run(base::MessagePump::Delegate*) /builds/worker/checkouts/gecko/ipc/glue/MessagePump.cpp:235:9
#65 0x71977716ca61 in RunHandler /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:363:3
#66 0x71977716ca61 in MessageLoop::Run() /builds/worker/checkouts/gecko/ipc/chromium/src/base/message_loop.cc:345:3
#67 0x71977db314b2 in XRE_InitChildProcess(int, char**, XREChildData const*) /builds/worker/checkouts/gecko/toolkit/xre/nsEmbedFunctions.cpp:647:34
#68 0x58b3882ba5c6 in content_process_main /builds/worker/checkouts/gecko/browser/app/../../ipc/contentproc/plugin-container.cpp:57:28
#69 0x58b3882ba5c6 in main /builds/worker/checkouts/gecko/browser/app/nsBrowserApp.cpp:375:18
#70 0x71978c429d8f in __libc_start_call_main csu/../sysdeps/nptl/libc_start_call_main.h:58:16
#71 0x71978c429e3f in __libc_start_main csu/../csu/libc-start.c:392:3
#72 0x58b3882902f8 in _start (/home/user/workspace/browsers/m-c-20240413085157-fuzzing-debug/firefox-bin+0x592f8) (BuildId: 8553aaf648eb5b578f899bbf9a05117a2b83de03)
```
|
|
1,895,707 | 16,926,547 |
Seeing a lot of crash reports on Sentry on nightly.
|
|
1,895,711 | 16,926,575 |
### Steps to reproduce
1. Browse to a site in Fenix nightly
2. Select share from the options menu
3. Select a device from SEND TO DEVICE
### Expected behavior
The site should open on the device you selected
### Actual behavior
An error is displayed `Unable to send`
### Device information
* Firefox version: 127.0a1
* Android device model: Samsung S24+
* Android OS version: Android 14
### Any additional information?
This is not reproducible in 125 release or 126 beta
|
|
1,895,865 | 16,927,806 |
Created attachment 9400893
rec of the issue.gif
**[Affected versions]:**
- Firefox RC 126.0 - Build ID: 20240506203248
**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64
**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
- `nimbus.debug` set to `true`
- `messaging-system.log` set to `all`
- Have the "Browser Console" opened.
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=embedded-import-spotlight-existing-users&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Restart the browser and observe the behavior.
4. Focus the "Browser Console" and observe the content.
**[Expected result]:**
- Step 3: The "Embedded Import Spotlight" is successfully triggered.
- Step 4: No errors related to the "EMBEDDED_IMPORT_SPOTLIGHT" are displayed.
**[Actual result]:**
- Step 3: The "Embedded Import Spotlight" is not triggered
- Step 4: A "TARGETING_EXPRESSION_ERROR" related to the "EMBEDDED_IMPORT_SPOTLIGHT" is displayed.
**[Additional Notes]:**
- This issue is reproducible on all the branches of both "[Early Day User](https://experimenter.services.mozilla.com/nimbus/embedded-import-spotlight/summary)" and "[Existing Users](https://experimenter.services.mozilla.com/nimbus/embedded-import-spotlight-existing-users/summary)" experiments.
- Attached a screen recording of the issue.
|
|
1,895,866 | 16,927,808 |
**[Affected versions]:**
- Firefox RC 126.0 - Build ID: 20240506203248
**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64
**[Steps to reproduce]:**
1. Open the browser and navigate to the "https://experimenter.services.mozilla.com/nimbus/embedded-import-spotlight/summary" page.
2. Scroll down to any treatment branches and observe the message targeting.
**[Expected result]:**
- The message targets profiles younger than 28 days.
**[Actual result]:**
- The message targets profiles older than 28 days: `!((currentDate|date - profileAgeCreated|date) / 86400000 < 28)`.
**[Additional Notes]:**
- This issue is reproducible on all the branches of the "[Early Day User](https://experimenter.services.mozilla.com/nimbus/embedded-import-spotlight/summary)" experiment.
|
|
1,896,090 | 16,929,136 |
Created attachment 9401075
rec of the issue.gif
**[Affected versions]:**
- Firefox RC 126.0 - Build ID: 20240509170740
**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64
**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
- `nimbus.debug` set to `true`
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=embedded-import-spotlight-existing-users&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Restart the browser and observe the spotlight's "X" button placement.
**[Expected result]:**
- The "X" button is displayed in the top-right part of the "Embedded Import Spotlight".
**[Actual result]:**
- The "X" button is displayed in the top-right part of the browser.
**[Additional Notes]:**
- This issue is reproducible on all the branches of both "[Early Day User](https://experimenter.services.mozilla.com/nimbus/embedded-import-spotlight/summary)" and "[Existing Users](https://experimenter.services.mozilla.com/nimbus/embedded-import-spotlight-existing-users/summary)" experiments.
- Attached a screen recording of the issue.
|
|
1,896,339 | 16,932,473 |
Created attachment 9401356
Screen_recording_20240513_113953.mp4
### Steps to reproduce
1. Create a new collection with multiple tabs
2. Go back to home screen
3. Swipe to delete last tab from collection
### Expected behavior
The last element from the collection is simply deleted, without the rest of the collection being affected.
### Actual behavior
The whole collection is deleted. Undoing the deletion restores the collection with only one element.
### Device information
* Firefox version: Nightly 127.0a1
* Android device model: Pixel 7
* Android OS version: Android 13
### Any additional information?
|
|
1,896,364 | 16,932,606 |
Created attachment 9401384
rec of the issue.gif
**[Affected versions]:**
- Firefox RC 126.0 - Build ID: 20240509170740
**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64
**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
- `nimbus.debug` set to `true`
- Have the "Browser Console" opened.
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=embedded-import-spotlight&optin_branch=control&optin_collection=nimbus-preview".
3. Restart the browser and observe the behavior.
4. Focus the "Browser Cosole" and observe the displayed telemetry events.
**[Expected result]:**
- Step 3: The "EMBEDDED_IMPORT_SPOTLIGHT" is not triggered.
- Step 4: No telemetry events related to the "EMBEDDED_IMPORT_SPOTLIGHT" are generated.
**[Actual result]:**
- Step 3: An overlay is displayed on the opened tab and an "IMPRESSION" telemetry event related to the "EMBEDDED_IMPORT_SPOTLIGHT" is generated.
- Step 4: An "IMPRESSION" telemetry event related to the "EMBEDDED_IMPORT_SPOTLIGHT" is generated.
**[Additional Notes]:**
- This issue is reproducible on the "Control" branch of both "[Early Day User](https://experimenter.services.mozilla.com/nimbus/embedded-import-spotlight/summary)" and "[Existing Users](https://experimenter.services.mozilla.com/nimbus/embedded-import-spotlight-existing-users/summary)" experiments.
- Attached a screen recording of the issue.
|
|
1,896,597 | 16,934,258 |
Created attachment 9401621
extensions links not working.mp4
**[Affected versions]:**
- Firefox Release 126.0 (Build ID: 20240509170740)
**[Affected Platforms]:**
- Windows 10
- Windows 11
[Prerequisites]:
- Have a non Firefox browser installed and make sure that you have at least one compatible add-on installed.
- Have the following prefs in the "about:config" page:
- nimbus.debug set to true
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=embedded-import-spotlight-existing-users&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Restart the browser.
4. From the "Embedded Import Spotlight" select the browser and the profile that has a compatible add-on installed.
5. Click the "Import to Firefox" button.
6. Click any of the links displayed under "Extensions" category.
7. Observe the behavior.
**[Expected result]:**
- The link is correctly opened in the background.
**[Actual result]:**
- Nothing happens.
**[ Notes]:**
- The issue is NOT reproducible if the Import modal is triggered from "about:preferences#general" or "about:logins" page.
- Attached is a screen recording with the issue.
|
|
1,897,653 | 16,941,403 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0
Steps to reproduce:
1) Visit https://www.bitstamp.net/market/tradeview/
Actual results:
The TradeView component on the page does not load after the update to Firefox 126.0 on all of my devices.
Expected results:
The Tradeview component should have loaded like it did in previous versions and other browsers.
|
|
1,897,775 | 16,944,256 |
Created attachment 9402757
20240520_152922.mp4
**Environment:**
Operating system: Android 12/ Android 13
Firefox version: Firefox Nightly 128.0a1 (2016021279-🦎128.0a1-20240516214828🦎)
**Preconditions:**
Clean profile
**Steps to reproduce:**
1. Navigate to: https://www.dropbox.com/home
2. Perform account login
3. Tap inside the search field located in the page header and observe the result
**Expected Behavior:**
The search page is opened
**Actual Behavior:**
Nothing happens
**Notes:**
- Reproducible regardless of the status of ETP
- Reproducible on the latest build of Firefox Nightly and Release
- Works as expected using Chrome
- Attachment provided
- Issue found during WebCompat team [Top100] websites testing
|
|
1,899,029 | 16,952,784 |
User Agent: Mozilla/5.0 (Android 10; Mobile; rv:128.0) Gecko/128.0 Firefox/128.0
Steps to reproduce:
While downloading a file, pressing: Pause, Cancel (it will delete the file from the download, but in the phone storage it will still be available) or switching from Wifi connection to Mobile Data during the download, will show the button: Resume download and will resume downloading, but even if the file will be downloaded, in the phone storage the file will be unusable, for example an .apk file cannot be installed.
Actual results:
Hitting the break buttons and switching from one connection to another causes the file to appear wrong.
Expected results:
The filer must follow each action separately so that the file is available correctly.
|
|
1,899,757 | 16,960,131 |
Created attachment 9404776
vmplayer_6pfNgooQrX.mp4
**[Affected versions]:**
- Firefox Nightly 128.0a1 - Build ID: 20240529214854
- Firefox Beta 127.0b8 - Build ID: 20240529091551
- Firefox Release 126.0.1 - Build ID: 20240526221752
**[Affected Platforms]:**
- Windows 10
- macOS 14
- Ubuntu 22.04
**[Prerequisites]:**
- Have a Firefox build installed and use a new profile.
- Be enrolled in any branch (except control) of the Pin Email and Calendar experiment ([early day](https://experimenter.services.mozilla.com/nimbus/pin-email-and-calendar-tabs-early-day-user/summary) / [existing](https://experimenter.services.mozilla.com/nimbus/pin-email-and-calendar-tabs-existing-user/summary)) through forced enrollment.
- Unenroll from any experiment or rollout that the profile might be in using the about:studies page.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites and open a new tab.
2. Right click the `reddit` Top Site and choose the `Open Link in a New Tab`.
3. Repeat step 2.
4. Repeat step 2 and observe the current tab.
**[Expected result]:**
- No message is displayed.
**[Actual result]:**
- The "Pin" message is displayed.
**[Notes]:**
- Attached a screen recording of the issue.
|
|
1,900,191 | 16,962,706 |
Steps to reproduce:
1. Open and play Live video (Not all but several live. It seems low latency live stream)
e.g. https://www.youtube.com/watch?v=jQaDDtiu05E w/ 1080p. Or other low latency video streams.
Actual Results:
Video stops after for a while. But audio is playing.
Profiler log: https://share.firefox.dev/4aEXK8R
When the buffer length reaches 0s, the image seems to stop without recovery.
|
|
1,900,423 | 16,966,385 |
[Figma](https://www.figma.com/design/5hUBRTrDG3iWwi26KyLhtz/New-Tab?node-id=6510-70042&t=ZbwDxaSiCdEMAO5c-0)
Clean up layout styles for wallpaper v2.
|
|
1,900,486 | 16,966,710 |
Created attachment 9405403
Screenshot 2024-06-03 at 3.23.39 PM.png
STEPS TO REPLICATE
1) You will need to use Review Checker by going to an Amazon, Best Buy, or Walmart PDP
2) Opt in when you see the opt-in screen by hitting "Yes, try it"
3) You'll need to fill out the Satisfaction microsurvey, which is triggered by being at least on your 2nd session and having already visited 5 PDPs that have available Fakespot Reviews Analyses on them. You can also simulate this experience by manually setting these preferences in about:config while testing:
browser.shopping.experience2023.survey.enabled must be true (experiment does this)
browser.shopping.experience2023.survey.optedInTime must be 24 hours ago (try 1696550403)
browser.shopping.experience2023.survey.hasSeen must be false
browser.shopping.experience2023.survey.pdpVisits must be 5
browser.shopping.experience2023.optedIn must be 1
4) Complete the Satisfaction Microsurvey - you should be asked 2 questions, then you'll see a green confirmation message.
5) Hit "Turn off Review Checker" to disable the feature (at any point after having filled out the survey)
6) Navigate to another PDP
7) Manually turn on Review Checker again from the Shopping Icon
EXPECTED:
- Review Checker should work as expected, you should be able to see an opt-in screen telling you about using the Review Checker
ACTUAL RESULTS
- See a blank Review Checker sidebar with only "Thank you for the feedback" in green, or if you dismissed that, then you should only see a blank screen in that sidebar where there normally would be content, with Review Checker as a title
ADDITIONAL NOTES
- The blank screen doesn't seem to happen if you hit X, the Shopping icon, or turn off Auto-Open to temporarily close out the Review Checker. It seems to only happen after you fill out the Microsurvey, and, at any point after filling out the Microsurvey, disable the Review Checker feature by clicking "Turn off Review Checker"
|
|
1,901,057 | 16,970,513 |
It appears that with the v2 search rollout, we are not sending the clickUrl to Admarketplace
https://searchfox.org/mozilla-central/source/browser/components/search/BrowserSearchTelemetry.sys.mjs#185
|
|
1,901,325 | 16,972,274 |
Created attachment 9406192
Solarwinds_Papertrail_dashboard_organization_selection_dropdown.png
**User Agent**: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:128.0) Gecko/20100101 Firefox/128.0
**Steps to reproduce**
1. Have access to at least two different SolarWinds Papertrail organizations (Mozilla has 4 that I'm aware of).
2. Log into Solarwinds Papertrail.
3. Navigate to https://papertrailapp.com/
4. Take note of what the current dashboard looks like.
5. In the top right corner, click the current organization name (Mozilla Marketing in the attached screenshot) and select a different organization from the dropdown.
**Expected results**
* The organization listed in the top right corner changes to the newly selected, different organization.
* The dashboard for the newly selected organization is displayed.
**Actual results**
* The organization listed in the top right corner does not change.
* The dashboard for the previously selected organization is displayed.
**Notes**
* Two other teammates were also able to reproduce this in Nightly 128.0a1.
* I do not see this bug in release Firefox 126.0.1.
|
|
1,901,497 | 16,974,874 |
**Environment:**
Operating system: Windows 10
Firefox version: Firefox 126.0/Firefox 128.0a1
**Steps to reproduce:**
1. Navigate to: https://fairfaxmedia.pressreader.com/the-dominion-post
2. Zoom in and out inside the article using the mouse wheel
3. Observe
**Expected Behavior:**
Zooming is smooth
**Actual Behavior:**
Zooming presents issues
**Notes:**
- Reproduces regardless of the status of ETP
- Reproduces in Firefox Nightly, Firefox Release
- Does not reproduce in Chrome
- Performance profile: https://share.firefox.dev/3yPrvq2
- About:memory report and troubleshooting info are attached
Created from https://github.com/webcompat/web-bugs/issues/137959
|
|
1,901,979 | 16,978,134 |
Created attachment 9406948
Window2.mp4
**Found in**
* Nightly 129.0a1 (2024-06-11)
**Affected versions**
* Nightly 129.0a1 (2024-06-11)
* Beta 128
* Release 127.0 (64-bit)
**Affected platforms**
* All
**Preconditions**
* browser.shopping.experience2023.enabled - true
browser.shopping.experience2023.optedIn - 1
**Steps to reproduce**
1. Open a Private Window.
2. Reach any product details page on Amazon.
3. Click inside the Normal window and Open a new Tab. (If youre on a product details page in the normal window Simply open the Review Checker.)
4. Go back to the Private window and Hit the Back button.
**Expected result**
* The Review Checker should not be displayed at all in a Private window.
Going back to the Search results should close the Private Window automatically.
**Actual result**
* The Review Checker is opened when the user interacts with the Normal Window.
Going back from the Product Details page in the Private window will keep the Sidebar open.
**Regression range**
Not a regression.
|
|
1,902,267 | 16,980,035 |
Created attachment 9407208
DownloadCompleteUnactionable.mp4
### Steps to reproduce
1. Have the new toolbar enabled and set to be shown on top (issue does not reproduce when the toolbar is at bottom)
2. Download a file (can use https://www.thinkbroadband.com/download for test downloads)
3. Check the "download complete" dialog
### Expected behavior
The "download complete" dialog is shown fully and the user can easily interact with.
### Actual behavior
The main action - the "Open" button of the "download complete" dialog is obstructed by the navigation bar.
|
|
1,902,313 | 16,980,248 |
From bug 1882040
When trying to swipe back a short (swiping from top to bottom), the website refreshs and does not go back to the last short video.
Steps to Reproduce:
When trying to swipe back a short (swiping from top to bottom), the website refreshs and does not go back to the last short video.
See bug 1882040 comment 9 for some more details about what's going on.
|
|
1,902,761 | 16,982,593 |
### Steps to reproduce
1. Ensure a TalkBack is running
1. Open Firefox and confirm the a tab is opened
1. If this is a New Tab:
1. dismiss the keyboard (until the bug 1902757 is resolved) and, if opened, any OMC onboarding notifications or type in any URL
1. open any tab, i.e. `wikipedia` from tiles
1. With TalkBack, navigate to the open tab in the tabstrip and observe the TB announcement
### Expected behavior
1. The selected or current state of the tab is announced by TB, i.e. for Wikipedia: `Wikipedia, selected, tab, Double-tap to activate` (it may include additional list announcements like `In list` that are not in the scope of this bug, a role `tab` is covered in the bug 1902760)
### Actual behavior
1. No state is announced for the current tab, the user would not know which tab is, in fact, opened at the moment. This would be especially severe for multiple opened tab and/or for users with cognitive disabilities.
### Device information
* Firefox version: Nightly 129.0a1 (build #2016026447)
* Android device model: Samsung Galaxy Tab S7+
* Android OS version: 13
### Any additional information?
Another major browser on the same device does announce the state as `Selected tab` (which, testing shows, is a part of the accessible name/`contentDescription` of the control).
|
|
1,902,801 | 16,982,893 |
Crash report: https://crash-stats.mozilla.org/report/index/7f8fae61-15b1-4dfa-9252-8ade80240610
MOZ_CRASH Reason: ```assertion `left != right` failed
left: 0
right: 0```
Top 10 frames of crashing thread:
```
0 XUL MOZ_Crash mfbt/Assertions.h:317
0 XUL RustMozCrash mozglue/static/rust/wrappers.cpp:18
1 XUL mozglue_static::panic_hook mozglue/static/rust/lib.rs:98
2 XUL core::ops::function::Fn::call library/core/src/ops/function.rs:79
3 XUL <alloc::boxed::Box<F, A> as core::ops::function::Fn<Args>>::call library/alloc/src/boxed.rs:2034
3 XUL std::panicking::rust_panic_with_hook library/std/src/panicking.rs:783
4 XUL std::panicking::begin_panic_handler::{{closure}} library/std/src/panicking.rs:657
5 XUL std::sys_common::backtrace::__rust_end_short_backtrace library/std/src/sys_common/backtrace.rs:171
6 XUL rust_begin_unwind library/std/src/panicking.rs:645
7 XUL core::panicking::panic_fmt library/core/src/panicking.rs:72
```
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- **First crash report:** 2024-06-10
- **Process type:** Parent
- **Is startup crash:** No
- **Has user comments:** No
- **Is null crash:** Yes - all crashes happened on null or near null memory address
By analyzing the backtrace, the regression may have been introduced by a patch [1] to fix Bug 1890186.
[1] https://hg.mozilla.org/mozilla-central/rev?node=ad954710c53f
:pehrsons, since you are the author of the potential regressor, could you please take a look?
|
|
1,902,989 | 16,985,833 |
This macOS crash signature saw an increase in volume compared to a low base.
Crash report: https://crash-stats.mozilla.org/report/index/3aa02c0e-d301-473d-8680-507820240617
MOZ_CRASH Reason: ```assertion failed: input_nbytes > 0```
Top 10 frames:
```
0 XUL MOZ_Crash(char const*, int, char const*) mfbt/Assertions.h:317
0 XUL RustMozCrash mozglue/static/rust/wrappers.cpp:18
1 XUL mozglue_static::panic_hook mozglue/static/rust/lib.rs:98
2 XUL core::ops::function::Fn::call library/core/src/ops/function.rs:79
3 XUL <alloc::boxed::Box<F, A> as core::ops::function::Fn<Args>>::call library/alloc/src/boxed.rs:2034
3 XUL std::panicking::rust_panic_with_hook library/std/src/panicking.rs:783
4 XUL std::panicking::begin_panic_handler::{{closure}} library/std/src/panicking.rs:649
5 XUL std::sys_common::backtrace::__rust_end_short_backtrace library/std/src/sys_common/backtrace.rs:171
6 XUL rust_begin_unwind library/std/src/panicking.rs:645
7 XUL core::panicking::panic_fmt library/core/src/panicking.rs:72
```
|
|
1,903,027 | 16,986,173 |
When not using VPIO we set up an aggregate device containing both the input and the output device. We have a bug in reading the input channel count out of the HAL unit on top of the aggregate device, because it behaves differently than the VPIO unit. If the output channel count is higher than the input channel count, we mix them up and get stuck in a reinit-loop because we try to over-render in the input callback.
I hit this when using Apple Studio Display for both input and output because that configuration is blocklisted for VPIO, and has 1 input channel and 2 output channels.
[Tracking Requested - why for this release]: Audio input cannot be captured for some devices and constraints combinations on macOS.
|
|
1,903,827 | 16,991,699 |
### Steps to reproduce
1. Ensure a TalkBack is running
1. Open Firefox and confirm the a tab is opened
1. If this is a New Tab:
1. dismiss the keyboard (until the bug 1902757 is resolved) and, if opened, any OMC onboarding notifications or type in any URL
1. open any tab, i.e. wikipedia from tiles
1. Open another tab (repeating step 3)
1. With TalkBack, navigate to the first open tab in the tabstrip
1. Using a navigational gesture of TalkBack (swiping left-to-right with one finger, in LTR/English, for instance), navigate to the `Close tab` button within this tab and observe the TB announcement
1. Repeat steps 5-6 for the second tab and compare the TalkBack announcements for two `Close tab` buttons.
### Expected behavior
1. A context is provided and it is clear, which tab would be closed, when activated.
1. Navigation with TB shortcuts between buttons makes it clear, which tab's Close button is focused
### Actual behavior
1. Both buttons are announced the same - `Close tab` - and it is not clear, which tab would be, in fact, closed if one of them is activated.
1. While navigating with TB shortcuts between buttons, is not clear, which tab's Close button is focused.
### Device information
* Firefox version: Nightly 129.0a1 (build #2016026447)
* Android device model: Samsung Galaxy Tab S7+
* Android OS version: 13
### Any additional information?
1. The severity of this issue could've been access-S4 if Close buttons would've been hidden when multiple tabs are opened. In that case, i.e. as another major browser does, when only one tab has an on-screen Close button, there are less other options when guessing which tab would be, in fact, closed when this control is activated. But in the situation when there are multiple `Close tab` buttons present in the reading order, it is hard to navigate to the needed one and make a precise choice. Especially, with the selected/current state information being missed (addressed in bug 1902761)
1. Another major browser on the same device does announce the title of the tab, i.e. `Close Wikipedia tab`, but another remediation option could be grouping a tab view which currently includes both the tab and its Close button.
|
|
1,904,168 | 16,994,169 |
Created attachment 9409054
dns_over_https.jpg
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:127.0) Gecko/20100101 Firefox/127.0
Steps to reproduce:
Set "DNS over HTTPS" to "Max Protection", using Cloudflare as a provider, then hard-refresh any video on youtube.
Sometimes it works with default or increased protection, but max protection is the only way it's 100% consistent
Actual results:
There's a consistent 10+ second delay compared to not using DNS over HTTPS. Sometimes it's 30 seconds, sometimes it's more.
In addition to that, the video will keep sometimes freeze at the 20 second mark for a while.
In the network monitor, I see a lot of "NS_Binding_Aborted" for "videoplayback?[...]" which are otherwise absent when DNS over HTTPS is disabled. (See attached screenshot)
Expected results:
The video loads nearly instantly and doesn't pause at the 20 second mark when DNS over HTTPS is completely disabled. This should be the normal behavior
|
|
1,892,487 | 16,899,557 |
Not totally sure why this doesn't just work. They are inputs, so should have default tabbing behaviour. However, it does not work.
[Tracking Requested - why for this release]: UX and possible a11y issue
|
|
1,892,612 | 16,900,331 |
Created attachment 9397751
screenshot of the opened tab
In the last 6 days, there have been reports from 13 different users in the German-speaking Firefox support forum, all reporting the same problem. Rarely has there been a problem with Firefox that has brought so many new users to our support forum, so the number of affected users may be much higher. However, it is unclear whether there is a cause in Firefox at all or whether Mozilla's solution may ultimately be a support article or something similar.
The reported issue is that Firefox always opens a tab with the address https://0.0.0.1 by itself. This can happen when following links, but also when opening new windows. All users report the first occurrence since Firefox 125.0.1, although it cannot be ruled out that this is only a coincidental temporal connection to the release of Firefox 125. So far, only one user has been able to run mozregression and all builds have been fine.
One user reports that the problem does not occur on all websites. He was not able to reproduce on DeepL or ChatGPT, but on google.de, gmail.com and wikipedia.org.
One user has observed that whenever this happens, an unknown icon appears in the Windows taskbar at the same time, which disappears immediately.
An ADWcleaner scan from some users did show Malware and removing it solved it for some users.
What all users have in common is that they use Windows.
The following questions remain:
- Why is the problem suddenly occurring for so many users
- Why is only Firefox affected?
Let me know if there is specific information you would like me to request.
|
|
1,892,732 | 16,902,997 |
Created attachment 9397860
Learn more about Firefox Suggest not working.mp4
**[Affected versions]:**
- Firefox Release 125.0.2
- Firefox Release 125.0.1
**[Affected Platforms]:**
- Windows 10
- macOS 13.1
- Ubuntu 22.4
[Prerequisites]:
- Be enrolled in the Yelp experiment.
- Have the browser.search.region set to "US".
**[Steps to reproduce]:**
1. Open the Firefox browser using the profile from prerequisites.
2. In the urlbar type a keyword that triggers a Yelp suggestion (eg: restaurant).
3. Click the "Feedback" button of the Yelp result.
4. Click the "Learn more about Firefox Suggest" option.
5. Observe the behavior.
**[Expected result]:**
- The Firefox Suggest SUMO page is opened in a new tab.
**[Actual result]:**
- Nothing happens.
**[Regression]**
- The issue is NOT reproducible on Firefox 124 release, considering this using mozregression tools we have found the following pushlog: [Link](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=4199577c0d6419bfad168375b8eb9f8b89df095a&tochange=77104ab988852b524803ce06c1b3d1cc3eabe952).
- Based on the Pushlog link, it seems that Bug 1883378 introduced this behavior.
**[ Notes]:**
- Due to the changes made starting with Firefox 126, the issue is not reproducible because the "Learn more about Firefox Suggest" option was changed to "Manage Firefox Suggest".
- This issue is also reproducible for MDN suggestions.
- The issue is NOT reproducible for Pocket, Weather, Navigational, Dynamic Wikipedia
- Attached is a screen recording of the issue.
|
|
1,893,106 | 16,905,599 |
See bug 1866595 comment 24 which can happen with a built-in mic because of the vpio force-list introduced in bug 1880244.
|
|
1,894,061 | 16,913,948 |
I've recently started seeing `Extra properties should have string values.` in my browser console after startup (on local nightly builds - possibly also distributed nightly builds but I can't recall off-hand).
That's coming from https://searchfox.org/mozilla-central/rev/2e7374599f4020d0490ec8c5e877c179c9e153c9/toolkit/components/telemetry/core/TelemetryEvent.cpp#848 so it's a telemetry event where some of the `extra` bits are invalid.
Standard8 did some digging on matrix:
> Gijs: I see it as well. I quickly added debug and the first three params to `RecordEvent` are `session_restore` `backup_can_be_loaded` `session_file`
> Gijs: https://searchfox.org/mozilla-central/rev/2e7374599f4020d0490ec8c5e877c179c9e153c9/browser/components/sessionstore/SessionFile.sys.mjs#358 maybe? That's a boolean, not a boolean string...
> Its definitely the `can_load` key
> Oh, that's subtle
Kelly, would you mind taking a look?
|
|
1,894,614 | 16,917,448 |
In Firefox 125 we enabled a new feature on release (bug 1882478) to present a suggestion on the address bar if the user has a url on their clipboard.
We have had a [couple of reports on Reddit](https://www.reddit.com/r/firefox/comments/1cgxysc/ever_since_update_the_second_i_press_the_search/) of users seeing long hangs when clicking on the address bar.
One user has been able to [capture a profile](https://share.firefox.dev/4dmjmZV), which shows a 75 second hang with this stack:
```
ZwUserGetClipboardData [win32u.dll]
GetClipboardData [user32.dll]
CClipDataObject::OleGetClipboardData(unsigned int, void**) [com\ole32\ole232\clipbrd\clipdata.cpp]
CClipDataObject::GetData(tagFORMATETC*, tagSTGMEDIUM*) [com\ole32\ole232\clipbrd\clipdata.cpp]
RepeatedlyTryGetData::<lambda_19>::operator()() const [widget/windows/nsClipboard.cpp]
RepeatedlyTry(RepeatedlyTryGetData::<lambda_19>, std::_Binder<std::_Unforced,void (&)(long, const nsTString<char> &),const std::_Ph<1> &,nsTLiteralString<char> >) [widget/windows/nsClipboard.cpp]
RepeatedlyTryGetData(IDataObject&, tagFORMATETC*, tagSTGMEDIUM*) [widget/windows/nsClipboard.cpp]
nsClipboard::FillSTGMedium(IDataObject*, unsigned int, tagFORMATETC*, tagSTGMEDIUM*, unsigned long) [widget/windows/nsClipboard.cpp]
nsClipboard::GetNativeDataOffClipboard(IDataObject*, unsigned int, unsigned int, char const*, void**, unsigned int*) [widget/windows/nsClipboard.cpp]
nsClipboard::GetDataFromDataObject(IDataObject*, unsigned int, nsIWidget*, nsITransferable*) [widget/windows/nsClipboard.cpp]
nsClipboard::GetNativeClipboardData(nsITransferable*, int) [widget/windows/nsClipboard.cpp]
nsBaseClipboard::GetData(nsITransferable*, int, mozilla::dom::WindowContext*) [widget/nsBaseClipboard.cpp]
...
readFromClipboard [chrome://browser/content/browser.js:3091:27]
isActive [resource:///modules/UrlbarProviderClipboard.sys.mjs:49:11]
js::RunScript
tryMethod [resource:///modules/UrlbarUtils.sys.mjs:2365:12]
start [resource:///modules/UrlbarProvidersManager.sys.mjs:405:14]
startQuery [resource:///modules/UrlbarProvidersManager.sys.mjs:215:19]
```
|
|
1,894,849 | 16,918,933 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0
Steps to reproduce:
This bug is reproduceable in a new Firefox profile, though I do not know when it started. According to [this article though](https://blog.mozilla.org/attack-and-defense/2021/10/14/implementing-form-filling-and-accessibility-in-the-firefox-pdf-viewer/), Firefox's PDF viewers is supposed to render the tags in a PDF to screen readers.
1. With NVDA (Windows screen reader), open a tagged PDF in Firefox, e.g.:
https://www.ssa.gov/pubs/EN-05-10023.pdf
2. Press D to move to the first page, where the first piece of text should be "Social Security Numbers for Children".
Actual results:
This heading is broken into two elements, i.e.:
Social SecurityNumbers for
Children
Expected results:
NVDA should have announced that this was a level-one heading.
|
|
1,894,933 | 16,919,561 |
**STR:**
1. Open Nightly with a fresh profile
2. Go to about:preferences#privacy
3. Check "Delete cookies and site data when Firefox is closed"
**Expected:**
In the "History" section on the same `about:preferences` page the dropdown is switched to "Use custom settings for history". The "Clear history when Nightly closes" checkbox is checked.
The settings modal to the right of the checkbox shows "Cookies and site data", Temporary cached files and pages" selected. The items "history" and "site settings" are *not* checked.
History is not cleared on shutdown.
**Actual:**
The settings modal to the right of the checkbox shows "Cookies and site data", Temporary cached files and pages" selected. The item "history" is *also checked*.
History is cleared on shutdown.
[Tracking Requested - why for this release]:
Data loss bug, users that only want to clear site data will have their entire history cleared on shutdown too.
|
|
1,895,110 | 16,920,522 |
Crash report: https://crash-stats.mozilla.org/report/index/9a060de6-0aad-43e1-a28c-ba2c10240505
MOZ_CRASH Reason: ```Shutdown hanging at step XPCOMShutdownThreads. Something is blocking the main-thread.```
Top 9 frames:
```
0 xul.dll MOZ_Crash(char const*, int, char const*) mfbt/Assertions.h:317
0 xul.dll mozilla::(anonymous namespace)::RunWatchdog(void*) toolkit/components/terminator/nsTerminator.cpp:244
1 nss3.dll _PR_NativeRunThread(void*) nsprpub/pr/src/threads/combined/pruthr.c:399
2 nss3.dll pr_root(void*) nsprpub/pr/src/md/windows/w95thred.c:139
3 ucrtbase.dll thread_start<unsigned int (__cdecl*)(void*), 1>
4 kernel32.dll BaseThreadInitThunk
5 mozglue.dll mozilla::interceptor::FuncHook<mozilla::interceptor::WindowsDllInterceptor<mo... toolkit/xre/dllservices/mozglue/nsWindowsDllInterceptor.h:150
5 mozglue.dll patched_BaseThreadInitThunk(int, void*, void*) toolkit/xre/dllservices/mozglue/WindowsDllBlocklist.cpp:562
6 ntdll.dll RtlUserThreadStart
```
|
|
1,895,599 | 16,925,577 |
I had intended to explicitly test this behavior prior to merge, but in the many revisions and changes it slipped by. I have found that the `zip` crate is unable to read our omnijar files due to [the optimized layout](https://taras.glek.net/post/optimized-zip-format/).
This is a significant defect that should be fixed before the crash reporter gets to release.
|
|
1,905,505 | 17,005,121 |
The event page lifecycle is managed by a timer ([IdleManager](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/parent/ext-backgroundPage.js#988)) that terminates an event page as soon as there is no detected activity.
The timer starts when the event page wakes up ([resetTimer()](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/parent/ext-backgroundPage.js#801-803)), and is guaranteed to stop when the background stops for any reason (regular termination, process crash, extension unload) (by [calling `clearState()`](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/parent/ext-backgroundPage.js#500-501)).
Whenever any activity occurs, signaled through the internal "background-script-reset-idle" event, [resetTimer() is called](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/parent/ext-backgroundPage.js#774) again, which extends the lifetime by rescheduling the timer. This design assumes that `background-script-reset-idle` is only called when the background script exists. If the background is already stopped, calling `resetTimer()` will just schedule a [timer that eventually calls `terminateBackground()`](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/parent/ext-backgroundPage.js#1058).
The first step of `terminateBackground()` [is to `await bgStartupPromise`](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/parent/ext-backgroundPage.js#813,817), which means that if anything causes `terminateBackground()` to be called while the background is inactive, that it will immediately terminate the background script at the next startup of the event page.
I audited all entries that trigger "background-script-reset-idle":
- [ParentAPIManager.recvAPICall](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/ExtensionParent.sys.mjs#1208-1211) resets the timer before processing an API call. Before it gets there, it looks up the context via [`getContextById`](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/ExtensionParent.sys.mjs#1181), which throws if the context has already been unloaded. Experimentally I confirmed that unloading the background event browser [via `setBgStateStopped`](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/parent/ext-backgroundPage.js#508) triggers a synchronous `message-manager-close` notification that [erases the context](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/ExtensionParent.sys.mjs#997,1001). If we ever decide to drop the use of this notification in favor of [recvProxyClosed](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/ExtensionParent.sys.mjs#1131-1135) (which is tracked in bug 1595186), then we have to carefully examine that doing so will not cause bugs like this.
- [Various resets within `terminateBackground()`](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/parent/ext-backgroundPage.js#845,853,894) that ignore the termination request if there is another pending thing. This will never be called while the background page is stopped because there is an [earlier return if the background is not running](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/parent/ext-backgroundPage.js#822-824).
- [EventManager's resetIdle](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/ExtensionCommon.sys.mjs#2790,2792) may reset idle before dispatching an event. At the surface it seems to work all right: before calling `resetIdle()` there is always a `shouldFire()` call, which prevents the logic from running if the context has unloaded.
- HOWEVER, this logic can also run in the content process, AND [ExtensionChild's `emit` method forwards the message to the parent via the process message manager](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/ExtensionChild.sys.mjs#528). When the message is received in the parent, the event [is forwarded without further checks](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/Extension.sys.mjs#3096-3097), potentially after a context has unloaded.
- Moreover, the idle reset event is dispatched for EventManagers from any extension context, even non-background pages (a seen in the [resetIdleOnEvent definition in EventManager constructor](https://searchfox.org/mozilla-central/rev/cac3778e4407b9b6831326465d84e4f60648b912/toolkit/components/extensions/ExtensionCommon.sys.mjs#2327-2333)). This means that the bug can trivially be triggered, simply by triggering an event in a non-background extension context when the background is suspended.
- This "keep event page alive when an extension event is triggered in any extension document" logic seems bizarre, and I filed bug 1905504 to fix this.
This is not a theoretical problem, it has repeatedly been observed in the wild, e.g. at https://discourse.mozilla.org/t/one-of-my-manifest-v3-addons-is-not-waking-up-when-it-should/131349/36
|
|
1,905,771 | 17,008,771 |
Created attachment 9410702
Button with on-screen text AI Chatbot has accessible name Tree Style Tab in the Accessibility tree
### Found in:
* Nightly 129.0a1 (2024-07-01)
### STR:
1. Have a Fx sidebar opened, i.e. with `ctrl/cmd+B` open a Bookmarks sidebar. Or have `Tree Style Tabs` extension installed
1. Reach `about:preferences#experimental`
1. Enable the `AI Chatbot integration`
1. Select the ChatGPT AI provider (or any other)
1. Confirm the sidebar view is updated to the `AI Chatbot`
1. Using a screen reader, navigate to and observe the announcement of the `AI Chatbot` control at the top of the sidebar.
1. Alternatively, open a browser developer tools > Accessibility > and select the sidebar's title button via the `Pick accessible object from the page`
### Expected:
1. The on-screen name of the sidebar is serving as an accessible name of the button and is announced as `AI Chatbot` (which would be the `name` field value in the A11y dev tools)
### Actual:
1. The on-screen name of the sidebar is updated to `AI Chatbot` but the accessible name of the button remains as the previous sidebar view, i.e. `Tree Style Tabs` (which is also the `name` field value in the A11y dev tools)
### Note:
I have not noticed this behavior with the sidebar before, thus filing the bug in the GenAI sidebar's component. That's being said, if someone could confirm the behavior on their machines to confirm or close this bug, I'll appreciate it. Filing from macOS but both the Accessibility tree in Dev Tools and the MacOS Accessibility Inspector are confirming the name of the accessible is as described in "Actual" section above, thus other platforms should be affected too.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.