Bug ID
int64 961
1.91M
| Comment ID
int64 3.98k
17.1M
| Author
stringlengths 8
48
| Comment Text
stringlengths 1
64.3k
⌀ |
|---|---|---|---|
1,907,373 | 17,020,874 |
User Agent: Mozilla/5.0 (Android 13; Mobile; rv:130.0) Gecko/130.0 Firefox/130.0
Steps to reproduce:
Download and install Firefox nightly on Android
Actual results:
URL bar only displays TLD and not path or query string
Expected results:
display full URL including path and query string
|
|
1,907,436 | 17,021,222 |
(Filed as a copy of https://mozilla-hub.atlassian.net/browse/EXP-4689)
*[Affected versions]:*
Firefox build version: Firefox Beta 129.0b1, Build ID: 20240708194140
*[Affected Platforms]:*
Windows 10 x64;
macOS 14.3/14.5
Linux Mint 21.2
*[Prerequisites]:*
Have access to the Nimbus console.
Have a launched desktop experiment created with a user pref not registered in the “about:config” page using the prefFlips feature configuration.
Set up the latest Firefox Beta to point to the Stage server and set the “messaging-system.log” pref to “all” value.
*[Steps to reproduce]:*
Enroll in the newly created experiment.
Have a colleague with access to Nimbus click the “End experiment” button from the Experimenter page.
Approve the changes on the Experimenter page.
Approve the changes in the Remote Settings Writer and wait for the experiment to be completed.
Restart the browser.
Go to the “about:config” page and search for the pref that was set by the experiment.
*[Expected result]:*
The pref set by the experiment cannot be found after the experiment was disabled since it wasn’t previously registered in the “about:config”.
*[Actual result]:*
The pref set by the experiment is displayed in the “about:config” page having the same value.
*[Notes]:*
This issue is reproducible only with experiments having preferences that are not registered in the “about:config” page already.
This issue is also reproducible if the Stage collection is changed to another collection (e.g.: Prod collection).
|
|
1,907,484 | 17,021,585 |
Created attachment 9412409
screenshot of bug
### Steps to reproduce
1. Open a Private Browsing tab and visit some site, e.g. https://example.org/
2. Long-press the URL bar, to trigger a context-menu to open.
### Expected behavior
Context menu should be easy to distinguish over the UI that it overlaps.
### Actual behavior
Context menu is the same color purple as the UI that it overlaps (the newly-introduced nav bar)
### Device information
* Firefox version: 130.0a1 2024-07-11
* Android device model: Pixel 8
* Android OS version: 14
|
|
1,907,546 | 17,021,906 |
Created attachment 9412450
Screenshot_2024-07-12-14-28-55-11_984e1414ae90666a90f12ff17ec14a7f.jpg
### Prerequisites
Make sure to enable from Secret Settings the "Enable Navigation Toolbar" feature.
### Steps to reproduce
1. Open a website for which you can create an account on (I've encountered this issue on cnn.com).
2. Go to the sign up section, and create an account using the "Use strong password" feature.
3. After the completion of your new account observe the page.
### Expected behavior
The user is signed in, and the page is displayed.
### Actual behavior
The "Use strong password" feature is still displayed under the nav bar.
Not reproducible when the "Enable Navigation Toolbar" feature is OFF/disabled.
### Device information
* Firefox version: Nightly 130.0a1 from 7/12
* Android device: Oppo Find X3 Lite (Android 11), Samsung Galaxy S24 (Android 14)
## Additional information
* not reproducible on bbc.com, theverge.com, wikipedia.org, bookzone.ro
|
|
1,907,649 | 17,022,640 |
If the pref flips feature receives a configuration that would set a pref to a value of a different type, it will throw, which will cause issues with enrollment.
|
|
1,907,709 | 17,023,149 |
For some reason searching for "Advertising" doesn't find that section. On the other hand searching for "collection" finds the section "Nightly Data Collection and Use". I think this has something to do with the `search-header` class.
|
|
1,907,958 | 17,026,357 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0
Steps to reproduce:
Open PDF
highlight text
print
text printed is not highlighted
Actual results:
The text was not highlighted when using firefox, but other programs and other machines printed highlighted text.
Expected results:
Text should be highlighted with the appropriate color, when edited in PDF and printed.
|
|
1,907,968 | 17,026,420 |
The DisableFirefoxStudies enterprise policy disables the "Shield" feature, but Nimbus doesn't look for this at all. it only checks the `datareporting.healthreport.uploadEnabled` and `app.shield.optoutstudies.enabled` prefs.
|
|
1,908,473 | 17,029,691 |
Originally encountered trying to use https://open.spotify.com/ , which produces an error saying "Playback of protected content is not enabled."
A simpler testcase (no login) is:
0. ensure DRM is enabled and you have a downloaded CDM for Widevine
1. open private browsing window
2. open https://shaka-player-demo.appspot.com/demo/
ER:
Sintel widevine demo is playable
AR:
Sintel widevine demo is greyed out and can't be played
On Spotify, I got an `Uncaught (in promise) EMEError: No supported keysystem was found` error.
I'm told :alwu knows what's up in this area. :-)
|
|
1,902,255 | 16,979,921 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:127.0) Gecko/20100101 Firefox/127.0
Steps to reproduce:
When I sort my INBOX by date and also enable "Grouped by sort" ...
Actual results:
... TB versions before the UI redesign showed the number of messages in the time period "(#unread/#total)" in the separator line. Unfortunately, this has been removed in the new UI and I'm still missing it.
Expected results:
Please bring back this feature.
|
|
1,902,428 | 16,980,773 |
User Agent: Mozilla/5.0 (Android 14; Mobile; rv:127.0) Gecko/127.0 Firefox/127.0
Steps to reproduce:
Select "media picker" to upload an image and it does not work. You can try this in any image uploading website. Additionally, it makes the browser tab unresponsive after selecting "media picker". However, selecting gallery works( I have shown this towards the end of the video to not get confused). Please view the video to understand what I mean by media picker.
Actual results:
https://youtube.com/shorts/bo5DuWHr6oc
Please view the video.
Expected results:
Selecting "media picker" should work and not stall the browser tab.
|
|
1,902,639 | 16,981,730 |
Created attachment 9407501
tab_hover_0.gif
**Found in**
* 128.0b2
**Affected versions**
* 129.0a1 (2025-06-13)
* 128.0b2
**Tested platforms**
* Affected platforms: Windows 10x64, Ubuntu
* Unaffected platforms: macOS 13
**Preconditions**
* browser.tabs.hoverPreview.enabled: true
**Steps to reproduce**
1. Disable Show an image preview when you hover on a tab from Preferences.
2. Open some random tabs.
3. Hover over a tab and move the mouse to the next tab.
**Expected result**
* Tab preview is displayed for the correct tab.
**Actual result**
* Tab preview is displayed for the previous tab.
**Regression range**
* Before bug 1892394 the tab preview was displayed on the previous tab even if the mouse was on another tab which was caused by bug 1890397. After bug 1892394 is fixed the tab preview is displayed in the correct position on the currently hovered tab but the tab preview is for the previous tab.
**Additional notes**
* Attached is a screen recording.
* To reproduce the issue the tab hover needs to be changed right when the tab preview should appear.
* This only happens when `Show an image preview when you hover on a tab` is disabled.
|
|
1,902,759 | 16,982,591 |
### 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 (via the New Tab > either enter URL or activate a tile, i.e. a Pocket)
1. Observe the TB announcement when the new tab is opened
### Expected behavior
1. A title of the newly opened tab would be announced, i.e. for the Pocket tile a Pocket tab would be announced, and the TalkBack would proceed with announcing the web content (the TB focus is to be either placed on the newly opened web content or on the first focusable element of this new web content)
### Actual behavior
1. The TalkBack focus is shifted to the first tab on the tabstrip and this first tab's title is announced, while visually the newly opened web content is loading on the web content area.
1. If there are multiple tabs opened and the tabstrip is overflowing, the first even partially visible tab is being focused with TalkBack, not the first one in the tablist.
1. This feels like a high severity access-S3, bordering access-S2, because:
1. the user would have to guess, if the new tab was, in fact, opened.
1. And then they'll need to tediously navigate to the content passing all the other controls.
1. They may not even know that the content is showing from the tab that they just opened, because another tab would be announced, so it's likely that a TB user may try to re-activate the tab that is opened but they just not aware of that.
1. Plus, for users with cognitive difficulties relying on TB to understand the content, this change would be confusing.
### 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 moves the TB focus on the content wrapper and starts reading the page.
|
|
1,903,341 | 16,988,581 |
Created attachment 9408219
poc.js
Steps to reproduce:
### Environment
commit : ae0ed821959cc6b5b255b0774becd34c317e53f8
configure :
```
ac_add_options --enable-project=js
ac_add_options --enable-debug
ac_add_options --enable-optimize
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-debug-orig-@CONFIG_GUESS@
```
build command :
```
./mach build
```
### Proof of concept
./js --setpref=wasm_js_string_builtins=true ./poc.js
```
[995145] Assertion failure: isJSObject(), at /gecko-dev/js/src/wasm/WasmAnyRef.h:304
#01: ???[/gecko-dev/obj-debug-orig-x86_64-pc-linux-gnu/dist/bin/js +0x2758f48]
#02: ???[/gecko-dev/obj-debug-orig-x86_64-pc-linux-gnu/dist/bin/js +0x30ea6fb]
#03: ???[/gecko-dev/obj-debug-orig-x86_64-pc-linux-gnu/dist/bin/js +0x30ea4f6]
#04: ??? (???:???)
Segmentation fault
```
Actual results:
### Stack dump
```
[----------------------------------registers-----------------------------------]
RAX: 0x5555559918c9 ("MOZ_ASSERT(isJSObject())")
RBX: 0x7ffff6235100 --> 0x0
RCX: 0x555558c569a0 --> 0x5555559918c9 ("MOZ_ASSERT(isJSObject())")
RDX: 0x1
RSI: 0x0
RDI: 0x7ffff7c107d0 --> 0x0
RBP: 0x7fffffffc970 --> 0x7fffffffc990 --> 0x7fffffffca10 --> 0x7fffffffca20 --> 0x7fffffffca40 --> 0x7f
ffffffca70 (--> ...)
RSP: 0x7fffffffc970 --> 0x7fffffffc990 --> 0x7fffffffca10 --> 0x7fffffffca20 --> 0x7fffffffca40 --> 0x7f
ffffffca70 (--> ...)
RIP: 0x555557cacf59 (<_ZNK2js4wasm6AnyRef10toJSObjectEv+137>: mov DWORD PTR ds:0x0,0x130)
R8 : 0x0
R9 : 0x3
R10: 0x0
R11: 0x0
R12: 0x7fffffffc9d8 --> 0x0
R13: 0x7fffffffd008 --> 0x7ffff507d0a8 --> 0xfffe12d8e6e03d30
R14: 0x4a ('J')
R15: 0x15b793
EFLAGS: 0x10202 (carry parity adjust zero sign trap INTERRUPT direction overflow)
[-------------------------------------code-------------------------------------]
0x555557cacf48 <_ZNK2js4wasm6AnyRef10toJSObjectEv+120>: lea rax,[rip+0xfffffffffdce497a]
# 0x5555559918c9
0x555557cacf4f <_ZNK2js4wasm6AnyRef10toJSObjectEv+127>: lea rcx,[rip+0xfa9a4a] # 0x555
558c569a0 <gMozCrashReason>
0x555557cacf56 <_ZNK2js4wasm6AnyRef10toJSObjectEv+134>: mov QWORD PTR [rcx],rax
=> 0x555557cacf59 <_ZNK2js4wasm6AnyRef10toJSObjectEv+137>: mov DWORD PTR ds:0x0,0x130
0x555557cacf64 <_ZNK2js4wasm6AnyRef10toJSObjectEv+148>: call 0x5555571bf6b0 <abort()>
0x555557cacf69 <_ZNK2js4wasm6AnyRef10toJSObjectEv+153>: lea rdi,[rip+0xfffffffffdce491b]
# 0x55555599188b
0x555557cacf70 <_ZNK2js4wasm6AnyRef10toJSObjectEv+160>: lea rsi,[rip+0xfffffffffdce48ab]
# 0x555555991822
0x555557cacf77 <_ZNK2js4wasm6AnyRef10toJSObjectEv+167>: mov edx,0x120
[------------------------------------stack-------------------------------------]
0000| 0x7fffffffc970 --> 0x7fffffffc990 --> 0x7fffffffca10 --> 0x7fffffffca20 --> 0x7fffffffca40 --> 0x7
fffffffca70 (--> ...)
0008| 0x7fffffffc978 --> 0x55555863e6fb (<_ZL23UncheckedCastToArrayI16ILb1EEPN2js15WasmArrayObjectEN2JS6
HandleINS0_4wasm6AnyRefEEE+11>: mov rbx,rax)
0016| 0x7fffffffc980 --> 0x7fffffffcc10 --> 0x7ffff6235170 --> 0x7fffffffc9c8 (0x00007ffff6235170)
0024| 0x7fffffffc988 --> 0x7ffff6235100 --> 0x0
0032| 0x7fffffffc990 --> 0x7fffffffca10 --> 0x7fffffffca20 --> 0x7fffffffca40 --> 0x7fffffffca70 --> 0x7
fffffffcad0 (--> ...)
0040| 0x7fffffffc998 --> 0x55555863e4f6 (<_ZN2js4wasm8Instance23stringFromCharCodeArrayEPS1_Pvjj+118>: m
ov r12,rax)
0048| 0x7fffffffc9a0 --> 0xaaaaaaaaaaaaaaaa
0056| 0x7fffffffc9a8 --> 0xaaaaaaaaaaaaaaaa
[------------------------------------------------------------------------------]
Legend: code, data, rodata, value
Stopped reason: SIGSEGV
js::wasm::AnyRef::toJSObject (this=<optimized out>) at /gecko-dev/js/src/
wasm/WasmAnyRef.h:304
gdb-peda$ bt
#0 js::wasm::AnyRef::toJSObject() const (this=<optimized out>)
at /gecko-dev/js/src/wasm/WasmAnyRef.h:304
#1 0x000055555863e6fb in js::WrappedPtrOperations<js::wasm::AnyRef, JS::Handle<js::wasm::AnyRef>, void>::toJSObject() const (this=<optimized out>)
at /gecko-dev/js/src/wasm/WasmAnyRef.h:364
#2 UncheckedCastToArrayI16<true>(JS::Handle<js::wasm::AnyRef>) (ref={
value_ = 0x0,
static TagMask = 0x3,
static TagShift = 0x2,
static GCThingMask = 0xfffffffffffffffc,
static GCThingChunkMask = 0xfffffffffff00000,
static NullRefValue = 0x0,
static InvalidRefValue = 0xfffffffffffffffc,
static MaxI31Value = 0x3fffffff,
static MinI31Value = 0xc0000000
}, ref@entry={
value_ = 0x0,
static TagMask = 0x3,
static TagShift = 0x2,
static GCThingMask = 0xfffffffffffffffc,
static GCThingChunkMask = 0xfffffffffff00000,
static NullRefValue = 0x0,
static InvalidRefValue = 0xfffffffffffffffc,
static MaxI31Value = 0x3fffffff,
static MinI31Value = 0xc0000000
}) at /gecko-dev/js/src/wasm/WasmInstance.cpp:1969
#3 0x000055555863e4f6 in js::wasm::Instance::stringFromCharCodeArray(js::wasm::Instance*, void*, unsigned int, unsigned int)
(instance=<optimized out>, arrayArg=<optimized out>, arrayStart=0x15b793, arrayCount=0x4a)
at /gecko-dev/js/src/wasm/WasmInstance.cpp:2002
#4 0x000032da8a7cdfb3 in ()
#5 0x00007fffffffca40 in ()
#6 0x000032da8a7dc105 in ()
#7 0x00007ffff502a800 in ()
#8 0x00007ffff502a800 in ()
#9 0x00007fffffffca70 in ()
#10 0x000032da8a7bd382 in ()
#11 0x00007ffff502a800 in ()
#12 0x00007ffff625d200 in ()
#13 0x7ff8000000000000 in ()
#14 0x00000b7a7cd04062 in ()
#15 0x00007fffffffcad0 in ()
#16 0x000032da8a7bf03f in ()
#17 0x00007ffff625d200 in ()
#18 0x000055555793aca1 in js::CheckContextLocal::check() const (this=0x15b793)
at /gecko-dev/js/src/threading/ProtectedData.cpp:52
```
|
|
1,903,529 | 16,989,704 |
Created attachment 9408390
Screen Recording 2024-06-19 at 2.04.12 PM.mov
**[Affected versions]:**
- Firefox Release, 126.0, BUILD ID: 20240509170740
- Firefox Release, 127.0, BUILD ID: 20240606181944
**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64
**[Prerequisites]:**
- Have the [“user.js”](https://drive.google.com/drive/folders/1ciGuIn1OcXH30H5ivVXK1ED_BhzUtU6Y) downloaded on your computer.
**[Steps to reproduce]:**
1. Create a new Firefox profile using the “--first-startup” command but do not open it.
2. Navigate to the profile folder and paste the user.js from the prerequisites.
3. Open Firefox and navigate through the about:welcome pages until the “Addon Picker” one is displayed.
4. Click the “Add to Firefox” button from one of the extensions and finish the installation process.
5. Refresh the page after the “Installed” message is displayed and the button is grayed out.
**[Expected results]:**
- The “Installed” message is still displayed and the button is grayed out.
**[Actual results]:**
- The “Add to Firefox” button is displayed and actionable again.
**[Additional Notes]:**
- This issue is also reproducible when the user navigates to the next slide after installation and then back to the “Addon Picker” slide.
- The addon can be installed again when the “Add to Firefox” button is displayed after refreshing the page.
|
|
1,903,584 | 16,990,107 |
The [schema](https://hg.mozilla.org/mozilla-central/file/4c1dffe40676f3987692453b79514c4808833ee7/toolkit/components/nimbus/schemas/PrefFlipsFeature.schema.json) contains the following:
```
"if": {
"properties": {
"branch": {
"const": "default"
}
}
},
"then": {
"properties": {
"value": {
"type": ["string", "integer", "boolean", "description"] # <--
}
}
}
```
where the then.properties.value.type is invalid
|
|
1,903,589 | 16,990,152 |
**Found in**
* Nightly 129.0a1 (2024-06-19)
**Affected versions**
* Nightly 129.0a1 (2024-06-19)
* Beta 128
* Release 127.0 (64-bit)
**Affected platforms**
* All
**Steps to reproduce**
1. Open a PDF file in Firefox.
2. Add an image to the PDF file.
3. Open the Alt Text modal and write a description.
4. Copy and Paste the image inside the PDF file.
5. Hover over the Alt text button from the Pasted image.
**Expected result**
* The Alt Text file should be copied with the added image.
**Actual result**
* The Image is copied and pasted but without the Alt text
**Regression range**
Not a regression.
|
|
1,903,608 | 16,990,234 | null |
|
1,903,615 | 16,990,265 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:127.0) Gecko/20100101 Firefox/127.0
Steps to reproduce:
1. In about:preferences disable both settings "Recommend extensions as you browse" and "Recommend features as you browse".
2. Upgrade Firefox to version 127.0 or higher.
Actual results:
Both mentioned settings have been enabled after the upgrade.
Expected results:
Both settings should preserve their value through upgrades.
Additional details:
So far as I can see on looking through about:preferences all my other settings are untouched so I'm curious why only those 2 specific ones are enabled after each upgrade beginning with Firefox 127.0.
|
|
1,903,731 | 16,991,117 |
Created attachment 9408601
Firefox PDF Viewer Bug.zip
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
Steps to reproduce:
Open an existing PDF document in Firefox
Actual results:
The PDF document is not displayed correctly, the fonts have different widths, therefore some parts of the PDF document are not displayed correctly, see attached screenshot file "Firefox-127-PDF-Screen.png".
Expected results:
The Firefox viewer should display the file correctly and display the font widths correctly.
Other browsers such as chrome, edge display the file correctly, and Firefox should also display it correctly.
Attached is the affected PDF file and the screenshots of the PDF viewers in question (in the browsers).
Further in the attachment you will find an info screenshot of the Firefox version.
|
|
1,903,770 | 16,991,340 |
Created attachment 9408634
added.png
**Found in**
* 129.0a1 (2024-06-20)
**Affected versions**
* 129.0a1 (2024-06-20)
* Beta 128.0b5
**Affected platforms**
* ALL
**Steps to reproduce**
1. Open a PDF file in Firefox.
2. Add an image to the PDF file.
3. Enter Presentation mode.
**Expected result**
* The Image should be displayed in the middle of the file.
**Actual result**
* The added image spills out of the frame in Presentation mode.
**Regression range**
First bad: 2d86fcafc9255267c02bc3e6999c0ec7a1ba80d3
Last good: 56403f0275360530ba100601d5adfd0c8229aa88
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=14c24263d5cacf8afd824e97a256abc1519b5c87&tochange=2d86fcafc9255267c02bc3e6999c0ec7a1ba80d3
|
|
1,903,868 | 16,992,047 |
### 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 a few more tabs (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 from the first tab to the last tab's `Close tab` button and observe the TB announcement and the number of gestures required to pass the tab strip with gestures
1. Turn off the TalkBack and repeat steps 2-5 while using Universal Switch control or a Bluetooth keyboard for navigation between elements.
### Expected behavior
1. Navigation is efficient and requires as little of gestures as possible, for example:
1. only the currently opened tab needs 2 swipes/`Tab`s to move the focus of TalkBack / Universal Switch / BT Keyboard from this tab to another (the 1st gesture for the tab itself and the 2nd one to pass by the `Close` button), but the other tabs have their `Close` buttons hidden. This approach is used by another major browser on the same device.
1. We could possibly remove the `Close` buttons from the accessibility tree (i.e. make them `importantForAccessibility:false`), but we would have to ensure there is an easy way to close the tab with a screen reader/switch/keyboard-alone which is on Fx desktop is provided by the context menu. _But in this case, there is no context menu provided for tabs at the moment_ (without any assistive technology, both tap-and-hold or double-tab-and-hold were tried to confirm it).
### Actual behavior
1. Navigation requires 2 swipes/`tab` key presses to move the focus of TalkBack / Universal Switch / BT Keyboard from one tab to another.
### Device information
* Firefox version: Nightly 129.0a1 (build #2016026447)
* Android device model: Samsung Galaxy Tab S7+
* Android OS version: 13
### Note
This issue is on the lower end of accessibility severity 3, but it becomes especially noticeable when the tabs are overflowing and a user of assistive technology needs to navigate through the list of tabs.
|
|
1,904,648 | 16,999,653 |
Created attachment 9409492
bug.js
Steps to reproduce:
Checkout commit 9fcc11127fbfbdc88cbf37489dac90542e141c77 and invoke the js shell as follows:
```
js --fuzzing-safe <test-case>
```
Actual results:
```
Hit MOZ_CRASH(setFromOverlappingTypedArray with a typed array with bogus type) at js/src/vm/TypedArrayObject-inl.h:759
```
|
|
1,904,649 | 16,999,656 |
Created attachment 9409493
bug.js
Steps to reproduce:
Checkout commit 9fcc11127fbfbdc88cbf37489dac90542e141c77 and invoke the js shell as follows:
```
js --fuzzing-safe <test-case>
Actual results:
```
Assertion failure: false, at js/src/vm/SelfHosting.cpp:436
```
|
|
1,904,921 | 17,001,337 |
Created attachment 9409737
mobizen_20240625_212930.mp4
User Agent: Mozilla/5.0 (Android 11; Mobile; rv:129.0) Gecko/129.0 Firefox/129.0
Steps to reproduce:
When the Inactive tabs setting is enabled and we have inactive tabs in the tab tray and we have open for example more than 50 tabs and we are on the last open tab, every time the tab tray is opened it also opens at the top, where the tabs are inactive, even if we are on the last open tab.
Actual results:
The tab tray opens and shows the first tabs and inactive tabs, we're actually on the last tabs open, with about 50 tabs open.
Expected results:
You should always have the tab tray open at the last open tab, even if there are inactive tabs displayed in the tab tray.
|
|
1,904,937 | 17,001,392 |
This issue is reproducible on my Firefox Release 127 and Nightly 129 on Windows 11.
STR. ([reproduce steps video](https://drive.google.com/file/d/1F7iQ0l9GVEltX8kPreM1eOAMl1KNkYBT/view?usp=sharing))
1. go to https://www.youtube.com/watch?v=fCO7f0SmrDc
2. start video in 4K resolution
3. seek to the place near the end of buffered range many times, until video buffered range reaches to the end
4. seek back to the start position
Expected.
5. video keeps playing and shows the correct current time
Actual.
5. video's current time stuck at 0.00 (or 1.00 depends on where you seek to) and the buffered range won't keep growing. So video enters infinite buffering when reaching the end of buffering.
---
Here is the media [profile](https://share.firefox.dev/3L2mHR8) I captured on the latest Nightly on Windows 11.
|
|
1,905,119 | 17,002,778 |
Created attachment 9409990
CFR CBB.jpg
**[Affected versions]:**
- Firefox Beta 128.0b8 - Build ID: 20240626091446
**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.4
- Linux Ubuntu 20.04 x64
**[Prerequisites]:**
- Have a Firefox RTL build installed (ar, he, fa, etc).
- Have the following pref set:
`nimbus.debug` = `true`
**[Steps to reproduce]:**
1. Open the browser from the prerequisites.
2. Copy and paste the following link in order to force enroll in the “CBB ROW Hold-back with Promo” experiment: `about:studies?optin_slug=cbb-row-hold-back-with-promo&optin_branch=treatment-a&optin_collection=nimbus-preview`
3. Restart the browser.
4. Open a new Private Window.
5. Navigate to a website that contains a cookie banner. (e.g. bloomberg.com, cnn.com)
6. Observe the CFR message.
**[Expected result]:**
- The elements of the CFR message are correctly displayed respecting the RTL rules.
**[Actual result]:**
- The message’s arrow points to the Address Bar instead of being anchored to the "Tracking Protections" button.
- The X button, cookie icon, link, and text from the message's content are displayed in the same way as on the LTR builds.
- The X button overlaps part of the text from the message’s content.
**[Notes]:**
- Attached is a screenshot of the issue on 3 RTL builds (ar, he, fa, etc).
- This issue is probably reproducible with other RTL builds.
|
|
1,892,394 | 16,898,829 |
Created attachment 9397521
tab_hover_0.gif
**Found in**
* 126.0b2
**Affected versions**
* 127.0a1 (2024-04-18)
* 126.0b2
**Tested platforms**
* Affected platforms: Ubuntu 23.10, Windows 10x64
* Unaffected platforms: macOS 14
**Steps to reproduce**
1. Open a few tabs.
2. Hover over a random tab and move the cursor to the next tab before the tab preview is displayed.
**Expected result**
* The tab preview is displayed for the correct tab.
**Actual result**
* The tab preview is displayed on the wrong tab.
**Regression range**
* Mozregression points at bug 1890397.
**Additional notes**
* Attached a screen recording.
|
|
1,892,402 | 16,898,874 |
Created attachment 9397528
Survey panel text has no contrast with the "Dark space" theme
STR:
1. Install [Dark space - The best dynamic theme](https://addons.mozilla.org/en-US/firefox/addon/nicothin-space/) (130k users).
2. Open the new tab page and show the `NEWTAB_CSAT_SURVEY` message ("Help Firefox improve this page").
Survey text has no contrast against white background. It is using the text color from the new tab page but not the background color.
The same occurs with the [Firefox Color](https://addons.mozilla.org/en-US/firefox/addon/firefox-color/) extension and "New Tab Text" set to a light color.
The survey message only appears for me in the current Release 125 and not Beta 126 or Nightly 127.
|
|
1,892,449 | 16,899,282 |
Created attachment 9397577
firefox.126.0.b2.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0
Steps to reproduce:
When trying to access admin settings on my ADSL router on a private IP address, a dialogue box comes up requesting Username and Password (see picture attached). This I input either via copy and paste from a password manager or type it in manually.
Actual results:
The dialogue box disappears and then reappears again requesting authentication, and the page does not go to a secure page. I have tried to input the username and password many times with the same results.
Expected results:
The page should have cleared and the requested security-protected page displayed.
I have had this problem since the auto-upgrade to 126.0b2 (and also 126.0b1.)
Trying to access the page using Firefox 125.0b9 using a test, new and empty profile works as expected.
Linux Kubuntu 23.10, X11, KDE Plasma 5.27.8. QT 5.15.10.
Firefox originally downloaded from Mozilla beta site and has been automatically updates ever since.
|
|
1,892,699 | 16,902,833 |
Steps to reproduce:
When creating a generator that takes several arguments in Firefox version 125.0.1 (64 bit), I encounter a problem: the arguments arrya-like object is always empty, even if arguments are passed to the generator, although in the previous version, for example 124.0.2, it contains the passed arguments.
I run following code in developer console:
function* a(x, y, z) {
console.debug("Arguments length:", arguments.length);
yield x;
yield y;
yield z;
}
const x = a(3, 4, 5)
x.next()
Actual results:
Console output:
Arguments length: 0
Expected results:
Console output:
Arguments length: 3
This is how the code works in version 124.0.2
|
|
1,892,947 | 16,904,612 |
The clear cookies and site data when Firefox shuts down checkbox is not aligned with the new sanitizeOnShutdown prefs https://searchfox.org/mozilla-central/source/browser/components/preferences/privacy.js#2095. We should support the new prefs based on if the user is using the new clear history dialog.
|
|
1,893,460 | 16,907,856 |
Created attachment 9398645
Screenshot with the issue
**Found in**
* Nightly 127.0a1
**Affected versions**
* Nightly 127.0a1
**Tested platforms**
* Affected platforms: Windows 10 x64, Ubuntu 22.04 and macOS 13
**Preconditions**
* install an RTL build - ar in my case.
**Steps to reproduce**
1. Enable Screenshots by pressing the Cmd+Shift+S keys.
2. Do a Screenshot selection by mouse drag.
3. Observe the buttons of the Screenshot selection.
**Expected result**
* The 'Download', 'Copy' and 'X' buttons should be located on the left side of the Screenshot selection.
**Actual result**
* The buttons are located on the right side of the Screenshot selection. Please see the screenshot for more details.
**Regression range**
* Not a regression, it's reproducible only when the component version of Screenshots is enabled.
|
|
1,893,616 | 16,909,029 |
Created attachment 9398822
image_2024_04_26T10_44_05_788Z.png
**[Affected versions]:**
- Firefox Beta 126.0b5 (Build #20240424091756)
**[Affected Platforms]:**
- Windows 11 x64
- macOS 13.6.2
- Ubuntu 22.04 x64
**[Prerequisites]:**
- Have the latest Firefox Beta 125 installed using a non-English locale (DE or FR).
- Have a browser profile enrolled in the Control or Treatment A branches of the [WNP Messaging System + Nimbus Tooling](https://experimenter.services.mozilla.com/nimbus/wnp-messaging-system-nimbus-tooling/summary) experiment.
**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Update the browser to Beta 126.
3. Observe the 126 What's New page.
**[Expected result]:**
- The WNP is localized in the build's language.
**[Actual result]:**
- The WNP is displayed in English regardless of the build language.
**[Notes]:**
- The issue is most likely caused by the Nimbus override URL, since the en-US locale is hardcoded in the link.
"overrideUrl": "https://www.mozilla.org/en-US/firefox/126.0beta/whatsnew/?nimbusBranch=control"
- Attached a screenshot of the issue:
|
|
1,893,944 | 16,913,010 |
Created attachment 9399092
log.txt
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0
Steps to reproduce:
Access any .local sites such as homeassistant.local
Actual results:
The browser tab will be in a loading state for 10 seconds, afterwards the site will load instantly.
Expected results:
The site should load fast since the .local domain resolves almost instantly when queried for A/AAA records.
I've done some digging, attached you can find the log with the Network preset + GetAddrInfo.
It seems that the tab is stuck at loading while TYPE65 record is looked up.
2024-04-29 07:31:52.73349 starts the TYPE65 dns record
10 seconds afterwards
2024-04-29 07:32:02.740798 the lookup finishes with a fail status
It might be technically possible to have HTTPS records in mdns but as far as I know it is not widely used.
Perhaps .local domains should be skipped from TYPE65 lookups or perhaps firefox should load the site the moment either A or TYPE65 lookup is obtained.
|
|
1,893,945 | 16,913,011 |
Created attachment 9399093
Credit link for mountain wallpaper still showing link for red panda
STR:
1. Set `browser.newtabpage.activity-stream.newtabWallpapers.enabled = true`.
2. Change the new tab wallpaper image.
3. Scroll to the bottom of the page and hover the cursor over the "Photo by" links.
The text for the photo credit changes but the link destinations are for the last wallpaper before the page was reloaded.
|
|
1,893,979 | 16,913,369 |
Created attachment 9399124
image.png
**[Affected versions]:**
- Firefox Beta 126.0b6 (Build #20240426091720)
**[Affected Platforms]:**
- Windows 11 x64
- macOS 13.6.2
- Ubuntu 22.04 x64
**[Prerequisites]:**
- Have the latest Firefox Beta 125 installed.
- Have a browser profile enrolled in the Control or Treatment A branches of the [WNP Messaging System + Nimbus Tooling](https://experimenter.services.mozilla.com/nimbus/wnp-messaging-system-nimbus-tooling/summary) experiment.
**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Update the browser to Beta 126.
3. Observe the 126 What's New page.
**[Expected result]:**
- The "Say 'Hola' to Firefox translations" WNP is displayed.
**[Actual result]:**
- The "No account required. But you might want one." WNP is displayed.
**[Notes]:**
- The issue is reproducible since the latest update to the Nimbus recipe.
- Attached a screenshot of the issue:
|
|
1,894,740 | 16,918,259 |
from [comment 6](https://bugzilla.mozilla.org/show_bug.cgi?id=1892125#c6) on bug 1892125
I can still reproduce this issue [bug 1892125] on the latest Nightly 127.0a1 - tested on macOS 13. I reproduced it with both Copy and Download options of the Save full page dialog. Please see the [screen recording](https://imgur.com/a/LjQhKbk).
Here are the steps that I used.
1. Navigated to https://en.wikipedia.org/wiki/Sun
2. Restarted Nightly using the key shortcuts Cmd+Shift+J and then Cmd+Option+R
3. On the Wiki page - enable Screenshots using Cmd+Shift+S
4. Quickly clicked on the Save full page and then on the Copy button
Actual results - the Preview dialog is dismissed, no 'Screenshot copied' notification is shown and the screenshot is not copied. Please keep in mind that the issue is intermittent.
|
|
1,895,050 | 16,920,231 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:125.0) Gecko/20100101 Firefox/125.0
Steps to reproduce:
1. Download version K.a of the ARMv8-A Reference Manual from here: https://developer.arm.com/documentation/ddi0487/ka/
2. Open it in Firefox.
3. Set zoom to 125% (which is the default for me).
4. Try to scroll to the very end (or just press the "end" key on your keyboard).
Actual results:
The page is truncated about a quarter into page 13446 (out of 14777). It just... ends there.
The document is truncated earlier when using a higher zoom level, and the issue disappears entirely when using a low enough zoom level, which makes me think that this is an issue with Firefox and not pdfjs.
From my testing, it seems that the truncation happens at 17'900'000px document height. Is this a hardcoded limit?
Tested on arm64 macOS and x86_64 Ubuntu, both with Firefox 125.0.3.
Expected results:
It should just display the rest of the PDF.
|
|
1,895,242 | 16,923,304 |
Steps to reproduce:
Attempted to use dependency auto-publication with reference browser.
Actual results:
Gradle raised an error:
```
Caused by: org.gradle.internal.metaobject.AbstractDynamicObject$CustomMessageMissingMethodException: Could not find method configureEach() for arguments [substitute_local_ac_117uhdruob31cof1fcvudr9i$_run_closure2$_closure3$_closure4$_closure5@7864e8dd] on object of type org.gradle.api.internal.artifacts.ivyservice.dependencysubstitution.DefaultDependencySubstitutions.
```
Expected results:
Gradle should have synced normally.
(It seems the problem is linked to an erroneous linting behavior that flags an actually correct use of `all` and suggests to replace it with `configureEach` for `dependencySubstitution`.)
|
|
1,827,415 | 16,365,114 |
See bug 1827236
|
|
1,827,572 | 16,366,533 |
**Found in**
* Firefox 113.0b2
**Affected versions**
* Firefox 113 beta
* Nightly 114.0a1
**Tested platforms**
* Affected platforms: Windows 10, macOS 11.7
**Preconditions**
* Firefox is set as the default browser and it is pinned to the taskbar/dock;
* browser.ping-centre.log set to true;
* Have the "Browser Console" opened.
**Steps to reproduce**
1. Navigate to the "about:welcome" page and focus on the "Browser Console".
2. Observe the displayed pings.
**Expected result**
* A telemetry ping specific to the "about:welcome" and the "Get Started" slide should be triggered. It should look like this:
** TELEMETRY PING (about:welcome): {"experiments":{},"locale":"en-US","version":"112.0","release_channel":"release","event":"IMPRESSION","event_context":"{\"page\":\"about:welcome\"}","message_id":"MR_WELCOME_DEFAULT_0_AW_GET_STARTED_GLIMG","addon_version":"20230406114409","client_id":"41dee36e-9b18-4665-bde9-d93306a75f76","browser_session_id":"99799259-9c36-4b28-92b5-4d77a2445145"}
**Actual result**
* The telemetry ping is triggered but is specific to the "Easy setup" slide. It looks like this:
**TELEMETRY PING (about:welcome): {"experiments":{"beta-ech-validation":{"branch":"enabled-fallbacks"}},"locale":"en-US","version":"113.0","release_channel":"beta","event":"IMPRESSION","event_context":"{\"page\":\"about:welcome\"}","message_id":"MR_WELCOME_DEFAULT_0_AW_EASY_SETUP_EGLIMG","addon_version":"20230411180038","client_id":"f7f79348-4654-4655-ac78-62cd4c7236a2","browser_session_id":"b1e3278e-3045-40d6-b8cd-32c56a11b42d","attribution":{"dlsource":"mozillaci"}}
**Regression range**
This is a recent regression as it is not reproducible on the latest Firefox 112 release. I will look for a regression range as soon as possible.
|
|
1,827,573 | 16,366,535 |
Created attachment 9328094
FxApromptExp_ChooseYourLanguageSlide.gif
**[Affected versions]:**
- Firefox Beta 113.0b2 (Build ID: 20230411180038)
**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64
**[Prerequisites]:**
- Have the Firefox Beta 113.0b2 en-US build installed and opened.
- Have set the Japanese OS language.
- Have the “nimbus.debug” pref set to true in the “about:config” page.
**[Steps to reproduce]:**
1. Force enroll in the Treatment B branch of the experiment using the following link: about:studies?optin_slug=prompt-fxa-creation-after-import&optin_branch=treatment-b&optin_collection=nimbus-preview
2. Navigate to the “about:welcome” page.
3. Click the “Save and continue” button from the first screen and complete the import flow.
4. Observe the elements from the “Choose Your Language” screen.
**[Expected result]:**
- The title from the left part of the screen and the label of the primary button are translated into Japanese.
**[Actual result]:**
- The title from the left part of the screen is not translated.
- The “Switch to” label of the primary button is displayed.
**[Notes]:**
- This issue is ONLY reproducible when being enrolled in the experiment.
- This issue is NOT reproducible on the Treatment A branch of the experiment.
- The elements of the “Choose Your Language” screen are correctly displayed after the page refresh.
- This issue is also reproducible when the German(Germany) OS language is set.
- This issue is also reproducible when naturally enrolled in the experiment.
- Attached is a screen recording of the issue.
|
|
1,827,718 | 16,367,748 |
Both [`ASRouterTargeting#getEnvironmentSnapshot`](https://searchfox.org/mozilla-central/rev/ad732108b073742d7324f998c085f459674a6846/browser/components/newtab/lib/ASRouterTargeting.jsm#949) and [`ASRouter#getTargetingParameters`](https://searchfox.org/mozilla-central/rev/ad732108b073742d7324f998c085f459674a6846/browser/components/newtab/lib/ASRouter.jsm#1146) do not serialize arrays correctly. Insead they get serialized as an object with string keys. This breaks testing targeting expressions in ASRouter DevTools as well as any targeting payloads serialized for use with the background message service.
|
|
1,827,903 | 16,368,887 |
Created attachment 9328353
image.png
**Found in**
* 114.0a1 (2023-04-13)
**Affected versions**
* 114.0a1 (2023-04-13)
* 113.0b3 (default disabled)
**Tested platforms**
* Affected platforms: Windows 10x64, Ubuntu 20.04, macOS 12
* Unaffected platforms: none
**Preconditions**
* browser.migrate.content-modal.enabled:true
* have multiple browsers or multiple accounts for one browser that contains bookmarks
**Steps to reproduce**
1. Open about:preferences and click on Import data.
2. Click the dropdown menu to choose a browser and observe the window.
**Expected result**
* All browsers are correctly displayed, or maybe a scroll bar is present.
**Actual result**
* The browsers do not fit inside the dropdown and sometimes the dropdown is cut off.
**Regression range**
* Most likely started with the implementation of the new Import Wizard Experience. Will search for one ASAP to be sure.
**Additional notes**
* Attached a screenshot.
|
|
1,828,334 | 16,371,851 |
Created attachment 9328716
Protocol Handler Warning Bypass.pdf
A full copy of this bug bounty submission with full screenshots can be found in the attached PDF file. I have also attached a video recording of the persistent soft lock. However, as this can't be recorded on the soft-locked device, the recording quality is quite low.
Issue Context
A protocol handler is an application that knows how to interpret particular types of links: for example, a mail client is a protocol handler for "mailto:" links. This allows external applications to be opened via a browser by navigating to a link such as “mailto:[email protected]”.
Upon navigating to a protocol handler URL such as “calculator:calc” or “microsoft.windows.camera:aaaa”, browsers warn the user prior to triggering the protocol handler. This is due to how protocol handlers allow for the execution of programs outside of the browser context, and the security of these protocol handlers is outside of the browsers control.
Firefox will raise a warning prior to triggering the protocol handler in the following circumstances:
~ Navigation to a URL via an “<a>” tag.
~ A JavaScript redirect, such as window.open("calculator:calc").
~ Header based-redirects.
Issue description
Despite using a warning if a protocol handler URL is navigated to via the previously specified method, Firefox skips this check if the URL is directly navigated to directly via the URL bar. This can be done by entering it into the URL bar and pressing the “enter” key, or by setting the browser homepage to a URL containing a protocol handler and then re-opening Firefox.
One caveat to the above description is that the first time Firefox encounters a new protocol handler, it appears to silently ignore the request, and then upon any subsequent request it will automatically open.
This effectively circumvents the protection to prevent users from inadvertently executing protocol handlers.
Impact
Windows protocol handlers have been vulnerable to a number of remote code execution vulnerabilities in the past, any of which could have been leveraged in combination with this to function as a zero-click remote code execution vulnerability. Three such vulnerabilities are shown below:
~ https://positive.security/blog/ms-officecmd-rce
~ https://blog.doyensec.com/2018/05/24/electron-win-protocol-handler-bug-bypass.html
~ https://www.bleepingcomputer.com/news/security/new-windows-search-zero-day-added-to-microsoft-protocol-nightmare/
Zero-click Remote Code Execution
Real world situations where this is able to be leveraged as a zero-click remote code execution would include:
~ Social engineering, where a user is coerced into copy-pasting a URL into Firefox.
~ Compromising a cloud-sync session and setting the user's homepage to a protocol handler URL.
~ Lateral movement within a network, where a user can modify a user’s homepage via modifying config files on a victim's machine via an SMB share functionality.
~ User or system level persistence on a device via modifying either the Firefox configuration files or the windows registry keys to allow setting the user’s homepage.
If an attacker has file access to the victim machine machine, such as the previous two examples, this can be done without the need for a protocol handler vulnerability, as the user can simply add an unsafe protocol handler with user level privileges.
One-click Remote Code Execution
Alternatively for a one-click remote code execution, an attacker could use the Java Network Launch Protocol if Java is installed upon the host. Further information on this can be found in the following whitepaper:
https://cybir.com/wp-content/uploads/2021/06/JNLP-Injection-and-Attacks-Release.pdf
A example of this attack is the the following URL
“jnlp:https://docs.oracle.com/javase/tutorialJWS/samples/deployment/dynamictree_webstartJWSProject/dynamictree_webstart.jnlp”:
Upon clicking the run button, the Jar file referenced in the URL above is executed, in this case, opening a sample application.
Persistent Denial of Service
Another notable use for this vulnerability would be via the use of the “ms-cxh” and “ms-cxh-full” protocol handlers which can softlock some windows versions by creating a persistent black screen. This can be fixed through a series of commands found in the paper below, but is usually fixed with a full system reboot.
https://papers.vx-underground.org/papers/Windows/Analysis%20and%20Internals/2022-01-16%20-%20Notes%20on%20Windows%20MS-CXH%20and%20MS-CXH-FULL%20handlers.pdf
This was confirmed on an up-to-date windows version found here:
Edition: Windows 10 Home
Version: 21H2
OS Build: 19044.2846
Experience: Windows Feature Experience Pack 120.2212.4190.0
Once this setting is saved and Firefox is closed, every subsequent reopening of Firefox will soft-lock the computer. This will prevent all use of Firefox on the device without changing the specific file system configuration, as Firefox cannot be opened to remove this homepage setting. As this is a saved configuration, this will persist between reboots. To remove this soft-lock, the prefs.js file must be modified to remove the browser.startup.homepage value.
Steps to Replicate
Submit a protocol handler into the URL bar and press the “enter” key. If no applications open, re-submit the value and press the “enter” key again.
Here are three sample protocol handlers that will open an application on a default windows machine:
~ ms-photos:photos
~ microsoft.windows.camera:camera
~ ldap:ldap
To observe the homepage functionality, set the homepage at about:preferences#home to one of the above settings, then close and reopen Firefox. Once again, if no application opens on first reboot, close and reopen Firefox.
Remediation
Implement a protocol handler warning on all instances where a protocol handler is triggered from Firefox.
|
|
1,828,861 | 16,377,070 |
Created attachment 9329214
astral.png
When connecting to `astral.sh` it seems that in the initial request the 'Secure Connection Failed' appears, but when reloading it works again.
|
|
1,829,366 | 16,380,299 |
+++ This bug was initially created as a clone of Bug #1823164 +++
We have decided on a slightly different solution to bug 1823164.
|
|
1,829,619 | 16,383,901 |
Crash report: https://crash-stats.mozilla.org/report/index/59f035e7-257c-4363-9ae9-d4bdf0230419
From Sentry, [issue 1](https://mozilla.sentry.io/issues/4120649252/?project=6295551&query=is%3Aunresolved+level%3Afatal+firstSeen%3A-1w&referrer=issue-stream&sort=freq&statsPeriod=14d&stream_index=3) and [issue 2](https://mozilla.sentry.io/issues/4110166970/?project=6295551&query=is%3Aunresolved+level%3Afatal+firstSeen%3A-1w&referrer=issue-stream&sort=freq&statsPeriod=14d&stream_index=1)
Notes:
This seems to be happening in [navigateToDefaultBrowserAppsSettings](https://searchfox.org/mozilla-mobile/source/firefox-android/fenix/app/src/main/java/org/mozilla/fenix/ext/Activity.kt#121-134). A fix could be to make sure the activity described by the intent is present before navigating/starting the activity.
Java stack trace:
```
android.content.ActivityNotFoundException
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1809)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1523)
at android.app.Activity.startActivityForResult(Activity.java:4247)
at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:2)
at android.app.Activity.startActivityForResult(Activity.java:4205)
at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:1)
at android.app.Activity.startActivity(Activity.java:4544)
at android.app.Activity.startActivity(Activity.java:4512)
at org.mozilla.fenix.ext.ActivityKt.navigateToDefaultBrowserAppsSettings(Activity.kt:41)
at org.mozilla.fenix.ext.ActivityKt.openSetDefaultBrowserOption$default(Activity.kt:82)
at org.mozilla.fenix.onboarding.JunoOnboardingFragment$ScreenContent$1.invoke(JunoOnboardingFragment.kt:12)
at org.mozilla.fenix.onboarding.view.JunoOnboardingScreenKt$JunoOnboardingScreen$4$1.invoke(JunoOnboardingScreen.kt:8)
at androidx.compose.foundation.ClickableKt$genericClickableWithoutGesture$detectPressAndClickFromKey$1.invoke(Clickable.kt:183)
at androidx.compose.ui.input.key.KeyInputModifier.propagateKeyEvent-ZmokQxo(KeyInputModifier.kt:15)
at androidx.compose.ui.platform.AndroidComposeView.dispatchKeyEvent(AndroidComposeView.android.kt:126)
at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1630)
at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1630)
at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1630)
at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1630)
at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1630)
at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1630)
at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1630)
at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1630)
at android.view.ViewGroup.dispatchKeyEvent(ViewGroup.java:1630)
at com.android.internal.policy.DecorView.superDispatchKeyEvent(DecorView.java:421)
at com.android.internal.policy.PhoneWindow.superDispatchKeyEvent(PhoneWindow.java:1806)
at androidx.core.view.KeyEventDispatcher.dispatchKeyEvent(KeyEventDispatcher.java:103)
at androidx.core.app.ComponentActivity.dispatchKeyEvent(ComponentActivity.java:19)
at androidx.appcompat.app.AppCompatActivity.dispatchKeyEvent(AppCompatActivity.java:23)
at androidx.appcompat.view.WindowCallbackWrapper.dispatchKeyEvent(WindowCallbackWrapper.java:3)
at androidx.appcompat.app.AppCompatDelegateImpl$AppCompatWindowCallback.dispatchKeyEvent(AppCompatDelegateImpl.java:9)
at com.android.internal.policy.DecorView.dispatchKeyEvent(DecorView.java:335)
at android.view.ViewRootImpl$ViewPostImeInputStage.processKeyEvent(ViewRootImpl.java:4362)
at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:4327)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3878)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3931)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3897)
at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:4024)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3905)
at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:4081)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3878)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3931)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3897)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3905)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3878)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3931)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3897)
at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:4057)
at android.view.ViewRootImpl$ImeInputStage.onFinishedInputEvent(ViewRootImpl.java:4218)
at android.view.inputmethod.InputMethodManager$PendingEvent.run(InputMethodManager.java:2400)
at android.view.inputmethod.InputMethodManager.invokeFinishedInputEventCallback(InputMethodManager.java:1964)
at android.view.inputmethod.InputMethodManager.finishedInputEvent(InputMethodManager.java:1955)
at android.view.inputmethod.InputMethodManager$ImeInputEventSender.onInputEventFinished(InputMethodManager.java:2377)
at android.view.InputEventSender.dispatchInputEventFinished(InputEventSender.java:141)
at android.os.MessageQueue.nativePollOnce(Native Method)
at android.os.MessageQueue.next(MessageQueue.java:323)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:6200)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:911)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:801)
```
|
|
1,817,269 | 16,283,709 |
Created attachment 9318225
Firefox and computer information
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
Update to Firefox 110
Open any stream on https://www.twitch.tv
Actual results:
Low video frame rate
Lots of dropped frames
The bottom and top edges of the video flicker
Expected results:
Fluid video playback, no flicker
(If I disable hardware acceleration the problem disappears.
YouTube works fine with hardware acceleration)
|
|
1,817,525 | 16,285,490 |
Created attachment 9318507
voice input.mp4
### Steps to reproduce
1. Tap into the address bar and type the first part of a search query
2. Use voice input to complete your query
### Expected behavior
The voice input appends what you've already typed
### Actual behavior
The voice input replaces what you've already typed with what you've spoken
### Device information
* Firefox version: 110.0.1
* Android device model: Samsung Galaxy S9
* Android OS version: 10
### Any additional information?
|
|
1,817,598 | 16,286,188 |
Steps to reproduce:
On git commit 0e3779abe6ad44feb787a295fbb67bc9fe4e927a the attached sample asserts when invoked as `obj-x86_64-pc-linux-gnu/dist/bin/js --fuzzing-safe crash.js`. Bisecting the issue points to commit 54d824cb31489fb2884e3d23172cdde9808ee5ed related to bug 1816890.
```
const v2 = this.blackRoot();
v2[1000n] = 1000n;
gc();
```
```
#0 0x00005555573be107 in js::NativeObject::getDenseElement (this=0x3f42bd83e138, idx=0)
at js/src/vm/NativeObject.h:601
#1 0x000055555737013b in TraceRootArrays (trc=0x7ffff743c440, color=js::gc::MarkColor::Black)
at js/src/shell/js.cpp:801
#2 0x000055555736185e in TraceBlackRoots (trc=0x7ffff743c440, data=0x0)
at js/src/shell/js.cpp:810
#3 0x00005555584d91c6 in js::gc::GCRuntime::traceEmbeddingBlackRoots (this=0x7ffff7423728, trc=0x7ffff743c440)
at js/src/gc/RootMarking.cpp:379
#4 0x00005555584d8b69 in js::gc::GCRuntime::traceRuntimeCommon (this=0x7ffff7423728, trc=0x7ffff743c440,
traceOrMark=js::gc::GCRuntime::MarkRuntime) at js/src/gc/RootMarking.cpp:362
#5 0x00005555584d8701 in js::gc::GCRuntime::traceRuntimeForMajorGC (this=0x7ffff7423728, trc=0x7ffff743c440,
session=...) at js/src/gc/RootMarking.cpp:242
#6 0x000055555840c679 in js::gc::GCRuntime::beginMarkPhase (this=0x7ffff7423728, session=...)
at js/src/gc/GC.cpp:2880
#7 0x000055555840fbea in js::gc::GCRuntime::incrementalSlice (this=0x7ffff7423728, budget=...,
reason=JS::GCReason::API, budgetWasIncreased=false) at js/src/gc/GC.cpp:3614
#8 0x00005555584123b5 in js::gc::GCRuntime::gcCycle (this=0x7ffff7423728, nonincrementalByAPI=true,
budgetArg=..., reason=JS::GCReason::API) at js/src/gc/GC.cpp:4198
#9 0x0000555558413332 in js::gc::GCRuntime::collect (this=0x7ffff7423728, nonincrementalByAPI=true, budget=...,
reason=JS::GCReason::API) at js/src/gc/GC.cpp:4386
#10 0x00005555583f2432 in js::gc::GCRuntime::gc (this=0x7ffff7423728, options=JS::GCOptions::Normal,
reason=JS::GCReason::API) at js/src/gc/GC.cpp:4463
#11 0x000055555846616e in JS::NonIncrementalGC (cx=0x7ffff742f100, options=JS::GCOptions::Normal,
reason=JS::GCReason::API) at js/src/gc/GCAPI.cpp:297
#12 0x0000555557e39670 in GC (cx=0x7ffff742f100, argc=0, vp=0x7ffff4cf6090)
at js/src/builtin/TestingFunctions.cpp:705
#13 0x000055555756bd5e in CallJSNative (cx=0x7ffff742f100,
:Value*)>, reason=js::CallReason::Call, args=...)
at js/src/vm/Interpreter.cpp:459
#14 0x000055555756b59d in js::InternalCallOrConstruct (cx=0x7ffff742f100, args=..., construct=js::NO_CONSTRUCT,
reason=js::CallReason::Call) at js/src/vm/Interpreter.cpp:547
#15 0x000055555756c931 in InternalCall (cx=0x7ffff742f100, args=..., reason=js::CallReason::Call)
at js/src/vm/Interpreter.cpp:614
#16 0x000055555756c6f5 in js::CallFromStack (cx=0x7ffff742f100, args=..., reason=js::CallReason::Call)
at js/src/vm/Interpreter.cpp:619
```
|
|
1,817,611 | 16,286,274 |
Steps to reproduce:
1. Open Firefox with TalkBack enabled.
2. Browse to any URL, like https://www.google.com/ or make a search from the address bar.
3. Tap the screen at different points (simulating how to find something).
4. Navigate to any other websites, go backwards and forwards, open new tabs and close them (simulate a regular user's experience browsing the web), and repeat step 3 from time to time.
5. Open a custom tab or PWA and repeat step 3.
Actual results:
* Notice how TalkBack reads the title of the tab instead of nothing when tapping an empty part of the page and focuses the webview itself.
* Notice how, when tapping somewhere in the page with content, TalkBack starts reading it and, after the finger no longer touches the screen, the focus changes and TalkBack reads whichever content gained focus, not necessarily the one that was being tapped.
* When browsing multiple pages, doing searches, and going backwards and forwards, TalkBack reads either the URL of the current page, the title of the web search, or the title of a different tab if using a custom tab from another app or a PWA after a while.
Expected results:
* If tapping somewhere empty in a page, focus should not change to the webview itself, nor should TalkBack speak the title of the page.
* Focus should not change when no longer touching the screen, even if it goes to whatever was being tapped, its container, or an adjacent element.
* If speaking the title of the current page, it should actually be the title of the tab, not a URL, another tab's title, or a web search.
I believe that https://bugzilla.mozilla.org/show_bug.cgi?id=1813877 and its resolution in https://github.com/mozilla-mobile/firefox-android/pull/790 made these issues very noticeable, since the timing matches.
I'm using a Xiaomi Redmi Note 8 with MIUI 12.5.2.0, Android 11, TalkBack version 13.1.
|
|
1,817,659 | 16,286,495 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
1. Open dev tools
2. Go to network tab
3. Select any throttling option that is not "no throttling"
4. Try to load any web page
Actual results:
The browser acts as if it is completely offline, even when fast speeds are selected (Wi-Fi)
Expected results:
Just slow down the connection, not completely freeze it.
|
|
1,817,944 | 16,290,236 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
1. Download latest version of "Firefox Nightly for Developers" from Google Play
2. Open "https://webauthn.io"
3. After Enter demo username and click "Register"
Actual results:
It shows "The authenticator was unable to process the specified options, or could not create a new assertion signature"
Expected results:
Likes stable of Fenix, Wenauthn should works.
|
|
1,830,112 | 16,387,407 |
Created attachment 9330424
Set to default incomplete text.jpg
**[Affected versions]:**
- Firefox Beta 113.0b8 (Build #2015946947), e80fa83ad8+ GV: 113.0-20230425192707 AS: 97.4.1 2023-04-26T00:23:08.943312
**[Affected Platforms]:**
- Android 10 - Samsung S9
**[Prerequisites]:**
- Have the Firefox Beta 113.0b8 build installed.
- Set any of the following languages as default using the device’s settings: Spanish, French, German.
- Set the font size to the maximum using the device’s settings.
**[Steps to reproduce]:**
1. Open the browser from the prerequisites.
1.1. If the Juno Onboarding is not displayed, you were enrolled in the Control branch of the experiment. Use new profiles until you are enrolled in the Treatment branch.
2. Scroll down the “Set to default” card.
3. Observe the “Set to default” button.
**[Expected result]:**
- The text from the button is displayed entirely inside the button.
OR
- An ellipsis is displayed at the end of the button indicating that the string displayed is not complete.
**[Actual result]:**
- The text is not displayed entirely inside the button, there are strings missing depending on the font size and number of characters used for each language.
**[Notes]:**
- This issue is probably also reproducible with the “Notifications” card, but at the moment I don’t have an Android 13 device to verify. Will check this tomorrow and update the bug accordingly.
- This issue might be reproducible with other languages besides Spanish, French, and German.
- This issue is not reproducible using the English language.
- Attached is a screenshot of the issue.
|
|
1,830,605 | 16,390,330 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:114.0) Gecko/20100101 Firefox/114.0
Steps to reproduce:
Updated nightly.
Actual results:
KeepassXC cannot connect. Following their troubleshooting steps at https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide, I notice that keepassxc-proxy.exe does not load. Starting it manually did not help. All other configuration is correct as per that guide.
Expected results:
KeepassXC should keep working like it does in earlier builds. I rolled back to an older build and it works. This one works https://ftp.mozilla.org/pub/firefox/nightly/2023/04/2023-04-25-15-43-13-mozilla-central-l10n/firefox-114.0a1.en-GB.win64.installer.exe. Unsure of any later builds. Others have also reported this not working in latest nightly builds, on the keepassxc-browser github issues at https://github.com/keepassxreboot/keepassxc-browser/issues?q=is%3Aissue
|
|
1,830,725 | 16,392,694 |
Steps to reproduce:
1. Install Firefox from Microsoft Store
2. Launch it
OS is WIndows 11 with latest updates.
This does not happen when Firefox is installed from Mozilla website.
Actual results:
Empty window with grey placeholder UI displayed for about 10 seconds, with busy cursor. Then it unfreezes.
Expected results:
Firefox is launched without delays.
|
|
1,831,104 | 16,395,346 |
Created attachment 9331378
Bookmarks and History search suggestions pre-filled in the search bar are not accessed when hitting enter.mp4
### Steps to reproduce
1. Have some pages bookmarked and home browsing history.
2. Tap on the dropdown menu from the Google search engine icon.
3. Select the Bookmarks/History search engine.
4. Type in a valid search term (related to the saved bookmarks/browsing history).
5. Tap the pre-fill arrow displayed at the end of any search suggestion.
6. Once the URL for the desired search suggestion is pre-filled in the search bar, tap Enter/Go on the keyboard.
### Expected behavior
The link should be opened in a new tab.
### Actual behavior
The keyboard is dismissed, but the link is not opened.
### Device information
* Firefox version: Nightly 114.0a1 from 05/03
* Android device model: Lenovo Yoga Tab 11, Google Pixel 7
* Android OS version: Android 11, Android 13
### Any additional information?
This issue can also be reproduced when performing the search from Settings > Bookmarks/History menus.
|
|
1,831,574 | 16,398,242 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0
Steps to reproduce:
Opened PDF
Added Comments (C0)
Saved PDF with comments (S0)
Added Comments (C1)
Saved PDF again (selected override) (S1)
Added Comments (C2)
Saved PDF again (selected override) (S2)
Saved PDF again (selected override) (S3)
Actual results:
The changes from C1 were not saved in S1 but only in S2
The changes from C2 were not saved in S2 but only in S3
The Pattern seams to be that Changes from Cx only get saved in Save S(x+1) not in Sx
Expected results:
C1 should have been saved in S1. C2 should have been saved in S2
Generally Cx should be saved in Sx not in S(x+1)
|
|
1,831,971 | 16,402,203 |
If remote settings and Nimbus don't define a weather config, Firefox will show the suggestion on zero prefix. That means if remote settings contain a config but it hasn't been synced yet, Firefox will go from showing the suggestion on zero prefix to showing it on keywords after settings are synced.
Firefox shouldn't show the suggestion at all if there's no config.
|
|
1,832,105 | 16,403,332 |
**[Affected versions]:**
- Firefox Nightly 115.0a1 (Build ID: 20230508214159)
- Firefox Nightly 114.0b1 (Build ID: 20230508175934)
**[Affected Platforms]:**
- Windows 10 x64
- Linux Ubuntu 20.04 x64
- macOS 12.4
**[Prerequisites]:**
- Have a VPN client connected to a US server ( make sure the `browser.search.region` pref is set accordingly).
- Have the Firefox Nightly 115.0a1 build installed.
- Set the following prefs:
`browser.urlbar.weather.featureGate` = `true`
(Windows only) `browser.urlbar.weather.ignoreVPN` = `true`
**[Steps to reproduce]:**
1. Open the browser from the prerequisites.
2. Type the “weather” string in the Address Bar.
3. Click the Feedback button.
4. Click any of the first 2 options (“Report inaccurate location” or “Show less frequently”).
5. Click the Feedback button again.
6. Click any of the Dismiss options from the sub-menu (“Not relevant” or “Not interested”).
7. Observe the behavior.
**[Expected result]:**
- The weather suggestion is removed from the Address Bar panel and a Thank you message with the “Got it” button is displayed.
**[Actual result]:**
- Nothing happens, the weather result remains displayed.
**[Notes]:**
- We noticed that even though the dismiss buttons don’t work, the telemetry is incremented with each click for `firefox-suggest-weather-command-not-relevant` and `firefox-suggest-weather-command-not-interested` (depending on which one is clicked).
- Here is the [screen recording](https://drive.google.com/file/d/13LODdmQfvYXNLDjqibKKEOTFNxLM8nn6/view?usp=sharing) of the issue.
|
|
1,823,164 | 16,331,137 |
At least two users on reddit were unable to figure out how to download a PDF displayed by pdf.js. "Save as PDF" doesn't sound great to me when the opened document is already a PDF, instead of just "Download PDF".
The bottom of the share menu is maybe also not the immediately most obvious place to look.
|
|
1,823,484 | 16,334,516 |
Sometimes Firefox Relay integration is not featured in the autocomplete if it was offered before and user didn't opt in or opt out.
|
|
1,823,547 | 16,334,948 |
Crash report: https://crash-stats.mozilla.org/report/index/15eeee95-a8cc-4d16-8f2e-762960230320
Reason: ```EXCEPTION_ACCESS_VIOLATION_READ```
Top 10 frames of crashing thread:
```
0 xul.dll nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_RelocateUsingMemutils>::Length const xpcom/ds/nsTArray.h:410
0 xul.dll nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_RelocateUsingMemutils>::IsEmpty const xpcom/ds/nsTArray.h:413
0 xul.dll nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_RelocateUsingMemutils>::MoveConstructNonAutoArray<nsTArrayInfallibleAllocator> xpcom/ds/nsTArray-inl.h:633
1 xul.dll nsTArray_Impl<mozilla::Variant<mozilla::net::OnStartRequestParams, mozilla::net::OnDataAvailableParams, mozilla::net::OnStopRequestParams, mozilla::net::OnAfterLastPartParams>, nsTArrayInfallibleAllocator>::nsTArray_Impl xpcom/ds/nsTArray.h:1053
1 xul.dll nsTArray<mozilla::Variant<mozilla::net::OnStartRequestParams, mozilla::net::OnDataAvailableParams, mozilla::net::OnStopRequestParams, mozilla::net::OnAfterLastPartParams> >::nsTArray xpcom/ds/nsTArray.h:2721
1 xul.dll mozilla::net::EarlyHintPreloader::InvokeStreamListenerFunctions netwerk/protocol/http/EarlyHintPreloader.cpp:542
2 xul.dll mozilla::net::EarlyHintPreloader::OnStartRequest netwerk/protocol/http/EarlyHintPreloader.cpp:599
3 xul.dll mozilla::net::ParentChannelListener::OnStartRequest netwerk/protocol/http/ParentChannelListener.cpp:86
4 xul.dll mozilla::net::OpaqueResponseBlocker::OnStartRequest netwerk/protocol/http/OpaqueResponseUtils.cpp:234
5 xul.dll mozilla::net::OpaqueResponseBlocker::ResolveAndProcessData netwerk/protocol/http/OpaqueResponseUtils.cpp:475
```
The crashes I looked all were on the jemalloc poison value, and had the same general stack, where OpaqueResponseBlocker calls into ParentChannelListener calls into EarlyHintPreloader.
29 crashes. The first I see is this one from the 20230125094200 build: bp-cba079f0-03c0-4118-9da4-72c400230125
It looks like some Early Hints work landed around then (such as bug 1810546), but some ORB work also landed around then (bug 1778135) and that's also in the stack.
|
|
1,823,637 | 16,335,499 |
Steps to reproduce:
- Opened Thunderbird, layout Classic, clicked on a new message in the messages list, ordered by Date DESC
- While reading message, a new message appeared in the list
- Hit the Reply button on the message I was reading
(v112.0b1)
Actual results:
The compose window opened, and the message I was replying to was *the message above the one I was reading in the messages list*
Expected results:
The compose window opens with the message I was reading as the message to which I was replying.
|
|
1,824,091 | 16,339,076 |
It's possible that when the OHTTPService is loaded the network request fails.
We want to ensure that we retry fetching the config when the network is back up.
|
|
1,819,254 | 16,302,850 |
User Agent: Mozilla/5.0 (Android 13; Mobile; rv:109.0) Gecko/111.0 Firefox/111.0
Steps to reproduce:
Open any YouTube video. Watch it on full screen. While watching, you want to change quality or speed of the video so you click on settings icon on the top right corner. Now when you click on "quality" or "speed" option, the full screen mode disappears, i.e. landscape mode changes to portrait and you need to manually re-enter to full screen mode. You've to do it every time when you want to change those settings again.
(As a short note, I'm on firefox beta v 111.0b6)
Actual results:
When watching YouTube on fullscreen mode and clicking on "quality" or "speed" option from settings, the full screen mode disappears, i.e. landscape mode changes to portrait and you need to manually re-enter to full screen mode.
Expected results:
Quality or speed should have changed without exiting the full screen.
|
|
1,819,277 | 16,303,301 |
This is on linux with:
* Thunderbird daily 112.0a1 (2023-02-27) (64-bit)
* at-spi2-core 2.46.0
* python-atspi 2.46.0
However I expect it to be reproduceable on all the platforms.
### The problem
When using the new message list with the keyboard only, it is not possible to inwoke its context menu.
### Steps to reproduce
* Launch thunderbird, use tab or shift+tab or F6 and shift+F6 to focus the message list.
* Make sure pressing up / down arrow keys navigates in the list.
* Now eitherr press shift+F10 or dedicated applications key located on the right hand side of the keyboard, on the bottom, near the space key.
### Actual results
Nothing happens
### Expected
It should be possible to open the context menu for the selected message or multiple selected messages by using the keyboard without touching the mouse.
|
|
1,819,383 | 16,304,239 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
I opened the new Thunderbird
Actual results:
I can't see any of the emails that are in my IMAP account online NOR am I able to subscribe to them again. THey have disappeared since I opened TB last time!
I discovered more - the problem was that I had folders set on Unified. When I switched Unified off I found all the folders under the account. But there seems no point to have unified as an option if it doesn't include all the folders unified.. and if I have all and Unified together then a lot of stuff is in twice.
Expected results:
I should have NOT lost all the folders that were subscribed to when I last opened TB, there seems to be a need for more thought in how Unified Folders works to unify all folders and not just a small subset... There used to be Local folders that was where these folders went as I recall.
|
|
1,819,721 | 16,306,329 |
Created attachment 9320627
Now
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0
Steps to reproduce:
If the cursor is at the bottom left of the window causing the Status bar move to the right while a page is loading, the Status bar is not aligned to the right leaving an empty space.
Mozregression returned:
Bug 1789892 - Simplify statuspanel a bit. r=dao
I'm a bit baffled about bug 1789877. My best theory so far is that we're
inserting the element a bit deeper in the DOM and that causes us to
reflow slightly more stuff when tab-switching, but...
In any case while going through the code the status panel can be
simplified a bit now, so do that.
Differential Revision: https://phabricator.services.mozilla.com/D156876
pushlog_url: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b84775bfccf2243f664b1c15ca987a05c54a95e2&tochange=6fbacc7bb20a65608b74e3ea09cb71af0439cb07
Actual results:
Status bar not aligned correctly
Expected results:
Status bar aligned correctly
|
|
1,819,746 | 16,306,450 |
This crash is a regression starting in 111.0a1.
Crash report: https://crash-stats.mozilla.org/report/index/14a339ab-d707-446b-aeb2-18ead0230227
Java stack trace:
```
java.lang.NullPointerException: Attempt to invoke virtual method 'int android.view.Display.getRotation()' on a null object reference
at mozilla.components.compose.cfr.helper.DisplayOrientationListener.onDisplayChanged(DisplayOrientationListener.kt:7)
at android.hardware.display.DisplayManagerGlobal$DisplayListenerDelegate.handleMessage(DisplayManagerGlobal.java:476)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5597)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:984)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
```
|
|
1,819,760 | 16,306,514 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0
Steps to reproduce:
Mouse right click on the padlock symbol and release the mouse button on the Windows Explorer file area.
Actual results:
Firefox 112.0a1 Build-ID 20230301093735:
A shortcut file was created, but instead of type ".url" now as "url.download".
Windows can't work with the type ".download".
Expected results:
Create a shortcut file of type ".url" like in the version before.
Windows can open the shortcut in Firefox Nightly (my standard browser) again.
|
|
1,820,169 | 16,309,219 |
Created attachment 9321019
az_recorder_20230303_151556.mp4
### Steps to reproduce
1. Go to a different website that the ones from top sites.
2. Go to 3 dot menu > Add to shortcuts and observe the snackbar.
3. Go to 3 dot menu > Remove from shortcuts and observe the snackbar.
### Expected behavior
The snackbar is clearly visible
### Actual behavior
The snackbar is hidden behind the Address bar.
### Device information
* Firefox version: Nightly 112.0a1, Beta 111.0b8
* Android device model: Google Pixel 3A, Oppo Find X5, Google Pixel 7.
* Android OS version: 11, 13.
### Any additional information?
|
|
1,820,750 | 16,315,195 |
Created attachment 9321585
ss of the issue.png
**[Affected versions]:**
- Firefox Beta 111.0 - Build ID: 20230306162820
**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64
**[Prerequisites]:**
- Have a Firefox 111.0 es-ES locale installed.
- Have the "nimbus.debug" pref set to "true" in the "about:config" page.
**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=first-run-easy-set-up-fx111&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Navigate to the "about:welcome" page and observe the "Set Firefox as default browser" option.
**[Expected result]:**
- The "Set Firefox as default browser" option is correctly aligned.
**[Actual result]:**
- The "Set Firefox as default browser" option is NOT aligned with the rest of the page elements.
**[Additional Notes]:**
- This issue might be reproducible on other Firefox locales besides es-ES, however, I have not found them yet.
- Attached is a screenshot of the issue:
|
|
1,820,909 | 16,316,401 |
Created attachment 9321734
Screenshot_2023-03-08_08-17-02.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
1. Go to https://www.unicode.org/charts/PDF/U31350.pdf
1. Search for some random codepoints
Actual results:
The highlights are mispositioned. Even, for some codepoints, the highlight is invisible at all, thus I cannot locate the matched text.
Expected results:
Not so.
|
|
1,820,914 | 16,316,425 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
Ran WebGL conformance test - https://registry.khronos.org/webgl/conformance-suites/2.0.0/deqp/functional/gles3/negativetextureapi.html?webglVersion=2&quiet=0&quick=1
Actual results:
Crash - Crash signature https://crash-stats.mozilla.org/signature/?signature=mozilla%3A%3AIsTarget3D
Expected results:
Render the page to view test result with either pass or fail of conformance test.
|
|
1,821,025 | 16,317,016 |
[Central-as-beta-simulation](https://treeherder.mozilla.org/jobs?repo=try&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry&revision=08c117aa419f441acc5c518c084b06462687390a&selectedTaskRun=JSzJiKQITrWSY3TW9vlg5w.0)
[How to run these simulations](https://wiki.mozilla.org/Sheriffing/How_To/Beta_simulations#TRUNK_AS_EARLY_BETA)
[Failure log](https://treeherder.mozilla.org/logviewer?job_id=408260864&repo=try)
```
[task 2023-03-08T10:59:59.564Z] TEST-PASS | js/src/jit-test/tests/wasm/fac.js | Success (code 0, args "--test-wasm-await-tier2") [0.1 s]
[task 2023-03-08T10:59:59.580Z] /builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13 Error: Assertion failed: got false, expected true: extended-const must be enabled on release and beta
[task 2023-03-08T10:59:59.580Z] Stack:
[task 2023-03-08T10:59:59.580Z] @/builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13
[task 2023-03-08T10:59:59.580Z] Exit code: 3
[task 2023-03-08T10:59:59.580Z] FAIL - wasm/features.js
[task 2023-03-08T10:59:59.581Z] TEST-UNEXPECTED-FAIL | js/src/jit-test/tests/wasm/features.js | /builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13 Error: Assertion failed: got false, expected true: extended-const must be enabled on release and beta (code 3, args "") [0.1 s]
[task 2023-03-08T10:59:59.581Z] INFO exit-status : 3
[task 2023-03-08T10:59:59.581Z] INFO timed-out : False
[task 2023-03-08T10:59:59.581Z] INFO stderr 2> /builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13 Error: Assertion failed: got false, expected true: extended-const must be enabled on release and beta
[task 2023-03-08T10:59:59.581Z] INFO stderr 2> Stack:
[task 2023-03-08T10:59:59.581Z] INFO stderr 2> @/builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13
[task 2023-03-08T10:59:59.612Z] TEST-PASS | js/src/jit-test/tests/wasm/fac.js | Success (code 0, args "--wasm-compiler=optimizing --no-avx") [0.1 s]
[task 2023-03-08T10:59:59.638Z] /builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13 Error: Assertion failed: got false, expected true: extended-const must be enabled on release and beta
[task 2023-03-08T10:59:59.638Z] Stack:
[task 2023-03-08T10:59:59.639Z] @/builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13
[task 2023-03-08T10:59:59.639Z] Exit code: 3
[task 2023-03-08T10:59:59.639Z] FAIL - wasm/features.js
[task 2023-03-08T10:59:59.648Z] TEST-UNEXPECTED-FAIL | js/src/jit-test/tests/wasm/features.js | /builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13 Error: Assertion failed: got false, expected true: extended-const must be enabled on release and beta (code 3, args "--baseline-eager") [0.1 s]
[task 2023-03-08T10:59:59.649Z] INFO exit-status : 3
[task 2023-03-08T10:59:59.649Z] INFO timed-out : False
[task 2023-03-08T10:59:59.649Z] INFO stderr 2> /builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13 Error: Assertion failed: got false, expected true: extended-const must be enabled on release and beta
[task 2023-03-08T10:59:59.649Z] INFO stderr 2> Stack:
[task 2023-03-08T10:59:59.649Z] INFO stderr 2> @/builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13
[task 2023-03-08T10:59:59.652Z] /builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13 Error: Assertion failed: got false, expected true: extended-const must be enabled on release and beta
[task 2023-03-08T10:59:59.653Z] Stack:
[task 2023-03-08T10:59:59.653Z] @/builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13
[task 2023-03-08T10:59:59.653Z] Exit code: 3
[task 2023-03-08T10:59:59.653Z] FAIL - wasm/features.js
[task 2023-03-08T10:59:59.654Z] TEST-UNEXPECTED-FAIL | js/src/jit-test/tests/wasm/features.js | /builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13 Error: Assertion failed: got false, expected true: extended-const must be enabled on release and beta (code 3, args "--ion-eager --ion-offthread-compile=off --ion-check-range-analysis --ion-extra-checks --no-sse3 --no-threads") [0.1 s]
[task 2023-03-08T10:59:59.654Z] INFO exit-status : 3
[task 2023-03-08T10:59:59.654Z] INFO timed-out : False
[task 2023-03-08T10:59:59.655Z] INFO stderr 2> /builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13 Error: Assertion failed: got false, expected true: extended-const must be enabled on release and beta
[task 2023-03-08T10:59:59.655Z] INFO stderr 2> Stack:
[task 2023-03-08T10:59:59.655Z] INFO stderr 2> @/builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13
[task 2023-03-08T10:59:59.655Z] /builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13 Error: Assertion failed: got false, expected true: extended-const must be enabled on release and beta
[task 2023-03-08T10:59:59.656Z] Stack:
[task 2023-03-08T10:59:59.656Z] @/builds/worker/checkouts/gecko/js/src/jit-test/tests/wasm/features.js:90:13
[task 2023-03-08T10:59:59.656Z] Exit code: 3
```
|
|
1,821,079 | 16,317,245 |
We have an offtrain fix for the following bug by resizing the checkbox text but an on train fix would be better to handle the text alignment for the multi-select checkboxes for longer text/locales.
+++ This bug was initially created as a clone of Bug #1820750 +++
**[Affected versions]:**
- Firefox Beta 111.0 - Build ID: 20230306162820
**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64
**[Prerequisites]:**
- Have a Firefox 111.0 es-ES locale installed.
- Have the "nimbus.debug" pref set to "true" in the "about:config" page.
**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=first-run-easy-set-up-fx111&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Navigate to the "about:welcome" page and observe the "Set Firefox as default browser" option.
**[Expected result]:**
- The "Set Firefox as default browser" option is correctly aligned.
**[Actual result]:**
- The "Set Firefox as default browser" option is NOT aligned with the rest of the page elements.
**[Additional Notes]:**
- This issue might be reproducible on other Firefox locales besides es-ES, however, I have not found them yet.
- Attached is a screenshot of the issue:
|
|
1,821,219 | 16,317,957 |
The WebGPU spec says:
```
enum GPUAutoLayoutMode {
"auto"
};
dictionary GPUPipelineDescriptorBase : GPUObjectDescriptorBase {
required (GPUPipelineLayout or GPUAutoLayoutMode) layout;
};
```
but Mozilla Central's `dom/webidl/WebGPU.webidl` says:
```
dictionary GPUPipelineDescriptorBase : GPUObjectDescriptorBase {
GPUPipelineLayout layout;
};
```
This leads to WebGPU CTS failures like:
```
assert_unreached: - EXCEPTION: GPUDevice.createComputePipeline: 'layout' member of GPUPipelineDescriptorBase is not an object. testAdapter@https://web-platform.test:8443/_mozilla/webgpu/webgpu/api/operation/adapter/requestAdapter.spec.js:35:27 Reached unreachable code
wpt_fn@https://web-platform.test:8443/_mozilla/webgpu/common/runtime/wpt.js:65:25
```
|
|
1,825,538 | 16,350,455 |
**Found in**
* 113.0a1 (2023-03-30)
**Affected versions**
* Beta 112.0b7
* Release 111.0.1
**Affected platforms**
* ALL
**Steps to reproduce**
1. Set Network.trr.mode to 3 in about:config.
2. Install the nordvpn addon and connect to US.
3. Reach any website.
**Expected result**
* Users should be able to reach the page ?
**Actual result**
* The Unable to find Proxy server error page is returned with Strict Network.trr mode and VPN
**Regression range**
Not Applicable
|
|
1,825,710 | 16,351,546 |
Created attachment 9326179
alpenglow dark.jpg
**Found in**
* 113.0a1(20230330214245)
**Affected versions**
* 113.0a1(20230330214245)
**Tested platforms**
* Affected platforms: macOS 13, Ubuntu 22, Windows 10
**Preconditions**
* Have VPN connected to US.
* Google as default search engine.
* browser.search.region set to US
* browser.urlbar.trending.featureGate set to true
**Steps to reproduce**
1. Launch FF.
2. Go to about:addons.
3. Change the browser theme to Dark and Alpenglow.
4. Open a new tab.
5. Click on the urlbar and enter Google Search mode.
**Expected result**
* The Google Trending Predictions icon are visible for each suggested element.
**Actual result**
* The Google Trending Predictions icons are barely visible in Dark theme and almost invisible in Alenglow.
|
|
1,825,916 | 16,352,799 |
Created attachment 9326395
ff.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0
Steps to reproduce:
1. open firefox nightly
2. press f12 to open dev tools and go to networks tab
3. go to https://www.youtube.com/ or may be https://bugzilla.mozilla.org
4. right click at network table header to show protocol
5. you should see at least 1 http/2 in networks request
Actual results:
all request protocol is http/1.1
Expected results:
some or all network request should be http/2
|
|
1,826,356 | 16,357,410 |
Created attachment 9326900
Screenshot 2023-04-04 at 14.44.32.png
**[Affected versions]:**
- Firefox Nightly 113.0a1, BUILD ID: 20230321213816
**[Affected Platforms]:**
- Windows 10x64
**[Prerequisites]:**
- Firefox is not set as the default browser.
- Have the [“user.js”](https://drive.google.com/file/d/1q_Ho49np4ra-fZ5CGfe0MaKNbJeH0N18/view?usp=share_link) file saved on your computer.
**[Steps to reproduce]:**
1. Create a new profile using the “-p –first-startup” syntax in the Command Prompt window, but do not open it.
2. Navigate to the profile folder and paste the [“user.js”](https://drive.google.com/file/d/1q_Ho49np4ra-fZ5CGfe0MaKNbJeH0N18/view?usp=share_link) file from the prerequisites.
3. Open the browser using the profile created.
4. Observe the description text from “Set to default for a week” spotlight.
**[Expected results]:**
- The “We notice that Firefox is not set as your default browser. Give as a try(we promise you won’t regret it!)” body string is displayed.
**[Actual results]:**
- The “We notice that Firefox is not set as your default browser. Give as a stry(we promise you won’t regret it!)” body string is displayed.
|
|
1,826,466 | 16,358,190 |
### Steps to reproduce
1. Set the app to the light theme.
2. With unified search enable, tap the search engine icon.
3. Select Bookmarks, Tabs or History icon in unified search.
### Expected behavior
Icons are visible
### Actual behavior
Icons are not visible
### Device information
* Firefox version:
113 Nightly
* Android device model:
Pixel 7
* Android OS version:
13
### Any additional information?
|
|
1,826,555 | 16,358,794 |
Created attachment 9327107
Screenshot 2023-04-05 at 16.11.39.png
**[Affected versions]:**
- Firefox Nightly 113.0a1, BUILD ID: 20230321213816
**[Affected Platforms]:**
- Windows 10x64
**[Prerequisites]:**
- Firefox is not set as the default browser.
- Have the [“user.js”](https://drive.google.com/file/d/1q_Ho49np4ra-fZ5CGfe0MaKNbJeH0N18/view?usp=share_link) file saved on your computer.
**[Steps to reproduce]:**
1. Create a new profile using the “-p –first-startup” syntax in the Command Prompt window, but do not open it.
2. Navigate to the profile folder and paste the [“user.js”](https://drive.google.com/file/d/1q_Ho49np4ra-fZ5CGfe0MaKNbJeH0N18/view?usp=share_link) file from the prerequisites.
3. Open the browser using the previously created profile.
4. Observe the elements from the “Set to Default” spotlight.
**[Expected results]:**
- The “X” (close) button is located in the upper right corner of the spotlight.
**[Actual results]:**
- The “X” (close) button is not displayed on the “Set to default” spotlight.
**[Notes]:**
- According to the [Figma](https://www.figma.com/file/c83OEio9DhCQKuabx2tIEl/NUO-Experiments-2023?node-id=2-372&t=7GHCcWYORUxalQYc-0) documentation the "X" button should be present in the upper right corner of the spotlight.
- Attached a screenshot of the issue.
|
|
1,827,042 | 16,361,645 |
Steps to reproduce:
Sort messages with newest at bottom of message list.
Select bottom (newest) message.
Close Thunderbird.
Re-open Thunderbird.
Actual results:
Thunderbird always opens with message list scrolled to top.
Expected results:
Thunderbird opens with message list scrolled to bottom since that's how it was last time it was closed (as it does on Thunderbird 102).
|
|
1,822,016 | 16,323,884 |
I noticed while working on additional telemetry for the bookmarks library and sidebar (bug 1819081) that regardless of whether a history item or a bookmark item is clicked in the app menu or library navbar, it's being reported as 'bookmark-item' due to [this line of code](https://searchfox.org/mozilla-central/source/browser/modules/BrowserUsageTelemetry.jsm#700) and because both history items and bookmark items both contain the `.bookmark-items` class.
I'm not sure if this was intentional with work done in bug 1620358, or something changed since that was implemented but we should probably distinguish between 'history items' and 'bookmark items'.
I haven't investigated all of the toolbar surfaces this telemetry covers to see if it applies to all surfaces, I only happened to notice the two surfaces previously mentioned while stepping through the debugger.
|
|
1,822,283 | 16,325,542 |
On first run, both the activation ping and the client deduplication ping will be sent at similar times. The metric that we use for both pings `activation.identifier` doesn't update quick enough and the same hashed GaID is sent for both.
|
|
1,822,288 | 16,325,561 |
Created attachment 9322961
DeviceMigrationPosition.gif
**[Affected versions]:**
- Firefox Release 111.0 (Build ID: 20230309232128)
**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64
**[Prerequisites]:**
- Have the Firefox Release 111 build installed and opened.
- Have set a different OS language than Firefox.
- Have the “nimbus.debug” pref set to true in the “about:config” page.
**[Steps to reproduce]:**
1. Force enroll in the Treatment B branch of the experiment using the following link: about:studies?optin_slug=device-migration-new-user-onboarding-pt-2&optin_branch=treatment-b&optin_collection=nimbus-preview
2. navigate to the "about:welcome" page and click the “Skip this step” button from the first screen.
3. Observe what happens.
**[Expected result]:**
- The “Choose Your Language” screen is displayed.
**[Actual result]:**
- The “Device Migration” screen is displayed.
**[Notes]:**
- Based on [Figma](https://www.figma.com/file/c83OEio9DhCQKuabx2tIEl/NUO-Experiments-2023?node-id=2%3A376&t=UrSiCJKtdKPdsyMm-0), the “Device Migration” screen should be displayed after the “Choose Your Language” one.
- This issue is also reproducible in the Treatment A branch of the experiment.
- It is also reproducible when naturally enrolling in the experiment.
- Attached is a screen recording of the issue.
|
|
1,822,466 | 16,327,123 |
Created attachment 9323158
err.jpg
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0
Steps to reproduce:
We have the following env:
selenium java 4.7.2
geckodriver 0.32.1
firefox 110.0
After updating firefox from 109.0.1 to 110.0 we have a problem with ExpectedConditions.stalenessOf(element).
Example of code:
WebElement html = seleniumSettings.getWebDriver().findElement(By.tagName("html"));
seleniumSettings.getWebDriver().get("about:blank");
seleniumSettings.getWebDriver().get(page);
new WebDriverWait(seleniumSettings.getWebDriver(), seleniumSettings.getDefaultTimeout())
.withMessage("Element exist.")
.until(ExpectedConditions.stalenessOf(html));
Actual results:
Test break on WebDriverWait with the following error - Caused by: org.openqa.selenium.NoSuchElementException: Unknown element with id...
Expected results:
WebDriverWait should execute correctly
|
|
1,822,712 | 16,328,517 |
Steps to reproduce:
On git commit 8ed22fcd56968c95a73a6c82b42f732f01a4bdae the attached sample asserts in the js-shell when invoked via `obj-x86_64-pc-linux-gnu/dist/bin/js --fuzzing-safe crash.js`. The issue doesn't appear to be a recent regressor, a version from end of 2021 is affected as well. I'm not sure whether this is s-s, on release builds there is no segfault/exception.
```
#0 js::Proxy::getOwnPropertyDescriptor (cx=cx@entry=0x7ffff7430100, proxy=proxy@entry=..., id=id@entry=..., desc=desc@entry=...)
at js/src/proxy/Proxy.cpp:190
#1 0x00005555571c4e36 in js::GetOwnPropertyDescriptor (cx=cx@entry=0x7ffff7430100, obj=obj@entry=..., id=id@entry=...,
desc=desc@entry=...) at js/src/vm/JSObject.cpp:2023
#2 0x00005555576ebfcc in js::ForwardingProxyHandler::getOwnPropertyDescriptor (this=<optimized out>, cx=0x7ffff7430100,
proxy=..., id=..., desc=...) at js/src/proxy/Wrapper.cpp:56
#3 0x00005555576bea32 in js::BaseProxyHandler::set (this=0x555558922700 <js::Wrapper::singletonWithPrototype>,
cx=0x7ffff7430100, proxy=..., id=..., v=..., receiver=..., result=...)
at js/src/proxy/BaseProxyHandler.cpp:148
#4 0x00005555576d8d70 in js::Proxy::setInternal (cx=0x7ffff7430100, proxy=proxy@entry=..., id=id@entry=..., v=v@entry=...,
receiver=receiver@entry=..., result=...) at js/src/proxy/Proxy.cpp:561
#5 0x00005555576d89fa in js::Proxy::set (cx=0x7ffff79f8a00 <_IO_stdfile_2_lock>, proxy=..., id=..., v=..., receiver_=...,
result=...) at js/src/proxy/Proxy.cpp:572
#6 0x0000555556eb6150 in SetObjectElementOperation (cx=0x7ffff7430100, value=..., receiver=..., obj=..., id=...,
strict=<optimized out>) at js/src/vm/Interpreter.cpp:1854
#7 Interpret (cx=cx@entry=0x7ffff7430100, state=...) at js/src/vm/Interpreter.cpp:3207
#8 0x0000555556eaa015 in js::RunScript (cx=cx@entry=0x7ffff7430100, state=...)
at js/src/vm/Interpreter.cpp:431
#9 0x0000555556ec7762 in js::ExecuteKernel (cx=cx@entry=0x7ffff7430100, script=script@entry=...,
envChainArg=envChainArg@entry=..., evalInFrame=evalInFrame@entry=..., result=...)
at js/src/vm/Interpreter.cpp:818
#10 0x0000555556ec7e11 in js::Execute (cx=cx@entry=0x7ffff7430100, script=script@entry=..., envChain=..., rval=rval@entry=...)
at js/src/vm/Interpreter.cpp:850
#11 0x0000555557075b26 in ExecuteScript (cx=cx@entry=0x7ffff7430100, envChain=..., script=..., rval=rval@entry=...)
hax/gecko-fuzzilli/js/src/vm/CompilationAndEvaluation.cpp:472
#12 0x0000555557075e00 in JS_ExecuteScript (cx=cx@entry=0x7ffff7430100, scriptArg=scriptArg@entry=...)
at js/src/vm/CompilationAndEvaluation.cpp:496
#13 0x0000555556de02b0 in RunFile (cx=0x7ffff7430100, filename=0x7fffffffea5f "crash_2023_03_15_2.js", file=<optimized out>, compileMethod=CompileU
tf8::DontInflate,
compileOnly=false, fullParse=<optimized out>) at js/src/shell/js.cpp:1098
#14 0x0000555556ddf755 in Process (cx=cx@entry=0x7ffff7430100, filename=0x1 <error: Cannot access memory at address 0x1>, forceTTY=false, kind=kind
@entry=FileScript)
at js/src/shell/js.cpp:1697
#15 0x0000555556da12ef in ProcessArgs (cx=0x7ffff7430100, op=0x7fffffffe438) at js/src/shell/js.cpp:10577
#16 Shell (cx=0x7ffff7430100, op=op@entry=0x7fffffffe438) at js/src/shell/js.cpp:10801
#17 0x0000555556d9add7 in main (argc=<optimized out>, argv=<optimized out>) at js/src/shell/js.cpp:11233
```
```
const o0 = {};
const v2 = new Proxy(o0, o0);
const v8 = this.wrapWithProto(v2, {});
function f9(a10) {
return v8;
}
class C11 extends f9 {
#b;
static {
const v13 = new this();
v8.#b = 0;
}
}
```
|
|
1,822,754 | 16,328,805 |
## Overview
Target: SpiderMonkey ARM64 latest of 2023/3/15 - commit `5860c73273ab6a71408c8b595db695c149155dff`
Wrong lowering of UDiv MIR in ARM64 Ion compiler results in wrong optimization result.
## Proof of Concept Code
```wat
(module
(type (;0;) (func (param i32) (result i32)))
(import "mem" "mem" (memory (;0;) 1024))
(func (;0;) (type 0) (param i32) (result i32)
local.get 0
i32.const -1 ;; any value of -2^n will work
i32.div_u)
(export "main" (func 0)))
```
```js
// [('i32.div_u', 'i32', ('i32.const',))]
// const code = new Uint8Array([...]);
const code = new Uint8Array([0,97,115,109,1,0,0,0,1,6,1,96,1,127,1,127,2,13,1,3,109,101,109,3,109,101,109,2,0,128,8,3,2,1,0,7,8,1,4,109,97,105,110,0,0,10,9,1,7,0,32,0,65,127,110,11,11,1,0]);
let memory = new WebAssembly.Memory({
initial: 1024
})
const module = new WebAssembly.Module(code);
const instance = new WebAssembly.Instance(module, {
mem: {
mem: memory
}
});
// print(instance.exports.main(0, 1, 2))
print(instance.exports.main(-2)); // any value would work
```
```
$ builds/arm64_debug/dist/bin/js --wasm-compiler=baseline poc.js
0
$ builds/arm64_debug/dist/bin/js --wasm-compiler=ion poc.js
-2
```
## Root Cause Analysis
When lowering `UDiv`, shift value is calculated with the absolute value of the divisor. When the divisor is the negation of an integer which is power of two, `LDivPowTwoI` LIR will be generated with `shift=0`, resulting in an identity (`x -> x`) or right shift operation, which is wrong.
```c++
// src/jit/arm64/Lowering-arm64.cpp:574
void LIRGeneratorARM64::lowerUDiv(MDiv* div) {
LAllocation lhs = useRegister(div->lhs());
if (div->rhs()->isConstant()) {
int32_t rhs = div->rhs()->toConstant()->toInt32();
int32_t shift = mozilla::FloorLog2(mozilla::Abs(rhs)); // [*] Bug
if (rhs != 0 && uint32_t(1) << shift == mozilla::Abs(rhs)) { // [1] rhs=0xffffffff, shift=0, abs=1
LDivPowTwoI* lir = new (alloc()) LDivPowTwoI(lhs, shift, false); // [2] shift=0, negativeDivisor=false
if (div->fallible()) {
assignSnapshot(lir, div->bailoutKind());
}
define(lir, div);
return;
}
(...)
}
(...)
}
```
We are handling the case where `rhs` is constant. Therefore, `rhs` is considered as a signed integer, and shift value is calculated with absolute value of `rhs`. ([*] Bug part) To explain more in detail, the compiler enters the condition [1] when `rhs` is `-2^n`, and in [2], `LDivPowTwoI` LIR will be generated. The LIR will be later handled with an identity or a right shift operation in the code generation. (See `src/jit/arm64/CodeGenerator-arm64.cpp:515` for more detail)
If we think of an example where `rhs=-1`, `abs(rhs)=1`, so `shift=0`. `shift=0` will be later handled as an identity operation in the code generation.
The expected behavior is to consider `rhs` as an **unsigned** value. Then, the code will work as intended.
You can refer to the following result codes below:
- arm64 baseline
```
0xbe069c8b000 d10043ff sub sp, sp, #0x10 (16)
0xbe069c8b004 f90007fe str x30, [sp, #8]
0xbe069c8b008 f90003fd str x29, [sp]
0xbe069c8b00c 910003fd mov x29, sp
0xbe069c8b010 71008d5f cmp w10, #0x23 (35)
0xbe069c8b014 540000e0 b.eq #+0x1c (addr 0xbe069c8b030)
0xbe069c8b018 d4a00000 unimplemented (Exception)
0xbe069c8b01c d503201f nop
0xbe069c8b020 d10043ff sub sp, sp, #0x10 (16)
0xbe069c8b024 f90007fe str x30, [sp, #8]
0xbe069c8b028 f90003fd str x29, [sp]
0xbe069c8b02c 910003fd mov x29, sp
0xbe069c8b030 910003fc mov x28, sp
0xbe069c8b034 d2800a10 mov x16, #0x50
0xbe069c8b038 f2a00010 movk x16, #0x0, lsl #16
0xbe069c8b03c cb3063e8 sub x8, sp, x16
0xbe069c8b040 f9401ef0 ldr x16, [x23, #56]
0xbe069c8b044 eb08021f cmp x16, x8
0xbe069c8b048 54000043 b.lo #+0x8 (addr 0xbe069c8b050)
0xbe069c8b04c d4a00000 unimplemented (Exception)
0xbe069c8b050 d10143ff sub sp, sp, #0x50 (80)
0xbe069c8b054 b9004fe0 str w0, [sp, #76]
0xbe069c8b058 f90023f7 str x23, [sp, #64]
0xbe069c8b05c 12800000 mov w0, #0xffffffff
0xbe069c8b060 b9404fe1 ldr w1, [sp, #76]
0xbe069c8b064 1ac00821 udiv w1, w1, w0
0xbe069c8b068 2a0103e0 mov w0, w1
0xbe069c8b06c 14000002 b #+0x8 (addr 0xbe069c8b074)
0xbe069c8b070 d4200000 brk #0x0
0xbe069c8b074 910143ff add sp, sp, #0x50 (80)
0xbe069c8b078 f94003fd ldr x29, [sp]
0xbe069c8b07c f94007fe ldr x30, [sp, #8]
0xbe069c8b080 910043ff add sp, sp, #0x10 (16)
0xbe069c8b084 910003fc mov x28, sp
0xbe069c8b088 d65f03c0 ret
```
- arm64 ion
```
0x2ed13ecb6000 d10043ff sub sp, sp, #0x10 (16)
0x2ed13ecb6004 f90007fe str x30, [sp, #8]
0x2ed13ecb6008 f90003fd str x29, [sp]
0x2ed13ecb600c 910003fd mov x29, sp
0x2ed13ecb6010 71008d5f cmp w10, #0x23 (35)
0x2ed13ecb6014 540000e0 b.eq #+0x1c (addr 0x2ed13ecb6030)
0x2ed13ecb6018 d4a00000 unimplemented (Exception)
0x2ed13ecb601c d503201f nop
0x2ed13ecb6020 d10043ff sub sp, sp, #0x10 (16)
0x2ed13ecb6024 f90007fe str x30, [sp, #8]
0x2ed13ecb6028 f90003fd str x29, [sp]
0x2ed13ecb602c 910003fd mov x29, sp
0x2ed13ecb6030 910003fc mov x28, sp
0x2ed13ecb6034 2a0003e2 mov w2, w0
0x2ed13ecb6038 2a0203e1 mov w1, w2
0x2ed13ecb603c 2a0103e0 mov w0, w1 ;; [!] Bug here: function returns as arg1
0x2ed13ecb6040 f94003fd ldr x29, [sp]
0x2ed13ecb6044 f94007fe ldr x30, [sp, #8]
0x2ed13ecb6048 910043ff add sp, sp, #0x10 (16)
0x2ed13ecb604c 910003fc mov x28, sp
0x2ed13ecb6050 d65f03c0 ret
```
## Suggested Patch
`rhs` must be considered as an **unsigned** value when lowering UDiv MIR to LIR. The following two lines of code would be fixed.
```diff
// src/jit/arm64/Lowering-arm64.cpp:574
void LIRGeneratorARM64::lowerUDiv(MDiv* div) {
LAllocation lhs = useRegister(div->lhs());
if (div->rhs()->isConstant()) {
- int32_t rhs = div->rhs()->toConstant()->toInt32();
- int32_t shift = mozilla::FloorLog2(mozilla::Abs(rhs));
+ uint32_t rhs = div->rhs()->toConstant()->toUint32();
+ int32_t shift = mozilla::FloorLog2(rhs);
if (rhs != 0 && uint32_t(1) << shift == mozilla::Abs(rhs)) {
LDivPowTwoI* lir = new (alloc()) LDivPowTwoI(lhs, shift, false);
if (div->fallible()) {
assignSnapshot(lir, div->bailoutKind());
}
define(lir, div);
return;
}
(...)
}
(...)
}
```
|
|
1,822,995 | 16,330,326 |
Steps to reproduce:
On git commit 585fe519f14ca8f241370573a902fc6d53cf8ac6 the attached sample asserts in the js-shell when invoked as `obj-x86_64-pc-linux-gnu/dist/bin/js --baseline-warmup-threshold=10 --fuzzing-safe --ion-warmup-threshold=100 crash.js`
Bisecting the issue points to commit cc0a423c96d6ffc5d0d6ea1fabdb0f62b7d534bf related to bug 1816890.
Might not actually be s-s, just flagging as a precaution.
```
function f0(a1, a2, a3) {
try {
a2(a1, a2);
} catch(e5) {
const v7 = new Set();
const v8 = v7.add();
function f9(a10, a11) {
a11.sameZoneAs = v8;
return this;
}
f9(v8, f9).newGlobal(f9).blackRoot(a1);
}
return a2;
}
const v17 = this.wrapWithProto(f0, this);
const v19 = Proxy.revocable(f0, v17);
v19.proxy(v17, v17);
v19.proxy(v19, v17);
gc();
```
```
#0 0x00005555573d321b in js::GCPtr<js::ArrayObject*>::~GCPtr (this=0x7ffff4c26a18)
at js/src/gc/Barrier.h:616
#1 0x00005555573d318d in ShellCompartmentPrivate::~ShellCompartmentPrivate (
this=0x7ffff4c26a10) at js/src/shell/js.cpp:582
#2 0x000055555737fcb0 in js_delete<ShellCompartmentPrivate> (p=0x7ffff4c26a10)
at obj-x86_64-pc-linux-gnu/dist/include/js/Utility.h:555
#3 0x000055555736ffb4 in DestroyShellCompartmentPrivate (gcx=0x7ffff7423740,
compartment=0x7ffff74033a0) at js/src/shell/js.cpp:4156
#4 0x0000555558421769 in JS::Compartment::destroy (this=0x7ffff74033a0,
gcx=0x7ffff7423740) at js/src/gc/GC.cpp:2125
#5 0x0000555558421b41 in JS::Zone::sweepCompartments (this=0x7ffff74fe000,
gcx=0x7ffff7423740, keepAtleastOne=false, destroyingRuntime=false)
at js/src/gc/GC.cpp:2176
#6 0x0000555558422409 in js::gc::GCRuntime::sweepZones (this=0x7ffff7423728,
gcx=0x7ffff7423740, destroyingRuntime=false)
at js/src/gc/GC.cpp:2243
#7 0x000055555842a195 in js::gc::GCRuntime::incrementalSlice (this=0x7ffff7423728,
budget=..., reason=JS::GCReason::API, budgetWasIncreased=false)
at js/src/gc/GC.cpp:3724
#8 0x000055555842c435 in js::gc::GCRuntime::gcCycle (this=0x7ffff7423728,
nonincrementalByAPI=true, budgetArg=..., reason=JS::GCReason::API)
at js/src/gc/GC.cpp:4212
#9 0x000055555842d3b2 in js::gc::GCRuntime::collect (this=0x7ffff7423728,
#10 0x000055555840c402 in js::gc::GCRuntime::gc (this=0x7ffff7423728, options=JS::GCOptions::Normal,
reason=JS::GCReason::API) at js/src/gc/GC.cpp:4477
#11 0x00005555584803de in JS::NonIncrementalGC (cx=0x7ffff7430100, options=JS::GCOptions::Normal,
reason=JS::GCReason::API) at js/src/gc/GCAPI.cpp:297
#12 0x0000555557e521a0 in GC (cx=0x7ffff7430100, argc=0, vp=0x7ffff4cf3090)
at js/src/builtin/TestingFunctions.cpp:706
#13 0x000055555757affe in CallJSNative (cx=0x7ffff7430100,
native=0x555557e51cd0 <GC(JSContext*, unsigned int, JS::Value*)>, reason=js::CallReason::Call, args=...)
at js/src/vm/Interpreter.cpp:459
#14 0x000055555757a7dd in js::InternalCallOrConstruct (cx=0x7ffff7430100, args=..., construct=js::NO_CONSTRUCT,
reason=js::CallReason::Call) at js/src/vm/Interpreter.cpp:553
#15 0x000055555757bbd1 in InternalCall (cx=0x7ffff7430100, args=..., reason=js::CallReason::Call)
at js/src/vm/Interpreter.cpp:620
#16 0x000055555757b995 in js::CallFromStack (cx=0x7ffff7430100, args=..., reason=js::CallReason::Call)
at js/src/vm/Interpreter.cpp:625
#17 0x000055555756c664 in Interpret (cx=0x7ffff7430100, state=...)
at js/src/vm/Interpreter.cpp:3368
#18 0x000055555755e740 in js::RunScript (cx=0x7ffff7430100, state=...)
at js/src/vm/Interpreter.cpp:431
#19 0x000055555757d78c in js::ExecuteKernel (cx=0x7ffff7430100, script=..., envChainArg=..., evalInFrame=..., result=...)
at js/src/vm/Interpreter.cpp:818
#20 0x000055555757e035 in js::Execute (cx=0x7ffff7430100, script=..., envChain=..., rval=...)
at js/src/vm/Interpreter.cpp:850
#21 0x00005555577bf876 in ExecuteScript (cx=0x7ffff7430100, envChain=..., script=..., rval=...)
at js/src/vm/CompilationAndEvaluation.cpp:472
#22 0x00005555577bf9cd in JS_ExecuteScript (cx=0x7ffff7430100, scriptArg=...)
at js/src/vm/CompilationAndEvaluation.cpp:496
#23 0x00005555573a924f in RunFile (cx=0x7ffff7430100, filename=0x7fffffffea62 "crash_2023_03_16.js", file=0x7ffff7769020,
compileMethod=CompileUtf8::DontInflate, compileOnly=false, fullParse=false)
at js/src/shell/js.cpp:1098
#24 0x00005555573a8af5 in Process (cx=0x7ffff7430100, filename=0x7fffffffea62 "crash_2023_03_16.js", forceTTY=false,
kind=FileScript) at js/src/shell/js.cpp:1697
#25 0x00005555573829e8 in ProcessArgs (cx=0x7ffff7430100, op=0x7fffffffe420)
at js/src/shell/js.cpp:10584
#26 0x0000555557371983 in Shell (cx=0x7ffff7430100, op=0x7fffffffe420)
at js/src/shell/js.cpp:10808
#27 0x000055555736ca46 in main (argc=5, argv=0x7fffffffe688) at js/src/shell/js.cpp:11240
```
|
|
1,756,163 | 15,782,512 |
Created attachment 9264548
learn more button cannot be focused with keyboard naviagtion.mov
[Notes]:
- The issue seems to be intermittent since there are cases when the "dismiss" button can be focused with keyboard navigation and the panel is not dismissed.
[Affected Versions]:
- Nightly 99.0a1 (Build ID: 20220218090822);
[Affected Platforms]:
- Windows 10 x64
- Ubuntu 20.04 x64
- macOS 10.15.7
[Prerequisites]:
- Have a new Firefox profile with the following prefs set:
- Have the "browser.search.region" pref set to "US".
- Have the "browser.urlbar.bestMatch.enabled" set to "true".
[Steps to reproduce]:
1. Open the Firefox browser with the profile from prerequisites.
2. Open a new tab.
3. Type "amazon" in the Awesomebar.
4. Press the "Tab" key until the "dismiss" button is focused.
5. Press the "Tab" key.
6. Observe the behavior.
[Expected result]:
- The "Dismiss" button is correctly focused.
[Actual result]:
- The search panel is dismissed and the "Save to Pocket" toolbar button is focused.
[Additional Notes]:
- Attached is a screen recording of the issue.
|
|
1,756,176 | 15,782,602 |
**[Affected versions]:**
- Firefox 98.0b6 Build ID: 20220217185748
**[Affected Platforms]:**
- Windows 10 x64
- MacOS 11.6
- Ubuntu 20.04
**[Prerequisites]:**
- Have the Firefox browser en-US build installed/extracted.
- Have the “browser.search.region” pref set to the “US” value.
- Have the [user.js](https://drive.google.com/file/d/1cidGYhkKfCzD6IGak4yYfMzW_nMZQFld/view) file copied to your PC.
**[Steps to reproduce]:**
1. Create a new Firefox profile but do not open it.
2. Go to the recently created profile folder and paste the "user.js" from the prerequisites.
3. Open the Firefox profile.
4. Open a new "Private Window".
5. Click the "Stay private with Mozilla VPN" button.
6. Observe the parameters from the opened URL.
**[Expected result]:**
- The “https://www.mozilla.org/products/vpn?utm_medium=firefox-desktop&utm_source=privatebrowser&utm_campaign=private-browsing-vpn-link&utm_content=experiment-na” link is opened.
**[Actual result]:**
- The “https://www.mozilla.org/en-US/products/vpn/?utm_source=firefox-browser&utm_campaign=private-browsing-vpn-link&utm_medium=firefox-beta-browser” link is opened.
[Notes]:
- Based on the [Mana page](https://mana.mozilla.org/wiki/display/FPS/%5BCross+Promotion%5D+VPN+on+PBM+-+Fx98+beta), the link should be updated with the correct parameters.
|
|
1,756,755 | 15,788,306 |
Reported on Matrix. After bug 1748749, [getActionNameCB now calls ActionDescriptionAt instead of ActionNameAt](https://searchfox.org/mozilla-central/rev/9b0bdcc37419e6765223358a31a4a54d62e1cd97/accessible/atk/nsMaiInterfaceAction.cpp#54). This results in the localised action being returned instead of the unlocalised action, which breaks stuff related to clickables in Orca for non-English users.
|
|
1,757,138 | 15,791,098 |
Steps to reproduce:
1. Navigate to http://radio.indymedia.org in Android Firefox 97.2.0 (Build #2015863827)
2. Navigate to https://radio.indymedia.org which has HSTS header (Strict-Transport-Security: max-age=63072000; includeSubDomains; preload)
3. At this point, HSTS appears to work (HTTP request directs to HTTPS)
4. Use other apps for a while or reboot phone
5. Return to Firefox and visit http://radio.indymedia.org and it loads; however the browser should have redirected me to https://radio.indymedia.org
Actual results:
HTTP website loaded again despite HSTS policy
Expected results:
Automatic redirect to HTTPS
|
|
1,757,162 | 15,791,357 |
Steps to reproduce:
Specified a default in the constructor like so:
class Button {
#targetDefaults = 'default'
constructor(element, target = this.#targetDefaults) {
this.element = element
this.target = target
}
}
new Button(document.getElementById('butt'))
Code on CodePen: https://codepen.io/Moiety/pen/abVazdE/0090d1492e43588ded46c4a432f8c0bd?editors=1111
This code works in Chrome and Safari, but not Firefox.
Actual results:
Firefox throws an error: “Uncaught TypeError: can't access private field or method: object is not the right class”
Expected results:
this.target should be set to 'default' (via #targetDefaults)
|
|
1,757,418 | 15,794,938 |
**[Affected Versions]:**
- Firefox Beta 98.0b9 (Build ID: 20220224185616) - en-US
- Firefox Release 96.0.3 (Build ID: 20220126154723) - en-GB
- Firefox Release 94.0.2 (Build ID: 20211119140621) - en-CA
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15.7
**[Prerequisites]:**
- Have Firefox Release 96.0.3 installed on your computer.
- No "Pin to taskbar" spotlight was previously displayed.
- Have a Firefox profile younger than 28 days.
- Have at least a website accessed in the last 6 days.
- Firefox is not pinned to the taskbar.
- Have the `nimbus.debug` pref set to `true`.
- The Remote Settings [add-on](https://github.com/mozilla-extensions/remote-settings-devtools/releases) is installed and a Poll server was actioned using Stage-Preview.
**[Steps to reproduce]:**
1. Open Firefox Release 96.0.3 and force an enrollment into a previous ECO [experiment](about:studies?optin_slug=mcoman-test-eco-spotlight-3&optin_branch=treatment-a&optin_collection=nimbus-preview).
2. Restart the browser and dismiss the experiment’s spotlight.
3. Remove the experiment from the `about:studies` page.
4. Replace the existing "times.json" file in the Profile Folder from the `about:support` page with this [file](https://drive.google.com/file/d/1b2B2seAP9ybsm9wS5RCvCVUP-6ujNlXR/view?usp=sharing).
5. Restart the browser (several times if necessary) and observe the behavior.
**[Expected results]:**
- The “Pin to taskbar” modal is not displayed.
**[Actual results]:**
- The “Pin to taskbar” modal is displayed.
**[Notes]:**
- The issue is also reproducible using the steps described in this [comment](https://mozilla-hub.atlassian.net/browse/QA-1395?focusedCommentId=516985).
- If the user remains enrolled in the experiment, the "Pin to taskbar" spotlight is not displayed.
- [Here](https://drive.google.com/file/d/1EhLjEPQbu7jE9E0wgUHN2aRJKk8G1Q7Y/view?usp=sharing) is a screen recording of the issue.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.