Bug ID
int64 961
1.91M
| Comment ID
int64 3.98k
17.1M
| Author
stringlengths 8
48
| Comment Text
stringlengths 1
64.3k
⌀ |
|---|---|---|---|
1,661,975 | 15,012,423 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:82.0) Gecko/20100101 Firefox/82.0
Steps to reproduce:
Selected a portion of a webpage
used File->print
Actual results:
I can print the whole thing or a specific page however, I cannot print the selected portion of a webpage.
This works on Firefox 80 however, it fails on Firefox 82 (Currently my Firefox nightly is at build 20200830093945). System is Ubuntu 16.04. It is also failing on Ubuntu 18.04
Expected results:
Somewhere in the print dialog, if necessary, within the 'print using the system dialog', it should be possible to print just a selection. Reference Firefox 80, which behaves correctly.
|
|
1,662,098 | 15,014,268 |
Created attachment 9173031
website to about page - not trigger the default notification .gif
[Affected versions]:
- Nightly 82.0a1 (Build ID: 20200831091558);
- Beta 81.0b4 (Build ID: 20200829200810);
[Affected Platforms]:
- All Windows;
- All macOS;
- All Linux;
[Prerequisites]:
- Have a new clean Firefox Profile.
- The Firefox browser is NOT set as default.
- The "Restore previous session" feature is enabled.
[Steps to reproduce]:
1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to any website and close the other open tabs.
3. Close the browser.
4. Start the browser.
5. Click the "Home" button.
6. Observe the behavior.
[Expected result]:
- The "about:home" page is loaded and the "Set browser as default" notification bar is displayed.
[Actual result]:
- The "about:home" page is loaded and the "Set browser as default" notification bar is NOT displayed
[Notes]:
- The issue is also reproducible if you manually navigate from a website to "about:newtab", "about:home", or "about:welcome" page. However, if you focus the website then switch back to the "about*" page, the notification will be triggered.
- A similar behavior can be observed in the following scenario: If a new tab is opened but not focused, after the browser is restarted and the opened new tab is focused, the notification is not triggered (see this [screen recording](https://drive.google.com/file/d/1K-KPllaJSxyQW_0htou8-Pe0FtycBdtw/view?usp=sharing)).
|
|
1,668,876 | 15,065,473 |
To reproduce use a Windows ASan build with `MOZ_DISABLE_CONTENT_SANDBOX=1`. Open a tab, wait for content to load and then close the tab.
This is marked as a [fuzzblocker](https://firefox-source-docs.mozilla.org/tools/fuzzing/index.html#fuzz-blockers) because it blocks fuzzing on Windows.
```
==8484==ERROR: AddressSanitizer: heap-use-after-free on address 0x1238349e68d8 at pc 0x7ff60d8f19f4 bp 0x00543b5ff1a0 sp 0x00543b5ff1e0
READ of size 4 at 0x1238349e68d8 thread T1
#0 0x7ff60d8f19f3 in sandbox::BrokerServicesBase::TargetEventsThread z:\build\build\src\security\sandbox\chromium\sandbox\win\src\broker_services.cc:373
#1 0x7fffda90e448 in __asan::AsanThread::ThreadStart Z:\task_1600842074\fetches\llvm-project\llvm\projects\compiler-rt\lib\asan\asan_thread.cpp:262
#2 0x7ff8091f7bd3 in BaseThreadInitThunk+0x13 (C:\WINDOWS\System32\KERNEL32.DLL+0x180017bd3)
#3 0x7fffe10e49e2 in patched_BaseThreadInitThunk z:\build\build\src\mozglue\dllservices\WindowsDllBlocklist.cpp:592
#4 0x7ff80a80ce50 in RtlUserThreadStart+0x20 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x18006ce50)
0x1238349e68d8 is located 8 bytes inside of 40-byte region [0x1238349e68d0,0x1238349e68f8)
freed by thread T1 here:
#0 0x7fffda91098f in operator delete Z:\task_1600842074\fetches\llvm-project\llvm\projects\compiler-rt\lib\asan\asan_new_delete.cpp:160
#1 0x7ff60d8f0760 in sandbox::BrokerServicesBase::TargetEventsThread z:\build\build\src\security\sandbox\chromium\sandbox\win\src\broker_services.cc:373
#2 0x7fffda90e448 in __asan::AsanThread::ThreadStart Z:\task_1600842074\fetches\llvm-project\llvm\projects\compiler-rt\lib\asan\asan_thread.cpp:262
#3 0x7ff8091f7bd3 in BaseThreadInitThunk+0x13 (C:\WINDOWS\System32\KERNEL32.DLL+0x180017bd3)
#4 0x7fffe10e49e2 in patched_BaseThreadInitThunk z:\build\build\src\mozglue\dllservices\WindowsDllBlocklist.cpp:592
#5 0x7ff80a80ce50 in RtlUserThreadStart+0x20 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x18006ce50)
previously allocated by thread T26 here:
#0 0x7fffda91008f in operator new Z:\task_1600842074\fetches\llvm-project\llvm\projects\compiler-rt\lib\asan\asan_new_delete.cpp:99
#1 0x7ff60d8f50c6 in sandbox::BrokerServicesBase::AddTargetPeerInternal z:\build\build\src\security\sandbox\chromium\sandbox\win\src\broker_services.cc:702
#2 0x7ff60d8f594a in sandbox::BrokerServicesBase::AddTargetPeer z:\build\build\src\security\sandbox\chromium\sandbox\win\src\broker_services.cc:717
#3 0x7fffc36c7248 in mozilla::SandboxBroker::AddTargetPeer z:\build\build\src\security\sandbox\win\src\sandboxbroker\sandboxBroker.cpp:1441
#4 0x7fffc4cc730b in mozilla::ipc::WindowsProcessLauncher::DoFinishLaunch z:\build\build\src\ipc\glue\GeckoChildProcessHost.cpp:1589
#5 0x7fffc4cc748f in mozilla::ipc::BaseProcessLauncher::FinishLaunch z:\build\build\src\ipc\glue\GeckoChildProcessHost.cpp:1602
#6 0x7fffc4cf3ba2 in mozilla::MozPromise<void *,mozilla::ipc::LaunchError,0>::ThenValue<`lambda at z:/build/build/src/ipc/glue/GeckoChildProcessHost.cpp:1018:7',`lambda at z:/build/build/src/ipc/glue/GeckoChildProcessHost.cpp:1022:7'>::DoResolveOrRejectInternal z:\build\workspace\obj-build\dist\include\mozilla\MozPromise.h:769
#7 0x7fffc36b8271 in mozilla::MozPromise<void *,mozilla::ipc::LaunchError,0>::ThenValueBase::ResolveOrRejectRunnable::Run z:\build\workspace\obj-build\dist\include\mozilla\MozPromise.h:410
#8 0x7fffc39b7366 in mozilla::TaskQueue::Runner::Run z:\build\build\src\xpcom\threads\TaskQueue.cpp:158
#9 0x7fffc39d42c4 in nsThread::ProcessNextEvent z:\build\build\src\xpcom\threads\nsThread.cpp:1234
#10 0x7fffc39e009c in NS_ProcessNextEvent z:\build\build\src\xpcom\threads\nsThreadUtils.cpp:513
#11 0x7fffc4d201de in mozilla::ipc::MessagePumpForNonMainThreads::Run z:\build\build\src\ipc\glue\MessagePump.cpp:302
#12 0x7fffc4c664a5 in MessageLoop::RunHandler z:\build\build\src\ipc\chromium\src\base\message_loop.cc:327
#13 0x7fffc4c66275 in MessageLoop::Run z:\build\build\src\ipc\chromium\src\base\message_loop.cc:309
#14 0x7fffc39cc61d in nsThread::ThreadFunc z:\build\build\src\xpcom\threads\nsThread.cpp:442
#15 0x7fffd92495ae in _PR_NativeRunThread z:\build\build\src\nsprpub\pr\src\threads\combined\pruthr.c:399
#16 0x7fffd92228fb in pr_root z:\build\build\src\nsprpub\pr\src\md\windows\w95thred.c:139
#17 0x7ff808400e81 in beginthreadex+0x141 (C:\WINDOWS\System32\ucrtbase.dll+0x180020e81)
#18 0x7fffda90e448 in __asan::AsanThread::ThreadStart Z:\task_1600842074\fetches\llvm-project\llvm\projects\compiler-rt\lib\asan\asan_thread.cpp:262
Thread T1 created by T0 here:
#0 0x7fffda90f907 in __asan_wrap_CreateThread Z:\task_1600842074\fetches\llvm-project\llvm\projects\compiler-rt\lib\asan\asan_win.cpp:146
#1 0x7ff60d8ef242 in sandbox::BrokerServicesBase::Init z:\build\build\src\security\sandbox\chromium\sandbox\win\src\broker_services.cc:170
#2 0x7ff60d96c01a in mozilla::sandboxing::InitializeBrokerServices z:\build\build\src\security\sandbox\win\SandboxInitialization.cpp:167
#3 0x7ff60d96befc in mozilla::sandboxing::GetInitializedBrokerServices z:\build\build\src\security\sandbox\win\SandboxInitialization.cpp:184
#4 0x7ff60d892005 in NS_internal_main z:\build\build\src\browser\app\nsBrowserApp.cpp:336
#5 0x7ff60d89148e in wmain z:\build\build\src\toolkit\xre\nsWindowsWMain.cpp:131
#6 0x7ff60d988837 in __scrt_common_main_seh f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:288
#7 0x7ff8091f7bd3 in BaseThreadInitThunk+0x13 (C:\WINDOWS\System32\KERNEL32.DLL+0x180017bd3)
#8 0x7ff80a80ce50 in RtlUserThreadStart+0x20 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x18006ce50)
Thread T26 created by T0 here:
#0 0x7fffda90f907 in __asan_wrap_CreateThread Z:\task_1600842074\fetches\llvm-project\llvm\projects\compiler-rt\lib\asan\asan_win.cpp:146
#1 0x7ff808400d96 in beginthreadex+0x56 (C:\WINDOWS\System32\ucrtbase.dll+0x180020d96)
#2 0x7fffd922272d in _PR_MD_CREATE_THREAD z:\build\build\src\nsprpub\pr\src\md\windows\w95thred.c:153
#3 0x7fffd924a40c in _PR_NativeCreateThread z:\build\build\src\nsprpub\pr\src\threads\combined\pruthr.c:1058
#4 0x7fffd924ad73 in _PR_CreateThread z:\build\build\src\nsprpub\pr\src\threads\combined\pruthr.c:1184
#5 0x7fffd9240d2f in PR_CreateThread z:\build\build\src\nsprpub\pr\src\threads\combined\pruthr.c:1404
#6 0x7fffc39cf269 in nsThread::Init z:\build\build\src\xpcom\threads\nsThread.cpp:659
#7 0x7fffc39dec36 in nsThreadManager::NewNamedThread z:\build\build\src\xpcom\threads\nsThreadManager.cpp:628
#8 0x7fffc39e8d8c in NS_NewNamedThread z:\build\build\src\xpcom\threads\nsThreadUtils.cpp:161
#9 0x7fffc39e3172 in NS_NewNamedThread z:\build\build\src\xpcom\threads\nsThreadUtils.cpp:152
#10 0x7fffc4cc056c in mozilla::ipc::GetIPCLauncher z:\build\build\src\ipc\glue\GeckoChildProcessHost.cpp:927
#11 0x7fffc4ce8f4a in mozilla::ipc::BaseProcessLauncher::BaseProcessLauncher z:\build\build\src\ipc\glue\GeckoChildProcessHost.cpp:150
#12 0x7fffc4cbc726 in mozilla::ipc::GeckoChildProcessHost::AsyncLaunch z:\build\build\src\ipc\glue\GeckoChildProcessHost.cpp:692
#13 0x7fffc4cbf670 in mozilla::ipc::GeckoChildProcessHost::LaunchAndWaitForProcessHandle z:\build\build\src\ipc\glue\GeckoChildProcessHost.cpp:809
#14 0x7fffc4a5e581 in mozilla::net::SocketProcessHost::Launch z:\build\build\src\netwerk\ipc\SocketProcessHost.cpp:76
#15 0x7fffc3d07798 in mozilla::net::nsIOService::LaunchSocketProcess z:\build\build\src\netwerk\base\nsIOService.cpp:542
#16 0x7fffc45b62a1 in mozilla::net::nsHttpHandler::Init z:\build\build\src\netwerk\protocol\http\nsHttpHandler.cpp:470
#17 0x7fffc45b2dc5 in mozilla::net::nsHttpHandler::GetInstance z:\build\build\src\netwerk\protocol\http\nsHttpHandler.cpp:179
#18 0x7fffc4c29a71 in mozCreateComponent<mozilla::net::nsHttpHandler> z:\build\build\src\netwerk\build\nsNetModule.cpp:61
#19 0x7fffc393d0b4 in mozilla::xpcom::CreateInstanceImpl z:\build\workspace\obj-build\xpcom\components\StaticComponents.cpp:11914
#20 0x7fffc397efd2 in nsComponentManagerImpl::GetServiceLocked z:\build\build\src\xpcom\components\nsComponentManager.cpp:1330
#21 0x7fffc3981887 in nsComponentManagerImpl::GetServiceByContractID z:\build\build\src\xpcom\components\nsComponentManager.cpp:1517
#22 0x7fffc3988747 in nsGetServiceByContractIDWithError::operator() z:\build\build\src\xpcom\components\nsComponentManagerUtils.cpp:253
#23 0x7fffc3797434 in nsCOMPtr_base::assign_from_gs_contractid_with_error z:\build\build\src\xpcom\base\nsCOMPtr.cpp:91
#24 0x7fffc75778e5 in mozilla::dom::Navigator::GetAppVersion z:\build\build\src\dom\base\Navigator.cpp:1909
#25 0x7fffcc3850ab in mozilla::dom::workerinternals::RuntimeService::RegisterWorker z:\build\build\src\dom\workers\RuntimeService.cpp:1195
#26 0x7fffcc3ecda1 in mozilla::dom::WorkerPrivate::Constructor z:\build\build\src\dom\workers\WorkerPrivate.cpp:2420
#27 0x7fffcc37b06b in mozilla::dom::ChromeWorker::Constructor z:\build\build\src\dom\workers\ChromeWorker.cpp:22
#28 0x7fffc90cadfe in mozilla::dom::ChromeWorker_Binding::_constructor z:\build\workspace\obj-build\dom\bindings\WorkerBinding.cpp:287
#29 0x7fffd0f5ed9c in InternalConstruct z:\build\build\src\js\src\vm\Interpreter.cpp:728
#30 0x7fffd0f417f8 in Interpret z:\build\build\src\js\src\vm\Interpreter.cpp:3327
#31 0x7fffd0f26b0a in js::RunScript z:\build\build\src\js\src\vm\Interpreter.cpp:469
#32 0x7fffd0f5b26d in js::InternalCallOrConstruct z:\build\build\src\js\src\vm\Interpreter.cpp:637
#33 0x7fffd0f5dd17 in js::Call z:\build\build\src\js\src\vm\Interpreter.cpp:682
#34 0x7fffd0f605bf in js::CallGetter z:\build\build\src\js\src\vm\Interpreter.cpp:806
#35 0x7fffd15e07e9 in js::NativeGetProperty z:\build\build\src\js\src\vm\NativeObject.cpp:2603
#36 0x7fffd0f68edf in js::GetProperty z:\build\build\src\js\src\vm\Interpreter.cpp:4727
#37 0x7fffd0f42185 in Interpret z:\build\build\src\js\src\vm\Interpreter.cpp:3017
#38 0x7fffd0f26b0a in js::RunScript z:\build\build\src\js\src\vm\Interpreter.cpp:469
#39 0x7fffd0f5b26d in js::InternalCallOrConstruct z:\build\build\src\js\src\vm\Interpreter.cpp:637
#40 0x7fffd0f5dd17 in js::Call z:\build\build\src\js\src\vm\Interpreter.cpp:682
#41 0x7fffd170020d in js::CallSelfHostedFunction z:\build\build\src\js\src\vm\SelfHosting.cpp:1694
#42 0x7fffd12144b6 in AsyncFunctionResume z:\build\build\src\js\src\vm\AsyncFunction.cpp:128
#43 0x7fffd13a29ea in PromiseReactionJob z:\build\build\src\js\src\builtin\Promise.cpp:1853
#44 0x7fffd0f5ac40 in js::InternalCallOrConstruct z:\build\build\src\js\src\vm\Interpreter.cpp:600
#45 0x7fffd0f5dd17 in js::Call z:\build\build\src\js\src\vm\Interpreter.cpp:682
#46 0x7fffd10fe601 in JS::Call z:\build\build\src\js\src\jsapi.cpp:2830
#47 0x7fffc8346020 in mozilla::dom::PromiseJobCallback::Call z:\build\workspace\obj-build\dom\bindings\PromiseBinding.cpp:30
#48 0x7fffc3781cde in mozilla::PromiseJobRunnable::Run z:\build\build\src\xpcom\base\CycleCollectedJSContext.cpp:211
#49 0x7fffc375a733 in mozilla::CycleCollectedJSContext::PerformMicroTaskCheckPoint z:\build\build\src\xpcom\base\CycleCollectedJSContext.cpp:646
#50 0x7fffc375b7fb in mozilla::CycleCollectedJSContext::BeforeProcessTask z:\build\build\src\xpcom\base\CycleCollectedJSContext.cpp:445
#51 0x7fffc5a64aa6 in XPCJSContext::BeforeProcessTask z:\build\build\src\js\xpconnect\src\XPCJSContext.cpp:1405
#52 0x7fffc39d2f5a in nsThread::ProcessNextEvent z:\build\build\src\xpcom\threads\nsThread.cpp:1114
#53 0x7fffc39e009c in NS_ProcessNextEvent z:\build\build\src\xpcom\threads\nsThreadUtils.cpp:513
#54 0x7fffc39df6a0 in nsThreadManager::SpinEventLoopUntilInternal z:\build\build\src\xpcom\threads\nsThreadManager.cpp:702
#55 0x7fffd41c23a1 in XPTC__InvokebyIndex+0x71 (C:\Users\User\workspace\browsers\m-c-20201002092536-fuzzing-asan-opt\xul.dll+0x190b723a1)
#56 0x7fffc5af40d3 in XPCWrappedNative::CallMethod z:\build\build\src\js\xpconnect\src\XPCWrappedNative.cpp:1142
#57 0x7fffc5afa883 in XPC_WN_CallMethod z:\build\build\src\js\xpconnect\src\XPCWrappedNativeJSOps.cpp:947
#58 0x7fffd0f5ac40 in js::InternalCallOrConstruct z:\build\build\src\js\src\vm\Interpreter.cpp:600
#59 0x7fffd0f4199a in Interpret z:\build\build\src\js\src\vm\Interpreter.cpp:3337
#60 0x7fffd0f26b0a in js::RunScript z:\build\build\src\js\src\vm\Interpreter.cpp:469
#61 0x7fffd0f5b26d in js::InternalCallOrConstruct z:\build\build\src\js\src\vm\Interpreter.cpp:637
#62 0x7fffd0f5dd17 in js::Call z:\build\build\src\js\src\vm\Interpreter.cpp:682
#63 0x7fffd14de70c in js::fun_apply z:\build\build\src\js\src\vm\JSFunction.cpp:1209
#64 0x7fffd0f5ac40 in js::InternalCallOrConstruct z:\build\build\src\js\src\vm\Interpreter.cpp:600
#65 0x7fffd0f4199a in Interpret z:\build\build\src\js\src\vm\Interpreter.cpp:3337
#66 0x7fffd0f26b0a in js::RunScript z:\build\build\src\js\src\vm\Interpreter.cpp:469
#67 0x7fffd0f5b26d in js::InternalCallOrConstruct z:\build\build\src\js\src\vm\Interpreter.cpp:637
#68 0x7fffd0f5dd17 in js::Call z:\build\build\src\js\src\vm\Interpreter.cpp:682
#69 0x7fffd10fc947 in JS_CallFunctionValue z:\build\build\src\js\src\jsapi.cpp:2767
#70 0x7fffc5ae3ad6 in nsXPCWrappedJS::CallMethod z:\build\build\src\js\xpconnect\src\XPCWrappedJSClass.cpp:970
#71 0x7fffc3a1d9a4 in PrepareAndDispatch z:\build\build\src\xpcom\reflect\xptcall\md\win32\xptcstubs_x86_64.cpp:168
#72 0x7fffd41c23f8 in SharedStub+0x48 (C:\Users\User\workspace\browsers\m-c-20201002092536-fuzzing-asan-opt\xul.dll+0x190b723f8)
#73 0x7fffd0cdfdbf in nsXREDirProvider::DoStartup z:\build\build\src\toolkit\xre\nsXREDirProvider.cpp:971
#74 0x7fffd0c6fb76 in XREMain::XRE_mainRun z:\build\build\src\toolkit\xre\nsAppRunner.cpp:4622
#75 0x7fffd0c76b2a in XREMain::XRE_main z:\build\build\src\toolkit\xre\nsAppRunner.cpp:5038
#76 0x7fffd0c779b8 in XRE_main z:\build\build\src\toolkit\xre\nsAppRunner.cpp:5094
#77 0x7ff60d8920e7 in NS_internal_main z:\build\build\src\browser\app\nsBrowserApp.cpp:336
#78 0x7ff60d89148e in wmain z:\build\build\src\toolkit\xre\nsWindowsWMain.cpp:131
#79 0x7ff60d988837 in __scrt_common_main_seh f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:288
#80 0x7ff8091f7bd3 in BaseThreadInitThunk+0x13 (C:\WINDOWS\System32\KERNEL32.DLL+0x180017bd3)
#81 0x7ff80a80ce50 in RtlUserThreadStart+0x20 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x18006ce50)
```
|
|
1,669,414 | 15,070,189 |
Created attachment 9179798
Pictures.zip
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0
Steps to reproduce:
Operating system: Windows 8.1 & 10
Firefox version: Firefox Nightly's 83.0a1 ( previously 81.0a1, 82.0a1 )
Software: Estonian ID-card software
Card reader: OMNIKEY 1021
1. Connect the ID-card to the card reader
2. Open Nightly's 81.0a1 or 82.0a1 try to authenticate to e-portal (for testing purposes https://test-eid.eesti.ee/ for example)
3. Authentication windows pops-up
4. Enter the PIN code in order to access service
5. Authentication is successful
6. Remove the card and try with another ID-card
7. Authentication Windows pops and after entering the PIN code the authentication method fails
Actual results:
Authentication process is unsuccessful with other smart card and overall process takes a lot of time.
Expected results:
Authentication process is successful, where the swapped Smart-card certificates are read out.
Summary:
Starting from 81.0a1 version, the authentication method has changed, where the certificates are being read for the Firefox web browser “OS Cert module”. For actual results, swapping the ID-cards should indicate the certificate change. At the moment authenticating with one card after another is impossible.
When trying with the new updated version Nightly 83.0a1, some changes have happened but overall usage of the ID-card is still interrupted when using multiple ID-cards. Some examples are in attachment.
If the “OS Client cert module” is removed, then the authentication process is successful as live version (for example 81.0.1). Though after re-launch of of Nightly 83.0a1, the module is back again.
-The more there are certificates in Windows Certificate Storage, the more it takes time to send the ID-card information to Nightly 83.0a1. If there are more than 10 certificates in storage and Nightly 83.0a1 is opened during the Smart card reading, then it takes ~55 seconds in order to even do anything in Firefox browser(not responding is displayed).Given that Windows Certificate Storage is emptied from other card certificates, the opening of Nightly 83.0a1 and reading information from the ID-card took ~8 seconds.
When speaking of process background: in case of authenticating in Firefox browser the Estonian eID software uses Firefox pkcs11 loader JavaScript component to load the One-Pin OpenSC PKCS%11 driver by the browser. My hunch is, that for some reason the "OS Client Cert Module" interrupts with other components.
Question: Is “OC cert module” option coming to live version as well? If yes, are there any expectations of solution to the above problems
|
|
1,669,483 | 15,070,663 |
Created attachment 9179894
what's_new.gif
*Affected versions*
* 83.0a1 (20201006041051)
* 82.0b7 (20201002191150)
* 81.0.1 (20200930150533)
*Affected platforms*
* Windows 10x64
* macOS 11
* Ubuntu 18.04
*Steps to reproduce*
1. Open Firefox and What’s New panel from the hamburger menu.
2. Use the tab key to navigate between options.
*Expected result*
* All options can be selected.
*Actual result*
* `Notify me about new features` cannot be selected using keyboard navigation.
*Regression range*
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a291f439f35a9a96948de0bc6acc07bbf3a8625c&tochange=63e434e9fec084b475d7b6e57ee07e881ab8ad46
*Notes*
* Attached a screen recording.
**Suggested Severity: S3**
|
|
1,669,506 | 15,070,828 |
Created attachment 9179916
WronglyBehavior_ESCkey.gif
[Affected versions]:
- Firefox Nightly 83.0a1 (Build ID: 20201006041051)
[Affected Platforms]:
- Windows 10 x64
- Windows 7 x64
- Mac 10.15
[Prerequisites]:
- Have the latest Firefox Nightly browser installed.
- Have a new Firefox profile.
- Have the user.js for the “fission-enabled” branch downloaded to your PC.
[Steps to reproduce]:
1. Open the browser with the profile from prerequisites.
2. Navigate to the "about:support" page and open the profile folder.
3. Paste the user.js file from prerequisites and restart the browser.
4. Restart the browser for the second time and navigate to any website (e.g. https://www.wikipedia.org/).
5. Press the “Esc” key after the Fission experiment doorhanger is displayed.
6. Observe the behavior.
[Expected result]:
- The Fission experiment doorhanger is closed and nothing else happens.
[Actual result]:
- The Fission experiment doorhanger is closed and the “https://wiki.mozilla.org/Project_Fission” page is opened in a new tab.
[Notes]:
- Attached a screen recording with the issue.
|
|
1,669,634 | 15,072,153 |
**Affected versions**
- Firefox 82.0b8
- Firefox 83.0a1
**Affected platforms**
- Windows 7 & 10
- macOS 11
- Ubuntu 20.04
**Steps to reproduce**
1. Launch Firefox
2. Access for example [Facebook](https://www.facebook.com/) page and close it back for ~5 times
3. Restart Firefox and access Facebook again
**Expected result**
- A CFR recommendation for Facebook add-on is shown in the address bar
**Actual result**
- No CFR recommendation is shown
**Regression range**
- Will see for a regression
**Additional notes**
- Youtube and Google Translate pages are affected as well
**Suggested severity**
- S2
|
|
1,669,698 | 15,072,574 |
I can permanently reproduce this crash during shutdown of Firefox with the following steps:
1. Start Firefox with the `--remote-debugger` argument
2. When started quit Firefox
3. Wait for the crash reporter dialog to pop-up.
Crash report: https://crash-stats.mozilla.org/report/index/ac8a24bf-40e4-4fd7-bcd1-f30bf0201007
Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS
Top 10 frames of crashing thread:
```
0 XUL remote::startup::handler::RemoteAgentHandler::allocate::Observe remote/startup/handler.rs:39
1 XUL nsObserverList::NotifyObservers xpcom/ds/nsObserverList.cpp:70
2 XUL nsObserverService::NotifyObservers xpcom/ds/nsObserverService.cpp:287
3 XUL NS_InvokeByIndex
4 XUL XPCWrappedNative::CallMethod js/xpconnect/src/XPCWrappedNative.cpp:1142
5 XUL XPC_WN_CallMethod js/xpconnect/src/XPCWrappedNativeJSOps.cpp:947
6 XUL js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:600
7 XUL Interpret js/src/vm/Interpreter.cpp:3337
8 XUL js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:637
9 XUL JS_CallFunctionValue js/src/jsapi.cpp:2768
```
Could this just be a moved stack signature now that bug 1660893 is fixed?
|
|
1,669,801 | 15,073,264 |
**Note**
* When the user engages in a WebRTC conference and shares a window, then clicks the screen-sharing icon from the tray/menu bar, he will notice that an incorrect message is displayed.
**Affected versions**
* Nightly v83.0a1
**Affected platforms**
* Windows 10
* Windows 7
* Mac OS 10.15
**Steps to reproduce**
1. Engage in a WebRTC call.
2. Share mic and camera. (irrelevant but normally necessary)
3. Share any window. (not a screen!)
4. Click on the Screen Sharing icon from the tray (bottom taskbar on Windows / top menu bar on Mac OS)
**Expected result**
* A correct message is displayed.
- Perhaps a similar behavior to the one seen when sharing screens:
- Case 1: When sharing 1 screen
"
Sharing Screen with "<<sharing tab name>>"
Control Sharing
"
- Case 2: When sharing 2 screens
"
Sharing Screen with 2 tabs
Control Sharing on "<<sharing tab name>>"
Control Sharing on "<< another sharing tab name>>"
"
**Actual result**
* An incorrect message is displayed:
" Sharing Windows with 0 tabs. "
**Regression range**
This is a new implementation.
**Additional notes**
* Linux OS does not have this functionality yet.
|
|
1,670,358 | 15,077,486 |
Created attachment 9180814
test_and_output.zip
# Version
```
commit 62c443a7c801ba9672de34c2867ec1665a4bbe67
parent b2dee52fd392f7130bc3858a70c683faa773aa8f
hg 48f10c4139655c2c4d52fa773f1fd760ea681d42
git 62c443a7c801ba9672de34c2867ec1665a4bbe67
author Gijs Kruitbosch <[email protected]>
committer Gijs Kruitbosch <[email protected]>
commit time Fri, 11 Sep 2020 15:05:50 +0000
```
# Steps to reproduce
- Enable address sanitizer in mozconfig.
- In [TestGCPostBarriers.cpp](https://searchfox.org/mozilla-central/source/xpcom/tests/gtest/TestGCPostBarriers.cpp),
add `array->Compact()` after [line 58](https://searchfox.org/mozilla-central/source/xpcom/tests/gtest/TestGCPostBarriers.cpp#58) and before [line 64](https://searchfox.org/mozilla-central/source/xpcom/tests/gtest/TestGCPostBarriers.cpp#64)
- run the gtest with `./mach gtest GCPostBarriers.nsTArray`
# More details
The key intuition is that the added `Compact` will cause the array to reallocate
and trying to access array items using an old address will lead to use-after-free error.
We came across this when we were working on something similar to a [ChaosMode](https://searchfox.org/mozilla-central/source/mfbt/ChaosMode.h) feature where we wanted to make array reallocation happen more often.
---
We have attached a test file with some print statements and the output file.
Our output file shows that the error happens when `RunTest` is first called with a `nsTArray` at [line 96](https://searchfox.org/mozilla-central/source/xpcom/tests/gtest/TestGCPostBarriers.cpp#95-96).
Our output file also shows that reallocation happened several times in the loop [line 52-58](https://searchfox.org/mozilla-central/source/xpcom/tests/gtest/TestGCPostBarriers.cpp#52-58),
which indicates that the extra reallocation triggered by `Compact` should not
affect later code.
Before being populated, the array was passed to `JS_AddExtraGCRootsTracer`
together with `TraceArray` at [line 44](https://searchfox.org/mozilla-central/source/xpcom/tests/gtest/TestGCPostBarriers.cpp#44).
In `TraceArray`, we found an unsafe use of addresses of array items.
```
template <class ArrayT>
static void TraceArray(JSTracer* trc, void* data) {
ArrayT* array = static_cast<ArrayT*>(data);
for (unsigned i = 0; i < array->Length(); ++i)
JS::TraceEdge(trc, &array->ElementAt(i), "array-element");
}
```
Here, `&array->ElementAt(i)` will become an invalid address if the array gets reallocated.
We added a print statement in `TraceArray` but didn't see it in the output file.
This could mean that there are other similarly unsafe code in `JS_GC`.
We also dumped all the array addresses and saw that
the UAF read is accessing the address right before the last reallocation from `Compact`.
The UAF address is the last element in the array but we don't know if the last one
is different from other elements.
We think there might be unsafe use of array addresses in the GC code or
the way `Compact` reallocates array is problematic.
|
|
1,670,907 | 15,081,683 |
**Affected versions**
* 83.0a1(2020-10-12)
* 82.0a(20201012131351)
**Affected platforms**
* macOS 10.14
* Ubuntu 18.04
* Windows 10x64
* Windows 7x64
**Steps to reproduce**
1. Launch FF.
2. Go to the burger menu
3. Go to Customize.
4. Put the Print button anywhere on the Toolbar.
**Expected result**
* Button is active and can be interacted with as soon as it has been set on the toolbar.
**Actual result**
* Button is greyed out and cannot be interacted with.
**Suggested Severity**
* Seeing as how this issue occurs on all devices used in our testing, but not blocking our access to the feature(there are multiple other ways to trigger modal) , I would S3 this issue
**Regression range**
* https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=70d0999325356b15d9b8b821a03cbd55ebf09b78&tochange=19eeff321de5d47400d4eea3b77b605884eaa598
Potential regressor: 1663173
**Additional notes**
* Print button can be interacted with as soon as the browser is restarted.
* Print button becomes unresponsive and greyed out as soon as the user changes its position.
* All other means of accessing the new modal are not compromised.
* This issue occurs for both old and new UI.
* Screen-cast of the issue: https://drive.google.com/file/d/1fkBnTN5SDjHiGpoFLD6Mi_s6NEWV2yA4/view?usp=sharing
|
|
1,670,943 | 15,082,014 |
One of the big missing features in the new printing UI on macOS is Black and White printing. The current printing dialog has a "Black & White" checkbox, but in the new UI the "Color mode" dropdown in locked to "Color". I expect this will be a major source of annoyance for users on macOS if we push the new UI out in its current state.
|
|
1,671,720 | 15,087,411 |
Crash report: https://crash-stats.mozilla.org/report/index/58408700-168a-4e63-924b-97e920201014
Reason: ```EXCEPTION_ACCESS_VIOLATION_READ```
Top 10 frames of crashing thread:
```
0 xul.dll TestHTTPAnswerRunnable::OnStartRequest dom/security/nsHTTPSOnlyUtils.cpp:437
1 xul.dll mozilla::extensions::ChannelWrapper::RequestListener::OnStartRequest toolkit/components/extensions/webrequest/ChannelWrapper.cpp:1073
2 xul.dll nsJARChannel::OnStartRequest modules/libjar/nsJARChannel.cpp:999
3 xul.dll nsInputStreamPump::OnInputStreamReady netwerk/base/nsInputStreamPump.cpp:390
4 xul.dll nsInputStreamReadyEvent::Run xpcom/io/nsStreamUtils.cpp:94
5 xul.dll mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:515
6 xul.dll mozilla::detail::RunnableFunction<`lambda at /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:88:7'>::Run xpcom/threads/nsThreadUtils.h:577
7 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1197
8 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:109
9 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:327
```
|
|
1,672,346 | 15,093,066 |
Nightly 84 with first party isolation enabled (`privacy.firstparty.isolate = true`) and tab containers in use.
The following exception happens when the PurgeTrackerService encounters the first tracker without interaction, at which point it stops without purging any cookies.
````
*** PurgeTrackerService:: Maybe purging http://youtube.com^firstPartyDomain=youtube.com.
Uncaught (in promise)
Exception { name: "NS_ERROR_MALFORMED_URI", message: "Component returned failure code: 0x804b000a (NS_ERROR_MALFORMED_URI) [nsIIOService.newURI]", result: 2152398858, filename: "resource://gre/modules/PurgeTrackerService.jsm", lineNumber: 114, columnNumber: 0, data: null, stack: "isAllowedThirdParty@resource://gre/modules/PurgeTrackerService.jsm:114:27\nmaybePurgePrincipal@resource://gre/modules/PurgeTrackerService.jsm:183:22\nasync*purgeTrackingCookieJars@resource://gre/modules/PurgeTrackerService.jsm:383:18\nasync*@debugger eval code:2:132\n@debugger eval code:3:3\ngetEvalResult@resource://devtools/server/actors/webconsole/eval-with-debugger.js:243:24\nexports.evalWithDebugger@resource://devtools/server/actors/webconsole/eval-with-debugger.js:167:14\nevaluateJS@resource://devtools/server/actors/webconsole.js:1118:38\nevaluateJSAsync/<@resource://devtools/server/actors/webconsole.js:1012:29\nexports.makeInfallible/<@resource://devtools/shared/ThreadSafeDevToolsUtils.js:103:22\n", location: XPCWrappedNative_NoHelper }
PurgeTrackerService.jsm:114
````
````
firstPartyOrigin: "https://mozilla.invisionapp.com^firstPartyDomain=invisionapp.com"
thirdPartyHost: "youtube.com"
````
|
|
1,672,394 | 15,093,298 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0
Steps to reproduce:
Logged into Google, Twitter and several other accounts.
Actual results:
Next day, after aproximately 24h hours I am logged out of these services again, but not all.
Expected results:
Should have been logged in still because Privacy Settings are set to keep active logins and cookies are not deleted on shutdown of Firefox.
|
|
1,672,463 | 15,093,806 |
We are already shipping to early beta and have since the summer.
|
|
1,672,528 | 15,094,188 |
## Summary
When using Firefox with Trusted Recursive Resolver (TRR), private IP addresses are
rejected by default (`network.trr.allow-rfc1918=false`). This protection can prevent
browser-based attacks of machines located on the LAN such as DNS-rebinding attacks.
However, this protection can be bypassed by using a IPv4-mapped IPV6 address
(eg. ::ffff:192.168.1.254).
This has been tested with Firefox Nightly 84.0a1 (2020-10-21) (64 bits) on Debian testing.
## Example
Let's create some domain names records:
~~~
$ dig @1.1.1.1 +short A wat4.urdhr.fr
::ffff:192.168.1.254
$ dig @1.1.1.1 +short AAAA wat6.urdhr.fr
::ffff:192.168.1.254
~~~
Let's check the are actually resolved by the DoH resolver
we are using:
~~~python
import dns.query
import dns.message
resolver = "https://cloudflare-dns.com/dns-query"
dns.query.https(dns.message.make_query("wat4.urdhr.fr", "A"), resolver).answer
# => [<DNS wat4.urdhr.fr. IN A RRset: [<192.168.1.254>]>]
dns.query.https(dns.message.make_query("wat6.urdhr.fr", "AAAA"), resolver).answer
# => [<DNS wat6.urdhr.fr. IN AAAA RRset: [<::ffff:192.168.1.254>]>]
~~~
When using TRR and `network.trr.allow-rfc1918=false`,
* http://wat4.urdhr.fr is not reachable in TRR
mode because the private IP address is rejected by Firefox;
* http://wat6.urdhr.fr however, is reachable
(assuming a web server is running on this IP address and port).
As far as I understand, the process is as follow:
1. the name is resolved to IPv6 ffff:192.168.1.254;
2. this IPv6 address is not considered a private IP address by `NetAddr::IsIPAddrLocal()`;
3. this IPv6 address generates a `AF_INET6` address in `DOHresp::Add()`;
4. this `AF_INET6` is passed to kernel;
5. kernel connects to 192.168.1.256.
## Code snippets
NetAddr derivation from DNS bytes:
~~~cpp
nsresult DOHresp::Add(uint32_t TTL, unsigned char* dns, unsigned int index,
uint16_t len, bool aLocalAllowed) {
NetAddr addr;
if (4 == len) {
// IPv4
addr.inet.family = AF_INET;
addr.inet.port = 0; // unknown
addr.inet.ip = ntohl(get32bit(dns, index));
} else if (16 == len) {
// IPv6
addr.inet6.family = AF_INET6;
addr.inet6.port = 0; // unknown
addr.inet6.flowinfo = 0; // unknown
addr.inet6.scope_id = 0; // unknown
for (int i = 0; i < 16; i++, index++) {
addr.inet6.ip.u8[i] = dns[index];
}
} else {
return NS_ERROR_UNEXPECTED;
}
if (addr.IsIPAddrLocal() && !aLocalAllowed) {
return NS_ERROR_FAILURE;
}
// While the DNS packet might return individual TTLs for each address,
// we can only return one value in the AddrInfo class so pick the
// lowest number.
if (mTtl < TTL) {
mTtl = TTL;
}
if (LOG_ENABLED()) {
char buf[128];
addr.ToStringBuffer(buf, sizeof(buf));
LOG(("DOHresp:Add %s\n", buf));
}
mAddresses.AppendElement(addr);
return NS_OK;
}
~~~
Checking if IP address is private:
~~~cpp
bool NetAddr::IsIPAddrLocal() const {
const NetAddr* addr = this;
// IPv4 RFC1918 and Link Local Addresses.
if (addr->raw.family == AF_INET) {
uint32_t addr32 = ntohl(addr->inet.ip);
if (addr32 >> 24 == 0x0A || // 10/8 prefix (RFC 1918).
addr32 >> 20 == 0xAC1 || // 172.16/12 prefix (RFC 1918).
addr32 >> 16 == 0xC0A8 || // 192.168/16 prefix (RFC 1918).
addr32 >> 16 == 0xA9FE) { // 169.254/16 prefix (Link Local).
return true;
}
}
// IPv6 Unique and Link Local Addresses.
if (addr->raw.family == AF_INET6) {
uint16_t addr16 = ntohs(addr->inet6.ip.u16[0]);
if (addr16 >> 9 == 0xfc >> 1 || // fc00::/7 Unique Local Address.
addr16 >> 6 == 0xfe80 >> 6) { // fe80::/10 Link Local Address.
return true;
}
}
// Not an IPv4/6 local address.
return false;
}
~~~
## Tests
These tests should be able to check the expected behavior (in `test_trr.js`):
~~~cpp
// verify RFC1918 IPv4-mapped address from the server is rejected
add_task(async function test7() {
dns.clearCache(true);
Services.prefs.setIntPref("network.trr.mode", 3); // TRR-only
Services.prefs.setCharPref(
"network.trr.uri",
`https://foo.example.com:${h2Port}/doh?responseIP=::ffff.192.168.0.1`
);
let [, , inStatus] = await new DNSListener(
"rfc1918.example.com",
undefined,
false
);
Assert.ok(
!Components.isSuccessCode(inStatus),
`${inStatus} should be an error code`
);
});
// verify RFC1918 IPv4-mapped address from the server is fine when told so
add_task(async function test8() {
dns.clearCache(true);
Services.prefs.setIntPref("network.trr.mode", 3); // TRR-only
Services.prefs.setCharPref(
"network.trr.uri",
`https://foo.example.com:${h2Port}/doh?responseIP=::ffff.192.168.0.1`
);
Services.prefs.setBoolPref("network.trr.allow-rfc1918", true);
await new DNSListener("rfc1918.example.com", "192.168.0.1");
});
~~~
## Additional Considerations
It would probably make sense to be able to reject the following networks
as well:
- 0.0.0.0/24
- 127.0.0.0/8
- ::1/128
These can be used for DNS-rebinding attacks on the local machine.
|
|
1,672,758 | 15,095,468 |
Reported via https://github.com/mozilla/geckodriver/issues/1796.
The following Marionette test hangs in `WebDriver:Back`:
```
self.marionette.navigate("http://testsite.surfly.com/multisession.html")
self.marionette.find_element(By.TAG_NAME, "a").click()
frame = self.marionette.find_element(By.ID, "bing_frame")
self.marionette.switch_to_frame(frame)
self.marionette.go_back()
```
Here the log output from 83 beta and Nightly:
```
1603382848864 Marionette DEBUG 2 -> [0,14,"WebDriver:Back",{}]
1603382848867 Marionette TRACE Received message beforeunload for https://www.bing.com/?surfly_switch_role=true&toWww=1&redig=9AB3F78B002D42CBBC68CAF9E45DD1F3
1603382848881 Marionette TRACE Received message pagehide for https://www.bing.com/?surfly_switch_role=true&toWww=1&redig=9AB3F78B002D42CBBC68CAF9E45DD1F3
```
In Firefox 82 it looks like:
```
1603382956071 Marionette DEBUG 2 -> [0,14,"WebDriver:Back",{}]
1603382956072 Marionette TRACE Received message beforeunload for https://www.bing.com/?surfly_switch_role=true&toWww=1&redig=C89C77A57617413BA7272BD4CC4AEE31
1603382956083 Marionette TRACE [19] Frame with id 4294967297 got removed
1603382956083 Marionette TRACE Received message pagehide for https://www.bing.com/?surfly_switch_role=true&toWww=1&redig=C89C77A57617413BA7272BD4CC4AEE31
```
I'll have to check which change for Firefox 82.0 broke that back navigation. Interesting is that we have tests that should have covered that. So it would be good to know what's different here.
|
|
1,673,388 | 15,101,051 |
+++ This bug was initially created as a clone of Bug #1670907 +++
**Affected versions**
82/83/84
**Affected platforms**
* macOS 10.14
* Ubuntu 18.04
* Windows 10x64
* Windows 7x64
**Steps to reproduce**
1. Launch FF.
2. Go to the burger menu
3. Go to Customize.
4. Put the Print button anywhere on the Toolbar.
**Expected result**
* Button is active and can be interacted with as soon as it has been set on the toolbar.
**Actual result**
* Button is not greyed out, but still doesn't do anything when clicked / activated.
|
|
1,673,446 | 15,101,440 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0
Steps to reproduce:
No change to configuration, just an upgrade to TB. Now I'm prompted to re-enter my password if the previous imap-pull (or smtp-push) for this account was older than 40 minutes or so (time not measured). Once the password is entered once per fetch/send, the password works, this is not a problem with mis-typing the password.
The behavior is the same for imap fetch and smtp send.
Win10, TB-78.4.0, and I do have a TB master password (and it is entered correctly). I do not store my email passwords in the TB credentials manager (I use keepass).
Actual results:
After upgrading to TB-78.4.0, I am prompted for my password for both sending and receiving multiple times within the same TB session. This is only in one of my three IMAP accounts:
- simple imap server at hostmonster; normal password (nothing else supported)
- outlook.office365.com; oauth2
- imap.mail.yahoo.com; oauth2
"hostmonster" is the problem account, the other two behave normally.
The laptop's network connection does not appear to glitch, and it does not hibernate/sleep. The AV/FW setup is standard windows, nothing special, and nothing has changed between TB-78.3 and TB-78.4 (or any time recently).
Expected results:
Before upgrading to TB-78.4.0 (78.3?), I would enter my email account password (once for fetch and once on-demand for send) at the beginning of the TB session. Once done, unless the password was changed or I restarted TB, I was not prompted for this password again.
|
|
1,673,511 | 15,101,898 |
From github: https://github.com/mozilla-mobile/fenix/issues/16106.
> [comment]: # (Please do your best to search for duplicate issues before filing a new issue so we can keep our issue board clean)
> [comment]: # (Every issue should have the exact bug and steps to reproduce described in it. Please do not file feedback list tickets as it is difficult to parse them and address their individual points)
> [comment]: # (Read https://github.com/mozilla-mobile/fenix#i-want-to-file-an-issue for more information)
>
> ## Steps to reproduce
> Click on a textbox,
> Scroll down till url hides (the keyboard does not hide)
> Click on any link on the page
>
> ### Expected behavior
> Nothing
> ### Actual behavior
> Keyboard now pops up on every page load, forever. Without any reason
> ### Device information
>
> * Android device: Asus Zenfone
> * Fenix version: nightly
>
>
Change performed by the [Move to Bugzilla add-on](https://addons.mozilla.org/en-US/firefox/addon/move-to-bugzilla/).
|
|
1,673,711 | 15,103,565 |
2 of these crashes today with 84.0a1 20201027095021 - both on Windows 7 but on different machines.
Crash report: https://crash-stats.mozilla.org/report/index/8d9141ca-8479-4dea-a86f-6831b0201027
MOZ_CRASH Reason: ```MOZ_RELEASE_ASSERT(pid != kInvalidProcessId)```
Top 10 frames of crashing thread:
```
0 xul.dll mozilla::dom::ContentParent::KillHard dom/ipc/ContentParent.cpp:3844
1 xul.dll nsTimerEvent::Run xpcom/threads/TimerThread.cpp:251
2 xul.dll mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:515
3 xul.dll mozilla::detail::RunnableFunction<`lambda at /builds/worker/checkouts/gecko/xpcom/threads/TaskController.cpp:85:7'>::Run xpcom/threads/nsThreadUtils.h:577
4 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1197
5 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
6 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:327
7 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:309
8 xul.dll nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
9 xul.dll nsAppShell::Run widget/windows/nsAppShell.cpp:602
```
|
|
1,664,065 | 15,028,763 |
Created attachment 9174809
Heartbeat notification
Heartbeat notifications have a white text on a light background that make them unreadable (see screenshot). This is not an issue in Firefox 79.
Steps to produce:
1. Download and install the Normandy devtools extension
2. Run one of the Heartbeat recipes
3. See that the notification is not readable.
|
|
1,664,257 | 15,030,076 |
First crash for 82.0a1 has build id 20200829091226, for 80 beta first affected is 81.0b4. Is there a change which got uplifted for beta 4 (or 3) and landed shortly before on central?
Crash report: https://crash-stats.mozilla.org/report/index/2ac9de80-6106-4a83-8cfa-318880200830
Top 10 frames of crashing thread:
```
0 xul.dll mozilla::WeakPtr<mozilla::layers::PersistentBufferProvider>::operator= mfbt/WeakPtr.h:257
1 xul.dll mozilla::layers::BorrowedSourceSurface::BorrowedSourceSurface gfx/layers/CanvasRenderer.cpp:27
2 xul.dll mozilla::layers::CanvasRenderer::BorrowSnapshot const gfx/layers/CanvasRenderer.cpp:66
3 xul.dll mozilla::layers::ShareableCanvasRenderer::UpdateCompositableClient gfx/layers/ShareableCanvasRenderer.cpp:189
4 xul.dll nsDisplayCanvas::CreateWebRenderCommands layout/generic/nsHTMLCanvasFrame.cpp:144
5 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommands gfx/layers/wr/WebRenderCommandBuilder.cpp:1653
6 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList gfx/layers/wr/WebRenderCommandBuilder.cpp:1758
7 xul.dll nsDisplayOwnLayer::CreateWebRenderCommands layout/painting/nsDisplayList.cpp:6335
8 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommands gfx/layers/wr/WebRenderCommandBuilder.cpp:1653
9 xul.dll mozilla::layers::WebRenderCommandBuilder::CreateWebRenderCommandsFromDisplayList gfx/layers/wr/WebRenderCommandBuilder.cpp:1758
```
|
|
1,664,402 | 15,031,042 |
[Sugested Severity:]
S2
[Description:]
Switching the browser.topsites.useRemoteSetting on/off/on, it is possible to alter the default topsite amazon.de into amazon.com.
Additionally, probably after the bug 1661008 fix, amazon.com also gets pinned by default and marked as a search shortcut. (this part is not reproducible on 81 b4)
[Environment:]
Windows 10, Ubuntu 20, Mac 10.13.6
81.0b9
[Steps:]
1. Create a new profile with:
user_pref("services.settings.load_dump", false);
user_pref("browser.topsites.useRemoteSetting", true);
user_pref("browser.search.region", "DE");
2. Start Firefox, observe topsites -> from RS top-sites collection.
4. Close Firefox, set browser.topsites.useRemoteSetting to false.
5. Start Firefox, observe topsites -> legacy configuration.
6. Close Firefox, set browser.topsites.useRemoteSetting to true.
7. Start Firefox, observe topsites -> from RS top-sites collection.
##### [Actual Result:]
2. (RS)amazon.de is listed, not pinned, not search shortcut
5. (legacy)amazon.com is listed, pinned, search shortcut.
7. (RS)amazon.com is listed, pinned, search shortcut.
##### [Expected Result:]
2. (RS)amazon.de is listed, not pinned, not search shortcut
5. (legacy)amazon.com is listed, pinned, search shortcut.
7. (RS)amazon.de is listed, not pinned, not search shortcut.
|
|
1,664,980 | 15,036,353 |
Created attachment 9175693
screencast issue.gif
**Affected versions**
* 82.0a1 (2020-09-14)
**Affected platforms**
* Windows 7
**Steps to reproduce**
1. Launch Firefox
2. Make sure print.tab_modal.enabled is set on true
3. Go to http://example.org/
4. Hit Ctrl + P
5. Expand More settings and select Print backgrounds
6. Switch between Destinations
**Expected result**
- The way the background is displayed stays constant
**Actual result**
- The way the background is displayed varies
**Regression range**
* First bad: 726130eb9a19a4a4619b33dc7fb02d1a25f3ca64
* Last good: b0add3579bcc35ed2bdf8749f230432acd8092b2
* Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b0add3579bcc3
5ed2bdf8749f230432acd8092b2&tochange=726130eb9a19a4a4619b33dc7fb02d1a25f3ca64
**Additional notes**
* The issue is intermittent and is triggered also by opening the modal several times (with the same destination), having a different outcome
**Suggested severity**
* S4
|
|
1,665,413 | 15,039,296 |
[Tracking Requested - why for this release]:
Late Beta simulation: https://treeherder.mozilla.org/#/jobs?repo=try&selectedTaskRun=YzyVPtK0SSSw8Bwm8ZmOtA.0&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception&revision=ef554a8be6eb26910bec9f9bb4e29bc8c34d44b0&searchStr=windows%2C10%2Cx64%2Cwebrender%2Cshippable%2Copt%2Creftests%2Ctest-windows10-64-shippable-qr%2Fopt-reftest-e10s%2Cr1
Log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=315848752&repo=try&lineNumber=15196
Last green job on late beta simulation: https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&revision=28b47eafcd46278db37983f55d2dd779453279ec&searchStr=windows%2C10%2Cx64%2Cwebrender%2Cshippable%2Copt%2Creftests%2Ctest-windows10-64-shippable-qr%2Fopt-reftest-e10s%2Cr1&selectedTaskRun=QD-OF2wxS3qUS-UZ3g9iGA.0
|
|
1,665,739 | 15,041,532 |
Please be aware this would turn into a production failure for beta next Monday.
central-as-beta simulation: https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&selectedTaskRun=Plc30SJcSIut9ZWRG23aXA.0&resultStatus=success%2Ctestfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable&revision=314b5bf834e4bd95b88642c4397504af8c18ac2e&searchStr=browser-chrome
Log: https://treeherder.mozilla.org/logviewer.html#?job_id=315958094&repo=try
[task 2020-09-17T14:54:39.034Z] 14:54:39 INFO - Observed addon-install-blocked for 1 installs
[task 2020-09-17T14:54:39.035Z] 14:54:39 INFO - Install of http://example.com/browser/toolkit/mozapps/extensions/test/xpinstall/recommended.xpi was in state 3
[task 2020-09-17T14:54:39.035Z] 14:54:39 INFO - Console message: 1600354032003 addons.repository DEBUG cacheAddons: enabled false IDs ["[email protected]"]
[task 2020-09-17T14:54:39.035Z] 14:54:39 INFO - Buffered messages logged at 14:48:38
[task 2020-09-17T14:54:39.035Z] 14:54:39 INFO - Longer timeout required, waiting longer... Remaining timeouts: 3
[task 2020-09-17T14:54:39.035Z] 14:54:39 INFO - Buffered messages logged at 14:50:08
[task 2020-09-17T14:54:39.035Z] 14:54:39 INFO - Longer timeout required, waiting longer... Remaining timeouts: 2
[task 2020-09-17T14:54:39.035Z] 14:54:39 INFO - Buffered messages logged at 14:51:38
[task 2020-09-17T14:54:39.035Z] 14:54:39 INFO - Longer timeout required, waiting longer... Remaining timeouts: 1
[task 2020-09-17T14:54:39.035Z] 14:54:39 INFO - Buffered messages logged at 14:53:02
[task 2020-09-17T14:54:39.035Z] 14:54:39 INFO - Console message: [JavaScript Error: "Unknown Collection "main/nimbus-desktop-experiments"" {file: "resource://services-settings/RemoteSettingsClient.jsm" line: 160}]
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - UnknownCollectionError@resource://services-settings/RemoteSettingsClient.jsm:160:5
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - sync@resource://services-settings/RemoteSettingsClient.jsm:470:13
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO -
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - Buffered messages finished
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - TEST-UNEXPECTED-FAIL | toolkit/mozapps/extensions/test/xpinstall/browser_doorhanger_installs.js | Test timed out -
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - Not taking screenshot here: see the one that was previously logged
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - TEST-UNEXPECTED-FAIL | toolkit/mozapps/extensions/test/xpinstall/browser_doorhanger_installs.js | No unexamined telemetry events after test is finished - [] deepEqual [{"method":"install","object":"unknown","value":"26","extra":{"step":"started","source":"test-host","method":"installTrigger"}},{"method":"install","object":"unknown","value":"26","extra":{"step":"download_started","source":"test-host","method":"installTrigger"}},{"method":"install","object":"extension","value":"26","extra":{"step":"download_completed","download_time":"203","source":"test-host","method":"installTrigger","addon_id":"[email protected]"}},{"method":"install","object":"extension","value":"26","extra":{"step":"site_warning","source":"test-host","method":"installTrigger","addon_id":"[email protected]"}}] - JS frame :: resource://testing-common/AddonTestUtils.jsm :: hookAMTelemetryEvents/< :: line 1969
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - Stack trace:
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - resource://testing-common/AddonTestUtils.jsm:hookAMTelemetryEvents/<:1969
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - chrome://mochikit/content/browser-test.js:nextTest:555
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - Console message: 1600354478623 addons.xpi DEBUG Cancelling download of http://example.com/browser/toolkit/mozapps/extensions/test/xpinstall/recommended.xpi
[task 2020-09-17T14:54:39.036Z] 14:54:39 INFO - Console message: 1600354478647 addons.xpi DEBUG removeTemporaryFile: http://example.com/browser/toolkit/mozapps/extensions/test/xpinstall/recommended.xpi removing temp file /tmp/tmp-2w5.xpi
[task 2020-09-17T14:54:39.037Z] 14:54:39 INFO - GECKO(7851) | MEMORY STAT | vsize 3088MB | residentFast 357MB | heapAllocated 100MB
[task 2020-09-17T14:54:39.037Z] 14:54:39 INFO - TEST-OK | toolkit/mozapps/extensions/test/xpinstall/browser_doorhanger_installs.js | took 450144ms
|
|
1,666,249 | 15,046,209 |
Created attachment 9176872
cnameOf.zip
The API `browser.dns.resolve()` does not return the actual canonical name for any given hostname when DNS-over-HTTPS is enabled.
Steps to reproduce:
- Download the minimalist attached `cnameOf.zip` extension, unzip locally
- Launch Firefox
- Enable "Enable DNS over HTTPS" in `about:preferences`
- To be sure, quit/launch Firefox
- Navigate to `about:debugging#/runtime/this-firefox`
- Click "Load Temporary Add-on..."
- Pick the downloaded extension above
- Click the "Inspect" button for the loaded extension
- Activate the "Console" pane
- In the console, type `cnameOf('www.nytimes.com')`
- Result, failure: `canonicalName = www.nytimes.com`
- In the console, type `cnameOf('cdn.vox-cdn.com')`
- Result, failure: `canonicalName = cdn.vox-cdn.com`
The above works when disabling "Enable DNS over HTTPS":
- Disable "Enable DNS over HTTPS" in `about:preferences`
- Quit/launch Firefox
- Click "Load Temporary Add-on..."
- Pick the downloaded extension above
- Click the "Inspect" button for the loaded extension
- Activate the "Console" pane
- In the console, type `cnameOf('www.nytimes.com')`
- Result, success: `canonicalName = nytimes.map.fastly.net`
- In the console, type `cnameOf('cdn.vox-cdn.com')`
- Result, success: `canonicalName = prod.vox.map.fastly.net`
This was first reported on uBlock Origin's issue tracker:
<https://github.com/uBlockOrigin/uBlock-issues/issues/1190>
|
|
1,666,300 | 15,046,632 |
When fuzzing Firefox clipboard API content sanitization on pasting, I found sanitizer bypass with payload `<svg><style><image href=1 onerror=alert(document.domain)>`. When user copy from crafted malicious website, then paste the content, XSS will execute. It leads to universal XSS on latest stable release of Firefox, Firefox 78.3.0esr (64-bit), and Firefox Nightly 82.0a1 (2020-09-20).
## Steps to reproduce:
1. Go to https://sourc7.appspot.com/bugzilla/0447f4d26c48bd8d0526dce173f57b3ac5235b7b.html
2. Click Copy Text
3. Go to https://output.jsbin.com/gocizet/ (TinyMCE Rich Editor form)
4. Paste with Ctrl+V or Right click -> Paste into TinyMCE form
5. XSS will execute [pop alert(document.domain)]
|
|
1,666,356 | 15,047,035 |
STR:
1. Lauch VO on `data:text/html,<input type="checkbox">Hello`
2. VO+U to checkbox rotor
Expected:
VO lists the checkbox
Actual:
nothing
|
|
1,666,568 | 15,048,640 |
Created attachment 9177177
emscripten_test.zip
Example crash report: https://crash-stats.mozilla.org/report/index/a028e387-9af2-4489-a85d-6ede40200922
Top 10 frames of crashing thread:
```
0 libxul.so js::ObjectGroup::defaultNewGroup js/src/vm/ObjectGroup.cpp:541
1 libxul.so js::NewObjectWithGivenTaggedProto js/src/vm/JSObject.cpp:857
2 libxul.so js::SavedFrame::create js/src/vm/SavedStacks.cpp:563
3 libxul.so js::SavedStacks::getOrCreateSavedFrame js/src/vm/SavedStacks.cpp:1753
4 libxul.so js::SavedStacks::saveCurrentStack js/src/vm/SavedStacks.cpp:1307
5 libxul.so js::CaptureStack js/src/jsexn.cpp:221
6 libxul.so js::ErrorToException js/src/jsexn.cpp:331
7 libxul.so js::ReportErrorNumberVA js/src/vm/ErrorReporting.cpp:477
8 libxul.so JS_ReportErrorNumberASCII js/src/jsapi.cpp:4702
9 libxul.so js::ReportOverRecursed js/src/vm/JSContext.cpp:309
```
This started to crash consistently for us on Emscripten CI, which runs Firefox Dev edition, so this may be a regression that happened in the last few days.
The crashes almost always have
MOZ_RELEASE_ASSERT(CurrentThreadCanAccessZone(zone))
failing in them.
To reproduce in emscripten,
./tests/runner.py browser.test_pthread_create
Attached is a zip of the build files, just run a webserver and browse to the HTML. (Will need either a COOP/COEP-enabled server, or to flip the "insecure" flag, happens either way.)
|
|
1,666,645 | 15,049,031 |
[Tracking Requested - why for this release]:
The [first NSS uplift for Nightly 83](https://phabricator.services.mozilla.com/D91070) wanted to update KnownRootHashes.json and RootHashes.inc -- some technical limitations caused our uplift script to fail to update them for the 82 cycle, and possibly the cycle before that.
Since they're out of date, telemetry using the new roots will be out-of-date. If we can, we should uplift a quick fix to beta for it. We can just carve the `.inc` file changes out of that commit and uplift those. It's even a NOBUILD scenario.
|
|
1,658,445 | 14,983,296 |
Steps to reproduce:
1. Open a web page with a text area or text field
3. Begin typing, ensuring that your cursor is inside of a text field
3. Do control/command-p
4. Hit escape
5. Keep typing
What happens:
Firefox lost your cursor and nothing is typed.
Expected result:
I should be able to continue typing where I was.
|
|
1,658,563 | 14,984,130 |
Created attachment 9169426
firefox_bug.PNG
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
We have HTML-links in our intranet which refer to local lnk-files. This lnk-Files refer to local Word-Templates.
Actual results:
FF offers to download the lnk-files instead of opening the refered Word-Templates. In our group-policy we defined everything correct for handling with local files from our intranet-ressource.
The problems occur since FF 78esr. IN FF 68esr everything was OK.
Expected results:
The refered lnk-files shoudl open the refered word-templates.
|
|
1,659,155 | 14,989,409 |
Created attachment 9170075
menus-srcUrl-redirect.zip
Since bug 1406253, the `info.srcUrl` field of the `contextMenus.onClicked` event returns the URL after redirects, instead of the URL of the image request.
Prior to that bug, and also in Chrome, the `info.srcUrl` field was the image's src element.
STR:
1. Load attached extension, which opens a tab with an image.
2. Right-click on the image and click on the extension's context menu.
Expected (Chrome 84):
- A dialog with a URL ending with "before-redirect".
Actual (Firefox 81):
- A dialog with a URL ending with "after-redirect"
I'm inclined to resolve the bug as follows:
- ~Update MDN to clarify that `info.srcUrl` may differ from the `<img>`'s src attribute. In Chrome, this is always the URL of the initial request. In Firefox, this is the final URL (after any redirects).~ EDIT: The alternative is preferred, see comment 2 and comment 3.
- Add a unit test to make sure that the behavior continues to be as documented.
The alternative is to let `info.srcUrl` be the initial URL again. This would result in consistent behavior between Firefox and Chrome. I guess that few users cared either way, since nobody has filed a bug about this (I only discovered this when I [investigated a report about DownThemAll not working on Twitter](https://bugzilla.mozilla.org/show_bug.cgi?id=1621249#c4)).
Some extensions ([including DownThemAll](https://github.com/downthemall/downthemall/blob/858b8f277e8f9c0a080193916c6f01c73aa437a0/lib/background.ts#L505-L531)) use `info.srcUrl` to identify the element to which the context menu is anchored from a content script. Since there is a superior alternative (`info.targetElementId` + [`browser.menus.getTargetElement`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/menus/getTargetElement)), I would recommend extension authors to use that API to really identify the target element without having to traverse the whole DOM to find the image element of interest.
|
|
1,659,463 | 14,992,660 |
**Affected versions**
* 81.0a1 (BuildId:20200816214203)
**Affected platforms**
* Windows 10 64bit
* macOS 10.14
* Ubuntu 18.04 64bit.
**Preconditions**
* Ensure that the `print.tab_modal.enabled` pref is set to `true`
**Steps to reproduce**
1. Launch Firefox.
2. Open print preview
3. Click the Scale radio button.
**Expected result**
* The scale has an arrow stepper (Though giving the possibility of mouse-only users to increase/decrease the scale value).
**Actual result**
* mouse-only users can’t increase/decrease the scale value easily since there is no arrow stepper.
**Regression Window**
* I don’t think that this is a regression..seems more of a design bug https://mozilla.invisionapp.com/share/MFWMR6H5X3K#/screens/411388964
|
|
1,659,655 | 14,993,952 |
[Affected versions]:
Nightly 81.0a1 (2020-08-18)
[Affected platforms]:
Platforms: Mac OsX, Windows 10, Ubuntu
Steps :
1. Launch the Firefox browser and have one set of credentials saved for www.facebook.com in about:logins
2. Set up a Primary Password and restart the browser.
3. Reach www.facebook.com and click cancel on the PP prompt.
4. Enter a new set of credentials and Hit the Login button in order for the Primary Password prompt to be displayed.
5. Click the Cancel button on the PP prompt.
Expected Results :
The Primary Password prompt should no longer be displayed after clicking the cancel button
Actual Results :
The PP prompt is displayed multiple times after Hitting the Cancel button.
|
|
1,659,730 | 14,994,445 |
Created attachment 9170676
360Browser-Cannot-Import_Directly.jpg
**Precondition**
Make sure you have *360 Browser* installed
**Steps to reproduce**
1. Open Firefox
2. Open the Bookmarks library by pressing "*Ctrl+Shift+B*"
3. Press the *Import/Export Arrows* -> *Import Data from another browsers...* button
**Actual Results**
*360 Browser* isn't listed
**Expected Results**
*360 Browser* is listed
**Note**
You can import bookmarks via .HTML file but those are not added directly onto the Bookmarks Toolbar
|
|
1,660,458 | 14,999,550 |
Perfherder has detected a build_metrics performance regression from push [8cb615e26bdcff161b73c03d919db2c7cf140e16](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=8cb615e26bdcff161b73c03d919db2c7cf140e16). As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
0.42% installer size osx-shippable opt nightly 75,624,499.58 -> 75,944,078.75
Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perf.html#/alerts?id=26763), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/).
For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
|
|
1,660,490 | 14,999,820 |
Created attachment 9171411
screencast issue .gif
Crash report: https://crash-stats.mozilla.org/report/index/b0d02945-49b0-41ef-82e6-9aa120200821
Top 10 frames of crashing thread:
```
0 xul.dll RetainedDisplayListBuilder::MergeDisplayLists layout/painting/RetainedDisplayListBuilder.cpp:838
1 xul.dll RetainedDisplayListBuilder::MergeDisplayLists layout/painting/RetainedDisplayListBuilder.cpp:838
2 xul.dll RetainedDisplayListBuilder::MergeDisplayLists layout/painting/RetainedDisplayListBuilder.cpp:838
3 xul.dll RetainedDisplayListBuilder::MergeDisplayLists layout/painting/RetainedDisplayListBuilder.cpp:838
4 xul.dll RetainedDisplayListBuilder::MergeDisplayLists layout/painting/RetainedDisplayListBuilder.cpp:838
5 xul.dll RetainedDisplayListBuilder::MergeDisplayLists layout/painting/RetainedDisplayListBuilder.cpp:838
6 xul.dll RetainedDisplayListBuilder::AttemptPartialUpdate layout/painting/RetainedDisplayListBuilder.cpp:1498
7 xul.dll static nsLayoutUtils::PaintFrame layout/base/nsLayoutUtils.cpp:4216
8 xul.dll mozilla::PresShell::Paint layout/base/PresShell.cpp:6371
9 xul.dll nsViewManager::ProcessPendingUpdatesPaint view/nsViewManager.cpp:460
```
**Affected versions**
* 81.0a1
**Affected platforms**
* macOS 10.14
* Windows 10
**Unaffected platforms**
* Ubuntu 18.04
**Steps to reproduce**
1. Launch Firefox
2. Make sure print.tab_modal.enabled is set on true
3. Go to https://www.w3schools.com/html/html_iframe.asp
4. Bring the context menu up with right click
5. Go to This Frame - Print Frame
**Actual result**
* Tab crashes
**Regression range**
* First bad: 8a50074624329979203ec0a51d240e20e0c1c1fa
* Last good: 173c59907b33d4f35b1699521d5f02f8c47cd75b
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=173c59907b33d4f35b1699521d5f02f8c47cd75b&tochange=8a50074624329979203ec0a51d240e20e0c1c1fa
* Potential regressor: 1659457
**Suggested severity**
* S3
|
|
1,666,739 | 15,049,850 |
*Affected versions*
* 83.0a1 (20200922154306)
* 82.0b2 (20200922183749)
*Affected platforms*
* Windows 7/10x64
* macOS 10.12
* Ubuntu 18.04
*Steps to reproduce*
1. Open Firefox with a new profile and go to a random Youtube video.
2. If an ad is playing, click the skip ads button while the PiP description is shown.
*Expected result*
* The ad is skipped.
*Actual result*
* PiP Player is opened.
*Regression range*
* I will search for one ASAP.
*Notes*
* Attached a screen recording: [link](https://drive.google.com/file/d/1B3jBpKgzMxmMWLlIH9PRC3rnWlzvTro3/view?usp=sharing).
* The issue can be reproducible even when the firefox window is smaller and `Skip Ads` button overlaps the PiP button (see the attached screen recording)
* When `I like this ad/ I dislike this ad` buttons are present the PiP button is underneath them when the size of the window is smaller (the issue is seen in the screen recording as well).
**Suggested Severity: S3**
|
|
1,666,827 | 15,050,424 |
Created attachment 9177414
navigate-in-preview.mp4
STR
1. Open a page with a link on it (maybe https://en.wikipedia.org/wiki/Firefox)
2. Start a print
3. Click on a link in the preview browser
Expected results: Nothing happens
Actual results: The preview browser is navigated
Mozregression pointed to this pushlog https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=be24fd0c7bc5f87b103ef59141bcf539bf07c635&tochange=168ce28f004948c7b2646d5f613c1bda7af62de6
|
|
1,667,031 | 15,051,796 |
I see this on a clean profile on a local build from Tuesday's mozilla-central, ie:
```
./mach run --temp-profile
```
reproduces reliably (a second or two after startup):
```
TypeError: (destructured parameter) is null UrlbarInput.jsm:1329:1
setSearchMode resource:///modules/UrlbarInput.jsm:1329
observe resource:///modules/UrlbarInput.jsm:1711
notifyAction resource://gre/modules/SearchUtils.jsm:189
_updateFromManifest resource://gre/modules/SearchEngine.jsm:1072
_reloadEngines resource://gre/modules/SearchService.jsm:832
AsyncFunctionNext self-hosted:674
```
Looking at the code, the [`observe` method](https://searchfox.org/mozilla-central/rev/3d53187b90605ccef321c9cadbba762ad06a6381/browser/components/urlbar/UrlbarInput.jsm#1709-1711) looks like it expects `subject.name` to be non-undefined/null, but it never QIs `subject`, and so AIUI there's no guarantee of this being the case.
Adding
```
subject.QueryInterface(Ci.nsISearchEngine);
```
before it fixes the issue.
It's not clear to me what the consequences of this bug are, and/or what's going to happen once we fix it... but we still should.
|
|
1,667,102 | 15,052,226 |
Crash report: https://crash-stats.mozilla.org/report/index/c27d1c1c-2530-4f43-9ce4-c4d000200924
Top 10 frames of crashing thread:
```
0 @0x858481e6
1 @0xebeacfc6
2 xul.dll mozilla::net::Http2Stream::TransmitFrame netwerk/protocol/http/Http2Stream.cpp:971
3 xul.dll mozilla::net::Http2Stream::OnReadSegment netwerk/protocol/http/Http2Stream.cpp:1516
4 xul.dll static mozilla::net::nsHttpTransaction::ReadRequestSegment netwerk/protocol/http/nsHttpTransaction.cpp:725
5 xul.dll nsBufferedInputStream::ReadSegments netwerk/base/nsBufferedStreams.cpp:446
6 xul.dll mozilla::net::nsHttpTransaction::ReadSegments netwerk/protocol/http/nsHttpTransaction.cpp:752
7 xul.dll mozilla::net::Http2Stream::ReadSegments netwerk/protocol/http/Http2Stream.cpp:164
8 xul.dll mozilla::net::Http2Session::ReadSegmentsAgain netwerk/protocol/http/Http2Session.cpp:2815
9 xul.dll mozilla::net::nsHttpConnection::OnSocketWritable netwerk/protocol/http/nsHttpConnection.cpp:1993
```
Most of these crashes seem to be `EXCEPTION_ACCESS_VIOLATION_EXEC` which might be scary?
|
|
1,667,121 | 15,052,338 |
Bug 1654397 incorrectly sets the crypto scheme when using CBCS to CENC, this typo should be fixed.
|
|
1,667,319 | 15,053,588 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:82.0) Gecko/20100101 Firefox/82.0
Steps to reproduce:
https://codepen.io/argggh/pen/OJNdwKo demonstrates the issue. Basically:
1. Safari produces offer with one audio m-line and one video m-line (hardcoded in STR above)
2. Firefox responds with answer containing the same amount of active tracks from its side
3. Firefox adds additional video/audio tracks
4. Firefox produces new offer, reversing roles
Actual results:
Offer from step 4 contains two "a=rtpmap:98" lines in the first video m-line, with different codecs:
a=rtpmap:98 H264/90000
a=rtpmap:99 rtx/90000
a=rtpmap:100 VP8/90000
a=rtpmap:101 rtx/90000
a=rtpmap:121 VP9/90000
a=rtpmap:125 rtx/90000
a=rtpmap:97 H264/90000
a=rtpmap:98 rtx/90000
Expected results:
Offer should contain rtpmap with consistent codecs per RTP payload type.
|
|
1,667,368 | 15,053,935 |
Created attachment 9177872
Screenshot 2020-09-25 14.05.18.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0
Steps to reproduce:
Step one - open Inspector (Ctrl + Shift + C).
No more steps required!
Actual results:
Depending how "lucky" you are, you can get:
- multiple nodes highlighted with no way to deselect them (see attachment with 3 pre-selected nodes)
- no node is highlighted BUT also node can be highlighted - it's just stuck
Expected results:
There should be no highlighting issues.
I think there were some rare random issues also before, but this is definitely regression in 82. It happens also in clean Firefox profile.
|
|
1,667,377 | 15,054,008 |
If there is a navigation to be observed by [waitForNavigationCompleted](https://searchfox.org/mozilla-central/rev/89d33e1c3b0a57a9377b4815c2f4b58d933b7c32/testing/marionette/navigate.js#179) the specified callback, which triggers the navigation, is actually never called when there are no page load events expected or the set page load strategy capability is `None`. Instead it just returns a resolved promise:
https://searchfox.org/mozilla-central/rev/89d33e1c3b0a57a9377b4815c2f4b58d933b7c32/testing/marionette/navigate.js#194-196
This is a regression from bug 1612831.
|
|
1,667,668 | 15,055,772 |
Created attachment 9178100
Screenshot_2020-09-27 File Sync Software - Sync Home Resilio Sync.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
I went to https://www.resilio.com/individuals/.
Actual results:
The Downloads section of the website showed a broken "Desktop Downloads" layout, with a stretched Tux and text not being where it's supposed to be.
Expected results:
The layout should have been normal, like it is in Beta, with no stretched Tux and text in the correct places.
Note: this happens in a fresh profile as well.
|
|
1,667,811 | 15,057,991 |
STR:
Navigate to Site A
Navigate to Site B
Navigate to any Extension page (e.g. uBlock dashboard or reader mode page in Fenix)
Hit Back, and back again
Expected:
Navigated to Site B, then A
Actual:
Navigated to Site B, then Extension page
From there one navigating back "loops" between Site B and the extension page. It's not possible to navigate further back in history.
|
|
1,667,985 | 15,059,281 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0
Steps to reproduce:
Leave browser do sync or manually trigger sync.
Actual results:
3 PCs were unable to sync their add-on data. I have had a chance to observe it when setting up FF on a new PC. It seems everything but add-ons data is being synced just fine (tabs, bookmarks, add-ons themselves (as in a list + enabled/disabled status)), but add-on data is not, I have had a chance to observe effects (or the lack of) of this on 3 add-ons with data sync:
- uBlock Origin - on a new PC after allowing a cloud storage support I am not getting the last backup and my other instance doesn't see a newly added cloud backups from my another machine
- Firefox Multi-Account Containers - while I have sync on (I was setting up another machine a month or so ago and it synced the data) I am not getting my list of containers from my other PCs
- Skip Redirect - today on my old PC I noticed there is now a sync option so I activated it and a couple of hours later I have even tried to force the upload by "Sync now" within Sync options in FF, however on my new PC I am not receiving data (as in exceptions added to matching rules)
After using add-on "About sync" I was able to get:
- a chance to see the add-on reporting that FF sync failed
- a look at error logs (I see one for each 10 minutes, I guess this is a standard delay for FF sync)
both for all PCs.
Here is a snippet of lines around the error:
1601147785925 Sync.Engine.Extension-Storage WARN Got exception, aborting processIncoming: BridgeError: Error parsing JSON data: missing field `extId`(resource://services-sync/bridged_engine.js:136:5) JS Stack trace: BridgeError@bridged_engine.js:136:5transformError@bridged_engine.js:404:14 handleError@bridged_engine.js:419:16
1601147785926 Sync.Engine.Extension-Storage TRACE Event: weave:engine:sync:error
1601147785926 Sync.ErrorHandler TRACE Handling weave:engine:sync:error
1601147785926 Sync.Status DEBUG Status for engine extension-storage: error.engine.reason.unknown_fail
1601147785926 Sync.Status DEBUG Status.service: success.status_ok => error.sync.failed_partial
1601147785926 Sync.ErrorHandler DEBUG extension-storage failed: BridgeError: Error parsing JSON data: missing field `extId`(resource://services-sync/bridged_engine.js:136:5) JS Stack trace: BridgeError@bridged_engine.js:136:5 transformError@bridged_engine.js:404:14 handleError@bridged_engine.js:419:16
I can also provide one of these logs, but I would like to ask for a suggestion what type of data is there which I may want to redact before posting, I see e.g. some ID of some sort in URLs
https://sync-1-us-west1-g.sync.services.mozilla.com/1.5/___here___/storage/history?batch=true&commit=true
Expected results:
Add-on data being synced properly between browsers.
|
|
1,668,247 | 15,060,956 |
Created attachment 9178717
rec of the issue 3.gif
**[Affected versions]:**
- Firefox Release 81.0 - Build ID: 20200917005511
- Firefox Beta 82.0b5 - Build ID: 20200929175845
- Firefox Nightly 83.0a1 - Build ID: 20200929213959
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Ubuntu 18.04 x64
**[Prerequisites]:**
- You are logged in to Pocket.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Click the "Save to Pocket" button from the right part of the "Address Bar".
3. Press the "Tab" key twice and observe the behavior.
**[Expected result]:**
- The "Remove Page" hyperlink is visibly focused.
**[Actual result]:**
- No elements from the Pocket doorhanger are focused.
**[Notes]:**
- The functionality part of the elements is not affected. For example, if after step 3 the "Enter" key is pressed, the website will be removed from Pocket.
- Attached a screenshot of the issue.
|
|
1,668,265 | 15,061,033 |
Steps to reproduce:
* Go to gregtatum.com
* Use the inspect element button to inspect the "programming is poetry" graphic.
* Mouse over the tag in the inspector, this will show the box layout highlighter on the page.
* Repeatedly refresh the page while inspecting the element.
Expected results:
* The highlighter should continue to highlight the element, margins, and paddings.
Actual results:
* The highlighter disappears forever on the page. The only way to get it back is to close the tab, and re-open.
* No errors appear in the browser console.
I can reproduce this on 81 and 82 on macOS.
I get the following error on Nightly:
```
Error: Unexpected packet null, {"from":"server1.conn0.windowGlobal15032385539/frameTarget1","error":"noSuchActor","message":"No such actor for ID: server1.conn0.windowGlobal15032385539/frameTarget1"}
onPacket resource://devtools/shared/protocol/Front.js:320
onPacket resource://devtools/client/devtools-client.js:492
send resource://devtools/shared/transport/local-transport.js:68
makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
Front.js:321:15
Error: Unexpected packet null, {"from":"server1.conn0.windowGlobal15032385539/frameTarget1","error":"noSuchActor","message":"No such actor for ID: server1.conn0.windowGlobal15032385539/frameTarget1"}
onPacket resource://devtools/shared/protocol/Front.js:320
onPacket resource://devtools/client/devtools-client.js:492
send resource://devtools/shared/transport/local-transport.js:68
makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:103
ThreadSafeDevToolsUtils.js:82:13
```
However, I get this error only when the "Multiprocess Browser Console" is open, so I don't know if it's related.
|
|
1,686,964 | 15,217,920 |
Perfherder has detected a build_metrics performance regression from push [60625635f86daf1eb8d704cc4ec3d80d815c4495](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=60625635f86daf1eb8d704cc4ec3d80d815c4495). As author of one of the patches included in that push, we need your help to address this regression.
### Regressions:
| **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**|
|--|--|--|--|--|--|
| 0.22% | installer size | | osx-aarch64-shippable | aarch64 nightly | 79,157,791.71 -> 79,335,307.25 |
| 0.13% | installer size | | osx-aarch64-shippable | aarch64 nightly | 79,251,575.29 -> 79,355,105.08 |
Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=28445), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/).
For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
|
|
1,686,982 | 15,218,078 |
Created attachment 9197376
ebay urlbar url.gif
**[Notes]:**
- Not sure if it's related with the issue, but when the eBay Sponsored suggestion is opened, there is an "/" in the URL (ebay.de/?mkevt), but the "/" is missing when hovering the eBay Sponsored suggestion (ebay.de?mkevt).
**[Affected versions]:**
- Firefox Beta 85.0b9 (Build ID: 20210112185508)
- Firefox Release 84.0.2 (Build ID: 20210105180113)
- Firefox Nightly 86.0a1 (Build ID: 20210114083245)
**[Affected Platforms]:**
- Ubuntu 20.04
- macOS 10.15
- Windows 10
**[Prerequisites]:**
- Have the latest Firefox Beta version installed and open.
- Have the following preferences set:
- `browser.search.region` set to `DE` / `US` / `GB`
- `browser.topsites.experiment.ebay-2020-1` set to `true`
- `browser.partnerlink.useAttributionURL` set to `true`
- `browser.topsites.useRemoteSetting` set to `true`
**[Steps to reproduce]:**
1. Open a new tab page.
2. Click inside the address bar.
3. Click the eBay Sponsored suggestion.
4. Repeat the first 3 steps.
**[Expected result]:**
- The second time the eBay suggestion is clicked, the tab switches to the page opened in step 3.
**[Actual result]:**
- The eBay suggestion doesn’t recognize that the page is already open in another tab.
**[Additional Notes]:**
- The behavior of the tile is also different at ctrl+click - it opens the page in a new tab and focuses it instead of opening the link in the same tab.
- Attached is a recording of the behavior.
|
|
1,687,999 | 15,226,779 |
Created attachment 9198450
ss of the issue.png
**[Affected versions]:**
- Firefox Beta 85.0 RC1 - Build ID: 20210118153634
- Firefox Nightly 86.0a1 - Build ID: 20210121094402
**[Affected Platforms]:**
- Windows 10 x64
- Mac 10.15
- Linux Mint 20
**[Prerequisites]:**
- Have a Firefox profile with the following prefs in the "about:config" page:
- "browser.newtabpage.activity-stream.newNewtabExperience.enabled" pref set to "true"
- "browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar" set to "false"
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites and open a "New Tab".
2. Click inside the in-content "Search Bar" and observe the behavior.
**[Expected result]:**
- The in-content "Search Bar" is focused according to the [specifications](https://www.figma.com/file/hGOaTi5ufs2Ese6agbUN4G/New-New-Tab?node-id=2153%3A568).
**[Actual result]:**
- Two focuses are displayed on the in-content "Search Bar".
**[Additional Notes]:**
- This issue is not reproducible if the "browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar" pref is set to "true".
- Attached a screenshot of the issue.
|
|
1,688,490 | 15,229,941 |
Maybe Fission related, all 4 crashes have Fission enabled. (DOMFissionEnabled=1)
Crash report: https://crash-stats.mozilla.org/report/index/67bf183c-94a9-4eb4-864b-b6b5a0210124
Reason: ```EXC_BAD_ACCESS / KERN_INVALID_ADDRESS```
Top 10 frames of crashing thread:
```
0 XUL -[mozMenuItemAccessible moxIgnoreWithParent:] accessible/mac/mozSelectableElements.mm:265
1 XUL -[MOXAccessibleBase isAccessibilityElement] accessible/mac/MOXAccessibleBase.mm:399
2 XUL -[mozAccessible moxFocusedUIElement] accessible/mac/mozAccessible.mm:251
3 XUL -[MOXAccessibleBase accessibilityFocusedUIElement] accessible/mac/MOXAccessibleBase.mm:383
4 AppKit -[NSWindow accessibilityFocusedUIElement]
5 AppKit NSAccessibilityHandleFocusChangedForce
6 AppKit -[NSWindow _realMakeFirstResponder:]
7 XUL nsChildView::TearDownView widget/cocoa/nsChildView.mm:350
8 XUL nsChildView::Destroy widget/cocoa/nsChildView.mm:404
9 XUL nsCocoaWindow::Destroy widget/cocoa/nsCocoaWindow.mm:577
```
|
|
1,688,999 | 15,235,124 |
Crash report: https://crash-stats.mozilla.org/report/index/293f220a-f8d6-47c2-86f6-5064e0210126
MOZ_CRASH Reason: ```MOZ_CRASH()```
Top 10 frames of crashing thread:
```
0 firefox-bin mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33
1 libxul.so std::string::string /builds/worker/fetches/clang/include/c++/7.4.0/bits/basic_string.tcc:664
2 libxul.so mozilla::gl::GLContext::InitImpl gfx/gl/GLContext.cpp:541
3 libxul.so mozilla::gl::GLContext::Init gfx/gl/GLContext.cpp:321
4 libxul.so mozilla::gl::GLContextEGL::Init gfx/gl/GLContextProviderEGL.cpp:435
5 libxul.so mozilla::gl::GLContextEGL::CreateGLContext gfx/gl/GLContextProviderEGL.cpp:784
6 libxul.so mozilla::gl::GLContextEGL::CreateEGLPBufferOffscreenContextImpl gfx/gl/GLContextProviderEGL.cpp:1192
7 libxul.so mozilla::gl::GLContextEGL::CreateEGLPBufferOffscreenContext gfx/gl/GLContextProviderEGL.cpp:1213
8 libxul.so mozilla::gl::GLContextProviderEGL::CreateHeadless gfx/gl/GLContextProviderEGL.cpp:1227
9 libxul.so mozilla::WebGLContext::CreateAndInitGL dom/canvas/WebGLContext.cpp:367
```
|
|
1,689,095 | 15,235,972 |
Created attachment 9199517
search separator line too bright on dark theme.gif
**[Affected versions]:**
- Firefox Nightly 87.0a1, BuildID 20210127093943
**[Affected Platforms]:**
- Windows 10
- macOS 10.15
- Linux MX 4.19
**[Prerequisites]:**
- Have a new Firefox profile.
- Have the `browser.newtabpage.activity-stream.newNewtabExperience.enabled` pref set to `true`.
- Have the browser theme set to Dark.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab and scroll down the page until the Search bar is stuck to the top of the page.
3. Observe the Search separator line.
**[Expected results]:**
- The line is set at 10% opacity.
**[Actual results]:**
- The line is set at 100% opacity.
**[Additional notes]:**
- The issue is not reproducible on the old New Tab experience. And as far as I can tell it's due to the fact that we're using a different way to define the color on the old New Tab experience - RGBA 249 249 250 0.1 vs HEX #E1E0E6.
- The issue is not reproducible/not noticeable on Light/Default themes (OS light).
- Attached a screen recording of the issue.
@ewright, could you please take a look at this?
|
|
1,676,631 | 15,126,496 |
The following testcase crashes on mozilla-central revision 20201111-68867f327c62 (debug build, run with --fuzzing-safe --cpu-count=2 --ion-offthread-compile=off --baseline-eager --ion-warmup-threshold=0):
function f54() {
var a90 = arguments;
for (var i63 = 0; i63 < 10; ++i63) {
a90[unescape]
}
}
f54();
Backtrace:
received signal SIGSEGV, Segmentation fault.
0x0000555557a184e4 in js::jit::IonGetPropertyIC::update(JSContext*, JS::Handle<JSScript*>, js::jit::IonGetPropertyIC*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::MutableHandle<JS::Value>) ()
#0 0x0000555557a184e4 in js::jit::IonGetPropertyIC::update(JSContext*, JS::Handle<JSScript*>, js::jit::IonGetPropertyIC*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::MutableHandle<JS::Value>) ()
#1 0x000034d5b3f36cb3 in ?? ()
[...]
#21 0x0000000000000000 in ?? ()
rax 0x5555558261fc 93824995189244
rbx 0xfff9800000000000 -1829587348619264
rcx 0x5555580c8878 93825037797496
rdx 0x0 0
rsi 0x7ffff7105770 140737338431344
rdi 0x7ffff7104540 140737338426688
rbp 0x7fffffffb130 140737488335152
rsp 0x7fffffffae70 140737488334448
r8 0x7ffff7105770 140737338431344
r9 0x7ffff7f998c0 140737353717952
r10 0x58 88
r11 0x7ffff6dac7a0 140737334921120
r12 0x7ffff5688400 140737310655488
r13 0x7ffff6024000 140737320730624
r14 0x0 0
r15 0x7fffffffb640 140737488336448
rip 0x555557a184e4 <js::jit::IonGetPropertyIC::update(JSContext*, JS::Handle<JSScript*>, js::jit::IonGetPropertyIC*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::MutableHandle<JS::Value>)+4036>
=> 0x555557a184e4 <_ZN2js3jit16IonGetPropertyIC6updateEP9JSContextN2JS6HandleIP8JSScriptEEPS1_NS5_INS4_5ValueEEESB_NS4_13MutableHandleISA_EE+4036>: movl $0xae,0x0
0x555557a184ef <_ZN2js3jit16IonGetPropertyIC6updateEP9JSContextN2JS6HandleIP8JSScriptEEPS1_NS5_INS4_5ValueEEESB_NS4_13MutableHandleISA_EE+4047>: callq 0x555556ac2316 <abort>
Marking s-s because this assert can indicate JIT security issues.
|
|
1,676,878 | 15,128,286 |
Steps:
1. Open [Drive](https://drive.google.com).
2. Shift+Tab until you reach the folders side bar.
* Expected: VoiceOver reads the label for the tree, and the full selected item name, in my case "Priority".
* Actual: VoiceOver reads everything, but cuts off the first letter, only reads "riority".
4. DownArrow onto My Files, which in my case is the second item.
* Expected: VoiceOver reads the My Files folder name along with the fact that it is collapsed.
* Actual: VoiceOver reads "y Files", and does not indicate expanded or collapsed state.
Very simplified test case, which reproduces both problems and is roughly modeled after what is in Google Drive:
`data:text/html,<button>Before</button><div role="tree" tabindex="0" aria-label="My drive" aria-activedescendant="myfiles"><div id="myfiles" role="treeitem" aria-label="My files" aria-selected="true" aria-expanded="false">My files</div><div role="treeitem" aria-label="Shared items" aria-selected="false" aria-expanded="false">Shared items</div></div>`.
|
|
1,677,109 | 15,129,885 |
Created attachment 9187675
Amazon redisplayed.gif
**[Notes]:**
- The top-sites collection also contains the non-experiment version of Amazon for the US, DE and GB locales and eBay for DE and GB.
- This seems to cause them to be displayed after the user has dismissed the experiment versions. This could be considered ignoring user choice.
**[Affected versions]:**
- Firefox Beta 83 (Build ID: 20201112153044)
**[Affected Platforms]:**
- Windows
- Linux
- macOS
**[Prerequisites]:**
- Have Firefox Beta 83 installed and open.
- Be enrolled in a treatment branch of the “TopSites Launch Phase 3” experiment:
- Use the Stage environment.
- `browser.partnerlink.useAttributionURL` set to `true`
- `browser.topsites.experiment.ebay-2020-1` set to `true`
- `browser.search.experiment` set to `amazondotcom-adm`
- `browser.topsites.useRemoteSetting` set to `true`
**[Steps to reproduce]:**
1. Open a new tab.
2. Dismiss the Amazon Sponsored tile.
3. Observe the Top Sites displayed.
**[Proposed result]:**
- A non-sponsored Amazon top tile **is not** displayed after the user has dismissed its Sponsored version.
**[Current result]:**
- A non-sponsored Amazon top tile **is** displayed after the user has dismissed its Sponsored version.
**[Additional Notes]:**
- The behavior decribed in the steps can not be reproduced for eBay on the US version of the experiment.
- I am attaching a recording of the current behavior.
|
|
1,677,442 | 15,133,525 |
Created attachment 9187990
ETPStandardsvDisabled.png
**Environment:**
Browser / Version: Firefox Nightly
Operating System: Windows
**Prerequisites:**
ETP - Standard enabled.
**Steps to reproduce:**
1. Navigate to https://store.hp.com/ItalyStore/Merch/Product.aspx?id=3A661EA&opt=ABZ&sel=NTB
2. Click "360°" option.
3. Click the "360°" icon.
4. Observe the screen.
**Expected Behavior:**
360° animation loads.
**Actual Behavior:**
360° animation doesn't load.
**Notes:**
1. Screenshot attached.
2. The issue is not reproducible with ETP disabled.
|
|
1,678,237 | 15,138,975 |
Perfherder has detected a build_metrics performance regression from push [77ab0ef5c2035d065138c88ef087d6fe52c6e7fe](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=77ab0ef5c2035d065138c88ef087d6fe52c6e7fe). As author of one of the patches included in that push, we need your help to address this regression.
### Regressions:
| **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**|
|--|--|--|--|--|--|
| 1% | installer size | | osx-cross | | 79,249,562.17 -> 79,852,723.58 |
Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=27695), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/).
For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
|
|
1,678,258 | 15,139,215 |
Firefox 85.0a1 and 84.0b2 on Windows 8.1
From bug 1671906 (or bug 1673328):
The overlay buttons triggered for a debugger breakpoint are not reacting to clicks (continue, step) but the buttons in the right sidebar work as expected.
Steps to reproduce:
1. Open https://bugherder.mozilla.org/ (other pages will also work, you just have to know where to set a breakpoints and how to trigger it).
2. Open the debugger (either from the menu or with Ctrl+Shift+Z).
3. In the left sidebar, expand the folder and select the following file: bugherder.mozilla.org/thirdparty/bzjs/bz-0.4.3.js
4. Go to line 262: `var that = this;`
5. Click on the line number to set a breakpoint.
6. Put the following into the input field in the page: 36ef6c97da5bbabfa3d65ad493d1872bfb77b355
7. Click the 'Submit' button.
The breakpoint gets triggered.
8. Click on either the arrow (step over, supposed to go to next line in debugger) or play button (continue script execution).
Actual result: Nothing happens.
9. Click one of these buttons in the right sidebar
Actual and expected result: Expected action executed.
|
|
1,678,652 | 15,141,574 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
Upgraded to Firefox 83 on Ubuntu 20.10 on Wayland.
Actual results:
When I try to launch a webGL game:
Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated.
Specifically Pixi says:
Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support.
Expected results:
The game should have launched. There is no reason WebGL should fail.
|
|
1,678,793 | 15,142,494 |
Created attachment 9189325
ntp too big.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Firefox/85.0
Steps to reproduce:
I have nothing against the Firefox branding on the New Tab page now, but it's way too big, it actually looks ridiculous and silly. Please consider making it smaller, it's gigantic.
|
|
1,689,612 | 15,239,542 |
When GeckoView (also true in Fennec) requests for authentication, we do not provide the authenticator type which is used for sites that may need to specific a cross-platform (e.g. FIDO key) instead of a platform-specific (e.g. biometric reader)
Below are three cases that should work:
## Undefined
### Steps to reproduce
1. Go to webauthn.io
2. Enter any example username and "Authenticator Type" as "Undefined".
3. Click register.
### Expected
- The authenticator on Android should present NFC, Bluetooth, USB, and Biometric options.
### Actual
- The authenticator on Android does present all the above options as the expected.
## Cross-platform
### Steps to reproduce
1. Go to webauthn.io
2. Enter any example username and "Authenticator Type" as "Cross platform".
3. Click register.
### Expected
- The authenticator on Android should present NFC, Bluetooth, and USB options.
### Actual
- The authenticator on Android presents NFC, Bluetooth, USB, and Biometric options.
## Platform
### Steps to reproduce
1. Go to webauthn.io
2. Enter any example username and "Authenticator Type" as "Platform (TPM)".
3. Click register.
### Expected
- The authenticator on Android should present only the Biometric option.
### Actual
- The authenticator on Android presents NFC, Bluetooth, USB, and Biometric options.
|
|
1,689,894 | 15,241,311 |
Currently, it only accepts a pair of `Float32Array`, this was the old way of doing things, this changed in https://github.com/WebAudio/web-audio-api/issues/1195#issue-219940295.
This is nice for ergonomics.
|
|
1,690,186 | 15,244,871 |
Created attachment 9200589
about:support
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0
Steps to reproduce:
Enabled Container Tabs through one of the many different addons.
Actual results:
The Proton Tab subtext has insufficient padding when the coloured container tabs indicator is enabled.
Expected results:
Sufficient padding be present between the media status subtext and the container tabs indicated
|
|
1,690,278 | 15,245,571 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
I update FF 85 beta to 86 beta in a machine where our setup is installed.
I close Firefox if it is open.
I insert a smart card in the reader.
I wait for certificates to be populated in the Windows 'MY' store.
I launch Firefox.
I verify that this setting move to 'true'
Then I connect to our test secured site.
Actual results:
The PIN code is requested twice:
1°) by Firefox because the setup install our pkcs#11 as security module (via a dedicated webextension)
2°) by our CSP component which is also installed by the setup.
Here is a video of what happens: https://youtu.be/hXaaF8dWGjE
We notice the same certificate is presented in two entries in the certificate selection dialog.
Expected results:
Only one choice for the certificate to select,
Only one PIN code be entered for authentication to succeed.
|
|
1,690,296 | 15,245,647 |
From github: https://github.com/mozilla-mobile/fenix/issues/16368.
> [comment]: # (Please do your best to search for duplicate issues before filing a new issue so we can keep our issue board clean)
> [comment]: # (Every issue should have the exact bug and steps to reproduce described in it. Please do not file feedback list tickets as it is difficult to parse them and address their individual points)
> [comment]: # (Read https://github.com/mozilla-mobile/fenix#i-want-to-file-an-issue for more information)
>
> ## Steps to reproduce
> The following simplified page shows the problem:
> https://www.sleeping.pt/wp/testfixedbodybug.html
>
> The following video shows the problem:
> https://www.sleeping.pt/wp/wp-content/uploads/2020/10/2020_11_04_14_49_12.webm
>
> 1. Scroll down until the toolbar disappears.
>
> 2. Click anywhere in the document, to trigger the click event that makes the document fixed.
>
> 3. And we can see the space reserved for the toolbar menu but the toolbar is hidden.
>
> When the toolbar reserves the space it does not change the window.innerHeight value either.
>
> ### Expected behavior
> In this case, it is expected that the menu does not reserve space when it is hidden, and the document is set as fixed. Or reserve space but show up and change the window.innerHeight value.
>
> ### Actual behavior
> Reserve the space but don't show up and don't change the window.innerHeight value.
>
> ### Device information
>
> * Android device: A20e
> * Fenix version: 82.1.1
>
>
Change performed by the [Move to Bugzilla add-on](https://addons.mozilla.org/en-US/firefox/addon/move-to-bugzilla/).
|
|
1,690,308 | 15,245,699 |
Follow-up from bug 1684827.
When checking for element staleness during / after a cross-group navigation a `NoSuchElement` error is returned instead of a `StaleElementReference` error. The reason for that is the new browsing context id the top-level browsing context gets. For details see bug 1674329.
These changes of the browsing context including its id can only happen for the top-level browsing context, and not for child browsing contexts. As such I didn't notice this problem on bug 1684827.
When implementing the fix we have to make sure to add some wdspec tests that cover this scenario.
Thank you James Nord for reporting the issue!
|
|
1,690,331 | 15,246,049 |
Created attachment 9200700
AES_TEST_cdkp_cms_RSA-3072_pw_password.p12
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36 Edg/88.0.705.56
Steps to reproduce:
Attempted to import the attached PKCS#12 file which uses AES and SHA-1 for everything instead of mixing RC2/TDES/AES.
Actual results:
Firefox errors
Expected results:
It should import properly. The password is password
It imports into Windows 10 and OpenSSL.
|
|
1,691,075 | 15,251,145 |
**Steps to reproduce**
1. Open Firefox, navigate to https://www.google.com/
1. Open the Browser Toolbox, select the console
1. In Firefox, open the regular toolbox, select the debugger
**Actual results**
we get the following error:
> console.error: (new TypeError("can't access property "addEventListener", this is undefined", "resource://devtools/server/startup/worker.js", 24))
originating from https://searchfox.org/mozilla-central/rev/40205f1b55f1ba8a26fcbd362c20d843e8718a87/devtools/server/startup/worker.js#24
this code isn't covered by test, and was modified in Bug 1681888, which probably caused the regression
|
|
1,691,349 | 15,254,346 |
**Steps to reproduce**
1. Navigate to `about:preferences`
1. Open the inspector
1. On the `.main-content` element, use the context menu entry to take a screenshot of the node
**Actual results**
The browser hangs for some reason
---
|
|
1,691,478 | 15,255,195 |
When using the English_CA localized firefox with user.js region CA, i see a different order list in the amazon slot.
**Tested on**
Windows10 64bit
Affects:
Firefox Nightly 87.0a1
Firefox Release 85
Firefox Beta 86.0b7
**Steps to reproduce**
1) install firefox EN_CA localized version, and Use a user.js with :
Region: CA
Search log: true
Remotesettings : ON
Load Dump: FALSE
2) Run firefox with the above user.js, one with remotesettings ON, and another time with remotesettings OFF
3) Check topsite list order.
**actual result**
With remote settings ON, this is the order:
"1)Youtube
2)Amazon.ca
3)Facebook
4)Reddit
5)wikipedia
6)Twitter"
With remote settings OFF, this is the order:
"1)Youtube
2)Facebook
3)Reddit
4)wikipedia
5)Amazon.ca
6)Twitter"
Amazon has a different order
**Expected result**
Order should match with remotesettings on and off.
|
|
1,691,504 | 15,255,345 |
In MergeStacks, if I add the following line right before the `SetJSContextProfilerSampleBufferRangeStart` call near the end:
```cpp
fprintf(stderr, "%lu, %lu\n", samplePosInBuffer ? *samplePosInBuffer : 0, bufferRangeStart);
```
I get very inconsistent results: the values should be somewhat similar as that's what the JS engine depends on, but in practice the first one (`*samplePosInBuffer`) is *much* smaller (factor 1000 or so) than `bufferRangeStart`. Both values keep increasing.
Noticed this while tracking down confusing JS profiler results in bug 1684224.
|
|
1,674,088 | 15,106,150 |
Created attachment 9184485
log.txt.moz_log
**[Affected versions]:**
- Firefox Release 82.0 (BuildID 20201014125134)
- Firefox Release 82.0.1 (Build ID:20201026153733)
- Firefox Release 82.0.2 (Build ID: 20201027185343)
**[Affected Platforms]:**
- Windows 10
- Linux Mint 20 (intermittent)
**[Prerequisites]:**
- See this [document](https://docs.google.com/document/d/13yxuvfpIGojY1FSsUJYHKUUQldKkSW0UzrUirdC0kQ0/edit#bookmark=id.3qlajv1ku5v3) for the environment variable needed.
- Have Firefox Release installed and open.
- Have the Remote Settings environment set to Stage.
- Have `doh-rollout.enabled` set to `true`.
- Be enrolled in the 'Don't reset doh-rollout.mode at shutdown" branch of the "DNS-over-HTTPS usage rate study".
**[Steps to reproduce]:**
1. Navigate to various webpages.
2. Restart the browser.
3. Navigate to various webpages.
4. Navigate to "about:telemetry#histograms-tab" and observe the values of the`TRR_SKIP_REASON_TRR_FIRST`histogram.
**[Expected result]:**
- The numbers of items in the `10` and `14` buckets are not large.
**[Actual result]:**
- The numbers of items in the `10` and `14` buckets are larger than expected.
**[Notes]:**
- Attached are a [recording](https://drive.google.com/file/d/18Cwacr7a0u-ZpGAb0KRtWMGal6qwmkI0/view?usp=sharing) of the issue and the log for the session displayed in the recording.
- I am also attaching a [log](https://drive.google.com/file/d/1sJZ5_2yoCIwZOvC7q2hIrOcqOTW48K_L/view?usp=sharing) for a session using the "Both prefs" branch.
- This issue also seems reproducible for the "Both prefs" branch, though the `14` bucket seems to have fewer items on that branch.
- The issue does not seem reproducible for the "Control" or "Skip confirmation" branches.
- The issue seems to only be partially reproducible for Linux (the `14` bucket is larger sometimes, but the `10` bucket remains small) and does not seem to be reproducible for macOS 10.15.
|
|
1,674,158 | 15,106,702 |
Within `waitForNavigationCompleted` we [register a couple of listeners](https://searchfox.org/mozilla-central/rev/d866b96d74ec2a63f09ee418f048d23f4fd379a2/testing/marionette/navigate.js#328-335) (events, observer, message) that usually get all cleaned-up within [checkDone](https://searchfox.org/mozilla-central/rev/d866b96d74ec2a63f09ee418f048d23f4fd379a2/testing/marionette/navigate.js#207-229).
Sadly all those registered listeners aren't cleaned-up in case of a page load timeout. The reason for that is the usage of the `TimedPromise` and that it internally rejects the promise, and the code in `waitForNavigationCompleted` doesn't use the `catch` or `finally` methods.
That's a regression from moving the navigation code into the parent process (bug 1612831).
|
|
1,675,050 | 15,113,830 | null |
|
1,675,212 | 15,115,063 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.183 Safari/537.36
Steps to reproduce:
Press the delete button a little too long
Actual results:
unwanted emails are deleted.
Expected results:
Only one email should be deleted
|
|
1,675,523 | 15,117,415 |
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:82.0) Gecko/20100101 Firefox/82.0
Steps to reproduce:
Compared CKR_PUBLIC_KEY_INVALID between NSS's pkcs11t.h value and PKCS#11 v2.40's spec version and jdk8u's version.
Luckily CKR_PUBLIC_KEY_INVALID appears unused in NSS's codebase.
Actual results:
NSS's value was incorrect and differed from the latter two.
> lib/util/pkcs11t.h:1463:#define CKR_PUBLIC_KEY_INVALID 0x000001B
(This is the value of CKR_ACTION_PROHIBITED).
Expected results:
NSS's value should be corrected.
PKCS#11 v2.40:
https://www.cryptsoft.com/pkcs11doc/STANDARD/include/v240/pkcs11t.h line 1150
jdk8u:
https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/file/eb7f437285a1/src/share/native/sun/security/pkcs11/wrapper/pkcs11t.h#l1155
|
|
1,675,624 | 15,118,129 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:82.0) Gecko/20100101 Firefox/82.0
Steps to reproduce:
In UK locale (I understand the dictionary may differ, or the bug may not occur, in another locale), start firefox. Use options to remove "Chambers UK" from the one-click search engines, close and restart firefox.
Actual results:
"Chambers UK" dictionary added back in to the one-click search engines list.
Expected results:
No explicitly removed search engine should be added.
N.B. I'm classing this as a "defect" rather than "enhancement request" because it's silently undoing an explicitly changed setting.
|
|
1,675,755 | 15,118,879 |
Created attachment 9186217
array-split-reload.html
When mistakenly re-declaration of `let` or `const` on the browser console, then reload the page repeatedly or typing string.split("") or string.split(" ") while waiting browser console instant evaluation result, suddenly the tab is crashed. To trigger the crash, on the HTML file it need to initialize one constant variable i.e `const x = "A"`
Mostly when Firefox Nightly ASAN crash, it shows `AddressSanitizer: SEGV on unknown address (pc 0x7fa6e7dbe0b9 bp 0x7ffe338b3620 sp 0x7ffe338b3610 T0)` but the unknown address is not showed.
Sometimes Nightly ASAN shows `AddressSanitizer: use-after-poison on address 0x27f915ded218 at pc 0x7f4221357bb8 bp 0x7fffb52d8850 sp 0x7fffb52d8848
READ of size 8 at 0x27f915ded218 thread T0 (Web Content)`
Rare moment, Nightly ASAN show the unknown address: `AddressSanitizer: SEGV on unknown address 0x363339343840 (pc 0x7fdf867b7257 bp 0x7ffe9e3f92b0 sp 0x7ffe9e3f8e20 T0)` (reproduced on Firefox Nightly ASAN 2020-10-26) (64-bit)
It seems Nightly ASAN tried to access address 0x363339343840 which is potentially exploitable and worth to investigate further.
I've attached Firefox Nightly ASAN log, full GDB log (launch with command line `./mach run --debugger="gdb-9" --debugger-args="-q --args" --disable-e10s`), full valgrind log, and PoC video when reproduce the issue.
## Browser tested:
- Firefox 82.0.2 (64-bit) on Arch Linux
- Firefox 78.4.0esr (64-bit) on Arch Linux
- Firefox Nightly 84.0a1 (2020-11-05) (64-bit) on Windows 10
- Firefox Nightly ASAN 84.0a1 (2020-11-05) (64-bit) on Arch Linux
## Steps to Reproduce:
### Reload the page
1. Visit attached file: array-split-reload.html
2. Enter below text to the console:
>> const array = string.split("") ↵ (press enter)
>> const array = string.split("\n") ↵ (press enter)
3. Reload the page repeatedly
4. Tab is crashed.
### Console instant evaluation
1. Visit attached file: array-split.html
2. Open Web Developer -> Web Console (Ctrl+Shift+K)
3. Enter below text to the console:
>> const array = string.split("\n") ↵ (press enter)
>> const array = string.split("") ↵ (press enter)
4. Type to the console (without press enter):
>> string.split("")
>> string.split(" ")
>> string.split("")
>> string.split(" ")
>> string.split("")
>> string.split("\n")
>> string.split("")
If above doesn't crash the tab, reload the page, then re-type to the console (without press enter):
>> string.split("")
>> string.split(" ")
>> string.split("")
>> string.split(" ")
>> string.split("")
## What happened? (actual results)
Gah. Your tab just crashed.
```
AddressSanitizer:DEADLYSIGNAL
=================================================================
==236847==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x7fa6e7dbe0b9 bp 0x7ffe338b3620 sp 0x7ffe338b3610 T0)
==236847==The signal is caused by a READ memory access.
==236847==Hint: this fault was caused by a dereference of a high value address (see register values below). Dissassemble the provided pc to learn which register was used.
error: address range table at offset 0x5c90 has an invalid tuple (length = 0) at offset 0x5ca0
#0 0x7fa6e7dbe0b9 in runtimeFromAnyThread /builds/worker/checkouts/gecko/js/src/gc/Cell.h:335:27
#1 0x7fa6e7dbe0b9 in IsOwnedByOtherRuntime<js::BaseShape *> /builds/worker/checkouts/gecko/js/src/gc/Marking.cpp:170:23
#2 0x7fa6e7dbe0b9 in ShouldMark<js::BaseShape *> /builds/worker/checkouts/gecko/js/src/gc/Marking.cpp:885:7
#3 0x7fa6e7dbe0b9 in void DoMarking<js::BaseShape>(js::GCMarker*, js::BaseShape*) /builds/worker/checkouts/gecko/js/src/gc/Marking.cpp:941:8
#4 0x7fa6e7dbe04d in bool js::gc::TraceEdgeInternal<js::BaseShape*>(JSTracer*, js::BaseShape**, char const*) /builds/worker/checkouts/gecko/js/src/gc/Marking.cpp:675:5
#5 0x7fa6e7dc5250 in js::GCMarker::eagerlyMarkChildren(js::Shape*) /builds/worker/checkouts/gecko/js/src/gc/Marking.cpp:1249:13
#6 0x7fa6e7d94223 in markAndScan<js::Shape> /builds/worker/checkouts/gecko/js/src/gc/Marking.cpp:1032:5
#7 0x7fa6e7d94223 in traverse<js::Shape *> /builds/worker/checkouts/gecko/js/src/gc/Marking.cpp:1042:3
#8 0x7fa6e7d94223 in traverseEdge<JSObject *, js::Shape> /builds/worker/checkouts/gecko/js/src/gc/Marking.cpp:1132:3
#9 0x7fa6e7d94223 in js::GCMarker::processMarkStackTop(js::SliceBudget&) /builds/worker/checkouts/gecko/js/src/gc/Marking.cpp:2102:3
#10 0x7fa6e7d93422 in js::GCMarker::markUntilBudgetExhausted(js::SliceBudget&, js::GCMarker::ShouldReportMarkTime) /builds/worker/checkouts/gecko/js/src/gc/Marking.cpp:1835:7
#11 0x7fa6e7d4331a in js::gc::GCRuntime::markUntilBudgetExhausted(js::SliceBudget&, js::GCMarker::ShouldReportMarkTime) /builds/worker/checkouts/gecko/js/src/gc/GC.cpp:5662:17
#12 0x7fa6e7d523de in js::gc::GCRuntime::incrementalSlice(js::SliceBudget&, mozilla::Maybe<JSGCInvocationKind> const&, JS::GCReason, js::gc::AutoGCSession&) /builds/worker/checkouts/gecko/js/src/gc/GC.cpp:6795:13
#13 0x7fa6e7d55ed5 in js::gc::GCRuntime::gcCycle(bool, js::SliceBudget, mozilla::Maybe<JSGCInvocationKind> const&, JS::GCReason) /builds/worker/checkouts/gecko/js/src/gc/GC.cpp:7249:3
#14 0x7fa6e7d58213 in js::gc::GCRuntime::collect(bool, js::SliceBudget, mozilla::Maybe<JSGCInvocationKind> const&, JS::GCReason) /builds/worker/checkouts/gecko/js/src/gc/GC.cpp:7484:9
#15 0x7fa6e7d32de3 in gcSlice /builds/worker/checkouts/gecko/js/src/gc/GC.cpp:7575:3
#16 0x7fa6e7d32de3 in js::gc::GCRuntime::gcIfRequested() /builds/worker/checkouts/gecko/js/src/gc/GC.cpp:7769:7
#17 0x7fa6e7d0345b in gcIfNeededAtAllocation /builds/worker/checkouts/gecko/js/src/gc/Allocator.cpp:451:5
#18 0x7fa6e7d0345b in bool js::gc::GCRuntime::checkAllocatorState<(js::AllowGC)1>(JSContext*, js::gc::AllocKind) /builds/worker/checkouts/gecko/js/src/gc/Allocator.cpp:406:10
#19 0x7fa6e7d05674 in JSString* js::AllocateStringImpl<JSString, (js::AllowGC)1>(JSContext*, js::gc::InitialHeap) /builds/worker/checkouts/gecko/js/src/gc/Allocator.cpp:209:15
#20 0x7fa6e717665d in AllocateString<JSThinInlineString, js::CanGC> /builds/worker/checkouts/gecko/js/src/gc/Allocator.h:61:32
#21 0x7fa6e717665d in new_<js::CanGC> /builds/worker/checkouts/gecko/js/src/vm/StringType-inl.h:322:10
#22 0x7fa6e717665d in AllocateInlineString<js::CanGC, unsigned char> /builds/worker/checkouts/gecko/js/src/vm/StringType-inl.h:35:31
#23 0x7fa6e717665d in NewInlineString<js::CanGC, unsigned char> /builds/worker/checkouts/gecko/js/src/vm/StringType-inl.h:63:25
#24 0x7fa6e717665d in JSLinearString* js::Int32ToString<(js::AllowGC)1>(JSContext*, int) /builds/worker/checkouts/gecko/js/src/jsnum.cpp:816:7
#25 0x7fa6e79fd6ee in js::IdVectorToArray(JSContext*, JS::Handle<JS::GCVector<JS::PropertyKey, 0ul, js::TempAllocPolicy> >) /builds/worker/checkouts/gecko/js/src/debugger/Frame.cpp:1926:23
#26 0x7fa6e7a8c431 in js::DebuggerObject::CallData::getOwnPropertyNamesMethod() /builds/worker/checkouts/gecko/js/src/debugger/Object.cpp:778:24
#27 0x7fa6e7aad28e in bool js::DebuggerObject::CallData::ToNative<&(js::DebuggerObject::CallData::getOwnPropertyNamesMethod())>(JSContext*, unsigned int, JS::Value*) /builds/worker/checkouts/gecko/js/src/debugger/Object.cpp:243:10
#28 0x7fa652f6344f (<unknown module>)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /builds/worker/checkouts/gecko/js/src/gc/Cell.h:335:27 in runtimeFromAnyThread
==236847==ABORTING
JavaScript error: resource:///modules/ContentCrashHandlers.jsm, line 50: TypeError: can't access property "permanentKey", browser is undefined
```
|
|
1,675,926 | 15,120,160 |
Created attachment 9186460
Screenshot from 2020-11-07 13-39-05.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
1. Open a new tab
2. Type a search keyword and a search term, e. g. `w test` (if w = Wikipedia)
3. Press <kbd>Enter</kbd>, then quickly switch to another tab in the same window, or open a new tab
Actual results:
After the search result page has loaded, the Awesome Bar shows the title of the search keyword next to an empty search field.
Expected results:
It should show the URL of the currently loaded page.
|
|
1,676,116 | 15,122,598 |
Created attachment 9186609
recommendation.jpg
User Agent: Mozilla/5.0 (Linux; rv:50) Gecko
Steps to reproduce:
1. Login to web-interface of GMail
Actual results:
2a. Get 'recommendation' (see attached screenshot)
Expected results:
2b. Nothing, while 'recommendations' was already disabled.
|
|
1,676,185 | 15,122,999 |
Created attachment 9186676
BUG2.jpg
##### [Suggested Severity:]
S3
##### [Description:]
Pinning a non-sponsored topsite will move the topsites from the current position.
##### [Environment:]
Windows 10
83.0b10-trybuild
##### [Preconditions:]
There are sponsored tiles listed in the topsites.
##### [Steps:]
1. Download and install RO localized Firefox.
2. Create an user.js and set: browser.topsites.useRemoteSetting = true and browser.search.region to "RO", connecting to the staging main-preview.
3. Start the browser with the predefined profile.
4. Open a new about:preferences#home and set topsites to be shown on 4 rows.
5. Open a new tab.
6. Pick any sponsored or non-sponsored topsite and choose to pin it using the menu.
##### [Actual Result:]
The topsite is pinned. The topsite is moved from the current position to position +x, where x represents the number of sponsored topsites in front of it.
##### [Expected Result:]
The topsite is pinned in the current position.
##### [Note:]
The behavior doesn’t reproduce if the sponsored top-sites are disabled. (browser.newtabpage.activity-stream.showSponsoredTopSites = false)
SEE SCREENSHOT ATTACHED, WARNER MOVED POSITION WHEN PINNED it also loosed its image.
|
|
1,676,191 | 15,123,050 |
**Affected versions**
- Firefox 83.0b4
- Firefox 84.0a1
**Affected platforms**
- Windows 7
- macOS 10.15.7
- Ubuntu 20.04
**Steps to reproduce**
1. Launch Firefox
2. Access a page of choice and then print preview it
3. Select "Black and white" setting from Color mode
4. Print the page
**Expected result**
- The page is printed only in black and white
**Actual result**
- The page is still printed with colors
**Regression range**
- Tried with a 81.0a1 build with the old modal, but I wasn't able to find a setting to change between black and white or color
**Additional notes**
- The printer is a HP Officejet 6500 E710n-z
- Driver on Linux - HP Officejet 6500 e710n-z, hpcups 3.20.3 (color, 2-sided printing)
- Driver on macOS 10.15.7 - 4.2.2
**Suggested severity**
- S2
|
|
1,676,250 | 15,123,436 |
`urlbar.tips.tabtosearch_onboard-shown` is counted every time `UrlbarProviderTabToSearch` [sends an onboarding result to the muxer](https://searchfox.org/mozilla-central/rev/919f7400e2e12bc963ee2ae8400ef961972c3059/browser/components/urlbar/UrlbarProviderTabToSearch.jsm#289,292). This is wrong in two ways:
1. The probe is incremented on every keystroke rather than just once when the search engine domain is autofilled (see bug 1675611), and
2. The probe is incremented when the user's typed query partially matches a search engine domain, but it is not autofilled. For example, searching for "a" matches "amazon.com", but if the user's profile doesn't autofill "amazon.com", the onboarding result is not shown but the probe is incremented.
|
|
1,681,724 | 15,168,736 |
## Summary
A multithreaded Wasm project I am working on has started crashing in recent Firefox versions with a compartment mismatch. `mozregression` identified bug 1660862 (https://hg.mozilla.org/integration/autoland/rev/4d530fda38c294549a80f51db315c9279fdbec77) as the cause.
## STR
1. Clone the demo repo at https://github.com/jryans/wasm-warp-compartment-mismatch
2. `yarn install` (to get a local HTTP server with COOP / COEP headers)
3. `yarn serve`
4. Go to http://localhost:5000
5. Wait ~10s for the large Wasm blob to download
6. Crash (reproduces every time)
## Notes
* Opening the browser DevTools somehow prevents the crash (perhaps because the debugger sets the JIT down a different path)
## Crash reports
* https://crash-stats.mozilla.org/report/index/490a9c3a-53a9-464f-835c-ca7ef0201210
* https://crash-stats.mozilla.org/report/index/2fb6a7f8-941e-4574-800c-bc0da0201210
* https://crash-stats.mozilla.org/report/index/b7111bdd-e17e-4f03-a329-a06280201210
* https://crash-stats.mozilla.org/report/index/f86abc5f-ebb1-4e9d-9c4a-429c30201210
* https://crash-stats.mozilla.org/report/index/ba14e939-4ebf-4aa9-9d86-a8cd20201210
* https://crash-stats.mozilla.org/report/index/605f946a-437e-4cba-872d-214ee0201210
|
|
1,681,818 | 15,169,327 |
Created attachment 9192484
video of bug
**[Sugested Severity:]**
S3
**[Description:]**
when I remove search shortcuts in a particular order and then press "Restore Default Search Engines", Bookmarks, Tabs, and History are removed forever.
**[Steps:]**
1. Open Firefox with a new profile.
2. Go to about:preferences#search
3. Remove two search shortcuts immediately above Bookmarks
4. Remove the rest of bookmarks from top to bottom. It's important to press remove twice or thrice after removing all possible search engines.
5. Hit Restore Default Search Engines
**[Actual result:]**
Search engines are restored but bookmarks, tabs, and history are lost forever
**[Expected result:]**
Search engines are restored and bookmarks, tabs, and history are kept
|
|
1,681,909 | 15,170,001 |
Steps:
1. Go to any web site. I used [this](https://github.com/WebKit/webkit/blob/cce091ba67241e75a8b3ce91bc029b1223d51d90/Source/WebCore/accessibility/AccessibilityList.cpp#L136) code listing. When the page loads, VoiceOver does not focus on the line that is being linked to, so you have to use the Search feature to quickly get to the starting line number.
2. Press VoiceOver+F and enter 136.
3. Press Enter.
Expected: VoiceOver jumps to the table and onto the line number 136.
Actual: VoiceOver lands on the "Go to Homepage" link.
I can reproduce search failures like this on any page, VoiceOver usually just jumps to the next focusable element.
Setting this to a P2 because this is a common usage pattern by VoiceOver usrs on MacOS. They use VoiceOver search rather than Find In Page.
|
|
1,682,005 | 15,170,529 |
From github: https://github.com/mozilla-mobile/fenix/issues/16203.
> ## Steps to reproduce
> 1. Make sure you are signed in with your FxA account, and have multiple bookmarks saved.
> 2. Go to Bookmarks, select at least 6-7 pages, and choose to open them in new tabs.
> 3. Go to the tabs tray and open each page, one by one. Let the pages load.
>
> ### Expected behavior
> The browsing should go smoothly, without issues.
>
> ### Actual behavior
> Fenix crashes. First, the tabs tray remains blank, and the user cannot access anything else. Fenix freezes. Force closed doesn't solve the issue every time.
>
> ### Device information
> * Android device: Samsung Galaxy Tab A6 (Android 5.1.1)
> * Fenix version: 10/26 Nightly build
>
> ### Notes
> * Reproduced it 2/2. Did not reproduced the crash when opening multiple pages from History.
> * Not reproducible on Xiaomi Mi8 Lite (Android 9)
>
> ### Details of the crash
> 0e2f9fdd-44b8-4a64-8a8c-1955d37df93b
> <native crash>
> * Socorro: https://crash-stats.mozilla.org/report/index/bp-da124479-34dc-4670-9c7d-880c10201027
> ----
> <native crash>
>
Change performed by the [Move to Bugzilla add-on](https://addons.mozilla.org/en-US/firefox/addon/move-to-bugzilla/).
|
|
1,682,877 | 15,179,223 |
[Tracking Requested - why for this release]: Reproducible crash after cancel file picker when print using "Microsoft Print to PDF"
Crash report: https://crash-stats.mozilla.org/report/index/c8d7e558-a2a1-486a-87cf-d20490201216
MOZ_CRASH Reason: ```MOZ_CRASH(IPC FatalError in the parent process!)```
Top 10 frames of crashing thread:
```
0 xul.dll mozilla::ipc::FatalError ipc/glue/ProtocolUtils.cpp:189
1 xul.dll static mozilla::ipc::IPDLParamTraits<mozilla::embedding::PrintData>::Read ipc/ipdl/PPrintingTypes.cpp:230
2 xul.dll mozilla::embedding::PPrintingParent::OnMessageReceived ipc/ipdl/PPrintingParent.cpp:606
3 xul.dll mozilla::dom::PContentParent::OnMessageReceived ipc/ipdl/PContentParent.cpp:14913
4 xul.dll mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2073
5 xul.dll mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:739
6 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1200
7 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
8 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:327
9 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:309
```
Steps to reproduce:
1. Open any web page. e.g. https://ftp.mozilla.org/pub/firefox/nightly/2020/11/
2. Ctrl+P and choose "Microsoft Print to PDF" and Print
3. When File picker dialog opened, cancel the dialog.
Actual results:
Browser crash
Expected results:
No crash.
|
|
1,683,318 | 15,182,473 |
Created attachment 9193923
localPages.gif
**Affected versions**
* Firefox 86.0a1 (BuildId:20201218095607)
**Affected platforms**
* Windows 10 64bit
* macOS 10.14
* Ubuntu 20.04 64bit.
**Steps to reproduce**
1. Launch Firefox.
2. Open a random webpage (non about/local page).
3. Open a different tab and access the about:support page.
4. Hit CTRL + P on the about page.
**Expected result**
* The print preview is displayed for the about page.
**Actual result**
* The print preview is displayed on a different tab.
**Regression Range**
* This seems to be a regression:
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6307b67c66ffa34fdbdb8481cc95f58a5cc8df29&tochange=84d74806a0f714937f8de369fef595c5220f9381
* Potential regressor: Bug 1670122
**Notes**
* For further information please observe the attached screencast.
* It seems that the only way to trigger the print preview for the local pages is by closing all the other tabs.
* This issue is reproducible with both Fission enabled and disabled.
* [Suggested Severity] I think that S3 fits for this issue.
|
|
1,683,520 | 15,183,751 |
Created attachment 9194117
nss_ecdsa_verify_poc.cpp
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0
Steps to reproduce:
ECDSA verification using the following parameters
public key X: 3287081257432259362393812976079081421412151647138720924241920297746134087425717291680098733199669585693238116089896462389392776287267107954818562468740630350
public key Y: 5047884165615205077529306077209628022504281088340332331957752940735437106855961661784277419343640566825146183053470636970974876726952117391717027289712479371
cleartext: {0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00} (59 bytes)
signature R: 2398833381252220480870377713423558965855096706378426427899888394173467690495466969487925690736977872006638457011575098146569145494858882127318415314133391193
signature S: 2318419597317490008949351307731018419258702345790149047845632642305600089435507511726637998566288744337568482741407664437071146659987012556995409299000152793
digest: NULL
using the "ECDSA_VerifyDigest" function (where 'cleartext' is the data that is passed as-is to this function, not hashed) fails, but it succeeds in OpenSSL, Botan and wolfCrypt, which suggests that NSS is wrong.
Probably not a security issue, unless whatever bug is causing this can be exploited into doing the reverse (verifying signatures when it should not), so I'm marking it as security bug just in case.
Actual results:
Print:
Verify: 0
Expected results:
Print:
Verify: 1
|
|
1,683,658 | 15,185,887 |
**Affected versions**
* Firefox 86.0a1 (BuildId:20201218095607)
* Firefox 85.0b4 (BuildId:20201220193140)
**Affected platforms**
* Windows 10 64bit (NVDA version 2020.3)
* macOS 10.14 (VoiceOVer)
**Steps to reproduce**
1. Launch Firefox.
2. Open a random webpage
3. Hit CTRL + P in order to open the print preview.
4. Tab through the available print preview options until you reach the “Pages per Sheet”
**Expected result**
* NVDA reads “Pages per sheet combo box 1 collapsed”
**Actual result**
* NVDA reads “combo box 1 collapsed”
**Regression Range**
* I don’t think that this is a regression.
**Notes**
* [Suggested Severity] I think that S3 fits for this issue.
|
|
1,684,157 | 15,194,240 |
Created attachment 9194642
2020-12-24_11h51_48.gif
**[Notes]:**
- The issue is reproducible if the OS Theme is set to “Light” for the following Firefox themes: “Default”, “Light”, and “Alpenglow”.
- The issue is also reproducible if the OS Theme is set to “Dark” for the following Firefox theme: “Light”.
- The issue is not reproducible for Firefox “Dark” theme.
- The issue is not reproducible if the OS Theme is set to “Dark” for the following Firefox themes: “Default”, “Dark”, and “Alpenglow”.
**[Affected Versions]:**
- Firefox Beta 85.0b4 (Build ID: 20201220193140)
- Firefox Nightly 86.0a1 (Build ID: 20201223212750)
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15.6
- Ubuntu Linux 20.04 x64
**[Prerequisites]:**
- Have the `browser.newtabpage.activity-stream.newNewtabExperience.enabled` set to `true`.
- Have the Firefox browser theme set to “Light”.
**[Steps to reproduce]:**
1. Start the Firefox profile from prerequisites.
2. Open a “New Tab” page.
3. Click the “Personalize” button located in the top right corner of the page.
4. Focus the “Customize menu”, focus each element using keyboard navigation, and observe the elements.
**[Expected results]:**
- All the elements are visibly focused using keyboard navigation.
**[Actual results]:**
- Only the “Manage more settings” button is visibly focused using keyboard navigation.
**[Additional Notes]:**
- Attached 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.