Bug ID
int64 961
1.91M
| Comment ID
int64 3.98k
17.1M
| Author
stringlengths 8
48
| Comment Text
stringlengths 1
64.3k
⌀ |
|---|---|---|---|
1,620,782 | 14,681,842 |
**Steps to reproduce**
1. Open the console
1. Evaluate `new Set(Array.from({length: 10}, (_, i) => ({item: i})))`
1. Expand the set, the `<entries>` node and the `0` entry
**Expected results**
The `0` entry is expanded and I can see `item: 0`
**Actual results**
The `0` entry isn't expanded
---
Note that this doesn't impact Sets with more than 10 entries (e.g. `new Set(Array.from({length: 11}, (_, i) => ({item: i})))` is fine)
This does not impact `Map`.
This is probably because before fetching new properties we check if we already have them in the preview (https://searchfox.org/mozilla-central/rev/5a52cec97c41ae1eda9412dfe6f4099a9af4c7dd/devtools/client/debugger/packages/devtools-reps/src/object-inspector/utils/load-properties.js#182), and that probably triggers some issue
|
|
1,620,799 | 14,681,986 |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Steps to reproduce:
Build with arm32 without neon support.
Actual results:
/home/giuliobenetti/git/test-libnss/br-arm-cortex-a9-glibc/host/bin/arm-linux-gcc -o Linux2.6_arm_arm-linux-gcc.br_real_glibc_PTH_DBG.OBJ/Linux_SINGLE_SHLIB/gcm-arm32-neon.o -c -std=c99 -g -fPIC -pipe -ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -Wall -Wshadow -DNSS_NO_GCC48 -DXP_UNIX -DSHLIB_SUFFIX=\"so\" -DSHLIB_PREFIX=\"lib\" -DSHLIB_VERSION=\"3\" -DSOFTOKEN_SHLIB_VERSION=\"3\" -DRIJNDAEL_INCLUDE_TABLES -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE -D_REENTRANT -DNSS_NO_INIT_SUPPORT -DNSS_DISABLE_ALTIVEC -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -DFREEBL_NO_DEPEND -DFREEBL_LOWHASH -DUSE_HW_AES -DMP_ASSEMBLY_MULTIPLY -DMP_ASSEMBLY_SQUARE -DMP_USE_UINT_DIGIT -DSHA_NO_LONG_LONG -DKRML_VERIFIED_UINT128 -DMP_API_COMPATIBLE -I/home/giuliobenetti/git/test-libnss/br-arm-cortex-a9-glibc/host/arm-buildroot-linux-gnueabihf/sysroot/usr/include/nspr -I/home/giuliobenetti/git/test-libnss/br-arm-cortex-a9-glibc/build/libnss-3.51/dist/include -I../../../dist/public/nss -I../../../dist/private/nss -Impi -Iecl -Iverified -Iverified/kremlin/include -Iverified/kremlin/kremlib/dist/minimal -march=armv7 -mfpu=neon gcm-arm32-neon.c
cc1: error: target CPU does not support ARM mode
Expected results:
Need a way to avoid building gcm-arm32-neon.c and build gcm.c instead, so let's introduce NSS_DISABLE_GCM_ARM32_NEON to allow disabling it on arm32
|
|
1,620,818 | 14,682,083 |
Created attachment 9131731
browser-ff.txt
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.106 Safari/537.36
Steps to reproduce:
I have been randomly obtaining this Use-After-Free at a specific website that I was investigating. I don't have a reproducer so far. Not sure if it's due to recent Firefox code changes or has really been triggered intentionally since it was with a custom Firefox build and m-c-20200226162551-fuzzing-asan-opt.
Actual results:
```
=================================================================
==27386==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0001009c0 at pc 0x7f098a30d54a bp 0x7ffe5a8f3a60 sp 0x7ffe5a8f3a58
READ of size 8 at 0x60e0001009c0 thread T0 (Web Content)
#0 0x7f098a30d549 in SynchronizeLayoutHistoryState /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:3302:12
#1 0x7f098a30d549 in non-virtual thunk to nsDocShell::SynchronizeLayoutHistoryState() /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp
#2 0x7f09877e53f2 in nsDocumentViewer::Close(nsISHEntry*) /builds/worker/workspace/build/src/layout/base/nsDocumentViewer.cpp:1656:44
#3 0x7f09877e487d in nsDocumentViewer::~nsDocumentViewer() /builds/worker/workspace/build/src/layout/base/nsDocumentViewer.cpp:627:5
#4 0x7f09877e6ccd in nsDocumentViewer::~nsDocumentViewer() /builds/worker/workspace/build/src/layout/base/nsDocumentViewer.cpp:625:39
#5 0x7f09877e4486 in nsDocumentViewer::Release() /builds/worker/workspace/build/src/layout/base/nsDocumentViewer.cpp:613:1
#6 0x7f098a2e7cc7 in ~nsCOMPtr_base /builds/worker/workspace/build/src/obj-firefox/dist/include/nsCOMPtr.h:330:7
#7 0x7f098a2e7cc7 in nsDocShell::~nsDocShell() /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:450:1
#8 0x7f098a2e937d in nsDocShell::~nsDocShell() /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:411:27
#9 0x7f097edb2c88 in SnowWhiteKiller::Visit(nsPurpleBuffer&, nsPurpleBufferEntry*) /builds/worker/workspace/build/src/xpcom/base/nsCycleCollector.cpp:2460:9
#10 0x7f097ed91876 in void nsPurpleBuffer::VisitEntries<SnowWhiteKiller>(SnowWhiteKiller&) /builds/worker/workspace/build/src/xpcom/base/nsCycleCollector.cpp:942:23
#11 0x7f097ed92135 in nsCycleCollector::FreeSnowWhiteWithBudget(js::SliceBudget&) /builds/worker/workspace/build/src/xpcom/base/nsCycleCollector.cpp:2625:14
#12 0x7f09813d97dc in AsyncFreeSnowWhite::Run() /builds/worker/workspace/build/src/js/xpconnect/src/XPCJSRuntime.cpp:147:9
#13 0x7f097ef6cea8 in IdleRunnableWrapper::Run() /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:326:22
#14 0x7f097ef48bd8 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:1220:14
#15 0x7f097ef53a3c in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:481:10
#16 0x7f09801a9fcf in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/workspace/build/src/ipc/glue/MessagePump.cpp:87:21
#17 0x7f098009d1f7 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:315:10
#18 0x7f098009d1f7 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:308:3
#19 0x7f098009d1f7 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:290:3
#20 0x7f0987230cb8 in nsBaseAppShell::Run() /builds/worker/workspace/build/src/widget/nsBaseAppShell.cpp:137:27
#21 0x7f098ad63ca6 in XRE_RunAppShell() /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:944:20
#22 0x7f098009d1f7 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:315:10
#23 0x7f098009d1f7 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:308:3
#24 0x7f098009d1f7 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:290:3
#25 0x7f098ad63269 in XRE_InitChildProcess(int, char**, XREChildData const*) /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:779:34
#26 0x55fdb83a2433 in content_process_main /builds/worker/workspace/build/src/browser/app/../../ipc/contentproc/plugin-container.cpp:56:28
#27 0x55fdb83a2433 in main /builds/worker/workspace/build/src/browser/app/nsBrowserApp.cpp:303:18
#28 0x7f099ad2c1e2 in __libc_start_main /build/glibc-4WA41p/glibc-2.30/csu/../csu/libc-start.c:308:16
#29 0x55fdb82f7ddc in _start (/home/fuzzer/dev/m-c-20200226162551-fuzzing-asan-opt/firefox+0x9bddc)
0x60e0001009c0 is located 0 bytes inside of 160-byte region [0x60e0001009c0,0x60e000100a60)
freed by thread T0 (Web Content) here:
#0 0x55fdb836faad in free /builds/worker/fetches/llvm-project/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:123:3
#1 0x7f098a3be096 in nsSHEntry::Release() /builds/worker/workspace/build/src/docshell/shistory/nsSHEntry.cpp:81:1
#2 0x7f098a2e79a4 in ~nsCOMPtr_base /builds/worker/workspace/build/src/obj-firefox/dist/include/nsCOMPtr.h:330:7
#3 0x7f098a2e79a4 in nsDocShell::~nsDocShell() /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:450:1
#4 0x7f098a2e937d in nsDocShell::~nsDocShell() /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:411:27
#5 0x7f097edb2c88 in SnowWhiteKiller::Visit(nsPurpleBuffer&, nsPurpleBufferEntry*) /builds/worker/workspace/build/src/xpcom/base/nsCycleCollector.cpp:2460:9
#6 0x7f097ed91876 in void nsPurpleBuffer::VisitEntries<SnowWhiteKiller>(SnowWhiteKiller&) /builds/worker/workspace/build/src/xpcom/base/nsCycleCollector.cpp:942:23
#7 0x7f097ed92135 in nsCycleCollector::FreeSnowWhiteWithBudget(js::SliceBudget&) /builds/worker/workspace/build/src/xpcom/base/nsCycleCollector.cpp:2625:14
#8 0x7f09813d97dc in AsyncFreeSnowWhite::Run() /builds/worker/workspace/build/src/js/xpconnect/src/XPCJSRuntime.cpp:147:9
#9 0x7f097ef6cea8 in IdleRunnableWrapper::Run() /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:326:22
#10 0x7f097ef48bd8 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:1220:14
#11 0x7f097ef53a3c in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:481:10
#12 0x7f09801a9fcf in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/workspace/build/src/ipc/glue/MessagePump.cpp:87:21
#13 0x7f098009d1f7 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:315:10
#14 0x7f098009d1f7 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:308:3
#15 0x7f098009d1f7 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:290:3
#16 0x7f0987230cb8 in nsBaseAppShell::Run() /builds/worker/workspace/build/src/widget/nsBaseAppShell.cpp:137:27
#17 0x7f098ad63ca6 in XRE_RunAppShell() /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:944:20
#18 0x7f098009d1f7 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:315:10
#19 0x7f098009d1f7 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:308:3
#20 0x7f098009d1f7 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:290:3
#21 0x7f098ad63269 in XRE_InitChildProcess(int, char**, XREChildData const*) /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:779:34
#22 0x55fdb83a2433 in content_process_main /builds/worker/workspace/build/src/browser/app/../../ipc/contentproc/plugin-container.cpp:56:28
#23 0x55fdb83a2433 in main /builds/worker/workspace/build/src/browser/app/nsBrowserApp.cpp:303:18
#24 0x7f099ad2c1e2 in __libc_start_main /build/glibc-4WA41p/glibc-2.30/csu/../csu/libc-start.c:308:16
previously allocated by thread T0 (Web Content) here:
#0 0x55fdb836fd2d in malloc /builds/worker/fetches/llvm-project/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:145:3
#1 0x55fdb83a582d in moz_xmalloc /builds/worker/workspace/build/src/memory/mozalloc/mozalloc.cpp:52:15
#2 0x7f098a3ae651 in operator new /builds/worker/workspace/build/src/obj-firefox/dist/include/mozilla/cxxalloc.h:33:10
#3 0x7f098a3ae651 in mozilla::dom::CreateSHEntryForDocShell(nsISHistory*) /builds/worker/workspace/build/src/docshell/shistory/ChildSHistory.cpp:126:32
#4 0x7f098a3525d4 in nsDocShell::AddToSessionHistory(nsIURI*, nsIChannel*, nsIPrincipal*, nsIPrincipal*, nsIPrincipal*, nsIContentSecurityPolicy*, bool, nsISHEntry**) /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:11073:13
#5 0x7f098a33efc3 in nsDocShell::OnNewURI(nsIURI*, nsIChannel*, nsIPrincipal*, nsIPrincipal*, nsIPrincipal*, unsigned int, nsIContentSecurityPolicy*, bool, bool, bool) /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:10540:13
#6 0x7f098a33fbac in nsDocShell::OnLoadingSite(nsIChannel*, bool, bool) /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:10602:10
#7 0x7f098a2d9a8a in nsDocShell::CreateContentViewer(nsTSubstring<char> const&, nsIRequest*, nsIStreamListener**) /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:7705:33
#8 0x7f098a2d7c9c in nsDSURIContentListener::DoContent(nsTSubstring<char> const&, bool, nsIRequest*, nsIStreamListener**, bool*) /builds/worker/workspace/build/src/docshell/base/nsDSURIContentListener.cpp:168:20
#9 0x7f098195227a in nsDocumentOpenInfo::TryContentListener(nsIURIContentListener*, nsIChannel*) /builds/worker/workspace/build/src/uriloader/base/nsURILoader.cpp:632:18
#10 0x7f098194f84a in nsDocumentOpenInfo::DispatchContent(nsIRequest*, nsISupports*) /builds/worker/workspace/build/src/uriloader/base/nsURILoader.cpp:313:9
#11 0x7f098194e211 in nsDocumentOpenInfo::OnStartRequest(nsIRequest*) /builds/worker/workspace/build/src/uriloader/base/nsURILoader.cpp:191:8
#12 0x7f097faa807c in mozilla::net::HttpChannelChild::DoOnStartRequest(nsIRequest*, nsISupports*) /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:707:20
#13 0x7f097fab671c in mozilla::net::HttpChannelChild::OnStartRequest(nsresult const&, mozilla::net::nsHttpResponseHead const&, bool const&, mozilla::net::nsHttpHeaderArray const&, mozilla::net::ParentLoadInfoForwarderArgs const&, bool const&, bool const&, bool const&, unsigned long const&, int const&, unsigned int const&, nsTString<char> const&, nsTString<char> const&, mozilla::net::NetAddr const&, mozilla::net::NetAddr const&, unsigned int const&, nsTString<char> const&, long const&, bool const&, bool const&, bool const&, mozilla::net::ResourceTimingStructArgs const&, bool const&, mozilla::Maybe<unsigned int> const&, bool const&, nsILoadInfo::CrossOriginOpenerPolicy const&) /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:557:3
#14 0x7f097fb6d806 in operator() /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:411:15
#15 0x7f097fb6d806 in std::_Function_handler<void (), mozilla::net::HttpChannelChild::RecvOnStartRequest(nsresult const&, mozilla::net::nsHttpResponseHead const&, bool const&, mozilla::net::nsHttpHeaderArray const&, mozilla::net::ParentLoadInfoForwarderArgs const&, bool const&, bool const&, bool const&, unsigned long const&, int const&, unsigned int const&, nsTString<char> const&, nsTString<char> const&, mozilla::net::NetAddr const&, mozilla::net::NetAddr const&, short const&, unsigned int const&, nsTString<char> const&, long const&, bool const&, bool const&, bool const&, mozilla::net::ResourceTimingStructArgs const&, bool const&, mozilla::Maybe<unsigned int> const&, bool const&, nsILoadInfo::CrossOriginOpenerPolicy const&)::$_5>::_M_invoke(std::_Any_data const&) /builds/worker/fetches/clang/bin/../lib/gcc/x86_64-unknown-linux-gnu/7.4.0/../../../../include/c++/7.4.0/bits/std_function.h:316:2
#16 0x7f097f8e83ba in mozilla::net::ChannelEventQueue::RunOrEnqueue(mozilla::net::ChannelEvent*, bool) /builds/worker/workspace/build/src/obj-firefox/dist/include/mozilla/net/ChannelEventQueue.h:260:10
#17 0x7f097fab47ff in mozilla::net::HttpChannelChild::RecvOnStartRequest(nsresult const&, mozilla::net::nsHttpResponseHead const&, bool const&, mozilla::net::nsHttpHeaderArray const&, mozilla::net::ParentLoadInfoForwarderArgs const&, bool const&, bool const&, bool const&, unsigned long const&, int const&, unsigned int const&, nsTString<char> const&, nsTString<char> const&, mozilla::net::NetAddr const&, mozilla::net::NetAddr const&, short const&, unsigned int const&, nsTString<char> const&, long const&, bool const&, bool const&, bool const&, mozilla::net::ResourceTimingStructArgs const&, bool const&, mozilla::Maybe<unsigned int> const&, bool const&, nsILoadInfo::CrossOriginOpenerPolicy const&) /builds/worker/workspace/build/src/netwerk/protocol/http/HttpChannelChild.cpp:401:12
#18 0x7f098086677c in mozilla::net::PHttpChannelChild::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/build/src/obj-firefox/ipc/ipdl/PHttpChannelChild.cpp:862:28
#19 0x7f098057a777 in mozilla::dom::PContentChild::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/build/src/obj-firefox/ipc/ipdl/PContentChild.cpp:8563:32
#20 0x7f098019e122 in mozilla::ipc::MessageChannel::DispatchAsyncMessage(mozilla::ipc::ActorLifecycleProxy*, IPC::Message const&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:2214:25
#21 0x7f098019932a in mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:2136:9
SUMMARY: AddressSanitizer: heap-use-after-free /builds/worker/workspace/build/src/docshell/base/nsDocShell.cpp:3302:12 in SynchronizeLayoutHistoryState
Shadow bytes around the buggy address:
0x0c1c800180e0: fa fa fa fa fd fd fd fd fd fd fd fd fd fd fd fd
0x0c1c800180f0: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa
0x0c1c80018100: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
0x0c1c80018110: fd fd fd fd fa fa fa fa fa fa fa fa 00 00 00 00
0x0c1c80018120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 fa
=>0x0c1c80018130: fa fa fa fa fa fa fa fa[fd]fd fd fd fd fd fd fd
0x0c1c80018140: fd fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa
0x0c1c80018150: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c1c80018160: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c1c80018170: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c1c80018180: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==27386==ABORTING
```
|
|
1,620,824 | 14,682,112 |
Created attachment 9131735
site load fails.mp4
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Build ID: 20200307213339
Tabs may not load properly only when right after starting the browser.
Here are the requirements which I cannot reduce any further:
1. `network.trr.fetch_off_main_thread` is `true`
2. [Firefox Private Network](https://fpn.firefox.com/browser) extension is logged in (I use it outside US so your result may vary)
3. [uMatrix](https://addons.mozilla.org/firefox/addon/umatrix/) is enabled. Settings (and rules) leave as default.
4. (Maybe) a slow computer, network, or Firefox profile
### Steps to reproduce
1. Use Nightly 2020-03-07 build in a new profile. Prepare the above stuff.
2. Open https://www.reddit.com. Pinning the tab is not necessary but easier to test since the tab will automatically load right after starting the browser.
** I think any (heavy) site would work as long as it does not load instantly.
3. Focus the tab, restart browser either by:
a. `Ctrl-Alt-R` in *Browser Console*; or
b. Enable `Restore previous session`, close with X and start browser again.
4. Repeat Step 3 if you fail to reproduce the issue.
### Actual result
(Please refer to the attached video.)
The tab fails to load. Reloading it brings everything back to normal.
The issue can be reproduced 100% on my main profile, which I do not want to share, but only occasionally in a new profile, as seen in the attached video.
The maximum number of pinned tabs failed to load I have seen is 3 which is the maximum number of concurrent restores after restarting the browser.
### Notes
I cannot reproduce the issue if either requirement 1, 2, or 3 is omitted. Or maybe I did not re-test those conditions enough.
Other sites that fail to load include but not limited to logged-in [Gmail](https://mail.google.com/), [Google Calendar](https://calendar.google.com/), and [Pocket](https://app.getpocket.com/).
|
|
1,620,876 | 14,682,397 |
https://play.gl/ shows only black on nightly, but it works on 73.
There are tons of warnings, one about context lost, a bunch of them about using an unlinked program.
|
|
1,620,921 | 14,683,979 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
* find a canvas image, e.g. here https://tcdw.github.io/servalclock/
* right click on the image
* middle click "View Image" menu entry; or click+left click, shift+left click
Actual results:
Firefox says the URL is invalid.
Expected results:
Firefox should display the image in the newly opened tab / window.
150:21.81 INFO: Last good revision: 398b5e6b2dab72d5be60bc81b0fda2d2c27bfb25
150:21.81 INFO: First bad revision: b9740bd7bf8f1a0656c09a88fe6d7ee00586ee60
150:21.81 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=398b5e6b2dab72d5be60bc81b0fda2d2c27bfb25&tochange=b9740bd7bf8f1a0656c09a88fe6d7ee00586ee60
Being able to view images in new tabs is useful to view images closely or simultaneously without the need to save images on disk. The "Copy Image" is not available on canvas so it's useful for copying images too.
|
|
1,621,007 | 14,684,717 |
Created attachment 9131974
ss1.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
1. set the render engine to Direct3D 11.
2. open https://jsfiddle.net/copyliu/waLrm9jv/2/ and click run
3. shows "TEST PAGE" text broken.
Actual results:
"TEST PAGE" in test page is broken, see screenshot : ss1.png
Expected results:
"TEST PAGE" in test page is rendered correct.
|
|
1,621,241 | 14,686,346 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
1. Use a platform where safe area insets should always be zero (e.g. Windows).
2. Play around with anything that uses safe area insets, e.g. https://temp.chrismorgan.info/safe-area-inset.html (shows the numbers and highlights the safe area insets on the viewport).
3. Resize the viewport after loading the document.
Actual results:
Although on page load the safe area insets are zero, on resize, the bottom and right safe area insets become non-zero, seeming to duplicating the space allocations of UI elements from the opposite side.
I’m seeing `env(safe-area-inset-bottom)` becoming 28.5px when the window is maximised, or 25px when the window is not maximised. (These numbers look about right to correspond to the title bar in *some* way, though not directly as with the sidebar about to be discussed. I also have `#TabsToolbar` hidden via userChrome.css, but I don’t believe that’s relevant.)
I have a sidebar (Tree Style Tab) open normally, and when it’s open the browser seems to want to limit the safe area to the screen width minus *twice* the sidebar width. That is, with a 1500px-wide screen, a maximised window (outerWidth ~1500px) and a 200px sidebar (hence innerWidth 1300px), `safe-area-inset-right` will be 200px, and the safe area 1100px wide; unmaximising the window to 1400px wide (innerWidth 1200px), `safe-area-inset-right` will be 100px (again safe area 1100px wide). Shrink it further and by 1300px wide (innerWidth 1100px) `safe-area-inset-right` will have reached zero, where it will stay. (I confess that I’m now trying to imagine a situation in which negative safe area insets would be reasonable!)
My device has a scaling factor of 2×, but I do not believe that this is relevant—I switched it to 1× briefly to be reasonably sure (though without restarting everything).
Expected results:
The safe area insets should have stayed at zero.
This is a fairly recent regression, probably from the last week, fairly certainly from the last two.
|
|
1,621,503 | 14,688,334 |
After updating uBlock origin from version `1.25.0` to `1.25.2`, the add-on is in an inconsistent state, making it unresponsive. For more details see the [Fenix related issue](https://github.com/mozilla-mobile/fenix/issues/9082).
Steps to reproduce:
1. Install uBlock version [1.25.0](https://addons.mozilla.org/firefox/downloads/file/3509800/ublock_origin-1.25.0-an+fx.xpi)
2. Request to update to version `1.25.2`.
I believe the issue is related that we are not honouring the below contract with [runtime.onUpdateAvailable](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/onUpdateAvailable). As uBlock is listening to [runtime.onUpdateAvailable](https://github.com/gorhill/uBlock/blob/2cbbc300847de5451815291446f2403db0dca371/src/js/start.js#L381) but doesn't call `runtime.reload()` , the add-on is getting into a weird inconsistent state, where even if the [user restarts the app](https://github.com/mozilla-mobile/fenix/issues/9082#issuecomment-597163715), the extension is not usable anymore until the add-on is [disable and enable back](https://github.com/mozilla-mobile/fenix/issues/9082#issuecomment-597288606) where `runtime.reload()` is called.
`<blockquote>`
If the extension is not listening for this event when an update becomes available, the extension is reloaded immediately and the update is applied. If the extension is listening, then the update will be applied the next time the extension is reloaded. This happens if:
- the browser is restarted [<- (This is not being honoured)](https://github.com/mozilla-mobile/fenix/issues/9082#issuecomment-597163715)
- the extension is disabled and re-enabled [<- (This is being honoured)](https://github.com/mozilla-mobile/fenix/issues/9082#issuecomment-597288606)
- the extension explicitly reloads itself by calling runtime.reload().
`</blockquote>`
|
|
1,621,523 | 14,688,419 |
Created attachment 9132464
drawing failure.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Steps to reproduce:
We updated to Firefox 74, and opened a scene in the Sumerian editor
Actual results:
Objects in the 3D Sumerian scene are not visible, only the grid. When viewed in play mode, with the grid disabled, we can see the objects rendered correctly. Based on Spector js captures, our conclusion is that the three transparent layers we have in the editor: gridRendering, cameraDebugRendering and LightDebugRendering, are not blending with underneath canvas the same way they did in previous versions. Instead, they are now overriding the canvas.
We are attempting to resolve the issue, but are reduced to diffing various builds until we find one that works. Do you all know of any changes to 3d blending or drawing schemas that may have changed in 74? Any help to resolve this issue would be appreciated.
I will update later with an observable scene, if possible
Expected results:
The 3D scene was previously drawing correctly.
|
|
1,629,928 | 14,754,343 |
Created attachment 9140470
firefoxnarrow.png
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Updated to Firefox with the new address bar, on my (Fedora Linux) system where Firefox is in a 1080x1920 window (maximized on a portrait-orientation FHD screen).
Actual results:
The autocomplete / suggestion / whatever list that appears when you start typing in the new address bar seems now to only ever render as wide as the address bar itself. Which on a 1080 wide window, with a search box and a few plugins, is only about 573 pixels wide. The margins and the 'fade out' effect on the right hand side of the list effectively eat a little more of that, to the point where you almost never get anywhere close to the full URL *or* full title of any page in the list. This is particular a problem for trying to sort through many similar URLs, for instance...Bugzilla bugs. See attached screenshot.
Expected results:
It should be possible for this UI element to be much wider, as it was in the previous design. I understand that this doesn't matter a lot if the window is very wide, as is often the case on landscape-oriented screens, but it's a big problem if it isn't.
|
|
1,629,947 | 14,754,463 |
Created attachment 9140479
key_focus.mp4
##### [Environment:]
77.0a1 20200414094457
76.0b4 20200412214314
using:
Ubuntu 18.04, Windows 10, Mac 10.13.6
##### [Steps:]
1. Start-up Firefox.
2. Access any login form.
3. Input any text as a password in the login form, then focus away.
4. Highlight the grey key in the permissions pannel.
5. Highlight the grey key, then click exactly on the key, then focus away.
6. Highlight again the grey key, then click towards any of the corners of the highlight.
##### [Actual Result:]
5. There is a click animation and password Message pannel is opened.
6. There is a click animation but password Message pannel is not opened.
##### [Expected Result:]
In both cases, the password permissions pannel is opened.
##### [Note:]
1. Althought the fix in bug 1570391 makes this issue a lot more visible and gives the impression the permission dismissed doorhanger icon doesn't always work, it is my impression that this is an older deeper issue here.
2. Towards the end of the screencast, when the focus moves from the grey icon toward the security icone, the highlight remains on the dismissed password icon, the highlight encapsulating now both of the icons - a separate bug can be logged for this issue if need be, but it seems to me that is somehow the same issue as bug 1570391.
##### [Regression Range:]
2020-04-14T18:21:30: DEBUG : Found commit message:
Bug 1570391 - Trigger highlighting when hovering over notification icon. r=johannh,pbz
Differential Revision: https://phabricator.services.mozilla.com/D67737
|
|
1,630,167 | 14,756,114 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
1. Install tabs-tabs-tabs[1], Tab Center Reborn[2] or any other extension that has the tabs permission
[1]: https://github.com/mdn/webextensions-examples/tree/master/tabs-tabs-tabs
[2]: https://addons.mozilla.org/firefox/addon/tabcenter-reborn/
2. Type `await browser.tabs.query({});` and get the id of a tab you can discard
3. Type `await browser.tabs.reload(tabId); setTimeout(() => browser.tabs.discard(tabId), 30);` by using the the tab id of above.
Note that this is not a theoretical case I can trigger it by doing F5 and unloading the tab with an extension that adds a context menu entry to do that.
Actual results:
Tab is discarded but the loading spinner doesn’t go away.
`await browser.tabs.get(tabId);` reports the tab as both `discarded: true` and `status: loading`.
Expected results:
– Discarded tab get back its favicon, instead of the loading spinner.
– WebExtensions API reports its status as `complete` instead of `loading` like for other discarded tabs.
|
|
1,630,171 | 14,756,132 |
**Filed by:** apavel [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=297680705&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/HhXXi3lFS82PgfUoHv9CRw/runs/0/artifacts/public/logs/live_backing.log
---
[task 2020-04-15T05:37:51.259Z] 05:37:51 INFO - TEST-START | browser/components/newtab/test/browser/browser_aboutwelcome_observer.js
[task 2020-04-15T05:37:51.285Z] 05:37:51 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak ++DOCSHELL 0x14b2cc800 == 13 [pid = 1787] [id = {c97d490f-92b7-c54a-8ad3-cc505ef74aa6}]
[task 2020-04-15T05:37:51.285Z] 05:37:51 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 37 (0x112afd200) [pid = 1787] [serial = 37] [outer = 0x0]
[task 2020-04-15T05:37:51.285Z] 05:37:51 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 38 (0x14b328c00) [pid = 1787] [serial = 38] [outer = 0x112afd200]
[task 2020-04-15T05:37:51.367Z] 05:37:51 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak --DOMWINDOW == 37 (0x11d80c800) [pid = 1787] [serial = 5] [outer = 0x0] [url = about:blank]
[task 2020-04-15T05:37:51.369Z] 05:37:51 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak --DOMWINDOW == 36 (0x11d8ed000) [pid = 1787] [serial = 8] [outer = 0x0] [url = about:blank]
[task 2020-04-15T05:37:51.369Z] 05:37:51 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak --DOMWINDOW == 35 (0x120833400) [pid = 1787] [serial = 14] [outer = 0x0] [url = about:blank]
[task 2020-04-15T05:37:51.369Z] 05:37:51 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak --DOMWINDOW == 34 (0x120754800) [pid = 1787] [serial = 11] [outer = 0x0] [url = about:blank]
[task 2020-04-15T05:37:51.369Z] 05:37:51 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak --DOMWINDOW == 33 (0x112a6a800) [pid = 1787] [serial = 2] [outer = 0x0] [url = about:blank]
[task 2020-04-15T05:37:51.387Z] 05:37:51 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 34 (0x11d8ec400) [pid = 1787] [serial = 39] [outer = 0x112afd200]
[task 2020-04-15T05:37:51.457Z] 05:37:51 INFO - GECKO(1775) | [1792, MainThread] WARNING: XPCOM objects created/destroyed from static ctor/dtor: file /builds/worker/checkouts/gecko/xpcom/base/nsTraceRefcnt.cpp, line 202
[task 2020-04-15T05:37:51.457Z] 05:37:51 INFO - GECKO(1775) | [1792, MainThread] WARNING: XPCOM objects created/destroyed from static ctor/dtor: file /builds/worker/checkouts/gecko/xpcom/base/nsTraceRefcnt.cpp, line 202
[task 2020-04-15T05:37:51.457Z] 05:37:51 INFO - GECKO(1775) | ### XPCOM_MEM_BLOAT_LOG defined -- logging bloat/leaks to /var/folders/_t/k5bnz3rn79q442jjl1g2z4n0000017/T/tmplorJGv.mozrunner/runtests_leaks_tab_pid1792.log
[task 2020-04-15T05:37:51.457Z] 05:37:51 INFO - GECKO(1775) | [1792, MainThread] WARNING: XPCOM objects created/destroyed from static ctor/dtor: file /builds/worker/checkouts/gecko/xpcom/base/nsTraceRefcnt.cpp, line 202
[task 2020-04-15T05:37:51.457Z] 05:37:51 INFO - GECKO(1775) | [1792, MainThread] WARNING: XPCOM objects created/destroyed from static ctor/dtor: file /builds/worker/checkouts/gecko/xpcom/base/nsTraceRefcnt.cpp, line 202
[task 2020-04-15T05:37:51.458Z] 05:37:51 INFO - GECKO(1775) | [1792, Main Thread] WARNING: XPCOM_MEM_BLOAT_LOG is set, disabling native allocations.: file /builds/worker/checkouts/gecko/tools/profiler/core/platform.cpp, line 221
[task 2020-04-15T05:37:52.198Z] 05:37:52 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak ++DOCSHELL 0x119fdbc00 == 14 [pid = 1787] [id = {95cfc2e0-e11b-3d4d-871f-846eac04150d}]
[task 2020-04-15T05:37:52.198Z] 05:37:52 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 35 (0x12507ee40) [pid = 1787] [serial = 40] [outer = 0x0]
[task 2020-04-15T05:37:52.198Z] 05:37:52 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 36 (0x11b762000) [pid = 1787] [serial = 41] [outer = 0x12507ee40]
[task 2020-04-15T05:37:52.284Z] 05:37:52 INFO - TEST-INFO | started process screencapture
[task 2020-04-15T05:37:52.428Z] 05:37:52 INFO - TEST-INFO | screencapture: exit 0
[task 2020-04-15T05:37:52.428Z] 05:37:52 INFO - Buffered messages logged at 05:37:51
[task 2020-04-15T05:37:52.428Z] 05:37:52 INFO - Entering test bound test_About_Welcome_Tab_Close
[task 2020-04-15T05:37:52.429Z] 05:37:52 INFO - TEST-PASS | browser/components/newtab/test/browser/browser_aboutwelcome_observer.js | Active window is not null - [object ChromeWindow] == true -
[task 2020-04-15T05:37:52.429Z] 05:37:52 INFO - TEST-PASS | browser/components/newtab/test/browser/browser_aboutwelcome_observer.js | AboutWelcomeObserver is not null - [object Object] == true -
[task 2020-04-15T05:37:52.437Z] 05:37:52 INFO - TEST-PASS | browser/components/newtab/test/browser/browser_aboutwelcome_observer.js | Terminated due to tab closed - "welcome-tab-closed" == "welcome-tab-closed" -
[task 2020-04-15T05:37:52.438Z] 05:37:52 INFO - Leaving test bound test_About_Welcome_Tab_Close
[task 2020-04-15T05:37:52.438Z] 05:37:52 INFO - Entering test bound test_About_Welcome_Location_Change
[task 2020-04-15T05:37:52.438Z] 05:37:52 INFO - Buffered messages finished
[task 2020-04-15T05:37:52.438Z] 05:37:52 INFO - TEST-UNEXPECTED-FAIL | browser/components/newtab/test/browser/browser_aboutwelcome_observer.js | Uncaught exception - [Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: chrome://mochitests/content/browser/browser/components/newtab/test/browser/browser_aboutwelcome_observer.js :: test_About_Welcome_Location_Change :: line 60" data: no]
[task 2020-04-15T05:37:52.438Z] 05:37:52 INFO - Stack trace:
[task 2020-04-15T05:37:52.438Z] 05:37:52 INFO - test_About_Welcome_Location_Change@chrome://mochitests/content/browser/browser/components/newtab/test/browser/browser_aboutwelcome_observer.js:60:47
[task 2020-04-15T05:37:52.438Z] 05:37:52 INFO - Async*Tester_execTest/<@chrome://mochikit/content/browser-test.js:1039:34
[task 2020-04-15T05:37:52.439Z] 05:37:52 INFO - async*Tester_execTest@chrome://mochikit/content/browser-test.js:1074:11
[task 2020-04-15T05:37:52.439Z] 05:37:52 INFO - nextTest/<@chrome://mochikit/content/browser-test.js:904:14
[task 2020-04-15T05:37:52.439Z] 05:37:52 INFO - SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:918:23
[task 2020-04-15T05:37:52.439Z] 05:37:52 INFO - Leaving test bound test_About_Welcome_Location_Change
[task 2020-04-15T05:37:52.439Z] 05:37:52 INFO - GECKO(1775) | [Child 1787: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 37 (0x14b4d7800) [pid = 1787] [serial = 42] [outer = 0x12507ee40]
[task 2020-04-15T05:37:52.439Z] 05:37:52 INFO - GECKO(1775) | console.warn: AboutWelcomeParent.jsm: Not handling AWPage:LOCATION_CHANGED because the browser doesn't exist.
[task 2020-04-15T05:37:52.440Z] 05:37:52 INFO - GECKO(1775) | MEMORY STAT | vsize 7641MB | residentFast 340MB | heapAllocated 139MB
[task 2020-04-15T05:37:52.440Z] 05:37:52 INFO - TEST-OK | browser/components/newtab/test/browser/browser_aboutwelcome_observer.js | took 1058ms
|
|
1,630,191 | 14,756,314 |
Created attachment 9140695
Recording of the issue
**Affected Versions**
Treeherder build: Nightly 77.0a1 ( 20200415040917) - with fix for Bug 1627658
Beta 76.0b4 (64-bit) - only for the dismissed doorhanger part, Beta is still affected by Bug 1627658 so it doesn't show the save doorhanger on form submit to check Expected 5.1
**Tested on**
Windows 10 x64
Ubuntu 18.04
**Steps to reproduce**
1. Have 1 set of credentials saved on facebook.com
2. Load the Log in Form (ensure credentials are autofilled)
3. Delete the autofilled credentials and type in new ones (observe the grey key icon)
4. Click on the grey icon to toggle the dismissed doorhanger
4.1 Check if the "Show password" checkbox is displayed (Nightly and Beta)
5. Click on Log In to toggle the save doorhanger on form submit
5.1.Check if the "Show password" checkbox is displayed (Nightly only)
**Expected**
4.1 The "Show password" toggle should be displayed for new credentials in the dismissed doorhanger (Nightly and Beta)
5.1 The "Show password" toggle should be displayed for new credentials in the save doorhanger that appears on form submit (Nightly only)
**Actual**
4.1 The "Show password" toggle is not displayed for new credentials in the dismissed doorhanger (Nightly and Beta)
5.1 The "Show password" toggle is not displayed for new credentials in the save doorhanger that appears on form submit (Nightly only)
**Regression-Range**
Introduced via the implementation of Dismissed Doorhanger, Bug 1536728. The show toggle appears correctly in the Save doorhanger on form submit by following the same scenario in Release 74 and Release 75.
**Note**
Release 75 has the pref disabled for the dismiss doorhanger.
|
|
1,630,473 | 14,758,210 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Enable security.osclientcerts.autoload
Have a client certificate available in Windows, issued by a certificate authority that Firefox does not know about, but Windows trusts
See that the client certificate is listed in Your Certificates
Try to go to a website that requires using the client certificate
Actual results:
The client certificate is not in the list of certificates to be selected or the list of certificates isn't show at all
Expected results:
The client certificate should have been available to be selected
|
|
1,630,757 | 14,759,958 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
1) Create a file on local disk containing a link that uses an external protocol (irc:, mailto:, sip:, etc.). For example: `<a href="sip:[email protected]">sip</a>`
2) Open that page in Firefox using a file:// URI
3) Click the link
I'm also experiencing this when the page is loaded from http://www.example.com (instead of file://) and the localfilelinks policy is set to include http://www.example.com in the whitelist. See http://kb.mozillazine.org/Links_to_local_pages_don%27t_work
Actual results:
The external program opens.
The current page contents are erased, leaving you with a blank page.
Expected results:
The external program opens.
The page contents are left unmodified.
|
|
1,631,089 | 14,762,255 |
Created attachment 9141390
screenshot-element-padding-border.png
This test fails for me locally on MacOS because the generated screenshot by Firefox is different compared to the reference image. What's strange is that the same test passes perfectly in CI:
https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&tier=1%2C2%2C3&searchStr=pup
Here the local failure details:
```
0:09.66 TEST_START: Firefox Browser Page ElementHandle.screenshot should take into account padding and border
0:09.66 TEST_END: FAIL, expected PASS
0:09.66 pid:36384 1) [FAIL] Firefox Browser Page ElementHandle.screenshot should take into account padding and border (screenshot.spec.js:137:5)
0:09.66 pid:36384 Message:
0:09.66 pid:36384 expect.toBeGolden failed: screenshot-element-padding-border.png mismatch! Output is saved in "output-firefox" directory
0:09.66 pid:36384 Stack:
0:09.66 pid:36384 Error: expect.toBeGolden failed: screenshot-element-padding-border.png mismatch! Output is saved in "output-firefox" directory
0:09.67 pid:36384 at applyMatcher (/Users/henrik/code/gecko/remote/test/puppeteer/utils/testrunner/Matchers.js:48:15)
0:09.67 pid:36384 at fit (/Users/henrik/code/gecko/remote/test/puppeteer/test/screenshot.spec.js:152:26)
0:09.67 pid:36384 at process._tickCallback (internal/process/next_tick.js:68:7)
```
Andrew, any idea why that's only failing on MacOS? What would have to be done to the reference image (will upload it in a moment) to get the test fixed, but also let it pass when using Chrome?
|
|
1,631,378 | 14,766,083 |
Created attachment 9141651
identityBox.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Install extension that overwrites default New Tab.
Observe the Offset of Address bar within identity-box.
Actual results:
Extension Name - The right offset is too big.
Expected results:
Extension Name - The right offset should batch the remaining ones.
|
|
1,631,404 | 14,766,253 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:77.0) Gecko/20100101 Firefox/77.0
Steps to reproduce:
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:77.0) Gecko/20100101 Firefox/77.0
security.osclientcerts.autoload: false
security.enterprise_roots.enabled: false
Steps:
1. Open Firefox, in Preferences → View Certificates install a TLS client certificate.
2. Attempt to view a website which during TLS connectivity requests a client certificate.
Actual results:
User is given an "SSL_ERROR_HANDSHAKE_FAILURE_ALERT" error page.
During the final part of TLS handshake the browser is sending an empty certificate field and no certificate verification message.
Expected results:
User should be prompted to use the installed TLS client certificate.
During the final part of TLS handshake the browser sends the client certificate and certificate verification.
|
|
1,631,739 | 14,768,695 |
Created attachment 9142011
firefox-ios.html
Firefox Version: v24.1
OS: iOS 13.3.1
Issue: Universal XSS on Firefox iOS Download link Action
Description:
Firefox iOS user clicks download link in hyperlink option and XSS is triggered on current url, When the hyperlink is in format https://anydomain/','123');alert(document.domain);//
Sample attack scenerio
* Attacker links https://attacker.com/','123');alert( in google.com index
* Victim click's download link on firefox iOS
* XSS is executed on victim's google.com domain
Steps to reproduce:
1. Open https://vinothkumar.tech/firefox-ios your iOS firefox browser.
2. Hold the link until preview popup appears.
3. Click Download Link
4. XSS is triggered
Root Cause:
https://github.com/mozilla-mobile/firefox-ios/blob/v24.1/Client/Frontend/Browser/BrowserViewController/BrowserViewController+WebViewDelegates.swift#L171
Unescaped url link is being appeneded to the javascript when download action clicked
```
currentTab.webView?.evaluateJavaScript("window.__firefox__.download('\(url.absoluteString)', '\(UserScriptManager.securityToken)')")
```
Fix:
```
let safeUrl = url.absoluteString.replacingOccurrences(of: "'", with: "%27")
currentTab.webView?.evaluateJavaScript("window.__firefox__.download('\(safeUrl)', '\(UserScriptManager.securityToken)')")
```
Youtube Unlisted Video: https://youtu.be/zkVVolyCrt0
POC:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Firefox Universal Download Link XSS POC</title>
</head>
<body>
<a href="http://vinothsparrow.herokuapp.com/','123');alert(document.domain);//">Download Link in Firefox</a><br><br>
</body>
</html>
|
|
1,631,749 | 14,768,748 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
click profile icon
click logins and passwords
go to any password and click copy password or click the show password icon
Actual results:
a windows security popup come up requesting my computers login pin/password
whether i close it or input the password firefox closes/crashes without the crash reporter opening
when i next launch firefox it resumes the previous session and reloads the tabs
Expected results:
password would have been copied or shown
|
|
1,632,093 | 14,771,279 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0
Steps to reproduce:
Updated Firefox Nightly today and attempted to watch YouTube.
Actual results:
Audio didn't work. I tried Twitch.tv as well but I encountered the same issue. No sound came through on any sites.
Expected results:
Audio should've been heard.
|
|
1,632,132 | 14,771,546 |
**Affected versions**
* 76.0b7, 77.0a1(2020.04.20)
**Affected platforms**
* Windows 10, macOS 10.15.3, Ubuntu 18.04;
**Steps to reproduce**
1. Launch Firefox and access https://longform.org/best
2. Click on the button to trigger the reader mode;
3. Change the theme for it on Black/Dark;
4. Click on the Narrate button click on the play button;
5. Click on Play to start narration;
6. Click on the Next/Previous button;
**Expected result**
* buttons appear as being available;
**Actual result**
* due to color setup next/previous buttons appear as being unavailable;
**Regression range**
* will check and provide one asap;
**Additional notes**
* attached recording to better illustrate the issue;
* ideally color would be changed to white as well for the 2 buttons, at least once available.
|
|
1,632,405 | 14,773,306 |
+++ This bug was initially created as a clone of Bug #1627658 +++
**Affected Versions**
Nightly 77.0a1(2020-04-22)
**Tested on**
Windows 10 x64
**Steps to reproduce**
1. Have 1 set of credentials saved on facebook.com
2. Load the Log in Form (ensure credentials are autofilled)
3. Delete the autofilled credentials and type in new ones (observe the grey key icon)
4. Click on Log In
**Expected**
The save doorhanger should be displayed on form submit (replaces the dismissed one)
**Actual**
Save doorhanger on form submit is not displayed, the grey key for the dismissed doorhanger remains displayed
**Regression-Range**
This regressed recently on Nightly due to Bug 1532377.
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6c5eddde0f5b187cb6891549d0d279394cd65423&tochange=cf66def9cbd002f21bab8e55083a165f82ea0217
|
|
1,632,441 | 14,773,481 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Page A open a new page B, then after some user actions on page B, this page should be closed by window.close().
Actual results:
Since 75 release, the page B is not closed anymore.
I can't find any relative information on 75 version's release note. Is that a know issue ? Or this is a new behavior relating to https://www.w3.org/TR/html52/browsers.html#dom-window-close specifications ?
Expected results:
Before 75 release of Firefox, the page B was closed.
|
|
1,632,556 | 14,774,301 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.113 Safari/537.36
Steps to reproduce:
Opened a page using Selenium via Python binding
Actual results:
navigator.webdriver returns false
Expected results:
navigator.webdriver should true
|
|
1,632,644 | 14,774,904 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Opened a PDF that contains an attachment that also is a PDF. For example: https://www.jeffersonscher.com/temp/Links-attachments-PDFs.pdf
The clicked the attached PDF to launch it in a new viewer.
Actual results:
PDF did not launch. Web Console displays:
Error: Access to 'blob:resource://pdf.js/d88abb45-ad65-447c-834b-d63f30884864?Amarin_COVID-19%20menu%20(01191490).PDF' from script denied
viewer.js:4510:14
Expected results:
The attached PDF should launch in a new tab in the PDF Viewer, similarly to what happens when you open the same PDF in the web app version of pdf.js at https://mozilla.github.io/pdf.js/web/viewer.html
Thread on SUMO: https://support.mozilla.org/questions/1285269
|
|
1,621,966 | 14,691,421 |
This bug is for crash report bp-530e206a-49bc-472e-99ed-da74e0200312.
```
Java stack trace:
java.lang.AssertionError
at org.mozilla.geckoview.GeckoSession.onWindowBoundsChanged(GeckoSession.java:2)
at org.mozilla.geckoview.GeckoSession.onSurfaceChanged(GeckoSession.java:8)
at org.mozilla.geckoview.GeckoDisplay.surfaceChanged(GeckoDisplay.java:4)
at org.mozilla.geckoview.GeckoDisplay.surfaceChanged(GeckoDisplay.java:1)
at org.mozilla.geckoview.GeckoView$Display.onSurfaceChanged(GeckoView.java:2)
at org.mozilla.gecko.SurfaceViewWrapper$ListenerWrapper.surfaceChanged(SurfaceViewWrapper.java:2)
at android.view.SurfaceView.updateSurface(SurfaceView.java:761)
at android.view.SurfaceView.setFrame(SurfaceView.java:378)
at android.view.View.layout(View.java:20945)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:325)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:325)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at androidx.swiperefreshlayout.widget.SwipeRefreshLayout.onLayout(SwipeRefreshLayout.java:11)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at androidx.coordinatorlayout.widget.CoordinatorLayout.onLayoutChild(CoordinatorLayout.java:54)
at androidx.coordinatorlayout.widget.CoordinatorLayout.onLayout(CoordinatorLayout.java:8)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:325)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1842)
at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1686)
at android.widget.LinearLayout.onLayout(LinearLayout.java:1595)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:325)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1842)
at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1686)
at android.widget.LinearLayout.onLayout(LinearLayout.java:1595)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:325)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1842)
at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1686)
at android.widget.LinearLayout.onLayout(LinearLayout.java:1595)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at android.widget.FrameLayout.layoutChildren(FrameLayout.java:325)
at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
at com.android.internal.policy.DecorView.onLayout(DecorView.java:902)
at android.view.View.layout(View.java:20948)
at android.view.ViewGroup.layout(ViewGroup.java:6279)
at android.view.ViewRootImpl.performLayout(ViewRootImpl.java:3037)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2545)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1636)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7946)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1092)
at android.view.Choreographer.doCallbacks(Choreographer.java:893)
at android.view.Choreographer.doFrame(Choreographer.java:812)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1078)
at android.os.Handler.handleCallback(Handler.java:907)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:216)
at android.app.ActivityThread.main(ActivityThread.java:7625)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987)
|
|
1,622,012 | 14,691,765 |
If Marionette hasn't been enabled we shouldn't run any of its code. Right now this happens because the component registers the `profile-after-change` observer notification. And as such we register for various other notifications, and in the worst case quit Firefox if eg. a XML parse error happens. See bug 1616856 for details.
I would suggest that we read the value of the `marionette.enabled` pref only during startup, and never update it when a user changes the pref during runtime. That way we can safely skip all the observer registrations, and don't have to worry about inconsistent states.
|
|
1,622,045 | 14,692,087 |
I somehow flipped the prefs for UserMessaging.
|
|
1,622,117 | 14,692,650 |
It seems that the addon is not always fully loaded in BootstrapScope, so accessing some necessary data can fail.
STR
- make an addon.xpi
- install addon
- drop addon onto firefox to install it again (as one might do during development)
A traceback occurs pointing to BootStrapScope.update not having "oldPermissions".
```
1584054209892 addons.xpi WARN Exception running bootstrap method update on [email protected]: TypeError: can't access property "origins", oldPermissions is undefined(resource://gre/modules/Extension.jsm:707:7) JS Stack trace: [email protected]:707:7
[email protected]:735:34
[email protected]:1643:25
[email protected]:1795:33
[email protected]:1970:18
[email protected]:2058:17
async*startInstall/this._startupPromise<@XPIInstall.jsm:1821:68
[email protected]:1837:9
async*[email protected]:1343:14
[email protected]:2090:18
[email protected]:1681:10
[email protected]:1340:14
[email protected]:2090:18
checkPrompt/<@XPIInstall.jsm:1652:12
async*[email protected]:1653:7
[email protected]:1337:14
[email protected]:2090:18
[email protected]:2681:29
[email protected]:2181:13
[email protected]:2321:30
[email protected]:2338:21
[email protected]:4065:26
handleUriInChrome/<@browser.js:1422:24
```
|
|
1,622,195 | 14,693,101 |
##### [Environment:]
Windows 10
Mac 10.15.3
Ubuntu 16804
##### [Versions:]
75.0b3 20200313021419
76.0a1 20200312215313
##### [Steps:]
1. Open Firefox with a new profile && browser is not default.
2. Enable browserconsole.
3. Open browser console and use the following snippet to modify the profile age:
* (async function() { let { ProfileAge } = ChromeUtils.import("resource://gre/modules/ProfileAge.jsm"); let age = await ProfileAge(); age._times = { firstUse: 1368255600000, created: 1368255600000 }; await age.writeTimes(); })(); *
4. Close the browser console.
5. Close and reopen the browser.
##### [Actual Result:]
As the browser is not the default one, the check_default_browser modal will be shown at the start-up while also the Search Tips are shown.
When the modal is actioned upon, the Search Tip is temporarily dismissed.
##### [Expected Result:]
The optimal user experience would be to show the Search Tips when we're certain that there is nothing that blocks it or obscures it, in order to offer the user the desired actionable choice.
##### [Note:]
Even though in this particular case, the Search Tips has been already loaded but is just not actionable and only readable-> there might be other cases similar to this one, but QA doesn't have a list with browser level modal/non-modal notifications with might have impact on Search Tips. (any hint/idea would be apreciated)
|
|
1,622,240 | 14,693,354 |
Created attachment 9133159
warnD.png
**Affected versions**
* 74.0, 75.0b3, 76.0a1 (2020-03-12);
**Affected platforms**
* Windows 10, macOS 10.13, Ubuntu 16.04;
**Steps to reproduce**
1. Launch Firefox, click on the 3line/Hambourger menu button;
2. Click on the Customize button;
3. Change to Dark Theme and Drag the Forget button on the bar(anywhere to be visible);
4. Exit the customize mode and click on the Forget button;
**Expected result**
* text in the menu is readable;
**Actual result**
* warning dark-red text on grey background is hard to read;
**Regression range**
* most likely not a regression, but will check asap;
**Additional notes**
* attached screenshot with the issue.
|
|
1,622,457 | 14,694,746 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
ctrl+shift+o produces a popup titled "Library" (show all bookmarks). For the downloads widget, the next line down in the display has buttons that ought to be together and NOT at the far end of the widget.
I have long file names and as a result, my "library" widget is3/4 the screen in size. The clear downloads button at the far right should be next to the organize button, followed by the search "button".
Actual results:
see above
Expected results:
see above
|
|
1,622,536 | 14,695,119 |
1. https://apps.kaonadn.net/5160639144132608/product.html#ProVC70000;:
2. Crash. Bughunter has reproduced the opt crash on Linux and Windows. I haven't reproduced locally on Linux opt but have reproduced the MOZ_CRASH locally with a day or so old debug build on Linux.
Bughunter's opt signature
[@ mozilla::ClientWebGLContext::CompressedTexImage(bool, unsigned char, unsigned int, int, unsigned int, mozilla::avec3<int> const&, mozilla::avec3<int> const&, int, mozilla::TexImageSource const&, int) const]
### Opt crash in Firefox 74 release
bp-6c87a08f-7a89-4132-8630-52cbc0200314
bp-09edb4ef-41f6-4d74-a115-55d930200314
[@ mozilla::GetRangeFromView ]
### Debug crash.
```
Hit MOZ_CRASH(invalid scalar type) at /builds/worker/workspace/build/src/obj-firefox/dist/include/jsfriendapi.h:1434
#01: mozilla::ClientWebGLContext::CompressedTexImage(bool, unsigned char, unsigned int, int, unsigned int, mozilla::avec3<int> const&, mozilla::avec3<int> const&, int, mozilla::TexImageSource const&, int) const (firefox-debug/dist/bin/libxul.so)
#02: mozilla::dom::WebGLRenderingContext_Binding::compressedTexImage2D(JSContext*, JS::Handle<JSObject*>, void*, JSJitMethodCallArgs const&) (firefox-debug/dist/bin/libxul.so)
#03: bool mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ThrowExceptions>(JSContext*, unsigned int, JS::Value*) (firefox-debug/dist/bin/libxul.so)
#04: CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), js::CallReason, JS::CallArgs const&) (firefox-debug/dist/bin/libxul.so)
#05: js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (firefox-debug/dist/bin/libxul.so)
#06: Interpret(JSContext*, js::RunState&) (firefox-debug/dist/bin/libxul.so)
#07: js::RunScript(JSContext*, js::RunState&) (firefox-debug/dist/bin/libxul.so)
#08: js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (firefox-debug/dist/bin/libxul.so)
#09: js::jit::DoCallFallback(JSContext*, js::jit::BaselineFrame*, js::jit::ICCall_Fallback*, unsigned int, JS::Value*, JS::MutableHandle<JS::Value>) (firefox-debug/dist/bin/libxul.so)
#10: ??? (???:???)
```
|
|
1,622,542 | 14,695,141 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
There're two Windows 10 OS accounts in the system. One is a local non-privileged user with empty password and another is an admin user with MS online account login. When clicking on eye icon or "copy" button to see/copy saved password in about:logins a Windows security window with "Verify your identity to reveal the saved password" message pops up.
Actual results:
While under non-privileged system user:
Empty password for non-privileged system user is declined, security window pops up again.
E-mail and password identities for admin system user is also declined, security window pops up again.
While under admin system user:
Identities for admin system user is correctly accepted, saved password is shown.
Empty password for non-privileged system user is declined, security window pops up again.
Expected results:
Security window must accept empty user password or shouldn't pop up at all if system user password is empty.
|
|
1,622,555 | 14,695,192 |
Created attachment 9133395
nss-lowhashtest-fixes.patch
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
Ran all tests in FIPS mode.
Actual results:
lowhashtest reported that all hash functions failed. This happened because it was being called once per hash function with the name of the function to test as its first argument.
Due to bugs in the argument parsing, it would test every function regardless of arguments and report a failure if any one of them failed, resulting in disabled functions (MD5...) erroneously disqualifying runs that were only supposed to test a different function.
Expected results:
If a hash function is specified on the command line, that hash function should be tested instead of all of them. In FIPS mode that means only disabled hash functions would fail instead of all of them.
|
|
1,622,604 | 14,695,397 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Change the page of alerts in the perfherder page
Actual results:
Gave the error message of invalid page
Expected results:
Should have gone to that page
|
|
1,622,617 | 14,695,467 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:73.0) Gecko/20100101 Firefox/73.0
|
|
1,622,640 | 14,695,545 |
Created attachment 9133442
response-injection-release.zip
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
Thunderbird has connected to an IMAP server and issued the starttls command. The server responds with "okay, let's start TLS now". However, the server (or some malicious party) also appends extra data after the starttls server response.
Example trace:
S: * OK [CAPABILITY IMAP4REV1 STARTTLS LOGINDISABLED]\r\n
C: 1 STARTTLS\r\n
S: 1 OK start TLS now\r\n* OK [ALERT] Huch?\r\n2 OK ...\r\n4 OK ...\r\n
----- <TLS handshake> --- everything after this line is encrypted -----
C: 2 capability\r\n
// Thunderbird proceeds with login, as "2 OK" was already received/buffered
C: 4 login \"alice\" \"password\"\r\n
// Thunderbird proceeds with list, as "4 OK" was already received/buffered
C: 5 list \"\" \"*\"\r\n
...
Actual results:
Thunderbird shows the alert, and also interprets both results even though they were provided via plaintext (w/o TLS.)
1 OK start TLS now\r\n* OK [ALERT] Huch?\r\n2 OK ...\r\n4 OK ...\r\n
It seems that when the server answers with multiple results attached directly after "1 OK start TLS now\r\n" response, all following responses are written to an internal buffer first. Only after that, all sockets are switched to speak TLS. However, the old responses are kept and thus end up being interpreted as if they were read via TLS.
This issue was first described by Wietse Venema (www.postfix.org/CVE-2011-0411.html). Theoretically, any other protocols supporting STARTTLS (SMTP, LDAP, ...) could also be affected.
Expected results:
Thunderbird must not interpret the additional data. Arguably, everything after "1 OK start TLS now\r\n" should be interpreted as the SERVER_HELLO TLS message. An easier to implement, but potentially breaking alternative is to discard the data.
Using the additional data allows an attacker to inject malicious responses, which are interpreted as if they came via a secure TLS connection.
I guess that this issue could in one way or another be exploited to obtain sensitive data or be very useful to mount a successful attack on STARTTLS.
Please see the attached test program for a demonstration of the issue.
You will need to provide a a certificate chain and a private key for the leaf certificate. I used the mkcert tool [1] to create a local root CA and issued a certificate for 127.0.0.1.
Thunderbird is configured as follows:
IMAP: 127.0.0.1:10143 (STARTTLS)
SMTP: 127.0.0.1:10587 (STARTTLS)
To make testing easier, the provided example server also implements the minimum SMTP functionality to pass thunderbirds account wizard. Thus, you can setup a fresh thunderbird profile (-ProfileManager) for testing.
[1] https://github.com/FiloSottile/mkcert
|
|
1,622,671 | 14,695,708 |
+++ This bug was initially created as a clone of Bug #1568373 +++
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
1. Play a video in your browser
2. Toggle on the Picture-in-Picture mode
3. Double-click on the player window to fullscreen it
Actual results:
The space not covered by video is a grey noise background - what's normally shown in the background of image documents.
Expected results:
The space not covered by the video should be solid black.
|
|
1,622,695 | 14,695,836 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Steps to reproduce:
New mail or reply in dark mode. 75.0b1
Actual results:
Create new mail or reply to mail. Text color indicates black on white, but everything is black. Turns out the indicator box for background is really "transparent" and if I change that to "white. Further testing indicates that the default background in dark mode is transparent (not white) and so it's just the defaults that need to change.
Expected results:
The release process needs to update the default colors for dark mode.
|
|
1,622,731 | 14,697,668 |
This bug is for crash report bp-01834f4a-8484-4e04-aeff-cfcab0200314.
```
Top 10 frames of crashing thread:
0 XUL mozilla::dom::XULTreeElement::GetTreeBodyFrame dom/xul/XULTreeElement.cpp:86
1 XUL mozilla::dom::XULTreeElement::GetColumns dom/xul/XULTreeElement.cpp:182
2 XUL nsCoreUtils::GetSensibleColumnCount accessible/base/nsCoreUtils.cpp:451
3 XUL mozilla::a11y::TableAccessible::IsProbablyLayoutTable accessible/generic/TableAccessible.cpp:136
4 XUL -[mozTablePartAccessible isLayoutTablePart] accessible/mac/mozTableAccessible.mm:17
5 XUL -[mozTablePartAccessible role] accessible/mac/mozTableAccessible.mm:37
6 XUL -[mozAccessible accessibilityIsIgnored] accessible/mac/mozAccessible.mm:136
7 AppKit __NSAccessibilityEntryPointIsAccessibilityElement_block_invoke.llvm.15474548225997367914
8 AppKit NSAccessibilityPerformEntryPointBOOL.llvm.15474548225997367914
9 AppKit NSAccessibilityEntryPointIsAccessibilityElement
```
macOS-specific accessibility crash. It looks like a NULL-pointer dereference and seems to have started in buildid 20200305212712. I could not find non-nightly crashes but these might just be under a different signature.
|
|
1,622,820 | 14,698,348 |
Created attachment 9133573
image.png
**Steps to reproduce**
1. Open the browser toolbox with the context selector pref on
1. Hit Shift + Enter multiple times to make the input taller
**Expected results**
Context selector button stays the same
**Actual results**
Context selector button grows (see screenshot)
|
|
1,622,941 | 14,699,198 |
Created attachment 9133702
text-attributes-changed.py
Steps to reproduce:
1. Launch the attached accessibility event listener
2. Load the following test case data:text/html,<textarea></textarea>
3. Type a misspelled word (e.g. "fooooo") in the textarea
Expected results: The listener would print a text-attributes-changed event.
Actual results: The listener doesn't print a text-attributes-changed event.
I'm nearly positive this is a regression, but it seems to be present in both Firefox stable and nightly, and I'm afraid I don't have time for a bisect.
Related aside: We do get the expected event from Thunderbird (e.g. the message composition body).
|
|
1,623,173 | 14,701,358 |
:rpl helped me with this. Right now when upgrading major versions we lose that property and the addons are enabled, see: https://github.com/mozilla-mobile/android-components/issues/6255
|
|
1,623,363 | 14,702,752 |
[Tracking Requested - why for this release]:
Central as beta simulation: https://treeherder.mozilla.org/#/jobs?repo=try&selectedJob=293663318&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable&revision=a5990ea36f6e4c35c86cac5767e11efd950c7cce
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=293663236&repo=try&lineNumber=178869
```
[task 2020-03-18T13:10:02.339Z] 13:10:02 INFO - TEST-PASS | devtools/client/webconsole/test/browser/browser_jsterm_eager_evaluation.js | Got eager evaluation result 3 -
[task 2020-03-18T13:10:02.339Z] 13:10:02 INFO - Leaving test bound
[task 2020-03-18T13:10:02.339Z] 13:10:02 INFO - Entering test bound
[task 2020-03-18T13:10:02.339Z] 13:10:02 INFO - Adding a new tab with URL: data:text/html;charset=utf-8,
[task 2020-03-18T13:10:02.339Z] 13:10:02 INFO - <script>
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - let x = 3, y = 4;
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - function zzyzx() {
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - x = 10;
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - }
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - function zzyzx2() {
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - x = 10;
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - }
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - var obj = {propA: "A", propB: "B"};
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - </script>
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO -
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - Tab added and finished loading
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - Opening the toolbox
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - Buffered messages logged at 13:10:01
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome://global/content/elements/panel.js" line: 62}]
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - Console message: [JavaScript Error: "Content Security Policy: The page’s settings blocked the loading of a resource at inline (“default-src”)." {file: "chrome://global/content/elements/panel.js" line: 62}]
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - Toolbox opened and focused
[task 2020-03-18T13:10:02.340Z] 13:10:02 INFO - Check that the setting is disabled
[task 2020-03-18T13:10:02.341Z] 13:10:02 INFO - Buffered messages finished
[task 2020-03-18T13:10:02.342Z] 13:10:02 INFO - TEST-UNEXPECTED-FAIL | devtools/client/webconsole/test/browser/browser_jsterm_eager_evaluation.js | Uncaught exception - at chrome://mochitests/content/browser/devtools/client/webconsole/test/browser/head.js:413 - TypeError: el is null
[task 2020-03-18T13:10:02.342Z] 13:10:02 INFO - Stack trace:
[task 2020-03-18T13:10:02.342Z] 13:10:02 INFO - checkConsoleSettingState@chrome://mochitests/content/browser/devtools/client/webconsole/test/browser/head.js:413:19
[task 2020-03-18T13:10:02.343Z] 13:10:02 INFO - @chrome://mochitests/content/browser/devtools/client/webconsole/test/browser/browser_jsterm_eager_evaluation.js:287:27
[task 2020-03-18T13:10:02.343Z] 13:10:02 INFO - Leaving test bound
[task 2020-03-18T13:10:04.459Z] 13:10:04 INFO - GECKO(3441) | [Parent 3441: Main Thread]: I/DocShellAndDOMWindowLeak --DOMWINDOW == 36 (0x7fe6d0d1a400) [pid = 3441] [serial = 281] [outer = (nil)] [url = about:blank]
[task 2020-03-18T13:10:04.823Z] 13:10:04 INFO - GECKO(3441) | [Child 3782: Main Thread]: I/DocShellAndDOMWindowLeak --DOMWINDOW == 4 (0x7fba0d693520) [pid = 3782] [serial = 116] [outer = (nil)] [url = about:blank]
[task 2020-03-18T13:10:04.932Z] 13:10:04 INFO - Removing tab.
[task 2020-03-18T13:10:04.932Z] 13:10:04 INFO - Waiting for event: 'TabClose' on [object XULElement].
[task 2020-03-18T13:10:04.952Z] 13:10:04 INFO - Got event: 'TabClose' on [object XULElement].
[task 2020-03-18T13:10:04.955Z] 13:10:04 INFO - GECKO(3441) | console.warn: "IGNORED REDUX ACTION:" ({type:"AUTOCOMPLETE_CLEAR"})
[task 2020-03-18T13:10:04.972Z] 13:10:04 INFO - GECKO(3441) | [Parent 3441, Main Thread] WARNING: '!inner', file /builds/worker/checkouts/gecko/dom/ipc/JSWindowActorService.cpp, line 182
[task 2020-03-18T13:10:04.972Z] 13:10:04 INFO - GECKO(3441) | [Parent 3441, Main Thread] WARNING: '!inner', file /builds/worker/checkouts/gecko/dom/ipc/JSWindowActorService.cpp, line 182
[task 2020-03-18T13:10:04.972Z] 13:10:04 INFO - Tab removed and finished closing
```
|
|
1,623,400 | 14,703,064 |
Created attachment 9134198
bug.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
Update Firefox Nightly to the latest build (build 2020-03-18 in this case).
Actual results:
Dektop push notifications are no longer appearing as they used to for sites where they were previously enabled. For new sites nottifications cannot be switched on (see pic attached).
Expected results:
Notifications should appear as usual.
|
|
1,623,501 | 14,703,623 |
Created attachment 9134263
whatsapp-http2-http3-WSS-cant-establish-connection-server.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
- Open
- https://web.whatsapp.com/
- Can't connect
- Sometimes connects after many tries
- Tried in another container
- Tried non Fission window
- Only on Firefox
`22:35:53.291 GETwss://web.whatsapp.com/ws
[HTTP/3 400 Bad Request 278335ms]`
and
```c
22:35:53.291 GETwss://web.whatsapp.com/ws
[HTTP/3 400 Bad Request 278335ms]
Request URL:wss://web.whatsapp.com/ws
Request Method:GET
Remote Address:31.13.85.51:443
Status Code:
400
Version:HTTP/3
Response Headers (63 B)
Raw Headers
date
Wed, 18 Mar 2020 22:39:47 GMT
Request Headers (573 B)
Raw Headers
Accept
*/*
Accept-Encoding
gzip, deflate, br
Accept-Language
en-US,en;q=0.5
Alt-Used
web.whatsapp.com
Cache-Control
no-cache
Connection
keep-alive, Upgrade
DNT
1
Host
web.whatsapp.com
Origin
https://web.whatsapp.com
Pragma
no-cache
Sec-Fetch-Dest
websocket
Sec-Fetch-Mode
websocket
Sec-Fetch-Site
same-origin
Sec-WebSocket-Extensions
permessage-deflate
Sec-WebSocket-Key
???????==
Sec-WebSocket-Version
13
Upgrade
websocket
User-Agent
Mozilla/5.0 (Windows NT 10.0; …) Gecko/20100101 Firefox/76.0
```
Actual results:
It's slow and hard to use Web Whatsapp in Firefox
But its too fast in chrome.
Why? And it's hard to connect.
`22:36:54.545 Firefox can’t establish a connection to the server at wss://web.whatsapp.com/ws. app.45a9afa0af17d19ea932.js:2:836999`
and
```c
22:36:54.545 Firefox can’t establish a connection to the server at wss://web.whatsapp.com/ws. app.45a9afa0af17d19ea932.js:2:836999
22:36:55.673
GETwss://web.whatsapp.com/ws
22:36:58.993
GETwss://web.whatsapp.com/ws
22:37:05.050
XHRGEThttps://web.whatsapp.com/status.json
22:37:15.673 Firefox can’t establish a connection to the server at wss://web.whatsapp.com/ws. 2 app.45a9afa0af17d19ea932.js:2:836999
22:38:12.181
GETwss://web.whatsapp.com/ws
22:38:18.192
XHRGEThttps://web.whatsapp.com/status.json
[HTTP/3 200 OK 185ms]
22:38:24.399
XHRGEThttps://web.whatsapp.com/status.json
[HTTP/3 200 OK 185ms]
22:38:28.429
XHRGEThttps://web.whatsapp.com/status.json
[HTTP/3 200 OK 149ms]
22:38:32.181 Firefox can’t establish a connection to the server at wss://web.whatsapp.com/ws.
```
Expected results:
- Improve HTTP2/HTTP3 sites support
- Improve errors debug.
- improve websocket errors info.
- Improve support for Whatsapp Web
Thanks!
|
|
1,623,529 | 14,703,774 |
Steps to reproduce:
1. Go to about:debugging and connect to Fenix on Android.
2. Click the Profile performance button.
3. Choose Settings -> Custom, and go to Edit Settings...
4. Check the "Java" feature checkbox.
5. Click Save settings and go back.
Expected results:
The Java feature should now be enabled.
Actual results:
The summary does not list the Java feature. Going back to edit setting shows the Java feature still unchecked.
The "host" Gecko doesn't support Java profiling. Are we ever asking the host for its supported profiler features? We shouldn't do that for remote profiling features.
|
|
1,623,599 | 14,704,360 |
After doing some detailed analysis of the telemetry data we're receiving about cache corruption, I realised that we are always detecting distributions as having corrupt caches. This is because of two reasons:
* Distribution engines are loaded separately from the legacy config, so we don't know how many engines would be loaded when we check the cache. As a result, the distribution is likely to have more engines than we expect, and therefore we think the cache is corrupt.
* Distribution engines are not being marked as built-in. This will also potentially confuse the detection, as we're comparing built-in engines only (bug 1623597)
There's a couple of adverse effects as a result of this:
* We'll be rebuilding the search engine cache every start-up, which may affect start-up performance (though I expect the effect to be small).
* If the user removes an engine that is added or altered by the distribution, this setting will not be preserved.
I'm going to handle the cache detection issue in this bug. The built-in issue I'll handle in bug 1623597, since I think that needs a little bit of its own focus to ensure there's no separate issue with that.
|
|
1,623,807 | 14,705,898 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
1. Enable DNS over HTTPS to a custom host (currently private to my organization)
2. Set network.trr.mode to 3
3. Visit http://jdebp.uk/FGA/web-fully-qualified-domain-name.html (note, this page loads fine)
4. Visit http://jdebp.uk./FGA/web-fully-qualified-domain-name.html (note, the host portion ends with a '.' marking this as a FQDN). The page fails to load.
5. set network.trr.mode to 5 (force normal DNS resolution)
6. Visit http://jdebp.uk/FGA/web-fully-qualified-domain-name.html (note, this page loads fine)
7. Visit http://jdebp.uk./FGA/web-fully-qualified-domain-name.html (note: FQDN---page loads fine)
Actual results:
When DoH is enabled and a URL with a FQDN is used, the domain cannot be found.
Expected results:
When DoH is enabled and a URL with a FQDN is used, the domain should be found.
|
|
1,623,885 | 14,706,593 |
Created attachment 9134646
Screenshot from 2020-03-20 09-20-56.png
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
Navigate to: https://gisanddata.maps.arcgis.com/apps/opsdashboard/index.html#/bda7594740fd40299423467b48e9ecf6
Navigate to Radio Garden: http://radio.garden/listen/world-wide-bluegrass/FJKguH4T
I have manually enabled WebGL in about:config & restarted; still does not work. I have the latest Intel drivers from GitHub. Chromium works flawlessly on both pages.
Actual results:
No main screen, or WebGL error message
Expected results:
Web page should have loaded.
|
|
1,623,905 | 14,706,715 |
Created attachment 9134671
CFR button bug
**Affected platforms**
* Windows
* Ubuntu
* macOS
**Steps to reproduce**
1. Launch Firefox.
2. Trigger the CFR addon recommandation.
3. Click the 'Not Now' option displayed on the doorhanger.
**Expected result**
* The doorhanger is dismissed and the CFR button is minimized, but still displayed.
**Actual result**
* The CFR button is not minimized.
**Regression range**
* Last good revision: e1a3a62f20351336f9afbcd3df26996b2acc14ae
* First bad revision: 532b71703571a8a65e58330208afa0b28febfba8
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e1a3a62f20351336f9afbcd3df26996b2acc14ae&tochange=532b71703571a8a65e58330208afa0b28febfba8
**Additional notes**
* This issue occurs for the CFR pin tab recommandation as well.
|
|
1,623,921 | 14,706,834 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
As by this bug on uBlock Origin tracker: https://github.com/uBlockOrigin/uBlock-issues/issues/942
1. Install latest uBlock Origin
1. Check "I am an advanced user (required reading)" in settings
2. Add this to My rules:
```
* * 3p block
taz.de * 1p-script block
taz.de * inline-script block
```
2. Add this to My filters:
```
taz.de##^.community.full
taz.de##^.rack.article
taz.de##^.sect_description
taz.de##^.shariff
taz.de##^.tail
taz.de##^#footer
taz.de##^#reward:xpath(../..)
```
3. Visit `https://taz.de/!5670441/`.
4. Observe the 301 to `https://taz.de/Buergermeister-Wahl-in-Stuttgart/!5670441/`.
5. Observe that the above rules are applied.
6. Observe that the above filters are not applied.
7. Visit `https://taz.de/Buergermeister-Wahl-in-Stuttgart/!5670441/`.
8. Observe that the rules are applied.
9. Observe that the filters are applied.
Actual results:
Most noticeable: footer section with comments is not removed when accessing through link shortener.
Expected results:
Footer sections should be removed when accessing page by link shortener or direct link.
Bisected to: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ff0b109afd62c3c2dd396463bb3632228e959ff3&tochange=a4c51f3f0bb1dd51ded827d3049d633f56662a7f -> https://bugzilla.mozilla.org/show_bug.cgi?id=1590898
|
|
1,624,047 | 14,707,608 |
My last-second fix for the diffoscope failure that caused bug 1602463 to initially be backed out inadvertently hid the real problem by keeping the agent from ever being packaged at all, because it didn't occur to me that build CONFIG values don't get automatically translated into preprocessor defines, so the one that I added a check for is never set there.
I have a patch which fixes that and also actually fixes the packaging problem that diffoscope found (which is that default-browser-agent.exe was ending up in the ARM64 package's `i686` EME build directory).
|
|
1,624,122 | 14,708,126 |
Created attachment 9134888
firefox-filetype-bug.png
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
Options -> Applications -> Select PDF Content Type -> Click the Down Arrow -> Click "Application Details" -> Dialog box opens.
Actual results:
First line in content area of the dialog box is:
"The following applications can be used to handle {$type} content."
Attached image shows result.
Expected results:
"The following applications can be used to handle PDF content."
Notes:
This doesn't seems to happen with other content types.
The "Application Details" option doesn't show up with all content types.
I only noticed this after I added a second application option for opening PDF files. It may or may not have been a problem before I did this.
|
|
1,624,124 | 14,708,133 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0
Steps to reproduce:
1. Install the uBlock Origin.(https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/)
2. Add this rule to `my filters` in uBlock Origin.
(`bugzilla.mozilla.org###header`)
3. Refresh the current page.
Actual results:
The header bar on this page **is not** hidden.
Expected results:
The header bar on this page is hidden.
|
|
1,624,300 | 14,711,052 |
Created attachment 9135082
high contrast.jpg
##### [Environment:]
tested on:
- affected: Windows 10, Windows 7 Pro
- not affected: Mac 10.13, Mac 10.15.2, Ubuntu 18.04
with:
- 75.0b7 20200322132212
- 76.0a1 20200323092419
##### [Steps to reproduce:]
1. Set Windows high contrast on (any of the high contrast profiles will do)
2. Launch Firefox (new profile)
3. Open Addressbar and type *update firefox*
##### [Actual result:]
Intervention is displyed.
The buttons for the Intervention/Tips are not visible in Windows high contrast modes.
##### [Expected result:]
Intervention is displyed.
The buttons for the Intervention/Tips are visible in Windows high contrast modes.
##### [Note:]
1. IMO, possibly the same root cause as bug 1623944.
2. This bug lists the STR for Interventions; for STR to trigger Search Tips, see https://bugzilla.mozilla.org/show_bug.cgi?id=1623944#c0
|
|
1,624,308 | 14,711,130 |
**Steps to reproduce**
1. With the context selection pref turned on, open the console in the regular window, as well as the browser toolbox
1. In the regular console, evaluate the following to start a worker
```js
var workerBlob = new Blob(
[workerRunner.toString().replace(/^function .+\{?|\}$/g, '')],
{ type:'text/javascript' }
);
var workerBlobUrl = URL.createObjectURL(workerBlob);
var worker = new Worker(workerBlobUrl);
worker.onmessage = function(event) {};
worker.postMessage('foo');
function workerRunner() {
self.onmessage = function(event) {
self.postMessage('launched worker via blob URL!');
}
};
```
3. In the browser toolbox, the evaluation context selector should have this new worker in the list, select it
4. Go back to the regular console, and evaluate `worker.terminate()` to stop the worker.
**Expected results**
In the browser toolbox, the context selector switched to the top-level context
**Actual results**
The selected context still is the worker we terminated, even if it doesn't appear in the context list
---
|
|
1,624,330 | 14,711,255 |
Created attachment 9135103
snippet-x.png
**[Affected versions]:**
- Firefox Release 74.0 Build ID 20200309095159
- Firefox Beta 75.0b7 Build ID 20200322132212
- Firefox Nightly 76.0a1 Build ID 20200323092419
**[Affected Platforms]:**
- Windows 10
- Mac OS 10.15.3
- Ubuntu 18.04 x64
**[Prerequisites]:**
- Have a Firefox profile with the following pref in the "about:config" page:
- "browser.newtabpage.activity-stream.asrouterExperimentEnabled" with "true" value;
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Navigate to "about:config#asrouter" page.
3. Click the “Show” button for a long text snippet with a button. (i.e. "NEWSLETTER_TEST_DEFAULTS")
4. Horizontally resize the browser to approximately half.
**[Expected result]:**
There are no layout issues.
**[Actual result]:**
Snippet dismiss option overlaps its button.
**[Notes]:**
- Issue can be reproduced with live snippets also, as the majority have long text and a button.
- Large screens need browser resize past half.
- Small or minimum browser resize wraps the snippet correctly.
|
|
1,624,384 | 14,711,813 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
first please make sure go to bookmarks and search for an object(you must bookmarks page before) and select all bookmarks with ctrl+a or right click and select all, then try to delete with delete key or etc( at least 100 bookmark)
Actual results:
crash happens and nothing delete.
here is 3 times that my browser crash:
https://crash-stats.mozilla.org/report/index/90f49bf7-c3ad-4ec0-a56b-7f7e80200322
----
https://crash-stats.mozilla.org/report/index/770fd0a7-bcc7-4ee3-96b6-e5a620200322
----
https://crash-stats.mozilla.org/report/index/a6ffbdbd-146d-48ef-8331-a403e0200322
Expected results:
bookmarks must be removed.
|
|
1,624,388 | 14,711,836 |
The summary kind of says it all; I forgot to copy the build flag for enabling the default browser agent over into the preprocessor defines for the installer build, so the installers never think the agent is enabled, so they never try to register its scheduled task.
|
|
1,624,550 | 14,712,924 |
Steps to reproduce:
1. Navigate to <https://emk.name/test/302.cgi>.
2. Click the first link to download a file.
Actual result:
The link color is not changed.
Expected result:
The link color should be changed.
Regression range: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=90cf0ce6c916dc56b5b5c0577f468fc5c4e89745&tochange=d9958362b9bd30f00a64627cb6041df808068cb9
|
|
1,636,445 | 14,804,639 |
Created attachment 9146773
update button not visible in high contrast
**Affected versions**
* Fx77.0b3
**Affected platforms**
* Windows
**Affected platforms**
* Have an older version of Fx installed (e.g. Fx71.0b3) and run it at least once (to create a profile).
* Have a high contrast theme enabled on the OS.
**Steps to reproduce**
1. Launch the latest stub intaller.
2. Change the focus from the 'Update' button.
**Expected result**
* The Update button should still be visilbe.
**Actual result**
* Only the label is visible, but not the button border.
**Additional notes**
* This issue does not occur on Firefox Nightly.
* This issue does not occur on old beta stub installers.
* Issue occurs on both, black and white high contrast themes.
* The issue occurs regardless of the stub installer locale.
|
|
1,575,798 | 14,315,556 |
Created attachment 9087345
screenshot with the issue.png
**Affected versions**
* latest Nightly 70.0a1
**Affected platforms**
* Windows 7 x64
* macOS 10.13
* Ubuntu 18.04 x64
**Steps to reproduce**
1. Launch Firefox.
2. Navigate to about:preferences#privacy, click on Custom and deselect the "Cookies" checkbox.
3. Go to https://www.reddit.com and click on the shield icon from URL bar.
**Expected result**
* The "Blocked" section contains the "Cross-Site Tracking Cookies" item.
**Actual result**
* The "Cross-Site Tracking Cookies" item is missing from the panel.
**Regression range**
* This does not seem to be a regression, I was able to reproduce this bug on older builds as well. e.g. 70.0a1 from 2019-08-16.
**Additional notes**
* please observe the attached screenshot.
|
|
1,575,811 | 14,315,638 |
**Affected versions**
* Firefox 70.a01
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04 x64
* macOS 10.13
**Steps to reproduce**
1. Open Facebook in two different tabs.
2. In the first tab click on shield icon and turn off Trackers Protection.
3. In the second tab click on shield icon and turn on Trackers Protection.
4. In the first tab click again on the shield icon and observe the blocked trackers.
5. Check the same thing in the second tab.
**Expected result**
* 4. Social Media Trackers are displayed in the "Blocked" section.
* 5. Social Media Trackers are displayed in the "Blocked" section
**Actual result**
* 4. Social Media Trackers are displayed in the "Blocked" section.
* 5. Social Media Trackers are displayed in the "None Detected" section.
**Regression range**
* I don't think this is a regression.
**Additional notes**
* After the page is refresh, Social Media Trackers are moved to "None Detected" section.
* This bug is reproducing on multiple sites: Twitter, LinkedIn, Instagram etc.
* This issue is reproducing when you change the setting from about:preferences#privacy, too:
1. Open Facebook and turn off Trackers Protection for that site.
2. Go to about:preferences#privacy.
3. In the Manage Exceptions... remove Facebook from the list and save the changes.
4. Go back to the tab that contains Facebook.
Actual results:
* Social Media Trackers are displayed in the "Blocked" section.
|
|
1,575,812 | 14,315,639 |
Created attachment 9087355
Screenshot_1.png
**Affected versions**
* Firefox 70.a01
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04 x64
* macOS 10.13
**Steps to reproduce**
1. Go to about:preferences#privacy.
2. Select the option Strict / Custom.
3. Go to any site that contains trackers and click on the shield icon.
4. Turn off Trackers Protection.
5. Click on the shield icon again and observe the behaviour.
**Expected result**
* The panel is correctly displayed.
**Actual result**
* The portion with “Allowed” and WHY? hyperlink are missing.
**Regression range**
* I don't think this is a regression.
**Additional notes**
* Please look at the attached image.
|
|
1,575,813 | 14,315,641 |
**Affected versions**
* Firefox 70.a01
**Affected platforms**
* Windows 10 x64
* Ubuntu 18.04 x64
* macOS 10.13
**Steps to reproduce**
1. Go to about:preferences#privacy.
2. Select Custom mode and make sure that everything is selected except "Fingerprinters".
3. Go to https://senglehardt.com/test/trackingprotection/test_pages/fingerprinting_and_cryptomining.html.
4. Click on the shield icon.
**Expected result**
* Fingerprinters are displayed in the "Allowed" section.
**Actual result**
* Fingerprinters are displayed in the "None Detected" section.
**Regression range**
* I don't think this is a regression.
**Additional notes**
* The same issue happens with Cryptominers.
* This issue is not reproducing with Cookies and Tracking Content.
|
|
1,575,820 | 14,315,680 |
Created attachment 9087362
rec of the issue.gif
[Affected versions]:
- Firefox Beta 69.0b15 - Build ID: 20190819184224
- Firefox Nightly 70.0a1 - Build ID: 20190821215524
[Affected Platforms]:
- All Windows
- All Linux
- All Mac
[Prerequisites]:
- Have a new Firefox profile;
- Have valid FxA credentials.
- You are not logged in to "Firefox Sync".
[Steps to reproduce]:
1. Open the browser with the profile from prerequisites and click the "Firefox Account" toolbar button.
2. Click the "Turn on Sync..." button and enter your credentials.
3. Open a "New Tab" and observe the behavior.
[Expected result]:
- The page is successfully opened and the "First Run Triplets" are displayed at the top of the page.
[Actual result]:
- The "First Run Triplets" are not displayed at all.
[Notes]:
- The "First Run Triplets" will be displayed again on the next opened tab.
- Attached a screen recording of the issue.
|
|
1,575,859 | 14,315,971 |
Created attachment 9087407
capture.gif
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
1. Open https://www.google.com/
2. Add a `block` cookie exception for https://www.google.com/
3. Open the Cross-Site Tracking Cookies sub-panel in the google's tab.
4. Refresh the page.
5. Open the Cross-Site Tracking Cookies sub-panel in the google's tab.
Actual results:
The label of the clear cookie exception button displayed as `Allowed` in Step 3, and displayed as `undefined` in Step 5.
Expected results:
The label of the clear cookie exception button should be displayed as `Blocked` in Steps 3 and 5.
---
Sorry for my bad English.
|
|
1,575,887 | 14,316,218 |
[Affected versions]:
- Firefox Beta 69.0b15 - Build ID: 20190819184224
- Firefox Nightly 70.0a1 - Build ID: 20190822095439
[Affected Platforms]:
- All Windows
- All Linux
- All Mac
[Prerequisites]:
- Have a new Firefox profile,
- Have no other tab already pinned.
[Steps to reproduce]:
1. Open the browser with the profile from prerequisites.
2. Open a new tab and navigate to "https://www.youtube.com/"
3. Change the system's time to 17 min into the future.
4. Repeat step 2 and 3 again.
5. Open a new tab and navigate to "https://www.youtube.com/".
6. Observe the right part of the "Adress Bar".
[Expected result]:
- The "CFR Recommendation" button is displayed in the right part of the "Address Bar".
[Actual result]:
- Only the "Page actions", "Save to Pocket" and "Bookmark this page" buttons are displayed.
[Regression Window]:
- Considering the fact that this issue is not reproducible with latest Firefox Release (68.0.2), using the Mozregression tool I have managed to find a regression:
Last good revision: d47d9f4bf9a9ea8b816534916292ca446c7543ce
First bad revision: 49f075579f00c253f32048b0b8f22bf8081be1ce
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d47d9f4bf9a9ea8b816534916292ca446c7543ce&tochange=49f075579f00c253f32048b0b8f22bf8081be1ce
[Notes]:
- Attached a screen recording of the issue.
|
|
1,575,947 | 14,316,717 |
Steps to reproduce:
In Firefox Nightly navigate to https://ca.warbyparker.com/ and observe the behavior.
Expected:
Site loads
Actual:
Site loads, but then goes blank due to an error: `TypeError: "_ is not a function"` here:
```
_ = k.µ,
E = k.ƒ,
S = n(4),
w = S.isEmpty,
L = S.kebabCase,
N = S.isFunction,
x = S.omit;
n(169);
var M = function (e) {
var t = e.props,
n = e.state;
return _(f(), 'c-formgroup', t.cssUtility, t.cssModifier, E(n.isFocused) ('-focus'), E(!w(t.txtError)) ('-error'))
},
```
When I set `dom.script_loader.external_scripts.utf8_parsing.enabled` to be false, the error goes away
From mozregression:
```
6:24.69 INFO: Narrowed inbound regression window from [5f48ef70, 613d59f3] (3 builds) to [a3e42056, 613d59f3] (2 builds) (~1 steps left)
6:24.69 INFO: No more inbound revisions, bisection finished.
6:24.69 INFO: Last good revision: a3e4205698b8711791e4bc97ceaceabaa137c553
6:24.69 INFO: First bad revision: 613d59f386c7a757825b4ad7055db072075f5670
6:24.69 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a3e4205698b8711791e4bc97ceaceabaa137c553&tochange=613d59f386c7a757825b4ad7055db072075f5670
```
|
|
1,576,252 | 14,318,771 |
Since it is privileged data, it needs to happen per extension rather than in common data which is shared.
|
|
1,576,266 | 14,318,868 |
STR:
1. Install an extension that calls `browser.urlbar.engagementTelemetry.set({ value: true })` [1]
2. Restart Firefox
3. Uninstall or disable the extension
4. Open about:config and observe that `browser.urlbar.eventTelemetry.enabled` remains true when it should have been cleared
If you skip step 2 -- i.e., don't restart Firefox -- the pref is cleared, as expected.
The `browser.urlbar.engagementTelemetry` browser setting maps to the `browser.urlbar.eventTelemetry.enabled` pref, which does not exist by default. See https://searchfox.org/mozilla-central/rev/a650fac7b069ded3d63eba530271ce80e6cafb1b/browser/components/extensions/parent/ext-urlbar.js#201
I'm not sure whether this is a bug in the `browser.urlbar` implementation or something deeper in the webextensions framework. I did some debugging and it looks like the problem is in or around `ExtensionPreferencesManager`.
When I restart Firefox and then unload the extension, `setPrefs` is called, and `prefs` is an empty object here: https://searchfox.org/mozilla-central/source/toolkit/components/extensions/ExtensionPreferencesManager.jsm#99
In contrast, when I don't restart Firefox before unloading the extension, `prefs` is `{ "browser.urlbar.eventTelemetry.enabled": undefined }`.
And when I give `browser.urlbar.eventTelemetry.enabled` a default value of `false` by adding it to browser/app/profile/firefox.js, `prefs` is `{ "browser.urlbar.eventTelemetry.enabled": false }`.
Here's an excerpt from a chat about it with Shane:
> mixedpuppy: ok, so what happens is that there is an initialvalue that is set via Preferences.get(prefname)
> mixedpuppy: if that initialvalue is undefined, then Preferences.reset(prefname) shoudl be called
> mixedpuppy: https://searchfox.org/mozilla-central/rev/a650fac7b069ded3d63eba530271ce80e6cafb1b/toolkit/components/extensions/ExtensionPreferencesManager.jsm#79-115
[1] e.g. https://github.com/0c0w3/urlbar-top-sites-experiment -- xpi in bug 1547670
|
|
1,576,343 | 14,319,313 |
STR:
1. Go to about:preferences and open Network Settings dialog.
2. Check 'Enable DNS over HTTPS'.
3. Click 'OK' to close the dialog.
4. Reopen the dialog.
ER:
'Use Provider' listbox has labels.
AR:
There is no label in 'Use Provider' listbox.
mozregression:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9234c94b4b9ac47d82496fb2b6442e5754ec4fd9&tochange=743b76c2c4fe581711b4164eade1d54a2a5f96fb
|
|
1,576,509 | 14,320,166 |
Right now, the contextual feature recommender adds a "Recommendations" button to the addressbar which does not get announced to screen reader users unless they happen to stumble upon it. We should figure out how to make this feature more obvious to screen reader users.
|
|
1,576,524 | 14,320,265 |
As reported on reddit: https://www.reddit.com/r/firefox/comments/cv08ek/bad_behavior_in_pop_up_window/
Steps to reproduce:
1. Install https://addons.mozilla.org/es/firefox/addon/popup/
2. Navigate to https://codepen.io/nadoaa/pen/vbJpyr
3. Click add-on toolbar icon to open page
4. Move mouse around the preview area
What happens:
The white circle does not track with the mouse cursor.
Expected result:
White circle should track with mouse cursor as previously.
There is a video of the issue available: https://reddit.com/link/cv08ek/video/c0ucmbzv1hi31/player
19:31.71 INFO: No more inbound revisions, bisection finished.
19:31.71 INFO: Last good revision: 3c4b55694127237c3dd740d5ed055959c4d783fe
19:31.71 INFO: First bad revision: 91d0c9066fd139285e025b0b87a70f61823281af
19:31.71 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3c4b55694127237c3dd740d5ed055959c4d783fe&tochange=91d0c9066fd139285e025b0b87a70f61823281af
|
|
1,576,605 | 14,322,561 |
Created attachment 9088101
about:support
Reproducible: reproducible with new profile, often
```
Steps to reproduce:
1. Create new profile and start browser
2. Open any video (e.g, https://videos.cdn.mozilla.net/uploads/mozillaorg/Mozilla_2014_i_am.webm )
3. Start playback if necessary
4. Left click on blue toggle button
--- if not reproduced, restart browser and repeat from step 2.
Or
Right click on the video and choose "Picture in Picture"
--- if not reproduced, restart browser and repeat from step 2.
```
Actual Results:
Nothing happens
Expected Results:
Should switch to PiP mode
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f246623260ee3b80c2021c48f5d56f54073f8060&tochange=b134d9db39a9da2cdb1a4b7c19e6023063fde7f4
Regressed by: Bug 1568320
|
|
1,576,888 | 14,325,109 |
We don't normally use px values for font-sizes, because OSes have different defaults and even offer customizing the default font size. Instead we use em to make text relatively smaller or bigger.
Also note that because the urlbar's font size is different across platforms, the current px values will look more or less inconsistent depending on the OS.
|
|
1,576,889 | 14,325,118 |
Judging by just looking at the code, this is probably not RTL-friendly: https://searchfox.org/mozilla-central/rev/325c1a707819602feff736f129cb36055ba6d94f/browser/themes/shared/urlbar-autocomplete.inc.css#67
You normally want to use `padding-inline-end` instead of `padding-right`.
|
|
1,576,990 | 14,325,873 |
[Tracking Requested - why for this release]:
Jean-Yves, this is a regression in Firefox 69 from Gfycat bug 1560440. I bisected this regression to this pushlog in 70 Nightly, though the fix (and this regression) were also uplifted to 69 Beta:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3179c40a2a25fdba731bed824fb4352bb8209e3b&tochange=c52127007a0162c72b87a8d4613400d3741bcd5f
### STR:
1. Play this btnn.mp4 video in Slack: https://app.slack.com/client/T027LFU12/C027LFU20/files/FMRGE3E7J
### Expected Result:
The video will play smoothing, showing a screen capture of Firefox for Android scrolling to left to right from "WELCOME" to "PRIVACY" to "ACCOUNT" pages.
### Actual Result:
In Firefox 69 and 70 on Windows, the video starts playback at time 0:01 instead of 0:00 and then gets stuck on a frame showing the "PRIVACY" page from time 0:04 to the end time 0:08.
|
|
1,577,107 | 14,327,578 |
Created attachment 9088647
IndexedDB_UAF.html
```cpp
void IDBObjectStore::AppendIndexUpdateInfo(
int64_t aIndexID, const KeyPath& aKeyPath, bool aUnique, bool aMultiEntry,
const nsCString& aLocale, JSContext* aCx, JS::Handle<JS::Value> aVal,
nsTArray<IndexUpdateInfo>& aUpdateInfoArray, ErrorResult& aRv) {
const bool localeAware = !aLocale.IsEmpty();
if (!aMultiEntry) {
...
return;
}
JS::Rooted<JS::Value> val(aCx);
if (NS_FAILED(aKeyPath.ExtractKeyAsJSVal(aCx, aVal, val.address()))) {
return;
}
bool isArray;
if (!JS_IsArrayObject(aCx, val, &isArray)) {
IDB_REPORT_INTERNAL_ERR();
aRv.Throw(NS_ERROR_DOM_INDEXEDDB_UNKNOWN_ERR);
return;
}
if (isArray) {
JS::Rooted<JSObject*> array(aCx, &val.toObject());
uint32_t arrayLength;
if (NS_WARN_IF(!JS_GetArrayLength(aCx, array, &arrayLength))) {
IDB_REPORT_INTERNAL_ERR();
aRv.Throw(NS_ERROR_DOM_INDEXEDDB_UNKNOWN_ERR);
return;
}
for (uint32_t arrayIndex = 0; arrayIndex < arrayLength; arrayIndex++) {
JS::Rooted<JS::Value> arrayItem(aCx);
if (NS_WARN_IF(!JS_GetElement(aCx, array, arrayIndex, &arrayItem))) { // JS_GetElement can trigger js getter, call deleteIndex here will free `aLocale`.
IDB_REPORT_INTERNAL_ERR();
aRv.Throw(NS_ERROR_DOM_INDEXEDDB_UNKNOWN_ERR);
return;
}
Key value;
auto result = value.SetFromJSVal(aCx, arrayItem, aRv);
if (!result.Is(Ok, aRv) || value.IsUnset()) {
// Not a value we can do anything with, ignore it.
aRv.SuppressException();
continue;
}
IndexUpdateInfo* updateInfo = aUpdateInfoArray.AppendElement();
updateInfo->indexId() = aIndexID;
updateInfo->value() = value;
if (localeAware) {
auto result =
value.ToLocaleBasedKey(updateInfo->localizedValue(), aLocale, aRv);// UAF occurs!
if (NS_WARN_IF(!result.Is(Ok, aRv))) {
if (result.Is(Invalid, aRv)) {
aRv.Throw(NS_ERROR_DOM_INDEXEDDB_UNKNOWN_ERR);
}
return;
}
}
}
} else {
...
}
}
```
|
|
1,577,181 | 14,328,180 |
Created attachment 9088710
screenshot issue address bar.png
[Affected versions]:
- 70.0a1 (2019-08-28)
[Affected platforms]:
- Windows 10
- macOS 10.13
[Steps to reproduce]:
- Access the about:preferences#search page
- Click the “Find more search engines” link and add several search engines
- Open a new tab and type anything inside the address bar
- Observe the address bar dropdown bottom
[Expected result]:
- All added search engines are visible and displayed on several rows when the case.
[Actual result]:
- The last added search engines are not displayed.
- The “Change search settings” button is nowhere to be found.
[Regression range]:
- Introduced in Fx 70.0a1 (2019-08-14) with the new design changes (bug 1561894).
[Additional notes]:
- Ubuntu 18.04 is not affected, the overflow implementation looks good.
|
|
1,577,316 | 14,328,966 |
Created attachment 9088846
Notification with settings cog menu
Notifications produced by extensions (`browser.notifications.create()`) now show a 'via' origin and setting cog. These refer to the extension only by their Internal UUID.
STR:
1. Install an extension that provides notifications (e.g. [webextensions-examples/notify-link-clicks](https://github.com/mdn/webextensions-examples/tree/master/notify-link-clicks-i18n) )
2. Trigger a notification
Actual Results:
The notification comes with a confusing 'via' origin message and semi-functional settings cog button. Choosing to disable notifications from the extension origin has no apparent effect - the origin is not added to the Notifications Exceptions List, no errors appear in the Browser Console, and future notifications continue to appear as normal.
Expected Results:
Assuming this is not an intentional change, notifications from extensions should not show the 'via' origin and settings cog.
|
|
1,577,324 | 14,329,022 |
See screenshot. That should look like a link, to signify that you can click on it.
|
|
1,577,388 | 14,329,526 |
STR:
1. Open https://pad.mozilla.org/p/7LVooPJ3OM (note: Mozilla auth required. This will _not_ reproduce with the public instance of etherpad)
2. Zoom the page by using Ctrl+mouse wheel to, say, 150%.
3. Switch to another tab
4. Switch back to the etherpad tab
Expected results:
Page zoom is preserved
Actual results:
Page zoom is reset to 100%.
I asked others on slack to reproduce this but they couldn't so it's possibly at least Windows specific.
I could not reproduce with beta but I _could_ reproduce with a fresh profile in Nightly so I don't believe it is profile / extension related.
|
|
1,577,587 | 14,330,845 |
Double clicking on the titlebar in mac os doesn't minimize firefox to the dock with the "Double click a window's titlebar to minimize the dock" preference enabled.
|
|
1,577,708 | 14,331,932 |
Created attachment 9089292
Screenshot from 2019-08-30 10-39-41.png
**Affected versions**
* 70.0b2, 70.0a1 (2019-08-29)
**Affected platforms**
* Ubuntu 16.04
**Steps to reproduce**
1. Launch Firefox swap to Dark Theme and enable the search bar;
2. Click inside the Search Bar and type any text;
3. Hover over the Change Search Settings button;
**Expected result**
* Buttons are properly displayed;
**Actual result**
* the default state of the background_color for the button is the on_hover one;
* the hover effect makes it so the text is not readable;
**Regression range**
* Pushlog [URL](https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=eff8c62bdeb71f78dbf0e2324b31d094355cf3dc&tochange=d3deef805f92d4a899d7b6de76b347328f33e54b)
* Potential regressor: bug 1561894;
**Additional notes**
* attached screenshot with the issue;
* 68, 69 builds are not affected;
|
|
1,577,719 | 14,332,008 |
This crash was found while dom fuzzing, however the testcase does not reproduce. It looks like the nr_reg_assoc_destroy method is used incorrectly here:
https://searchfox.org/mozilla-central/source/media/mtransport/third_party/nrappkit/src/registry/registrycb.c#185
=================================================================
==1654==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fed29ec5e10 at pc 0x7fed4011894e bp 0x7fed29ec5d50 sp 0x7fed29ec5d48
READ of size 8 at 0x7fed29ec5e10 thread T5 (IPDL Background)
#0 0x7fed4011894d in r_assoc_destroy /builds/worker/workspace/build/src/media/mtransport/third_party/nrappkit/src/util/libekr/r_assoc.c
#1 0x7fed40117d36 in nr_reg_assoc_destroy /builds/worker/workspace/build/src/media/mtransport/third_party/nrappkit/src/registry/registrycb.c:271:10
#2 0x7fed40117d36 in nr_reg_register_callback /builds/worker/workspace/build/src/media/mtransport/third_party/nrappkit/src/registry/registrycb.c:185
#3 0x7fed4011a477 in NR_reg_register_callback /builds/worker/workspace/build/src/media/mtransport/third_party/nrappkit/src/registry/registrycb.c:404:20
#4 0x7fed4011a477 in r_log_get_destinations /builds/worker/workspace/build/src/media/mtransport/third_party/nrappkit/src/log/r_log.c:571
#5 0x7fed40113826 in _r_log_init /builds/worker/workspace/build/src/media/mtransport/third_party/nrappkit/src/log/r_log.c:646:9
#6 0x7fed40113826 in r_log_init /builds/worker/workspace/build/src/media/mtransport/third_party/nrappkit/src/log/r_log.c:622
#7 0x7fed4011501d in NR_reg_init /builds/worker/workspace/build/src/media/mtransport/third_party/nrappkit/src/registry/registry.c:105:6
#8 0x7fed3566c25a in mozilla::RLogConnector::CreateInstance() /builds/worker/workspace/build/src/media/mtransport/rlogconnector.cpp:106:5
#9 0x7fed35340465 in mozilla::MediaTransportHandlerSTS::EnterPrivateMode() /builds/worker/workspace/build/src/media/webrtc/signaling/src/peerconnection/MediaTransportHandler.cpp:1090:3
#10 0x7fed3535c55a in mozilla::MediaTransportParent::RecvEnterPrivateMode() /builds/worker/workspace/build/src/media/webrtc/signaling/src/peerconnection/MediaTransportParent.cpp:118:20
#11 0x7fed346a2c45 in mozilla::dom::PMediaTransportParent::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/build/src/obj-firefox/ipc/ipdl/PMediaTransportParent.cpp:435:64
#12 0x7fed34d29ca0 in mozilla::ipc::PBackgroundParent::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/build/src/obj-firefox/ipc/ipdl/PBackgroundParent.cpp:3588:32
#13 0x7fed33ec0a86 in mozilla::ipc::MessageChannel::DispatchAsyncMessage(mozilla::ipc::ActorLifecycleProxy*, IPC::Message const&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:2184:25
#14 0x7fed33ebb7eb in mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:2108:9
#15 0x7fed33ebdda7 in mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::MessageChannel::MessageTask&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:1955:3
#16 0x7fed33ebec37 in mozilla::ipc::MessageChannel::MessageTask::Run() /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:1986:13
#17 0x7fed32cd7800 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:1225:14
#18 0x7fed32cdd628 in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:486:10
#19 0x7fed33ecb842 in mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) /builds/worker/workspace/build/src/ipc/glue/MessagePump.cpp:303:20
#20 0x7fed33dc5632 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:315:10
#21 0x7fed33dc5632 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:308
#22 0x7fed33dc5632 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:290
#23 0x7fed32cd114a in nsThread::ThreadFunc(void*) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:458:11
#24 0x7fed55d870bd in _pt_root /builds/worker/workspace/build/src/nsprpub/pr/src/pthreads/ptthread.c:198:5
#25 0x7fed559cb6da in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76da)
#26 0x7fed549a988e in clone (/lib/x86_64-linux-gnu/libc.so.6+0x12188e)
Address 0x7fed29ec5e10 is located in stack of thread T5 (IPDL Background) at offset 80 in frame
#0 0x7fed40117acf in nr_reg_register_callback /builds/worker/workspace/build/src/media/mtransport/third_party/nrappkit/src/registry/registrycb.c:119
This frame has 3 object(s):
[32, 40) 'ptr.addr.i' (line 271)
[64, 72) 'assoc' (line 121) <== Memory access at offset 80 overflows this variable
[96, 105) 'cb_id' (line 125) <== Memory access at offset 80 underflows this variable
HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork
(longjmp and C++ exceptions *are* supported)
Thread T5 (IPDL Background) created by T0 (Socket Process) here:
#0 0x55a35f8d829d in __interceptor_pthread_create /builds/worker/fetches/llvm-project/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:210:3
#1 0x7fed55d791b8 in _PR_CreateThread /builds/worker/workspace/build/src/nsprpub/pr/src/pthreads/ptthread.c:430:14
#2 0x7fed55d62d9e in PR_CreateThread /builds/worker/workspace/build/src/nsprpub/pr/src/pthreads/ptthread.c:503:12
#3 0x7fed32cd3639 in nsThread::Init(nsTSubstring<char> const&) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:672:8
#4 0x7fed32cdc770 in nsThreadManager::NewNamedThread(nsTSubstring<char> const&, unsigned int, nsIThread**) /builds/worker/workspace/build/src/xpcom/threads/nsThreadManager.cpp:415:12
#5 0x7fed32ce028a in NS_NewNamedThread(nsTSubstring<char> const&, nsIThread**, nsIRunnable*, unsigned int) /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:139:57
#6 0x7fed33e70282 in NS_NewNamedThread<16> /builds/worker/workspace/build/src/obj-firefox/dist/include/nsThreadUtils.h:71:10
#7 0x7fed33e70282 in (anonymous namespace)::ParentImpl::CreateBackgroundThread() /builds/worker/workspace/build/src/ipc/glue/BackgroundImpl.cpp:944
#8 0x7fed33e27fe4 in Alloc /builds/worker/workspace/build/src/ipc/glue/BackgroundImpl.cpp:818:30
#9 0x7fed33e27fe4 in mozilla::ipc::BackgroundParent::Alloc(mozilla::dom::ContentParent*, mozilla::ipc::Endpoint<mozilla::ipc::PBackgroundParent>&&) /builds/worker/workspace/build/src/ipc/glue/BackgroundImpl.cpp:640
#10 0x7fed33bf7d87 in mozilla::net::SocketProcessBridgeParent::RecvInitBackground(mozilla::ipc::Endpoint<mozilla::ipc::PBackgroundParent>&&) /builds/worker/workspace/build/src/netwerk/ipc/SocketProcessBridgeParent.cpp:41:8
#11 0x7fed349eb43d in mozilla::net::PSocketProcessBridgeParent::OnMessageReceived(IPC::Message const&) /builds/worker/workspace/build/src/obj-firefox/ipc/ipdl/PSocketProcessBridgeParent.cpp:130:69
#12 0x7fed33ec0a86 in mozilla::ipc::MessageChannel::DispatchAsyncMessage(mozilla::ipc::ActorLifecycleProxy*, IPC::Message const&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:2184:25
#13 0x7fed33ebb7eb in mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:2108:9
#14 0x7fed33ebdda7 in mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::MessageChannel::MessageTask&) /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:1955:3
#15 0x7fed33ebec37 in mozilla::ipc::MessageChannel::MessageTask::Run() /builds/worker/workspace/build/src/ipc/glue/MessageChannel.cpp:1986:13
#16 0x7fed32cd7800 in nsThread::ProcessNextEvent(bool, bool*) /builds/worker/workspace/build/src/xpcom/threads/nsThread.cpp:1225:14
#17 0x7fed32cdd628 in NS_ProcessNextEvent(nsIThread*, bool) /builds/worker/workspace/build/src/xpcom/threads/nsThreadUtils.cpp:486:10
#18 0x7fed33ec9e64 in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /builds/worker/workspace/build/src/ipc/glue/MessagePump.cpp:110:5
#19 0x7fed33dc5632 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:315:10
#20 0x7fed33dc5632 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:308
#21 0x7fed33dc5632 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:290
#22 0x7fed3c0a9149 in nsBaseAppShell::Run() /builds/worker/workspace/build/src/widget/nsBaseAppShell.cpp:137:27
#23 0x7fed3ff96acf in XRE_RunAppShell() /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:934:20
#24 0x7fed33dc5632 in RunInternal /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:315:10
#25 0x7fed33dc5632 in RunHandler /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:308
#26 0x7fed33dc5632 in MessageLoop::Run() /builds/worker/workspace/build/src/ipc/chromium/src/base/message_loop.cc:290
#27 0x7fed3ff96376 in XRE_InitChildProcess(int, char**, XREChildData const*) /builds/worker/workspace/build/src/toolkit/xre/nsEmbedFunctions.cpp:769:34
#28 0x55a35f922d73 in content_process_main /builds/worker/workspace/build/src/browser/app/../../ipc/contentproc/plugin-container.cpp:56:28
#29 0x55a35f922d73 in main /builds/worker/workspace/build/src/browser/app/nsBrowserApp.cpp:267
#30 0x7fed548a9b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96)
SUMMARY: AddressSanitizer: stack-buffer-overflow /builds/worker/workspace/build/src/media/mtransport/third_party/nrappkit/src/util/libekr/r_assoc.c in r_assoc_destroy
Shadow bytes around the buggy address:
0x0ffe253d0b70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0ffe253d0b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0ffe253d0b90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0ffe253d0ba0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0ffe253d0bb0: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f2 f2 f2
=>0x0ffe253d0bc0: 00 f2[f2]f2 00 01 f3 f3 00 00 00 00 00 00 00 00
0x0ffe253d0bd0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0ffe253d0be0: f1 f1 f1 f1 00 00 00 00 00 00 00 00 00 00 00 00
0x0ffe253d0bf0: 00 00 00 00 f2 f2 f2 f2 04 f2 01 f3 00 00 00 00
0x0ffe253d0c00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0ffe253d0c10: f1 f1 f1 f1 04 f3 f3 f3 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==1654==ABORTING
|
|
1,577,740 | 14,332,192 |
Created attachment 9089332
Screenshot 2019-08-30 at 11.42.22.png
See screenshot. Even as someone with good eyesight, I had to squint to read this. It's much too light to pass wcag contrast checks (1.82 : 1). Looks like the colour is specified as rgba(0,0,0,0.247).
|
|
1,577,742 | 14,332,200 |
We need to trump this z-index: https://searchfox.org/mozilla-central/rev/7088fc958db5935eba24b413b1f16d6ab7bd13ea/browser/themes/shared/tabs.inc.css#450
|
|
1,577,881 | 14,333,276 |
STR
- Open Browser Toolbox & Debugger
- Open Content Toolbox and select the Network panel
- Load devtools/client/netmonitor/src/components/App.js
- Try to create BP in the render method (line 64 or 67)
- It tends to work for the first time, try other files from DevTools code base in case of success. Also try to reload the page where Network panel is opened and consequently try to create the BP again.
```
There is an exception when trying to set a breakpoint using the BP gutter:
JavaScript error: resource://devtools/client/debugger/src/client/firefox/commands.js, line 201: TypeError: thread is null
```
This bug probably causes the blank-debugger panel crash
|
|
1,577,944 | 14,333,687 |
Created attachment 9089583
Loading the BBC news site when importing windows certificates: note the CSS takes 12.5 s to load.
Over the past three or four months I've noticed an intermittent but frequent massive performance regression in Firefox Nightly. Sites are often painfully slow to load and in some cases load incorrectly, for example, the site may fail to load its stylesheets.
The system I am using is a Windows 10 machine. I'm running 32 bit nightly (70.0a1, for example 2019-07-21 and 2019-08-30, but I think version 69 is affected, see later). The problem occurs even in safe mode and on a fresh profile.
(When investigating I used a mix of my normal profile and a fresh profile and normal mode and safe mode, so individual results later might be for any combination, however, this makes no difference.)
The problem shows only on sites that use TLS (that is, HTTPS sites). I think it's related to importing enterprise root certificates. I'm a home user but I have both AVG and Qustodio installed on this system. Although AVG does not have web filtering turned on and although Qustodio is not enabled for my account, they do install certificates. I think the mere presence of these certificates is a factor.
The problem has been difficult to track down because it has proven to be awkward to reproduce under controlled conditions. This is, I believe, because at least one component of the problem is a cascading failure where performance degrades over short time periods (maybe queues fill up). The problem shows most clearly when navigating rapidly between sites as that is the time it can affect resources loading early in the page as opposed to less important resources that load later. Having other tabs running might make things worse.
I think sites which trigger HTTPS requests as they unload are most likely to affect the next page.
Even when the problem isn't severe enough to cause complete failure of the page, it shows up clearly in the network debugging tab as long blocked and TLS handshake times. In the example later, a resource on a site that normally spends 100 ms blocked, 80 ms on the TLS handshake and 62 ms to load, can balloon to 6.2 seconds blocked and 6.2 seconds on the TLS handshake (but the loading time is unaffected at 50 ms). However, this is not the worst case and requests can time out.
The problem is easiest to reproduce if the disable cache option is selected on the network debugging tab but the problem shows in normal operation even when the cache is enabled.
Some experimentation showed that the problem is correlated with having the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Mozilla\Firefox\Certificates\ImportEnterpriseRoots set to 1 (presumably the equivalent about:config setting, security.enterprise_roots.enabled, would also trigger the problem but I haven't checked). If this key is set to 0 then the problem goes away completely.
Because the problem appears to be related to a sequence of browsing, I developed a test where I navigated to the four sites https://www.bleepingcomputer.com/, http://www.theregister.co.uk/, http://www.telegraph.co.uk/ and http://news.bbc.co.uk/ in that order. Although I've used HTTP URLs for some of the sites, they immediately redirect to the HTTPS variant.
I also found another site that would consistently show a difference in performance even though it never completely failed. It was https://chromachecker.com/info/en/page/webbrowser
Attached are two screenshots of the network debugging tab, one with ImportEnterpriseRoots set to 0 and one with it set to 1. This is for the last step in the sequence test. I've highlighted the first CSS load for the site being navigated to (BBC). I also draw your attention to the requests due to the site I've just left (as identified by the referrer header). I've marked those with a dark red dot on the screenshot. This shows how navigating to a low resource site can suffer from a sequence of other network requests getting in the way (I believe this is why the problem was so difficult to get a reproduction for).
Some investigation with Process Monitor shows a vast difference in the number of accesses to cert9.db and the associated -journal and -wal files. I believe this indicates a change in the number of database accesses due to certificate activity. I don't know if these accesses are directly the cause of the slowdown or just a marker.
For the chromachecker site, for one measurement run, with ImportEnterpriseRoots=0, the browser made 780 access to cert9.db and 130 accesses to each of the -journal and -wal files (different runs show slightly different numbers so 780/130 could be 720/120). With ImportEnterpriseRoots=1 I saw 36354 accesses to cert9.db and 6059 accesses to the -journal and -wal files. This is an increase of roughly a factor of 45.
At one point when I was experimenting with sequences (possibly not the same sequence I described earlier), I saw a change from 3570/595 accesses to 291660/48654, an 80-fold increase.
Having Process Monitor running does slow down the system but, for reference, on just chromachecker, the total time of the cert9.db* accesses increases from ~50 ms to ~2 s. For the sequence the time goes from ~250 ms to ~20 s.
Using moz-regresssion, I've tracked the regression down to the fix for bug 1551177 (skip self-signed intermediate certificates that aren't trust anchors in path building). That's why I've marked this against Firefox version 69 and against the Core Security: PSM component.
On the last working autoland build (8b074e2a3b68) for the chromachecker site for ImportEnterpriseRoots of 0 and 1, I saw 876/146 and 720/120 accesses respectively (the 876/146 measurement could be a normal variation). For the first broken autoland build (5a721a7648f2, https://hg.mozilla.org/integration/autoland/rev/5a721a7648f2) I saw 720/120 and 34308/5718 accesses.
Given that the problem is related to accessing the OS's root certificates and that bug 1551177 is something to do with self-signed certificates, I had a look at the Windows certificate store. However, at this point it's really getting past the level I can follow. The following information from Powershell might be useful to others:
```
PS C:\Users\Steven> import-module pki
PS C:\Users\Steven> cd Cert:\LocalMachine\Root
PS Cert:\LocalMachine\Root> @(dir -recurse | ? {$_.Issuer -ne $_.Subject}).Count
1
PS Cert:\LocalMachine\Root> @(dir -recurse | ? {$_.Issuer -eq $_.Subject}).Count
414
PS Cert:\LocalMachine\Root> @(dir -recurse | ? {$_.Issuer -like 'CN=*Qustodio*' }).Count
18
PS Cert:\LocalMachine\Root> @(dir -recurse | ? {$_.Issuer -like 'CN=*AVG*' }).Count
2
```
Searching through Bugzilla, I've found bug 1555306 (Collision on NS find_objects()/sqlite3PagerSharedLock() when fetching OSCP causes extereme variance in page load times), so I tried turning off the option "Query OCSP responder servers to confirm the current validity of certificates" but it had no effect.
I also found bug 1577038 (add PK11_GetCertsFromPrivateKey to return all certificates with public keys matching a particular private key) and related bug 1573542 (Slow performance (switching tabs, interacting with map) on this map) which sound potentially similar.
|
|
1,577,959 | 14,333,785 |
**Filed by:** rgurzau [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=264374586&repo=autoland
**Full log:** https://queue.taskcluster.net/v1/task/Z_mw3gwTTHCDlesitAwfPg/runs/0/artifacts/public/logs/live_backing.log
---
[task 2019-08-31T02:17:21.838Z] TEST START | karma
[task 2019-08-31T02:18:12.762Z] (node:76) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
[task 2019-08-31T02:18:12.763Z] npm ERR! code ELIFECYCLE
[task 2019-08-31T02:18:12.763Z] npm ERR! errno 1
[task 2019-08-31T02:18:12.763Z] npm ERR! [email protected] testmc:unit: `karma start karma.mc.config.js`
[task 2019-08-31T02:18:12.763Z] npm ERR! Exit status 1
[task 2019-08-31T02:18:12.763Z] npm ERR!
[task 2019-08-31T02:18:12.763Z] npm ERR! Failed at the [email protected] testmc:unit script.
[task 2019-08-31T02:18:12.763Z] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[task 2019-08-31T02:18:12.763Z]
[task 2019-08-31T02:18:12.763Z] npm ERR! A complete log of this run can be found in:
[task 2019-08-31T02:18:12.763Z] npm ERR! /builds/worker/.npm/_logs/2019-08-31T02_18_12_756Z-debug.log
[task 2019-08-31T02:18:12.785Z] TEST-UNEXPECTED-FAIL karma | activity-stream:CFRMessageProvider should have a total of 4 messages: expected [ Array(5) ] to have a length of 4 but got 5
[task 2019-08-31T02:18:12.785Z] AssertionError@http://localhost:9876/base/node_modules/chai/chai.js?db92883971379fbea71a12c25b271c26a3afc3f6:9449:13
[task 2019-08-31T02:18:12.785Z] [3]</module.exports/Assertion.prototype.assert@http://localhost:9876/base/node_modules/chai/chai.js?db92883971379fbea71a12c25b271c26a3afc3f6:239:13
[task 2019-08-31T02:18:12.785Z] assertLength@http://localhost:9876/base/node_modules/chai/chai.js?db92883971379fbea71a12c25b271c26a3afc3f6:2487:10
[task 2019-08-31T02:18:12.785Z] chainableMethodWrapper@http://localhost:9876/base/node_modules/chai/chai.js?db92883971379fbea71a12c25b271c26a3afc3f6:7664:49
[task 2019-08-31T02:18:12.785Z] [6]</module.exports/assert.lengthOf@http://localhost:9876/base/node_modules/chai/chai.js?db92883971379fbea71a12c25b271c26a3afc3f6:5850:60
[task 2019-08-31T02:18:12.785Z] @http://localhost:9876/base/test/unit/unit-entry.js?da638f48041069de6585dd0612caa8b3e937d55c:106428:12
[task 2019-08-31T02:18:12.785Z]
[task 2019-08-31T02:18:12.785Z] TEST-UNEXPECTED-FAIL karma | activity-stream:CFRMessageProvider should always have xpinstallEnabled as targeting if it is an addon: expected 'usesFirefoxSync == false' to include '(xpinstallEnabled == true)'
[task 2019-08-31T02:18:12.785Z] AssertionError@http://localhost:9876/base/node_modules/chai/chai.js?db92883971379fbea71a12c25b271c26a3afc3f6:9449:13
[task 2019-08-31T02:18:12.785Z] [3]</module.exports/Assertion.prototype.assert@http://localhost:9876/base/node_modules/chai/chai.js?db92883971379fbea71a12c25b271c26a3afc3f6:239:13
[task 2019-08-31T02:18:12.785Z] include@http://localhost:9876/base/node_modules/chai/chai.js?db92883971379fbea71a12c25b271c26a3afc3f6:940:10
[task 2019-08-31T02:18:12.785Z] chainableMethodWrapper@http://localhost:9876/base/node_modules/chai/chai.js?db92883971379fbea71a12c25b271c26a3afc3f6:7664:49
[task 2019-08-31T02:18:12.785Z] [6]</module.exports/assert.include@http://localhost:9876/base/node_modules/chai/chai.js?db92883971379fbea71a12c25b271c26a3afc3f6:5106:51
[task 2019-08-31T02:18:12.785Z] @http://localhost:9876/base/test/unit/unit-entry.js?da638f48041069de6585dd0612caa8b3e937d55c:106448:16
[task 2019-08-31T02:18:12.785Z]
|
|
1,578,031 | 14,334,259 |
```
from /root/firefox-gcc-last/obj-x86_64-pc-linux-gnu/js/src/jit/Unified_cpp_js_src_jit10.cpp:2:
/root/firefox-gcc-last/js/src/wasm/WasmTypes.h: In function 'constexpr bool js::wasm::GetOffsetGuardLimit(bool)':
/root/firefox-gcc-last/js/src/wasm/WasmTypes.h:2335:21: error: ?: using integer constants in boolean context, the expression will always evaluate to 'true' [-Werror=int-in-bool-context]
return hugeMemory ? HugeOffsetGuardLimit : OffsetGuardLimit;
~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
```
static constexpr bool GetOffsetGuardLimit(bool hugeMemory) {
#ifdef WASM_SUPPORTS_HUGE_MEMORY
return hugeMemory ? HugeOffsetGuardLimit : OffsetGuardLimit;
#else
return OffsetGuardLimit;
#endif
}
```
|
|
1,578,052 | 14,334,361 |
Created attachment 9089689
The focus indictor is barely visible around the toggle
In the protections panel accessed from the shield icon in the address bar, the focus indicator/outline for the protections toggle is nearly invisible because it overlaps the toggle. The outline should be outside of the toggle so it's visible.
|
|
1,578,075 | 14,334,468 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
1. Go to https://stronghold.co/careers/
2. Wait
macOS 10.15 “Catalina” Beta (19A546d)
Actual results:
Crashes after zero–three seconds. Happens every time.
https://crash-stats.mozilla.org/report/index/01b19d74-15e2-4fa3-8ffd-e91690190901
Expected results:
The page should load.
|
|
1,578,093 | 14,334,572 |
Created attachment 9089740
Actual_vs_expected.png
Nightly 70.0a1 (2019-09-01) (64-Bit
STR:
1.) Visit a page
2.) Take a look at the spacing between Lock icon and Address Text
Actual: It seems that the Address Text is 4px to far right.
Expected: The Address Text should be moved by 4px to the left, so that the Lock icon looks nicely centered between divider and text.
A screenshot is attached.
Thanks.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.