Bug ID
int64 961
1.91M
| Comment ID
int64 3.98k
17.1M
| Author
stringlengths 8
48
| Comment Text
stringlengths 1
64.3k
⌀ |
|---|---|---|---|
1,600,565 | 14,521,302 |
As detected by Cerberus, there was an increase in FORGET_SKIPPABLE_FREQUENCY after bug 1599445 landed:
https://telemetry.mozilla.org/new-pipeline/evo.html#!aggregates=Median!Mean!5th%2520percentile!25th%2520percentile!75th%2520percentile!95th%2520percentile&cumulative=0&end_date=null&include_spill=0&keys=&max_channel_version=nightly%252F72&measure=FORGET_SKIPPABLE_FREQUENCY&min_channel_version=nightly%252F72&processType=*&product=Firefox&sanitize=1&sort_keys=submissions&start_date=null&trim=1&use_submission_date=0
|
|
1,600,811 | 14,522,941 |
nsNetworkLinkService.mm tries to read network.netlink.route.check.IPv4 preference which was removed in bug 1593693
|
|
1,600,905 | 14,523,779 |
Created attachment 9113174
console-export-2019-12-3_13-51-28.txt
*Affected versions*
* 71.0-build5 (20191202093317)
* 72.0b1 (20191202142314)
* 73.0a1 (20191202091209)
*Affected platforms*
* Windows 10x64
*Steps to reproduce*
1. Download Firefox [73.0a1](https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/).exe and install it.
2. Open the installed Firefox.
3. Reinstall the build from Step1 on the same location while Firefox is opened.
4. After the installation is completed launch Firefox.
5. Open a new tab and try to load a page.
*Expected result*
* New Firefox window works as expected (or maybe not installed?).
*Actual result*
* Firefox is directly opened and many-core functionalities don’t work (loading a new webpage in a new tab, closing Fx from the “X” button, closing tabs, right-clicking brings an unusual context menu)
*Regression Range*
* Reproducible on Firefox 69.0.3 (20191009172106). I will search for one ASAP.
*Notes*
* Attached a console log from the browser while affected by this.
* Attached a screen recording.
* This issue once occurred to me after updating to the latest Nightly but I don’t have STR for this. I tried reproducing this issue when updating this but with no luck. Also, maybe worth mentioning that I had “Restore last session checked” and multiple windows opened across two monitors. Maybe some processes didn't correctly close while Firefox update was applied and led to this behavior.
|
|
1,600,953 | 14,524,061 |
Created attachment 9113226
TipsAreDismissed.mp4
[Affected versions]:
- Latest Firefox Nightly 73.0a1 (Build ID: 20191203094830)
[Affected Platforms]:
- Mac 10.14
- Windows 10 x64
- Ubuntu 16.04 x64
[Prerequisites]:
- Have the latest Nightly installed.
- Have the “devtools.chrome.enabled” pref set to “true”.
- Run the “(async function() { let { ProfileAge } = ChromeUtils.import("resource://gre/modules/ProfileAge.jsm"); let age = await ProfileAge(); age._times = { firstUse: 1368255600000, created: 1368255600000 }; await age.writeTimes(); })();” code on the browser console.
- Have access to the stage delivery console.
- Have an active branched add-on [recipe](https://delivery-console.stage.mozaws.net/recipe/881/).
- Have the “security.content.signature.root_hash” pref set to "DB:74:CE:58:E4:F9:D0:9E:E0:42:36:BE:6C:C5:C4:F6:6A:E7:74:7D:C0:21:42:7A:03:BC:2F:57:0C:8B:9B:90".
- Have the "app.normandy.api_url" pref set to "https://stage.normandy.nonprod.cloudops.mozgcp.net/api/v1".
- Have the "app.normandy.dev_mode" pref set to “true”.
- Have the "app.normandy.logging.level" pref set to “0”.
- Have the "services.settings.server" pref set to "https://settings.stage.mozaws.net/v1".
- Have the "xpinstall.signatures.dev-root" pref set to “true”.
- Create a new pref named “carmentips” and set it as “true”.
[Steps to reproduce]:
1. Open the Firefox browser with the profile from prerequisites.
2. Open a new tab.
3. Click anywhere on the tip except the “OK, Got It” button.
4. Observe what happens next.
[Expected result]:
- Nothing happens. The tip is not dismissed.
[Actual result]:
- The tip is dismissed.
[ Notes]:
- This issue is reproducible with both “Onboarding” and “Redirect” tips .
- Attached a screen recording with the issue.
|
|
1,601,014 | 14,524,822 |
This is a regression caused by me in bug 1553510 - I accidentally got rid of an early return if no migration was necessary.
|
|
1,601,024 | 14,524,868 |
Report from m-c 20191202-9420b5dc27e0
We've hit this a few times but the reported test cases trigger bug 1588357 so not sure if this is a dupe. If so that makes bug 1588357 a s-s bug.
```
==18881==ERROR: AddressSanitizer: heap-use-after-free on address 0x6110005bb548 at pc 0x7ff8f3f95a74 bp 0x7fff9bf357b0 sp 0x7fff9bf357a8
READ of size 8 at 0x6110005bb548 thread T0 (Web Content)
#0 0x7ff8f3f95a73 in get /src/obj-firefox/dist/include/nsCOMPtr.h:823:48
#1 0x7ff8f3f95a73 in operator nsISerialEventTarget * /src/obj-firefox/dist/include/nsCOMPtr.h:831:33
#2 0x7ff8f3f95a73 in GetOwningEventTarget /src/dom/workers/remoteworkers/RemoteWorkerChild.cpp:274:10
#3 0x7ff8f3f95a73 in mozilla::dom::RemoteWorkerChild::ErrorPropagationOnMainThread(mozilla::dom::WorkerErrorReport const*, bool) /src/dom/workers/remoteworkers/RemoteWorkerChild.cpp:675:3
#4 0x7ff8f3f3b395 in mozilla::dom::(anonymous namespace)::ReportErrorRunnable::WorkerRun(JSContext*, mozilla::dom::WorkerPrivate*) /src/dom/workers/WorkerError.cpp:91:20
#5 0x7ff8f3f6fa1e in mozilla::dom::WorkerRunnable::Run() /src/dom/workers/WorkerRunnable.cpp:369:12
#6 0x7ff8eb908748 in mozilla::ThrottledEventQueue::Inner::ExecuteRunnable() /src/xpcom/threads/ThrottledEventQueue.cpp:252:22
#7 0x7ff8eb8ff43f in mozilla::ThrottledEventQueue::Inner::Executor::Run() /src/xpcom/threads/ThrottledEventQueue.cpp:80:15
#8 0x7ff8eb8e74ea in nsThread::ProcessNextEvent(bool, bool*) /src/xpcom/threads/nsThread.cpp:1250:14
#9 0x7ff8eb8ee991 in NS_ProcessNextEvent(nsIThread*, bool) /src/xpcom/threads/nsThreadUtils.cpp:486:10
#10 0x7ff8ecb083ef in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /src/ipc/glue/MessagePump.cpp:88:21
#11 0x7ff8eca12622 in RunInternal /src/ipc/chromium/src/base/message_loop.cc:315:10
#12 0x7ff8eca12622 in RunHandler /src/ipc/chromium/src/base/message_loop.cc:308:3
#13 0x7ff8eca12622 in MessageLoop::Run() /src/ipc/chromium/src/base/message_loop.cc:290:3
#14 0x7ff8f46e8f58 in nsBaseAppShell::Run() /src/widget/nsBaseAppShell.cpp:137:27
#15 0x7ff8f8753216 in XRE_RunAppShell() /src/toolkit/xre/nsEmbedFunctions.cpp:934:20
#16 0x7ff8eca12622 in RunInternal /src/ipc/chromium/src/base/message_loop.cc:315:10
#17 0x7ff8eca12622 in RunHandler /src/ipc/chromium/src/base/message_loop.cc:308:3
#18 0x7ff8eca12622 in MessageLoop::Run() /src/ipc/chromium/src/base/message_loop.cc:290:3
#19 0x7ff8f8752a64 in XRE_InitChildProcess(int, char**, XREChildData const*) /src/toolkit/xre/nsEmbedFunctions.cpp:769:34
#20 0x562d82361c5c in content_process_main /src/browser/app/../../ipc/contentproc/plugin-container.cpp:56:28
#21 0x562d82361c5c in main /src/browser/app/nsBrowserApp.cpp:272:18
#22 0x7ff90ea49b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310
#23 0x562d822b706c in _start (/home/worker/builds/m-c-20191202220401-fuzzing-asan-opt/firefox+0x5506c)
0x6110005bb548 is located 200 bytes inside of 240-byte region [0x6110005bb480,0x6110005bb570)
freed by thread T14 (Worker Launcher) here:
#0 0x562d8232ed3d in free /builds/worker/fetches/llvm-project/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:123:3
#1 0x7ff8eca6ae1f in Release /src/obj-firefox/dist/include/mozilla/RefCounted.h:201:7
#2 0x7ff8eca6ae1f in Release /src/obj-firefox/dist/include/mozilla/ThreadSafeWeakPtr.h:213:23
#3 0x7ff8eca6ae1f in Release /src/obj-firefox/dist/include/mozilla/RefPtr.h:48:40
#4 0x7ff8eca6ae1f in Release /src/obj-firefox/dist/include/mozilla/RefPtr.h:373:36
#5 0x7ff8eca6ae1f in ~RefPtr /src/obj-firefox/dist/include/mozilla/RefPtr.h:79:7
#6 0x7ff8eca6ae1f in mozilla::ipc::BackgroundChildImpl::DeallocPRemoteWorkerChild(mozilla::dom::PRemoteWorkerChild*) /src/ipc/glue/BackgroundChildImpl.cpp:344:1
#7 0x7ff8ecb0f083 in mozilla::ipc::ActorLifecycleProxy::~ActorLifecycleProxy() /src/ipc/glue/ProtocolUtils.cpp:253:11
#8 0x7ff8ed28f167 in Release /src/obj-firefox/dist/include/mozilla/ipc/ProtocolUtils.h:914:3
#9 0x7ff8ed28f167 in Release /src/obj-firefox/dist/include/mozilla/RefPtr.h:48:40
#10 0x7ff8ed28f167 in Release /src/obj-firefox/dist/include/mozilla/RefPtr.h:373:36
#11 0x7ff8ed28f167 in ~RefPtr /src/obj-firefox/dist/include/mozilla/RefPtr.h:79:7
#12 0x7ff8ed28f167 in mozilla::ipc::PBackgroundChild::OnMessageReceived(IPC::Message const&) /src/obj-firefox/ipc/ipdl/PBackgroundChild.cpp:5877:5
#13 0x7ff8ecaff236 in mozilla::ipc::MessageChannel::DispatchAsyncMessage(mozilla::ipc::ActorLifecycleProxy*, IPC::Message const&) /src/ipc/glue/MessageChannel.cpp:2208:25
#14 0x7ff8ecafa251 in mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) /src/ipc/glue/MessageChannel.cpp:2130:9
#15 0x7ff8ecafc7c1 in mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::MessageChannel::MessageTask&) /src/ipc/glue/MessageChannel.cpp:1972:3
#16 0x7ff8ecafd687 in mozilla::ipc::MessageChannel::MessageTask::Run() /src/ipc/glue/MessageChannel.cpp:2003:13
#17 0x7ff8eb8e74ea in nsThread::ProcessNextEvent(bool, bool*) /src/xpcom/threads/nsThread.cpp:1250:14
#18 0x7ff8eb8ee991 in NS_ProcessNextEvent(nsIThread*, bool) /src/xpcom/threads/nsThreadUtils.cpp:486:10
#19 0x7ff8ecb09d94 in mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) /src/ipc/glue/MessagePump.cpp:333:5
#20 0x7ff8eca12622 in RunInternal /src/ipc/chromium/src/base/message_loop.cc:315:10
#21 0x7ff8eca12622 in RunHandler /src/ipc/chromium/src/base/message_loop.cc:308:3
#22 0x7ff8eca12622 in MessageLoop::Run() /src/ipc/chromium/src/base/message_loop.cc:290:3
#23 0x7ff8eb8e0f71 in nsThread::ThreadFunc(void*) /src/xpcom/threads/nsThread.cpp:458:11
#24 0x7ff90ff23ec5 in _pt_root /src/nsprpub/pr/src/pthreads/ptthread.c:201:5
#25 0x7ff90fb6b6da in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76da)
previously allocated by thread T14 (Worker Launcher) here:
#0 0x562d8232efbd in malloc /builds/worker/fetches/llvm-project/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:145:3
#1 0x562d823647fd in moz_xmalloc /src/memory/mozalloc/mozalloc.cpp:52:15
#2 0x7ff8eca6abfb in operator new /src/obj-firefox/dist/include/mozilla/cxxalloc.h:33:10
#3 0x7ff8eca6abfb in mozilla::ipc::BackgroundChildImpl::AllocPRemoteWorkerChild(mozilla::dom::RemoteWorkerData const&) /src/ipc/glue/BackgroundChildImpl.cpp:328:42
#4 0x7ff8ed29184c in mozilla::ipc::PBackgroundChild::OnMessageReceived(IPC::Message const&) /src/obj-firefox/ipc/ipdl/PBackgroundChild.cpp:6245:49
#5 0x7ff8ecaff236 in mozilla::ipc::MessageChannel::DispatchAsyncMessage(mozilla::ipc::ActorLifecycleProxy*, IPC::Message const&) /src/ipc/glue/MessageChannel.cpp:2208:25
#6 0x7ff8ecafa251 in mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) /src/ipc/glue/MessageChannel.cpp:2130:9
#7 0x7ff8ecafc7c1 in mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::MessageChannel::MessageTask&) /src/ipc/glue/MessageChannel.cpp:1972:3
#8 0x7ff8ecafd687 in mozilla::ipc::MessageChannel::MessageTask::Run() /src/ipc/glue/MessageChannel.cpp:2003:13
#9 0x7ff8eb8e74ea in nsThread::ProcessNextEvent(bool, bool*) /src/xpcom/threads/nsThread.cpp:1250:14
#10 0x7ff8eb8ee991 in NS_ProcessNextEvent(nsIThread*, bool) /src/xpcom/threads/nsThreadUtils.cpp:486:10
#11 0x7ff8ecb09d94 in mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) /src/ipc/glue/MessagePump.cpp:333:5
#12 0x7ff8eca12622 in RunInternal /src/ipc/chromium/src/base/message_loop.cc:315:10
#13 0x7ff8eca12622 in RunHandler /src/ipc/chromium/src/base/message_loop.cc:308:3
#14 0x7ff8eca12622 in MessageLoop::Run() /src/ipc/chromium/src/base/message_loop.cc:290:3
#15 0x7ff8eb8e0f71 in nsThread::ThreadFunc(void*) /src/xpcom/threads/nsThread.cpp:458:11
#16 0x7ff90ff23ec5 in _pt_root /src/nsprpub/pr/src/pthreads/ptthread.c:201:5
#17 0x7ff90fb6b6da in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76da)
Thread T14 (Worker Launcher) created by T0 (Web Content) here:
#0 0x562d8231974a in pthread_create /builds/worker/fetches/llvm-project/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:209:3
#1 0x7ff90ff15b99 in _PR_CreateThread /src/nsprpub/pr/src/pthreads/ptthread.c:458:14
#2 0x7ff90feff1ee in PR_CreateThread /src/nsprpub/pr/src/pthreads/ptthread.c:533:12
#3 0x7ff8eb8e33d6 in nsThread::Init(nsTSubstring<char> const&) /src/xpcom/threads/nsThread.cpp:673:8
#4 0x7ff8eb8edb01 in nsThreadManager::NewNamedThread(nsTSubstring<char> const&, unsigned int, nsIThread**) /src/xpcom/threads/nsThreadManager.cpp:550:12
#5 0x7ff8eb8f1af3 in NS_NewNamedThread(nsTSubstring<char> const&, nsIThread**, nsIRunnable*, unsigned int) /src/xpcom/threads/nsThreadUtils.cpp:139:57
#6 0x7ff8f3fa46fd in NS_NewNamedThread<16> /src/obj-firefox/dist/include/nsThreadUtils.h:71:10
#7 0x7ff8f3fa46fd in mozilla::dom::RemoteWorkerService::InitializeOnMainThread() /src/dom/workers/remoteworkers/RemoteWorkerService.cpp:82:17
#8 0x7ff8f3fa4128 in mozilla::dom::RemoteWorkerService::Initialize() /src/dom/workers/remoteworkers/RemoteWorkerService.cpp:49:28
#9 0x7ff8f3d1f192 in mozilla::dom::ContentChild::InitXPCOM(mozilla::dom::XPCOMInitData const&, mozilla::dom::ipc::StructuredCloneData const&) /src/dom/ipc/ContentChild.cpp:1353:3
#10 0x7ff8f3d1edd8 in mozilla::dom::ContentChild::RecvSetXPCOMProcessAttributes(mozilla::dom::XPCOMInitData const&, mozilla::dom::ipc::StructuredCloneData const&, nsTArray<LookAndFeelInt>&&, nsTArray<mozilla::dom::SystemFontListEntry>&&, mozilla::Maybe<base::FileDescriptor> const&, unsigned long const&) /src/dom/ipc/ContentChild.cpp:628:3
#11 0x7ff8eceb129f in mozilla::dom::PContentChild::OnMessageReceived(IPC::Message const&) /src/obj-firefox/ipc/ipdl/PContentChild.cpp:10564:56
#12 0x7ff8ecaff236 in mozilla::ipc::MessageChannel::DispatchAsyncMessage(mozilla::ipc::ActorLifecycleProxy*, IPC::Message const&) /src/ipc/glue/MessageChannel.cpp:2208:25
#13 0x7ff8ecafa251 in mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) /src/ipc/glue/MessageChannel.cpp:2130:9
#14 0x7ff8ecafc7c1 in mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::MessageChannel::MessageTask&) /src/ipc/glue/MessageChannel.cpp:1972:3
#15 0x7ff8ecafd687 in mozilla::ipc::MessageChannel::MessageTask::Run() /src/ipc/glue/MessageChannel.cpp:2003:13
#16 0x7ff8eb8e74ea in nsThread::ProcessNextEvent(bool, bool*) /src/xpcom/threads/nsThread.cpp:1250:14
#17 0x7ff8eb8ee991 in NS_ProcessNextEvent(nsIThread*, bool) /src/xpcom/threads/nsThreadUtils.cpp:486:10
#18 0x7ff8ecb083ef in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) /src/ipc/glue/MessagePump.cpp:88:21
#19 0x7ff8eca12622 in RunInternal /src/ipc/chromium/src/base/message_loop.cc:315:10
#20 0x7ff8eca12622 in RunHandler /src/ipc/chromium/src/base/message_loop.cc:308:3
#21 0x7ff8eca12622 in MessageLoop::Run() /src/ipc/chromium/src/base/message_loop.cc:290:3
#22 0x7ff8f46e8f58 in nsBaseAppShell::Run() /src/widget/nsBaseAppShell.cpp:137:27
#23 0x7ff8f8753216 in XRE_RunAppShell() /src/toolkit/xre/nsEmbedFunctions.cpp:934:20
#24 0x7ff8eca12622 in RunInternal /src/ipc/chromium/src/base/message_loop.cc:315:10
#25 0x7ff8eca12622 in RunHandler /src/ipc/chromium/src/base/message_loop.cc:308:3
#26 0x7ff8eca12622 in MessageLoop::Run() /src/ipc/chromium/src/base/message_loop.cc:290:3
#27 0x7ff8f8752a64 in XRE_InitChildProcess(int, char**, XREChildData const*) /src/toolkit/xre/nsEmbedFunctions.cpp:769:34
#28 0x562d82361c5c in content_process_main /src/browser/app/../../ipc/contentproc/plugin-container.cpp:56:28
#29 0x562d82361c5c in main /src/browser/app/nsBrowserApp.cpp:272:18
#30 0x7ff90ea49b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310
```
|
|
1,601,091 | 14,525,349 |
:jrmuizel writes in on Slack to let us know that `gfx.status.compositor` is `NULL` far too often. The metric, a string passed up via Geckoview Streaming Telemetry, should always be non-null in any application session that has ever loaded a geckoview.
Here's [the Glean SDK metric](https://searchfox.org/mozilla-central/rev/8bc24752246aeac8a9aed566cf1caccf88d97d11/toolkit/components/telemetry/geckoview/streaming/metrics.yaml#574) (showing it has an application lifetime). Here's [the Telemetry Scalar]https://searchfox.org/mozilla-central/rev/8bc24752246aeac8a9aed566cf1caccf88d97d11/toolkit/components/telemetry/Scalars.yaml#3046() and [the collection code](https://searchfox.org/mozilla-central/rev/8bc24752246aeac8a9aed566cf1caccf88d97d11/gfx/thebes/gfxPlatform.cpp#3767) (showing that it only has non-null values when set).
We haven't categorically ruled out that the collection code runs as frequently as we think it does, but given how bulletproof this code is on Firefox Desktop (`gfx.compositor` is pretty darn solid) I'm inclined to believe that the error's not there.
Remembering some talks in Whistler about how geckoviews sometimes aren't even launched if the user doesn't load web content, I looked at how many pings do and do not report a compositor based on how many searches they recorded: https://sql.telemetry.mozilla.org/queries/66656/source#168991
Looks like that theory's a bust too.
|
|
1,601,210 | 14,526,143 |
Created attachment 9113420
RedirectTipWronglyAppears.mp4
[Affected versions]:
- Latest Firefox Nightly 73.0a1 (Build ID: 20191203215345)
[Affected Platforms]:
- Mac 10.14
- Windows 10 x64
- Ubuntu 16.04 x64
[Prerequisites]:
- Have the latest Nightly installed.
- Have the “devtools.chrome.enabled” pref set to “true”.
- Run the “(async function() { let { ProfileAge } = ChromeUtils.import("resource://gre/modules/ProfileAge.jsm"); let age = await ProfileAge(); age._times = { firstUse: 1368255600000, created: 1368255600000 }; await age.writeTimes(); })();” code on the browser console.
- Have access to the stage delivery console.
- Have an active branched add-on [recipe](https://delivery-console.stage.mozaws.net/recipe/881/).
- Have the “security.content.signature.root_hash” pref set to "DB:74:CE:58:E4:F9:D0:9E:E0:42:36:BE:6C:C5:C4:F6:6A:E7:74:7D:C0:21:42:7A:03:BC:2F:57:0C:8B:9B:90".
- Have the "app.normandy.api_url" pref set to "https://stage.normandy.nonprod.cloudops.mozgcp.net/api/v1".
- Have the "app.normandy.dev_mode" pref set to “true”.
- Have the "app.normandy.logging.level" pref set to “0”.
- Have the "services.settings.server" pref set to "https://settings.stage.mozaws.net/v1".
- Have the "xpinstall.signatures.dev-root" pref set to “true”.
- Create a new pref named “carmentips” and set it as “true”.
- Have the “DuckDuckGo” engine selected as default search engine.
[Steps to reproduce]:
1. Open the Firefox browser with the profile from prerequisites.
2. Type any string inside the Address Bar and press the “Enter” key.
3. Observe the area under the Address Bar.
[Expected result]:
- The tip is not displayed.
[Actual result]:
- The “Redirect” tip is displayed under the Address Bar.
[ Notes]:
- This issue is not reproducible when having Google or Bing search engines set as default.
- Attached a screen recording with the issue.
|
|
1,601,227 | 14,526,238 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
I have a self signed personal certificate to access my tomcat java apps
Since 71 release, it doesn't work anymore
try to add it again, not work
Actual results:
SSL_ERROR_BAD_CERT_ALERT
when trying to view my personnal certificate, got a page corrupted certificate
no problem with firefox 70.0
Expected results:
See personal certificate
|
|
1,601,302 | 14,526,851 |
Created attachment 9113487
rec of the issue.gif
**[Affected versions]:**
- Firefox Release 71.0 - Build ID: 20191202093317
- Firefox Beta 72.0b2 - Build ID: 20191203141951
**[Affected Platforms]:**
- All Windows
- All Mac
- All Linux
**[Prerequisites]:**
- Have the latest Firefox Release (71.0) installed.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Click the "Firefox Menu" button from the top-right part of the window and select the "What's New" option.
3. Click the "Firefox now fights harder for your privacy" message and observe the behavior.
**[Expected result]:**
- The "[See what’s new in Firefox!](https://www.mozilla.org/en-US/firefox/71.0/releasenotes/)" page is opened.
**[Actual result]:**
- The "[Firefox Beta Release Notes](https://www.mozilla.org/en-US/firefox/71.0beta/releasenotes/?utm_source=whatsnew-panel&utm_medium=firefox-browser&utm_campaign=skyline-whatsnew-panel)" page is opened instead.
**[Notes]:**
- This issue is also reproducible on the latest Firefox Beta, with the mention that after following the steps from above the "[Firefox Nightly Release Notes](https://www.mozilla.org/en-US/firefox/72.0a1/releasenotes/?utm_source=whatsnew-panel&utm_medium=firefox-browser&utm_campaign=skyline-whatsnew-panel)" page is opened.
- Attached a screen recording of the issue.
|
|
1,601,450 | 14,527,799 |
This is a regression in Firefox Nightly in recent builds as early as 4:46 PST 20191204. Iris Nighty build validation revealed this first in https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&tier=1%2C2%2C3&revision=13fb375eaf14bd9fae5c607aa60015d2b3bd0f2d&searchStr=iris%2Cnightly-linux64-shippable%2Fopt&selectedJob=279610716 Subsequent test runs have failed.
Steps to reproduce:
1) Open about:config
2) Select the location bar with keyboard shortcut (cmd or ctrl + l)
3) type a few letters
Tested results:
about:config is left in the location bar with whatever you typed following it
Expected results:
typing should have overwritten the about:config text
Try the same in location bar with a url present and you get correct results. I expect the location bar shouldn't act any differently if we're in aboutconfig.
|
|
1,601,670 | 14,529,455 |
Created attachment 9113806
unknown_telemetry.png
[Affected Platforms]:
- All Windows
- All Mac
- All Linux
[Affected Versions]:
- Firefox Nightly 73.0a1, Build ID 20191205094649
- Firefox Beta 72.0b2, Build ID 20191203141951
[Prerequisites]:
- The "browser.ping-centre.log" pref is set to "true".
- The "browser.newtabpage.activity-stream.asrouter.devtoolsEnabled" pref is set to "true".
- The browser console is opened.
[Steps to reproduce]:
1. Open the browser with the profile from prerequisites and navigate to the "about:home#devtools" page.
2. Click the "Show" button from the "SIMPLE_TEST_1" message.
3. Observe the console output.
[Expected result]:
- An IMPRESSION telemetry ping is displayed in the browser console.
[Actual result]:
- The "Unknown ping type for ASRouter telemetry" error is displayed.
[Regression Range]:
- I've ran a regression check using mozregression and found the following pushlog that leads to a metabug, it is possible that the issue was introduced by the telemetry migration tracked in bug 1585147.
- Last good revision: 85aa4fa5722bdcb6e0d13f29951772d3c7806e42
- First bad revision: 40a815ecfbe3b248bedafdba52851b774d31efc8
- Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=85aa4fa5722bdcb6e0d13f29951772d3c7806e42&tochange=40a815ecfbe3b248bedafdba52851b774d31efc8
[Notes]:
- Only testing snippets are affected, the issue is not reproducible with live snippets.
- This issue is also reproducible for the CLICK and BLOCKED events.
- The "Unknown ping type for ASRouter telemetry" error is displayed when triggering and dismissing the snippet.
- I have attached a screenshot of the console output:
|
|
1,601,671 | 14,529,460 |
Created attachment 9113808
bug-proxy-websocket.txt
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36
Steps to reproduce:
On Windows 10.
- Launch Fiddler (Proxy)
- Be sure Proxy settings in Firefox are "Use System Proxy Settings"
- Go here https://websocket.org/echo.html
- Click Connect
Actual results:
Connection is OK but it doesn't go through proxy, it's a DIRECT connection (so it's a bug).
Expected results:
Connection should go into the proxy.
I tried with a PAC file and Manual proxy, there's no bug. Only with the "Use System proxy Settings" is buggy
|
|
1,601,708 | 14,529,710 |
Created attachment 9113850
example.png
Closing a dialog in `about:preferences` causes the content window to be outlined with the selection 'dotted line'.
STR:
- open `about:preferences`
- scroll to bottom and click `Settings...` button under `Network Settings`
- close the `Settings` dialog window
Expected behavior:
Dialog window should close and the preferences page should display normally
Expected behavior:
Dialog window closes and the preferences page is outlined (see attachment)
This is reproducible on Windows Nightly (73) and Beta.
|
|
1,601,712 | 14,529,747 |
The attached testcase crashes on mozilla-central revision 20191205-3dc70a33491f.
For detailed crash information, see attachment.
To reproduce the issue, perform the following steps:
1. Download the attached testcase, save as "test.bin".
2a. Build with --enable-fuzzing (requires Clang and ASan, also build gtests using `./mach gtest dontruntests`).
2b. Alternatively you can download builds from TC using `python -mfuzzfetch -a --fuzzing --tests gtest` (see https://github.com/MozillaSecurity/fuzzfetch).
3. Run MOZ_RUN_GTEST=1 LIBFUZZER=1 FUZZER=NetworkHttp2ProxyHttp2 objdir/dist/bin/firefox test.bin
This is a recent regression, the test reproduces deterministically and it requires HTTP2 proxied via HTTP2.
|
|
1,601,905 | 14,531,225 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
I`m Trying to open pdf file with space (-es) in its` name from recieved email attachment with thunderbird 68.3.0.
Actual results:
If Thunderbird version equal to 68.3.0, any PDF viewer (Acrobat reader, Foxit Reader) displays the message "file "_filename_part_after_Space.pdf" could not be opened" and\or "file not found". If Thunderbird ver. 68.2.x or lower, it opens such files successfuly. If I forward this file without changes, TB 68.3 fails to open it with the same result. If I rename the file, and remove space from its name, it opens successfuly in any version, including 68.3. Other file types (txt, png) doesn`t affected. Temporary copies of files in system temp folder appears in both cases, so looks like TB 68.3 makes all things right, but transfer the URL of file with spaces to pdf application incorrectly.
Expected results:
File with any name should be opened successfuly
|
|
1,602,033 | 14,531,922 | null |
|
1,602,193 | 14,532,756 |
Created attachment 9114336
Thunderbird-folder-not-highlighted.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36
Steps to reproduce:
Click on any folder on either an IMAP or POP server.
Actual results:
Messages are displayed as expected, but there is no visual indication in the folder list down the left as to which folder's messages are being displayed.
Expected results:
Until -- I think -- the 72.0b1 release, the selected folder was visually distinguished in the folder list on the left, thus providing a reminder as to which folder's messages are being displayed.
|
|
1,602,288 | 14,533,268 |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36
Steps to reproduce:
Build with uclibc i586
Actual results:
/home/giuliobenetti/git/br-libnss/host/bin/i586-buildroot-linux-uclibc-gcc -o Linux2.6_x86_i586-buildroot-linux-uclibc-gcc.br_real_glibc_PTH_DBG.OBJ/h_page.o -c -std=c99 -g -fPIC -Di386 -pipe -ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -D__USE_POSIX -Wall -Wshadow -DNSS_NO_GCC48 -DXP_UNIX -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_REENTRANT -DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -DSTDC_HEADERS -DHAVE_STRERROR -DHAVE_SNPRINTF -DMEMMOVE -D__DBINTERFACE_PRIVATE -I/home/giuliobenetti/git/br-libnss/host/i586-buildroot-linux-uclibc/sysroot/usr/include/nspr -I/home/giuliobenetti/git/br-libnss/build/libnss-3.48/dist/include -I../../../../dist/public/dbm -I../../../../dist/private/dbm h_page.c
h_page.c: In function ‘open_temp’:
h_page.c:1155:11: warning: implicit declaration of function ‘sigfillset’ [-Wimplicit-function-declaration]
(void)sigfillset(&set);
^~~~~~~~~~
h_page.c:1156:11: warning: implicit declaration of function ‘sigprocmask’ [-Wimplicit-function-declaration]
(void)sigprocmask(SIG_BLOCK, &set, &oset);
^~~~~~~~~~~
h_page.c:1156:23: error: ‘SIG_BLOCK’ undeclared (first use in this function); did you mean ‘DB_LOCK’?
(void)sigprocmask(SIG_BLOCK, &set, &oset);
^~~~~~~~~
DB_LOCK
h_page.c:1156:23: note: each undeclared identifier is reported only once for each function it appears in
h_page.c:1197:23: error: ‘SIG_SETMASK’ undeclared (first use in this function); did you mean ‘HIGH_MASK’?
(void)sigprocmask(SIG_SETMASK, &oset, (sigset_t *)NULL);
^~~~~~~~~~~
HIGH_MASK
make[5]: *** [../../../coreconf/rules.mk:393: Linux2.6_x86_i586-buildroot-linux-uclibc-gcc.br_real_glibc_PTH_DBG.OBJ/h_page.o] Error 1
|
|
1,615,901 | 14,643,556 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
1. navigate to https://duckduckgo.com/lite/
2. add as a search engine
3. set as default search engine
4. select text, right-click, "Search DuckDuckGo Lite"
Actual results:
page displays "forbidden"
Expected results:
search results displayed
|
|
1,615,930 | 14,643,726 |
The [original report](https://webcompat.com/issues/47740) is about a [looping video on twitter](https://twitter.com/HunterZ0/status/1217307579052744705).
But we can show the issue with a link directly to the video
https://video.twimg.com/tweet_video/EOS-yMjUwAAAGB-.mp4
on macOS, with firefox nightly 75.0a1 (2020-02-16) (64-bit)
the video plays until the end.
on android with firefox preview nightly 75.0a1 20200212093201
it stops on 98 and doesn't play until the ends.
|
|
1,615,977 | 14,645,253 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
1) using Firefox 74 (Developer Edition)
2) install StrokeIt application (for gestures)
3) in the StrokeIt, create command of type "Keys - Hotkey" with Hotkey: "ALT + HOME". Don't forget to define a gesture that will execute this command. Also make sure the gesture will be executed in Firefox, for example by defining it in "Global Actions".
4) perform gesture in Firefox
Actual results:
Hotkey no longer works.
Expected results:
Hotkey should open your homepage in active tab, just like it works with keyboard.
This is a regression. It worked in 73 and all other versions for past 10 years.
The issue seems to affect all hotkeys with "Alt" key. All other hotkeys works as expected.
|
|
1,616,079 | 14,646,057 |
This bug is for crash report bp-6b42f74b-7ac0-4dee-995d-c2e540200217.
```
Top 10 frames of crashing thread:
0 ntdll.dll RtlAcquireSRWLockExclusive
1 mozglue.dll mozilla::detail::MutexImpl::lock mozglue/misc/Mutex_windows.cpp:22
2 xul.dll mozilla::dom::WorkerRunnable::DispatchInternal dom/workers/WorkerRunnable.cpp
3 xul.dll mozilla::dom::WorkerRunnable::Dispatch dom/workers/WorkerRunnable.cpp:89
4 xul.dll mozilla::detail::RunnableFunction<`lambda at z:/task_1581648291/build/src/dom/workers/remoteworkers/RemoteWorkerChild.cpp:475:19'>::Run xpcom/threads/nsThreadUtils.h:562
5 xul.dll mozilla::MozPromise<nsTArray<bool>, nsresult, 0>::ThenValue<`lambda at z:/task_1581648291/build/src/extensions/permissions/nsPermissionManager.cpp:3300:29', `lambda at z:/task_1581648291/build/src/extensions/permissions/nsPermissionManager.cpp:3301:11'>::DoResolveOrRejectInternal xpcom/threads/MozPromise.h:727
6 xul.dll mozilla::MozPromise<RefPtr<mozilla::AllocPolicy::Token>, bool, 1>::ThenValueBase::ResolveOrRejectRunnable::Run xpcom/threads/MozPromise.h:403
7 xul.dll mozilla::AutoTaskDispatcher::TaskGroupRunnable::Run xpcom/threads/TaskDispatcher.h:197
8 xul.dll mozilla::EventTargetWrapper::Runner::Run xpcom/threads/AbstractThread.cpp:113
9 xul.dll mozilla::SchedulerGroup::Runnable::Run xpcom/threads/SchedulerGroup.cpp:282
```
these cross-platform content crash signatures are showing up in increased volume since firefox 73. in firefox 73.0b9 the sw-e10s work got disabled and those crashes stopped, so i assume they are related to this new feature.
the crashing addresses of a number of reports indicate that this is a UAF issue.
|
|
1,616,509 | 14,649,331 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
1) Drag images and Drop them into an DIV-Element with "contenteditable"-attribute.
2) Change order of images in the DIV (D&D)
Actual results:
1) Only the first images appears. More Images will not be droped.
2) Ordering impossible. Dragged Image is always droped in first Position
Expected results:
Before v73 Firefox handled D&D correct as expected.
Tested on MacOS and Windows 8.5.
|
|
1,616,545 | 14,649,598 |
Created attachment 9127534
installation directory sideload.png
[Affected versions]:
- Firefox 74.0b5/20200218224219
- Firefox 75.0a1/20200218213359
[Affected platforms]:
- Windows 10 Pro 64-bit
- macOS Catalina 10.15
- Ubuntu 16.04 LTS
[Prerequisites]:
Windows:
- Copy the add-on in the browser’s installation directory, under “browser” → “extensions”.
- The “extensions” folder must be created if non existent.
macOS:
- Copy the add-on in the browser’s installation directory, under “Contents”→”Resources”→”browser”→”extensions”.
- The “extensions” folder must be created if non existent.
- To access the above path, go to the location of the Firefox executable, right click it and in the displayed menu, select “Show package Contents”.
Ubuntu:
- Copy the add-on in the browser’s installation directory, under “browser” → “extensions”.
- The “extensions” folder must be created if non existent.
[Steps to reproduce]:
1. Launch the browser
2. Access the Add-ons Manager page (type about:addons in the URL bar)
3. Go to the Extensions tab
4. Notice that the previously sideloaded add-on is installed and disabled
5. Click on the three-dot menu on the add-on’s card
6. Observe that the “Remove” option is not available, instead the “Can’t Be Removed Why?” option is present
[Description]:
Add-ons can still be sideloaded in the installation directory of the browser in FX74/FX75, with no option to remove them afterwards from Add-ons Manager.
[Expected results]:
Sideloading add-ons in the installation directory should no longer be possible as of FX74/FX75. Only profile sideloads should be allowed.
[Actual results]:
Add-ons can still be sideloaded in the installation directory in FX74/FX75 and cannot be removed via Add-ons Manager.
|
|
1,616,596 | 14,649,897 |
~This issue seems similar to Bug 1528562, but the fix for Bug 1528562 doesn't cover this additional scenario yet (and [the existing test case doesn't trigger it because it is using a POST but it is pointing it directly to the redirect_url](https://searchfox.org/mozilla-central/rev/fca0be7e2cf2f922c9b927423ce28e8a04b3fd90/toolkit/components/extensions/test/mochitest/oauth.html#12), instead of receiving a POST reply and then navigating to the redirect_uri because of the Location header).~
While trying to trigger the same issue I'm able to trigger while trying identity.launchWebAuthFlow on a local test oauth server (using https://github.com/14gasher/oauth-example to run a demo oauth server locally), I noticed that our test case should already be testing exactly the scenario described above (POST http request + redirect due to a Location header in the POST http reply) and I've not been yet able to figure out what is different between what happens in the test case (which pass successfully with and without my patch) and when I trigger the issue on the local oauth demo server (where identity.launchWebAuthFlow is getting stuck without my patch).
|
|
1,616,793 | 14,651,528 |
Our initial assumption in bug 1608359 was wrong, users hide Top Sites in the New Tab Page for the most various reasons among which starting with a clean slate or the remove-bloat placebo effect.
Those same users are now surprised that we removed the top sites list from the urlbar, and the connection between the two features is totally hidden and undiscoverable.
|
|
1,617,210 | 14,654,305 |
Created attachment 9128166
screencast
_Posting this on behalf of another user in a Firefox support forum._
When using the debugger in the browser toolbox you can't expand the "target" property in the right sidebar. I don't know if other properties are also affected and if it's also an issue with the web debugger but I got the attached screencast which shows the issue better than I am able to explain it (I've never used the debugger).
According to mozregression it's a regression from bug 1567849.
|
|
1,617,275 | 14,654,931 |
Enterprise policy allows the min version of TLS to be locked to 1.2 (or 1.1).
If it is locked to a particular version, we should not be showing the deprecation page to allow someone to go below that version.
|
|
1,617,345 | 14,655,421 |
[Tracking Requested - why for this release]:
If you hide top sites on new tab (set `browser.newtabpage.activity-stream.feeds.topsites` to false) and restart Firefox, focusing the urlbar doesn't show the top sites anymore. That's because `this.activityStream.store.getState().TopSites.rows` is an empty array here: https://searchfox.org/mozilla-central/rev/c1e3d3edd4a9b784971555dc74a5de23d768b2e1/browser/modules/AboutNewTab.jsm#115 Which makes total sense because top sites are disabled.
Ed, how might we fix this? We need to show the top sites in the urlbar view even when they're hidden on new tab. Setting the pref to true, calling `AboutNewTab.getTopSites`, and then resetting it to false actually works, but it's hacky, and it also causes the top sites to flicker on and off if the current tab is new tab.
Requesting tracking because we want to enable top sites in the urlbar on release on 74.
|
|
1,617,419 | 14,655,844 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
I surfed on youtube.com, nothing out of the ordinary, I reloaded the youtube homepage a few times, and on the second or third time, a feature recommendation message appeared in the address bar. This message persisted over mutiple page reloads.
I have not been able to reproduce this in another browser session, but AFAIK the recommendation message also only appears sporadically even if enabled.
I do have both "Recommend extensions as you browse" and "Recommend features as you browse" options unchecked aka. disabled in the "General" -> "Browsing" preferences page.
(Screenshot: https://i.imgur.com/EtKkzXo.png)
Browser version info:
Name Firefox
Version 73.0.1
Build-ID 20200217142647
User-Agent Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0
System info:
OS: Ubuntu 18.04.4 LTS, x64
Packages:
firefox (amd64); Version "73.0.1+build1-0ubuntu0.18.04.1"
firefox-locale-de (amd64); Version "73.0.1+build1-0ubuntu0.18.04.1"
Actual results:
Firefox showed me a feature recommendation notification in the address bar for the feature "pinned tabs".
(See screenshot here: https://i.imgur.com/D8nknDR.png)
Expected results:
Firefox should not have shown this notification and respected the preferences ("Recommend extensions as you browse" and "Recommend features as you browse").
|
|
1,617,512 | 14,656,319 |
Via webcompat: https://github.com/webcompat/web-bugs/issues/48441
Another likely regression from bug 1477756.
|
|
1,617,893 | 14,660,601 |
Firefox 75.0a1 20200225094028 on Windows 8.1
Slack shows its own notification bar that one shall grant it permissions to show notifications despite already having granted it. Clicking the link to grant it doesn't show the notification prompt/doorhanger.
Steps to reproduce:
1. Open https://mozilla.slack.com
2. Try to grant notification permissions from inside the website.
If the issues cannot be reproduced with step 1 and 2, first ran an older Firefox Nightly and grant the notification permission with that before updating to an affected build.
Bisection points to bug 1614831 as being the cause.
|
|
1,618,158 | 14,662,593 |
This bug is for crash report bp-423e6e05-704b-4863-97df-a179e0200225.
```
Top 10 frames of crashing thread:
0 libxul.so neqo_crypto::agentio::agent_close third_party/rust/neqo-crypto/src/agentio.rs:265
1 libssl3.so ssl_DefClose security/nss/lib/ssl/ssldef.c:219
2 libxul.so neqo_crypto::agent::SecretAgent::close third_party/rust/neqo-crypto/src/agent.rs:684
3 libxul.so core::ptr::real_drop_in_place src/libcore/ptr/mod.rs:182
4 libxul.so core::ptr::real_drop_in_place src/libcore/ptr/mod.rs:182
5 libxul.so core::ptr::real_drop_in_place src/libcore/ptr/mod.rs:182
6 libxul.so core::ptr::real_drop_in_place src/libcore/ptr/mod.rs:182
7 libxul.so neqo_http3conn_release netwerk/socket/neqo_glue/src/lib.rs:98
8 libxul.so mozilla::net::Http3Session::~Http3Session netwerk/protocol/http/Http3Session.cpp:182
9 libxul.so <name omitted> netwerk/protocol/http/Http3Session.cpp:49
```
Additional stacks from PHC:
```
Free stack:
#0 replace_free(void*) (firefox-bin)
#1 neqo_crypto::agentio::agent_close (libxul.so)
#2 ssl_DefClose (libssl3.so)
#3 neqo_crypto::agent::SecretAgent::close (libxul.so)
#4 core::ptr::real_drop_in_place (libxul.so)
#5 core::ptr::real_drop_in_place (libxul.so)
#6 core::ptr::real_drop_in_place (libxul.so)
#7 core::ptr::real_drop_in_place (libxul.so)
#8 neqo_http3conn_release (libxul.so)
#9 mozilla::net::Http3Session::~Http3Session() (libxul.so)
#10 <name omitted> (libxul.so)
#11 mozilla::net::nsHttpConnection::CloseTransaction(mozilla::net::nsAHttpTransaction*, nsresult, bool) (libxul.so)
#12 mozilla::net::nsHttpConnection::OnInputStreamReady(nsIAsyncInputStream*) (libxul.so)
#13 non-virtual thunk to mozilla::net::nsHttpConnection::OnInputStreamReady(nsIAsyncInputStream*) (libxul.so)
#14 mozilla::net::nsSocketInputStream::OnSocketReady(nsresult) (libxul.so)
#15 mozilla::net::nsSocketTransport::OnSocketDetached(PRFileDesc*) (libxul.so)
Alloc stack:
#0 MaybePageAlloc(mozilla::Maybe<unsigned long> const&, unsigned long, bool) (firefox-bin)
#1 calloc (firefox-bin)
#2 PR_CreateIOLayerStub (libnspr4.so)
#3 neqo_crypto::agent::SecretAgent::new (libxul.so)
#4 neqo_crypto::agent::Client::new (libxul.so)
#5 neqo_http3conn_new (libxul.so)
#6 mozilla::net::Http3Session::Init(nsTSubstring<char> const&, nsISocketTransport*, mozilla::net::nsHttpConnection*) (libxul.so)
#7 mozilla::net::nsHttpConnection::Init(mozilla::net::nsHttpConnectionInfo*, unsigned short, nsISocketTransport*, nsIAsyncInputStream*, nsIAsyncOutputStream*, bool, nsIInterfaceRequestor*, unsigned int) (libxul.so)
#8 mozilla::net::nsHttpConnectionMgr::nsHalfOpenSocket::SetupConn(nsIAsyncOutputStream*, bool) (libxul.so)
#9 mozilla::net::nsHttpConnectionMgr::nsHalfOpenSocket::OnOutputStreamReady(nsIAsyncOutputStream*) (libxul.so)
#10 mozilla::net::nsSocketOutputStream::OnSocketReady(nsresult) (libxul.so)
#11 mozilla::net::nsSocketTransport::OnSocketReady(PRFileDesc*, short) (libxul.so)
#12 mozilla::net::nsSocketTransportService::DoPollIteration(mozilla::BaseTimeDuration<mozilla::TimeDurationValueCalculator>*) (libxul.so)
#13 mozilla::net::nsSocketTransportService::Run() (libxul.so)
#14 non-virtual thunk to mozilla::net::nsSocketTransportService::Run() (libxul.so)
#15 nsThread::ProcessNextEvent(bool, bool*) (libxul.so)
```
I can try to get filename/line numbers for the PHC stacks if necessary.
|
|
1,618,173 | 14,662,695 |
In our current implementation, `NS_HTTP_REFRESH_DNS` [1] is set to the http channel that connects to the DoH server.
This causes the URL is resolved every time without using the DNS cache.
[1] https://searchfox.org/mozilla-central/rev/96f1457323cc598a36f5701f8e67aedaf97acfcf/netwerk/protocol/http/nsHttpChannel.cpp#6863
|
|
1,618,229 | 14,662,959 |
Created attachment 9129167
2020-02-26_17h11_30.gif
**[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID 20200226092757
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64
**[Prerequisites]:**
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.endpoints` set to `http,https`.
- Have the value of the pref `browser.newtabpage.activity-stream.discoverystream.config` set to `{"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}`.
- Have the value of the pref `browser.search.region` set to `US`.
- The “Dark” theme is enabled in the “Themes” section located in “about:addons”.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab.
3. Hover the “Dismiss” button.
4. Observe the “Dismiss” button’s icon color.
**[Expected result]:**
- The “Dismiss” icon color respects the “Dark” theme colors. (#F9F9FA, Grey 10)
**[Actual result]:**
- The “Dismiss” icon color is #2A2A2E.
**[Notes]:**
- Attached a screen recording of the issue.
|
|
1,618,371 | 14,663,951 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Open an email in Outlook OWA. Click on a PDF attachment to preview it in the browser. Press the Print button.
Actual results:
Nothing happens.
Expected results:
A print dialogue should open so the user can select a printer and print the PDF.
|
|
1,618,466 | 14,664,522 |
Created attachment 9129417
2020-02-27_09h38_45.gif
**[Affected versions]:**
- Firefox Nightly 75.0a1 Build ID 20200226213903
**[Affected Platforms]:**
- Windows 10 x64
- macOS 10.15
- Arch Linux 5.3.6 x64
**[Prerequisites]:**
- Have the value of the pref browser.newtabpage.activity-stream.discoverystream.endpoints set to http,https.
- Have the value of the pref browser.newtabpage.activity-stream.discoverystream.config set to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":true,"layout_endpoint":"https://e5e8374d-fffa-4a77-a604-31603852b6fd.mock.pstmn.io/1615081-layout"}.
- Have the value of the pref browser.search.region set to US.
- The “Dark” theme is enabled in the “Themes” section located in “about:addons”.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab.
3. Open the “DOM and Style Inspector” by using CTRL/CMD+SHIFT+C.
4. Hover the “Collection title” and click it.
5. Observe the color displayed in the “Rules View list” section under “This Element”.
**[Expected result]:**
- The “Collection title” color displayed in “Inspector” is #D7D7DB.
**[Actual result]:**
- The “Collection title” color displayed in “Inspector” is #F9F9FA.
**[Notes]:**
- Attached a screen recording of the issue.
|
|
1,618,500 | 14,664,773 |
### Actual behavior
Changing WebExtension manifest for existing users/installations from
```json
"permissions": [
"<all_urls>",
"proxy",
"webRequest",
"webRequestBlocking"
],
```
to
```json
"permissions": [
"proxy"
],
"optional_permissions": [
"<all_urls>",
"webRequest",
"webRequestBlocking"
],
```
looses previously granted permissions that are moved to optional permissions.
### Expected behavior
Permissions should be preserved once granted, even when moved to be optional
### Steps to reproduce
- Install `permissions-0.2-fx.xpi` from https://github.com/stoically/test-webext-permissions-bug/releases/tag/v0.2
- Inspect the background console for the installed "Permissions" extension to see result of `permissions.getAll`
- Use Add-ons Manager to "Check for updates"
- Wait until "Permissions" updates to v0.3 (https://github.com/stoically/test-webext-permissions-bug/releases/tag/v0.3)
- Inspect the background console for the updated "Permissions" extension to see result of `permissions.getAll`
Tested with Nightly 75.0a1 (2020-02-26) (64-bit)
|
|
1,618,515 | 14,664,925 |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Build ID: 20200226213903
**Affected versions**
* Nightly 75.0a1
**Affected platforms**
Ubuntu 16.04
Windows 10 x64
Mac OS X 10.15
**Steps to reproduce**
1. Launch Firefox with a new profile.
2. Go to about:config and set the preference "privacy.purge_trackers.enabled" to "true".
3. Gather some cookies by navigating to:
- https://www.bbc.com/
- https://www.wikipedia.org/
- the “Sample 20 Trackers” link (followed the instructions from https://senglehardt.com/test/prio/)
4. Go to about:preferences#privacy and observe the cookies from the "Manage Cookies and Site Data" dialog.
5. Go to about:config and set "idle.lastDailyNotification" to "0".
6. Allow your computer to go "idle" and after 2 minutes check the cookies list again (from the "Manage Cookies and Site Data" dialog).
7. Open the Browser Console type the following command and press Enter:
Services.obs.notifyObservers(null, "idle-daily");
8. Go to about:preferences#privacy and observe the cookies from the "Manage Cookies and Site Data" dialog.
9. Go to about:config and set the preference "privacy.userInteraction.expiration" to "1"
10. Wait for 2 minutes, open the Browser console and type and Enter the following snippet:
await Components.classes["@mozilla.org/purge-tracker-service;1"].getService(Components.interfaces.nsIPurgeTrackerService).purgeTrackingCookieJars()
11. Go to about:preferences#privacy and observe the cookies from the "Manage Cookies and Site Data" dialog.
**Expected result**
3. Multiple cookies are created and some of them are from domains on the Disconnect Tracking Protection list (statcounter.com, www.internetbrands.com/, nr-data.net, mc.yandex.ru, statcounter.com) others are not (admetrica.ru. mozilla.org, bbc.co.uk, wikimedia.org, bbc.com).
6, 8 - the third-party cookies from domains on the Disconnect Tracking Protection list should be cleared.
11 - all the cookies from the Disconnect Protection list should be cleared.
**Actual result**
None of the attempts from steps 5, 7 9 and 10 are ended with cookies clearance. All the cookies that were initially created and visible in step 4 are also present in the "Manage Cookies and Site Data" dialog in steps 6, 8 and 11.
In steps 7 and 10, the following messages can be seen in the browser console, but even so, none of the cookies is cleared and the "Manage Cookies and Site Data" list is the same.
*** PurgeTrackerService: Purging trackers enabled, beginning batch. 2
*** PurgeTrackerService: All cookie purging finished, resetting list until tomorrow.
|
|
1,607,937 | 14,581,230 |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
1. Configure the ExtensionSettings policiy by way of the policies.json file in the C:\Program Files\Mozilla Firefox\distribution\ folder so that all extensions are blocked by default.
"ExtensionSettings": {
"*": {
"blocked_install_message": "Custom Message Still Needs to Go Here...",
"install_sources": ["https://addons.mozilla.org/"],
"installation_mode": "blocked",
"allowed_types": ["extension", "theme", "dictionary", "langpack"]
}
2. Open about:addons and attempt to install an extension such Facebook Container.
Actual results:
Error message "Firefox prevented this site from asking you to install software on your computer." received. The installation was blocked, but our custom message was not displayed to alert the employee who blocked the installation and why.
Expected results:
Error message should have been the custom one that was specified in the policy. If attempting the installation from https://addons.mozilla.org/en-US/firefox/addon/facebook-container/?src=search, I receive the message I was expecting.
"Facebook Container (@contain-facebook) is blocked by your system administrator. Custom Message Still Needs to Go Here...".
|
|
1,607,985 | 14,581,540 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
about:config , permissions.default.image=2
Actual results:
Images are still loaded and displayed.
Expected results:
Images should not be loaded.
|
|
1,608,011 | 14,581,691 |
Because I neglected to extract it from the tokenserver response :(
[Tracking Requested - why for this release]:
We really want telemetry which indicates what if a user is on the "new" sync storage node.
|
|
1,608,068 | 14,582,134 |
The attached crash information was detected while running CI tests with ThreadSanitizer on mozilla-central revision 12fb5e522dd3.
Looks like another GC race.
### General information about TSan reports
#### Why fix races?
Data races are undefined behavior and can cause crashes as well as correctness issues. Compiler optimizations can cause racy code to have unpredictable and hard-to-reproduce behavior.
#### Rating
If you think this race can cause crashes or correctness issues, it would be great to rate the bug appropriately as P1/P2 and/or indicating this in the bug. This makes it a lot easier for us to assess the actual impact that these reports make and if they are helpful to you.
#### False Positives / Benign Races
Typically, races reported by TSan are not false positives [1], but it is possible that the race is benign. Even in this case it would be nice to come up with a fix if it is easily doable and does not regress performance. Every race that we cannot fix will have to remain on the suppression list and slows down the overall TSan performance. Also note that seemingly benign races can possibly be harmful (also depending on the compiler, optimizations and the architecture) [2][3].
[1] One major exception is the involvement of uninstrumented code from third-party libraries.
[2] http://software.intel.com/en-us/blogs/2013/01/06/benign-data-races-what-could-possibly-go-wrong
[3] How to miscompile programs with "benign" data races: https://www.usenix.org/legacy/events/hotpar11/tech/final_files/Boehm.pdf
#### Suppressing unfixable races
If the bug cannot be fixed, then a runtime suppression needs to be added in `mozglue/build/TsanOptions.cpp`. The suppressions match on the full stack, so it should be picked such that it is unique to this particular race. The bug number of this bug should also be included so we have some documentation on why this suppression was added.
|
|
1,608,159 | 14,582,744 |
Created attachment 9119783
Screenshot
`image` needs to be inline-level too.
|
|
1,608,245 | 14,583,369 |
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
Per Bug 1607955, the KBKDF code introduced in Bug 1599603 confused Coverity with a elided NULL check on `sftk_SlotFromSessionHandle(...)`. While Coverity is incorrect (and the behavior is fine as-is), it isn't consistent with the KBKDF code's handling of `sftk_SessionFromHandle(...)` (which _is_ NULL checked).
In both cases, move to a `PR_ASSERT(...)` and mention why the value can't reasonably be NULL in the code. This'll aid debugging (in the rare case this code is called during shutdown and sessions are actively being removed), but not incur a performance penalty on non-DEBUG builds.
Actual results:
Coverity was confused.
Expected results:
The code should be written in a way that Coverity isn't confused.
(If you'd like to close this bug in favor of attaching the patch to 1607955 and re-opening it, feel free).
|
|
1,608,250 | 14,583,402 |
User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
When testing Bug 1608245, I realized that I had inadvertently broken `fipstest.c`'s handling of `KI` and `KI_len`. This lead to it passing bogus keys (with unusually large lengths exceeding the bounds of `sizeof KI`) to `kbkdf_Dispatch(...)`. Luckily this was an easy fix (and the underlying KBKDF implementation is fine; only the test code was broken).
I should've taken Bob's suggestion in the first place: when parsing the mech, store `KI_len` there, which makes the `KI` reading easy.
This does a little cleanup around the clearing the other fields while I'm here (to make everything consistent).
Actual results:
KBKDF CAVP tests fail to execute.
Expected results:
KBKDF CAVP tests should execute.
|
|
1,608,347 | 14,584,240 |
Created attachment 9119988
screenshot
Reproducible: always, seems depend on Network speed and CPU spec.(maybe in case of low spec environment)
Steps to reproduce:
(prerequisite)
1. Saved login password for a site such as bugzilla.mozilla.org
2. Master password is registered
3. Disable "Always check if Firefox is your default browser" to avoid alert dialog if this is not default browser
4. Other than the above is all default settings of browser.
(steps)
1. Clear everything including history, cache, login cookies etc.
Alt - History – Clear Recent History…
Select Everything and check all checkbox and click [Clear Now]
2. Open https://bugzilla.mozilla.org/enter_bug.cgi
3. Quickly close Master Password dialog without enter password And quit browser
4. Start browser again. Observe the bug
Actual Results:
Tabbar only has a "New Tab Page" tab, but the Master Password dialog pops up
Expected Results:
the Master Password dialog should not pop up
After the Master Password pops up at step 2, then leave for a while (i.e.the top site thumbnail is successfully created).
Then step3-4, no longer reproduce the bug.
So, I think Master Password dialog should not offer during thumbnail construction.
|
|
1,608,348 | 14,584,247 |
#### Affected versions:
Nightly 74.0a1 (2020-01-10), Beta 73.0b3
#### Affected platforms:
ALL
#### Steps:
1. Launch Firefox with a new profile and go to about:preferences.
2. Under General, go to Zoom section, check the "Zoom text only" checkbox and select any value from the "Default zoom" dropdown.
3. Access any website that contains text strings and photos.
#### Actual result:
The default zoom level is applied to entire content of the page.
#### Expected result:
Default zoom level should be applied just for text only.
|
|
1,608,505 | 14,585,274 |
I have only tested this on OS X, but it may be a problem on other platforms.
STR: Open two tabs to whereby.com (same room). Observe that neither end receives audio or video. Also observe that browser janks really badly (multi-second).
Edit STR: Seems to happen with any whereby call, whether tab-to-tab or with another browser.
Output from mozregression:
8:18.16 INFO: No more inbound revisions, bisection finished.
8:18.16 INFO: Last good revision: 6ad8baec4ca949e4ede0e79a0a2219cdc10f8bfd
8:18.16 INFO: First bad revision: cb00f09b36fc8ded65b2bf0ca1a86a669f8f0a4a
8:18.16 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6ad8baec4ca949e4ede0e79a0a2219cdc10f8bfd&tochange=cb00f09b36fc8ded65b2bf0ca1a86a669f8f0a4a
Looks like a regression from bug 1586370, or perhaps bug 1542321.
Bug 1607914 is likely a dupe.
Needinfoing padenot, since pehrsons is out.
|
|
1,608,554 | 14,585,642 |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
To reproduce - this assumes that a fresh Firefox profile is being used and that NVDA 2019.2.1 is running:
1. Open Firefox, and navigate to Tools/Options - ensure that NVDA's Focus Mode is enabled at this point
2. Open the "Search" panel, and either tab or shift + tab out of the Options in this panel and to the other visible controls on the screen - including the address bar and other tab-able items. The idea here is to prove that NVDA is able to navigate to these at this stage
3. Navigate back to the available options from within the Search panel, and in the selection of radio buttons that controls how the search box is selected, change this selection to "Add search bar in toolbar"
4. Finally, as before, either tab or shift + tab out of the Search settings, and into the on-screen controls
Actual results:
After changing this setting to force the Search Bar to appear separately to the Address Bar, on-screen controls should still be tab-able - which isn't initially the case after changing the above setting. It's worth noting that if Firefox is then closed and the same profile re-opened, these controls can then be tabbed to as expected. It's also worth mentioning that this isn't a new bug as such, and has been present since at least Firefox 71.
Expected results:
N/A
|
|
1,608,601 | 14,586,040 |
This is a last-minute nudges/tips bug that Harry found today. It's a problem on 72 and later versions. I don't think it's a show stopper -- we could ship the extension with it -- but I also think we should fix it. We should able to do it entirely from the add-on without landing any production code in m-c, but it will require an experiment API addition.
When the redirect tip is shown (for example on google.com), the input correctly is empty, but when you then click the tip's "Okay, Got It" button, the input's value is set to the page's URL. So you have to clear the input before you can search. It should remain empty when you click the button.
Harry found this while porting the extension in bug 1606909. The value is set to the URL by the handleRevert call here: https://searchfox.org/mozilla-central/rev/d4d6f81e0ab479cde192453bae83d5e3edfb39d6/browser/components/urlbar/UrlbarInput.jsm#615
The stack is:
_setValue (UrlbarInput.jsm#1076)
value (UrlbarInput.jsm#941)
URLBarSetURI (browser.js#3390)
handleRevert (UrlbarInput.jsm#434)
pickElement (UrlbarInput.jsm#615)
_on_mouseup (UrlbarView.jsm#1424)
handleEvent (UrlbarView.jsm#499)
|
|
1,608,760 | 14,588,557 |
This bug is for crash report bp-a0e45964-058a-496d-b04b-15eea0200112.
```
Top 10 frames of crashing thread:
0 xul.dll static js::ErrorObject::init js/src/vm/ErrorObject.cpp:477
1 xul.dll static js::ErrorObject::create js/src/vm/ErrorObject.cpp:530
2 xul.dll JS::CreateError js/src/jsexn.cpp:703
3 xul.dll mozilla::dom::ClonedErrorHolder::ToErrorValue dom/ipc/ClonedErrorHolder.cpp:286
4 xul.dll static mozilla::dom::ClonedErrorHolder::ReadStructuredClone dom/ipc/ClonedErrorHolder.cpp:225
5 xul.dll mozilla::dom::`anonymous namespace'::StructuredCloneCallbacksRead dom/base/StructuredCloneHolder.cpp:55
6 xul.dll JSStructuredCloneReader::startRead js/src/vm/StructuredClone.cpp:2626
7 xul.dll ReadStructuredClone js/src/vm/StructuredClone.cpp:650
8 xul.dll mozilla::dom::StructuredCloneHolder::ReadFromBuffer dom/base/StructuredCloneHolder.cpp:316
9 xul.dll mozilla::dom::ipc::StructuredCloneData::Read dom/ipc/StructuredCloneData.cpp:101
```
this crash signature is increasing during the 73.0b cycle - perhaps due to the changes in bug 1588839?
|
|
1,608,923 | 14,589,976 |
Created attachment 9120595
NVDA_FF_PIP_DD.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36
Steps to reproduce:
I have a custom html5 video player that has audio, therefore, the new PIP button appears on hover.
In Firefox + Windows 10, turn on NVDA screen reader. I also use highlighter plugin on NVDA to see where focus moves, but you do you.
Hover the video and invoke the PIP.
PIP launches the video in focusTrap popup.
Tab onto this video.
Notice that NVDA focuses each video player button, but only announces "Button". Each time you tab to another button, NVDA says "Button".
The user doesn't know if they are on play, close, etc.
Actual results:
Using NVDA on a PIP video, the video player buttons do not announce. They only say "button"
Expected results:
Each button on the video player should announce its name to the screen reader. For example, if play button has NVDA focus, it should announce "Play"
A screen reader user would not know which button they need to use to control video playback or close the PIP video unless the buttons announce their proper names.
|
|
1,608,991 | 14,590,359 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Open the Find Bar
Actual results:
See that "Match Diacritics" is missing the 5px margin to its left compared to all other buttons
Expected results:
5px margin should show
Fix would be to insert .findbar-match-diacritics in findBar.css lines 144-148.
|
|
1,609,144 | 14,591,615 |
This bug is for crash report bp-6dc80888-4ec3-428a-8a74-6033e0200114.
```
Top 10 frames of crashing thread:
0 XUL mozilla::dom::WindowGlobalParent::NotifyContentBlockingEvent dom/ipc/WindowGlobalParent.cpp:309
1 XUL mozilla::net::UrlClassifierCommon::NotifyChannelBlocked netwerk/url-classifier/UrlClassifierCommon.cpp:106
2 XUL mozilla::net::UrlClassifierCommon::NotifyChannelClassifierProtectionDisabled netwerk/url-classifier/UrlClassifierCommon.cpp:68
3 XUL mozilla::net::UrlClassifierCommon::AnnotateChannel netwerk/url-classifier/UrlClassifierCommon.cpp:518
4 XUL mozilla::net::UrlClassifierFeatureTrackingAnnotation::ProcessChannel netwerk/url-classifier/UrlClassifierFeatureTrackingAnnotation.cpp:155
5 XUL mozilla::detail::RunnableFunction<mozilla::net::AsyncUrlChannelClassifier::CheckChannel xpcom/threads/nsThreadUtils.h:563
6 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1220
7 XUL NS_ProcessPendingEvents xpcom/threads/nsThreadUtils.cpp:434
8 XUL nsBaseAppShell::NativeEventCallback widget/nsBaseAppShell.cpp:87
9 XUL nsAppShell::ProcessGeckoEvents widget/cocoa/nsAppShell.mm:440
```
There are 18 crashes (from 4 installations) in nightly 74 with buildid 20200114094410. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1599043.
The moz_crash_reason is always: `MOZ_DIAGNOSTIC_ASSERT(!IsInProcess())`.
[1] https://hg.mozilla.org/mozilla-central/rev?node=7316a18109f9
|
|
1,609,160 | 14,591,689 |
Created attachment 9120786
rec of the issue.gif
**[Affected versions]:**
- Firefox Release 72.0.1 - Build ID: 20200107212822
- Firefox Beta 73.0b4 - Build ID: 20200112220634
- Firefox Nightly 74.0a1 - Build ID: 20200114094410
**[Affected Platforms]:**
- Windows 10 x64
- Mac 10.15.2
- Ubuntu 18.04 x64
**[Prerequisites]:**
- Have a Firefox profile with the "browser.search.region" pref set to "US" in the "about:config" page.
**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Navigate to the "about:preferences#home" page.
3. Uncheck the "Top Sites" and "Recommended by Pocket" options.
4. Open a new tab and observe the displayed elements.
**[Expected result]:**
- Only the in-content "Search Bar" and the "Highlights" section are displayed.
**[Actual result]:**
- The "Firefox" name and logo are also displayed above the in-content "Search Bar".
**[Regression Window]:**
- Considering the fact that this issue is not reproducible on older Firefox versions, using the Mozregression tool, we have managed to find the following pushlog:
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8e8ea33ecb3da138dbd0af56c2e5550902e7b05a&tochange=777492b75f9745bd78dc96155ccd91523b788db0
From the pushlog, it seems that bug 1552289 has caused this behavior.
**[Notes]:**
- This issue is also reproducible with the "Discovery Steam" experience for the rest of the world.
- This issue is not reproducible on the "control" branch of the experiment.
|
|
1,609,330 | 14,593,326 |
Created attachment 9120954
screenshot.png
## What were you doing?
1. Open https://www.mozilla.org/en-US/
2. Open the animation inspector
3. Mouse over on "Get a Firefox Account" button.
## What happened?
Two CSS Transitions animations are displayed in the animation inspecor.
But the height of both animation graphs are too big.
See the attachment.
## Anything else we should know?
This might be regression of bug 1599410.
|
|
1,609,665 | 14,595,650 |
This bug is for crash report bp-3f7cd4e1-1124-45ef-a3d4-6dddc0200116.
```
Top 10 frames of crashing thread:
0 xul.dll mozilla::dom::ServiceWorkerRegistrationInfo::MaybeScheduleTimeCheckAndUpdate dom/serviceworkers/ServiceWorkerRegistrationInfo.cpp:460
1 xul.dll std::_Func_impl_no_alloc<`lambda at z:/task_1579054948/build/src/dom/serviceworkers/ServiceWorkerPrivateImpl.cpp:460:7', void, mozilla::dom::ServiceWorkerOpResult&&>::_Do_call
2 xul.dll mozilla::MozPromise<mozilla::dom::ServiceWorkerOpResult, mozilla::ipc::ResponseRejectReason, 1>::ThenValue<`lambda at z:/task_1579054948/build/src/dom/serviceworkers/ServiceWorkerPrivateImpl.cpp:840:7'>::DoResolveOrRejectInternal xpcom/threads/MozPromise.h:793
3 xul.dll mozilla::MozPromise<RefPtr<mozilla::AudioData>, mozilla::MediaResult, 1>::ThenValueBase::ResolveOrRejectRunnable::Run xpcom/threads/MozPromise.h:402
4 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1241
5 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
6 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
7 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308
8 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
9 xul.dll nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
```
another serviceworker-related crash signature that's popping up during the 73.0b cycle.
|
|
1,609,701 | 14,595,883 |
This issue came from originally from the [Fenix issue #7636](https://github.com/mozilla-mobile/fenix/issues/7636), the same steps there can apply here too. To be completely sure that this is not a bug on AC, I created a [simple GeckoView app]( https://github.com/Amejia481/fenix_issue_7636) that mimics the Fenix UI for changing the tracking protection settings, and I was able to replicate the same issue with GV in isolation for more details take a look at [this video](https://drive.google.com/file/d/1PKjxVnPGxGIKRVwJO_KtPae349L8HIjl/view?usp=sharing).
**Browser / Version**
GeckoView Nightly (🦎 7 4.0.20200113093823)
**Operating System**
Moto G5 Galaxy S8 (Android 7)
**Steps to reproduce:**
0. Wait until the page is loaded.
1. Tab the "TP SETTINGS" button.
2. Tab the "STRICT" button.
3. Press the back button (Now the page loads without the bottom ad banner).
4. Tab the "TP SETTINGS" button.
5. Tab the "RECOMMENDED" button.
6. Wait at least 3 seconds and press the back button.
7. Try to interact with any web content like clicking a link
**Expected Behavior:**
The page is refreshed, loaded and it is responsive.
**Actual Behavior:**
The page is refreshed, but never fully loads and it is unresponsive.
I believe the issue is linked to change the tracking protection setting from "Strict" to "Recommend" and refresh the session while the GeckoView is partially visible.
|
|
1,609,857 | 14,597,078 |
**Browser / Version**
Firefox Nightly 74.0a1 (2020-01-15)
**Operating System**
Windows 10
**Steps to reproduce:**
1. Go to https://etc.clona.ru/
2. Observe the Chat window.
**Expected Behavior:**
The Chat window is loaded.
**Actual Behavior:**
The Chat window is not loaded.
**Notes:**
1. Screenshot attached.
2. Disabling the ETP, fixes the issue.
_From the Webcompat bug 47716:_
Hello, I'm the admin resource for clona.ru. The new version of your browser blocks some of the content on the *.clona.ru pages. Built-in chat (https://www.cbox.ws/), is blocked on all pages *.clona.ru
eth.clona.ru
etc.clona.ru
clo.clona.ru
exp.clona.ru
ubiq.clona.ru
pirl.clona.ru
ella.clona.ru
aka.clona.ru
nilu.clona.ru
reosc.clona.ru
moac.clona.ru
dbix.clona.ru
If you manually disable Fingerprints, then everything works.
Please add to *.cbox.ws exception for *.clona.ru sites, in new browser versions.
Chat is an integral part of the site.
|
|
1,609,908 | 14,597,408 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
Open a webpage with a 3D canvas (WebGL context) on nightly, and resize the page dynamically.
Test page : https://threejs.org/examples/#webgl_materials_standard
(Setup: Nightly on Windows 10, Nvidia RTX 2060 card, And Preview Nightly on Android 10, OnePlus 6)
Actual results:
The content of the canvas, which previously resized correctly, now renders on a streched zone instead of adapting the ratio as it used to.
The size of the canvas is OK, but the rendered portion is stretched. It looks like a size setting problem, or more likely a problem when someone sets the webgl context viewport.
This bug happens on Desktop Nightly and on Preview Nighlty but not on regular stable-branch Firefox.
Expected results:
The aspect ratio of the drawn area should have adapted to the new canvas size.
(See stable Firefox or Chrome to compare)
|
|
1,610,085 | 14,598,552 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
Built latest nightly from hg repo and installed.
Actual results:
Everything seems to work, but links are no longer highlighted in color.
Expected results:
Standard behavior of links being highlighted in color.
|
|
1,610,193 | 14,599,291 |
Created attachment 9121771
memory-report.json.gz
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
1. Open https://www.youtube.com/
2. Reload ~15 times
Tested in safe mode
Actual results:
The process for the youtube tab uses 1GB of memory and it keeps increasing the more I reload the page.
I was using an extensions that auto reloads tabs and after about 10 hours it used ~10GB of memory.
Expected results:
Not use so much memory.
|
|
1,610,200 | 14,599,351 |
From https://www.reddit.com/r/firefox/comments/eqy7wf/firefox_fullscreen_f11_does_not_auto_hide/
Steps to reproduce:
1. Open Firefox.
2. Open a web page
3. Enter full screen (F11)
4. Use Ctrl-l to open address bar, navigate to any URL
What happens:
The addressbar does not autohide.
Expected result:
The address bar should autohide.
12:55.13 INFO: No more inbound revisions, bisection finished.
12:55.13 INFO: Last good revision: 12d4df6de36eaae416b024531d12eb8ee802835c
12:55.13 INFO: First bad revision: 2e388d4237d0473f6e14f4218290d54857be84d6
12:55.13 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=12d4df6de36eaae416b024531d12eb8ee802835c&tochange=2e388d4237d0473f6e14f4218290d54857be84d6
|
|
1,610,242 | 14,600,957 |
Created attachment 9121795
Untitled Diagram.png
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36
Steps to reproduce:
Click on the Push Health dropdown on the top-most navbar.
Actual results:
The second navbar containing the Progress, Linting... etc buttons hide the dropdown menu.
Expected results:
the drop-down menu should be on top of the second buttons.
|
|
1,610,334 | 14,601,751 |
+++ This bug was initially created as a clone of Bug #1608923 +++
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36
Steps to reproduce:
I have a custom html5 video player that has audio, therefore, the new PIP button appears on hover.
In Firefox + Windows 10, turn on NVDA screen reader. I also use highlighter plugin on NVDA to see where focus moves, but you do you.
Hover the video and invoke the PIP.
PIP launches the video in focusTrap popup.
Tab onto this video.
Notice that NVDA focuses each video player button, but only announces "Button". Each time you tab to another button, NVDA says "Button".
The user doesn't know if they are on play, close, etc.
Actual results:
Using NVDA on a PIP video, the video player buttons do not announce. They only say "button"
Expected results:
Each button on the video player should announce its name to the screen reader. For example, if play button has NVDA focus, it should announce "Play"
A screen reader user would not know which button they need to use to control video playback or close the PIP video unless the buttons announce their proper names.
----
In this bug, we should come up with a label for the "close" button and the "un-PiP" button, ie the left-most button in the bottom control bar. Both buttons do the same thing: they close the PiP window and re-select the tab that originally contained (and will now once more contain) the video.
:mheubusch, could you help us come up with a text label for this button to be used in accessibility software? Something like "Close and re-select tab", or "Move video back into webpage" or something along those lines perhaps...
|
|
1,610,338 | 14,601,783 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
- Enable e10
- Go to http://www.popuptest.com/ and run any test
- Once a popup is shown navigate to another site
This happens both in Firefox Reality and Fenix including the current Fennec Nightly.
Actual results:
Scrolling doesn't work anymore
Expected results:
Scrolling should work
|
|
1,610,371 | 14,602,006 |
User Agent: Mozilla/5.0 (X11; Linux i686; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Set: block All third-party cookies (or All cookies).
Allow a site by placing it as an exception in managing permissions.
Actual results:
The main site, the one we have put in exceptions, and all third party sites related to it (dozens of third parties in some cases) are authorized to save their cookies.
Expected results:
This should not be the behavior of this setting.
Only the main site must be authorized to save cookies. Only the site present in the exceptions and no third party.
|
|
1,602,502 | 14,536,403 |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
A java script client on Firefox beta connects to a server using libwebsocket. A self-signed certificate is used on the server.
The client first gets a socket.onopen(), then a socket.onerror(), then socket.onclose() with a code:1006 and an empty reason.
On the server side, it does receive LWS_CALLBACK_ESTABLISHED
Actual results:
Websoket works fine on 71.0 version but FireBox beta 72.0b4 closes websocket connection with a code:1006 and an empty reason
Expected results:
Websocket/self-signed certificate should work fine on FireBox beta 72.0b4
|
|
1,602,640 | 14,537,473 |
Created attachment 9114768
out.htm
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
1. Create an HTML document with a very long title (one such document, with a 3000-bytes-long title, is attached; generated with `echo '<title>' > out.htm; head -c 1000 /dev/urandom | hexdump >> out.htm; echo '</title>' >> out.htm`)
2. Get the window title from X11 (either as it is displayed by your window manager, or from `xwininfo -tree -root`)
Actual results:
The X11 window title is "{???}" (without quotation marks and without the usual " - Firefox Nightly").
Expected results:
The X11 window title begins with "0000000 38fd" and ends with "00003e8 - Firefox Nightly".
|
|
1,602,675 | 14,537,708 |
Created attachment 9114804
crash3.js
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.108 Safari/537.36
Steps to reproduce:
$ ./gecko-dev/js/src/ASAN/js/src/js --fuzzing-safe ./crash3.js
crash3.js:
function f(stdlib, foreign, buffer) {
"use asm";
var i32 =stdlib.Int32Array
function g(i) {
i=i|0;
var j=0;
for (; (j>>>0) < 100000; j=(j+1)|0)
i32[i>>2] = j;
}
return g
}
var g = f(this, null, new ArrayBuffer(1<<16));
timeout(.1, function cb() { return true });
g(1<<16);
Actual results:
Backtrace:
Assertion failure: error_, at /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmValidate.cpp:74
AddressSanitizer:DEADLYSIGNAL
=================================================================
==6338==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x555559990092 bp 0x7ffffffee1b0 sp 0x7ffffffee0e0 T0)
==6338==The signal is caused by a WRITE memory access.
==6338==Hint: address points to the zero page.
#0 0x555559990091 in mozilla::UniquePtr<char [], JS::FreePolicy>::reset(decltype(nullptr)) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/ASAN/dist/include/mozilla/UniquePtr.h:444:20
#1 0x555559990091 in mozilla::UniquePtr<char [], JS::FreePolicy>::~UniquePtr() /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/ASAN/dist/include/mozilla/UniquePtr.h:407
#2 0x555559990091 in js::wasm::Decoder::fail(unsigned long, char const*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmValidate.cpp:82
#3 0x5555597ed1dd in js::wasm::OpIter<(anonymous namespace)::IonCompilePolicy>::fail(char const*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmOpIter.h:910:13
#4 0x5555597ed1dd in js::wasm::OpIter<(anonymous namespace)::IonCompilePolicy>::readLinearMemoryAddress(unsigned int, js::wasm::LinearMemoryAddress<js::jit::MDefinition*>*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmOpIter.h:1628
#5 0x5555597f1610 in js::wasm::OpIter<(anonymous namespace)::IonCompilePolicy>::readTeeStore(js::wasm::ValType, unsigned int, js::wasm::LinearMemoryAddress<js::jit::MDefinition*>*, js::jit::MDefinition**) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmOpIter.h:1707:8
#6 0x5555597dc96e in EmitTeeStore((anonymous namespace)::FunctionCompiler&, js::wasm::ValType, js::Scalar::Type) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmIonCompile.cpp:2526:17
#7 0x555559796503 in EmitBodyExprs((anonymous namespace)::FunctionCompiler&) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmIonCompile.cpp
#8 0x555559778471 in js::wasm::IonCompileFunctions(js::wasm::ModuleEnvironment const&, js::LifoAlloc&, mozilla::Vector<js::wasm::FuncCompileInput, 8ul, js::SystemAllocPolicy> const&, js::wasm::CompiledCode*, mozilla::UniquePtr<char [], JS::FreePolicy>*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmIonCompile.cpp:4525:12
#9 0x5555597457ca in ExecuteCompileTask(js::wasm::CompileTask*, mozilla::UniquePtr<char [], JS::FreePolicy>*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmGenerator.cpp:737:12
#10 0x55555974768b in js::wasm::ModuleGenerator::locallyCompileCurrentTask() /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmGenerator.cpp:776:8
#11 0x55555974768b in js::wasm::ModuleGenerator::finishFuncDefs() /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/WasmGenerator.cpp:914
#12 0x5555596d43da in ModuleValidator<mozilla::Utf8Unit>::finish() /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/AsmJS.cpp:2156:13
#13 0x5555595d178a in RefPtr<js::wasm::Module const> CheckModule<mozilla::Utf8Unit>(JSContext*, js::frontend::Parser<js::frontend::FullParseHandler, mozilla::Utf8Unit>&, js::frontend::ParseNode*, unsigned int*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/AsmJS.cpp:6421:27
#14 0x555559490430 in bool DoCompileAsmJS<mozilla::Utf8Unit>(JSContext*, js::frontend::Parser<js::frontend::FullParseHandler, mozilla::Utf8Unit>&, js::frontend::ParseNode*, bool*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/AsmJS.cpp:7099:25
#15 0x555559490430 in js::CompileAsmJS(JSContext*, js::frontend::Parser<js::frontend::FullParseHandler, mozilla::Utf8Unit>&, js::frontend::ParseNode*, bool*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/wasm/AsmJS.cpp:7146
#16 0x55555801a5dc in js::frontend::Parser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::asmJS(js::frontend::ListNode*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:3507:8
#17 0x55555801a5dc in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::asmJS(js::frontend::ListNode*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:3520
#18 0x55555801a5dc in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::maybeParseDirective(js::frontend::ListNode*, js::frontend::ParseNode*, bool*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:3599
#19 0x555557feebf6 in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::statementList(js::frontend::YieldHandling) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:3676:12
#20 0x55555800ea23 in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::functionBody(js::frontend::InHandling, js::frontend::YieldHandling, js::frontend::FunctionSyntaxKind, js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::FunctionBodyType) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:2013:12
#21 0x55555800aa3f in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::functionFormalParametersAndBody(js::frontend::InHandling, js::frontend::YieldHandling, js::frontend::FunctionNode**, js::frontend::FunctionSyntaxKind, mozilla::Maybe<unsigned int> const&, bool) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:3219:12
#22 0x5555580097af in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::innerFunctionForFunctionBox(js::frontend::FunctionNode*, js::frontend::ParseContext*, js::frontend::FunctionBox*, js::frontend::InHandling, js::frontend::YieldHandling, js::frontend::FunctionSyntaxKind, js::frontend::Directives*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:2967:8
#23 0x5555580612a8 in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::innerFunction(js::frontend::FunctionNode*, js::frontend::ParseContext*, JS::Handle<js::frontend::FunctionCreationData>, unsigned int, js::frontend::InHandling, js::frontend::YieldHandling, js::frontend::FunctionSyntaxKind, js::GeneratorKind, js::FunctionAsyncKind, bool, js::frontend::Directives, js::frontend::Directives*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:3000:32
#24 0x555557ff44c3 in js::frontend::Parser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::trySyntaxParseInnerFunction(js::frontend::FunctionNode**, JS::Handle<js::frontend::FunctionCreationData>, unsigned int, js::frontend::InHandling, js::frontend::YieldHandling, js::frontend::FunctionSyntaxKind, js::GeneratorKind, js::FunctionAsyncKind, bool, js::frontend::Directives, js::frontend::Directives*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:2907:32
#25 0x555558017b80 in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::trySyntaxParseInnerFunction(js::frontend::FunctionNode**, JS::Handle<js::frontend::FunctionCreationData>, unsigned int, js::frontend::InHandling, js::frontend::YieldHandling, js::frontend::FunctionSyntaxKind, js::GeneratorKind, js::FunctionAsyncKind, bool, js::frontend::Directives, js::frontend::Directives*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:2945:27
#26 0x555558017b80 in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::functionDefinition(js::frontend::FunctionNode*, unsigned int, js::frontend::InHandling, js::frontend::YieldHandling, JS::Handle<JSAtom*>, js::frontend::FunctionSyntaxKind, js::GeneratorKind, js::FunctionAsyncKind, bool) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:2799
#27 0x555557ffa860 in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::functionStmt(unsigned int, js::frontend::YieldHandling, js::frontend::DefaultHandling, js::FunctionAsyncKind) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:3391:10
#28 0x555557ff5dba in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::statementListItem(js::frontend::YieldHandling, bool) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:8176:14
#29 0x555557feeadc in js::frontend::GeneralParser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::statementList(js::frontend::YieldHandling) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:3654:17
#30 0x555558162406 in js::frontend::Parser<js::frontend::FullParseHandler, mozilla::Utf8Unit>::globalBody(js::frontend::GlobalSharedContext*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/Parser.cpp:1502:20
#31 0x555558245d14 in js::frontend::ScriptCompiler<mozilla::Utf8Unit>::compileScript(js::frontend::BytecodeCompiler&, JS::Handle<JSObject*>, js::frontend::SharedContext*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/BytecodeCompiler.cpp:521:22
#32 0x55555818464a in JSScript* CreateGlobalScript<mozilla::Utf8Unit>(js::frontend::GlobalScriptInfo&, JS::SourceText<mozilla::Utf8Unit>&, js::ScriptSourceObject**) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/BytecodeCompiler.cpp:212:16
#33 0x55555818464a in js::frontend::CompileGlobalScript(js::frontend::GlobalScriptInfo&, JS::SourceText<mozilla::Utf8Unit>&, js::ScriptSourceObject**) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/frontend/BytecodeCompiler.cpp:230
#34 0x555556d1f148 in JSScript* CompileSourceBuffer<mozilla::Utf8Unit>(JSContext*, JS::ReadOnlyCompileOptions const&, JS::SourceText<mozilla::Utf8Unit>&) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/vm/CompilationAndEvaluation.cpp:73:10
#35 0x555556d2006a in JS::CompileUtf8FileDontInflate(JSContext*, JS::ReadOnlyCompileOptions const&, _IO_FILE*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/vm/CompilationAndEvaluation.cpp:145:10
#36 0x55555653e7ce in RunFile(JSContext*, char const*, _IO_FILE*, CompileUtf8, bool) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/shell/js.cpp:882:16
#37 0x55555653c4b2 in Process(JSContext*, char const*, bool, FileKind) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/shell/js.cpp:1512:14
#38 0x5555564ab29c in ProcessArgs(JSContext*, js::cli::OptionParser*) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/shell/js.cpp:10149:10
#39 0x5555564ab29c in Shell(JSContext*, js::cli::OptionParser*, char**) /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/shell/js.cpp:10753
#40 0x55555649a186 in main /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/shell/js.cpp:11415:12
#41 0x7ffff6827b96 in __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310
#42 0x5555563881f9 in _start (/home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/ASAN/dist/bin/js+0xe341f9)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /home/nesa320/lv_11721077/gecko-dev_11_26/gecko-dev-73/js/src/ASAN/dist/include/mozilla/UniquePtr.h:444:20 in mozilla::UniquePtr<char [], JS::FreePolicy>::reset(decltype(nullptr))
==6338==ABORTING
|
|
1,602,726 | 14,538,015 |
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
After Update Firefox ESR 68.2.0 to 68.3.0 running on Windows Server 2012R2/Citrix Envorinment as a normal User we can´t open HTML File-Links.
Actual results:
A Click to MS Word 2016 HTML-Link open a Dialog Window to start with Standard Program but Winword ist not starting.
Same for Excel, Powerpoint, Adobe Reader and so on.
Expected results:
Start the correct Program via MimeType.
As an Admin via RDP-Session there is no Problem. It Works fine.
|
|
1,602,728 | 14,538,023 |
STR:
1. Set `browser.urlbar.suggest.history = false`.
2. Clear all history.
3. Type "blog" in the address bar.
Expected:
Autocompletes to `blog.nightly.mozilla.org` bookmark.
Actual:
Bookmark does not autocomplete despite `browser.urlbar.suggest.bookmark` being enabled.
Visit the bookmark or enable `browser.urlbar.suggest.history` and autocomplete works as expected.
Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e9c9a624d055b54cf65a5361f5261a2278ec6d3e&tochange=36e230321fd00eab502391f7a16aff4aef35364d
Regressed by Bug 1582234.
|
|
1,602,800 | 14,538,546 |
When connecting to a remote Fenix and hitting the "Profile performance" button, I get a blank panel. The following error also occurs in the browser console:
`uncaught exception: Protocol error (unknownError): preference is not of the right type: devtools.performance.recording.entries`
|
|
1,602,804 | 14,538,579 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.97 Safari/537.36
Steps to reproduce:
1) Open http://janodvarko.cz/tests/debugger/watchpoints/
2) Follow test case #1, and click the "Click Me!" button in step #2
3) Set a watchpoint (set) on the age property of the person object
4) Click Resume to pause on the watchpoint
5) Click Resume again to finish pausing and resume execution
6) Click on the "Click Me!" button again in test case #1, step #2
7) Click on the age property's watchpoint marker to remove the watchpoint
8) Try adding a set/get watchpoint
Actual results:
You should be able to put back the watchpoint after removing it.
Expected results:
Nothing happens.
Error:
JavaScript error: , line 0: uncaught exception: Protocol error (noSuchActor): No such actor for ID: server0.conn0.child1/obj78
|
|
1,602,812 | 14,538,656 |
STR:
1. start nightly with new profile
2. navigate to any page, e.g. https://mozilla.org
3. use ctrl-L to select awesome bar contents
4. note that entire URL is selected (this is old behavior)
5. edit the url in any manner, e.g. append '#'
6. click in page to defocus awesome bar
7. use ctrl-L to select awesome bar again
What happens:
- cursor is placed at end of URL, no active selection
What is expected:
- entire URL is selected, as before
Notes:
- I see this with the megabar set either way, but it "feels" like it started with the introduction of the megabar mode.
- this was on Win10, but I'm assuming it's generic
- muscle memory has "switch to tab; ctrl-L; ctrl-C; switch to document; paste link". Now, sometimes, a ctrl-A has to be added, but not always.
|
|
1,602,870 | 14,539,216 |
Created attachment 9114931
example.html
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
Tabbing through a popup window's content does not cycle back to the browser controls and url after the end of the content is reached if window.open is used with the toolbar disabled (value of 0 instead of 1). I'm assuming the tabbing logic in the browser is expecting the tab to be visible, but that isn't always the case, so it fails to find it and prevents the full cycle from being completed. We noticed it when doing ADA testing for our products.
Actual results:
User has to shift + tab to get to earlier content.
Expected results:
User should have been able to tab through all content and then be placed back at the top.
|
|
1,603,020 | 14,540,077 |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36
Steps to reproduce:
The issue seems to be reproducible from 71.0 Firefox version (tested on Windows 10).
1. Open any page sample with contenteditable element. You can use https://codepen.io/jacekbogdanski/pen/QWwNOoV
2. Open FF search bar using CTRL + F keyboard combination.
3. Focus contenteditable element.
4. Start navigating using keyboard arrow keys.
Keyboard navigation works fine until you open a search bar. The issue didn't occur on Firefox 70.
Actual results:
It is possible to use all keys even if the search bar of Firefox is opened.
Expected results:
It is not able to move a caret.
|
|
1,603,221 | 14,541,678 |
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
setup: Clean windows device without firefox installed, and have 14 certificates ready to be installed. Also have a policies.json file ready for insertion.
1. Start off with a Windows device and install firefox 68.2 or higher (32 bit en-US). do not open firefox until policies.json file is placed in the distribution folder, and certs are placed in the certs directory I created.
2. go into C:\Program Files (x86)\Mozilla Firefox\distribution and place the policies.json in there to consume certificates. Do not open firefox.
(note: my policies.json file consumes certificates from a directory called: "C:\Program Files (x86)\Mozilla Firefox\certs" because the default path firefox uses to consume certificates requires a specific user name. I prefer to create the certs in the C drive where the path is not relative when creating in the "%APPDATA%\mozilla\firefox\certificates" directory.)
3. place the 14 certificates into "C:\Program Files (x86)\Mozilla Firefox\certs", the policies.json file will point here and pull the 14 certificates.
4. Open firefox and check the about:preferences and go to Privacy & Security to check the certificates.
5. check about:policies to see if my certificates are enabled and spelled correctly
Actual results:
I observe that only 5 of my 14 certificates are installed. I've even tried mitigating this by using the default directory for consuming certificates afterwards with the same results for versions 68.2 ESR and 68.3 ESR.
I tested the normal versions (68, 70, and 71) and they all imported the 14 certificates, regardless of the directory (such as the firefox default certificates folder, and the one I created called "certs")
Expected results:
All 14 certificates should have imported correctly. The last working version that imported correctly on a clean install was 68.1 ESR.
|
|
1,603,371 | 14,542,687 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Building on Ubuntu with clang 9 and libstdc++ 6 (gcc 8.3.0 and 9.2.1) results in the exact failure claimed to be fixed in https://bugzilla.mozilla.org/show_bug.cgi?id=1601907
Actual results:
https://launchpadlibrarian.net/455261494/buildlog_ubuntu-focal-amd64.firefox-trunk_73.0~a1~hg20191211r506473-0ubuntu0.20.04.1~umd1_BUILDING.txt.gz
```
9:16.92 In file included from Unified_cpp_js_src5.cpp:2:
9:16.92 /<<PKGBUILDDIR>>/js/src/builtin/intl/NumberFormat.cpp:403:25: error: constexpr function never produces a constant expression [-Winvalid-constexpr]
9:16.92 static constexpr size_t MaxUnitLength() {
9:16.92 ^
9:16.92 /<<PKGBUILDDIR>>/js/src/builtin/intl/NumberFormat.cpp:408:31: note: non-constexpr function 'length' cannot be used in a constant expression
9:16.93 length = std::max(length, std::char_traits<char>::length(unit.subtype));
9:16.93 ^
9:16.93 /usr/bin/../lib/gcc/x86_64-linux-gnu/9/../../../../include/c++/9/bits/char_traits.h:329:7: note: declared here
9:16.93 length(const char_type* __s)
9:16.93 ^
9:16.93 In file included from Unified_cpp_js_src5.cpp:2:
9:16.93 /<<PKGBUILDDIR>>/js/src/builtin/intl/NumberFormat.cpp:419:18: error: variable-sized object may not be initialized
9:16.93 char unitChars[MaxUnitLength() + 1] = {};
9:16.93 ^~~~~~~~~~~~~~~~~~~
```
Expected results:
Reverting https://hg.mozilla.org/mozilla-central/rev/c1db977cabfe fixed the failure.
|
|
1,603,397 | 14,542,877 |
Created attachment 9115415
issue.png
**Affected versions**
* Firefox 72.0b5
**Affected platforms**
* macOS 10.15
**Steps to reproduce**
1. Launch Firefox.
2. Access the "about:preferences#privacy" page.
3. Select the "Never remember history" option from the History dropdown list.
4. Observe the Restart Firefox dropdown.
**Expected result**
* The Cancel button not overlap the above message.
**Actual result**
* The Cancel button overlap the above message. Please see the attached screenshot.
**Regression range**
This is a recent regression.
GOOD : 2019.12.04 - 20191204215924
BAD: 2019.12.03 - 20191203215345
Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=3c08edf74d039af79f9daad8ff5b57ffb64fdab6&tochange=32f84899fc000d95337a25c14a27470d0c52e3ee
**Additional notes**
* Issue only on macOS, Firefox beta 72.0b4, 72.0b5, on nightly 73.0a1 from 2019.12.04 this issue is fixed. BAD nightly is 2019.12.03.
|
|
1,603,438 | 14,543,161 |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.79 Safari/537.36
Steps to reproduce:
Building with zlib.h not in the default system include path leads to build failure.
|
|
1,603,511 | 14,543,684 |
[Tracking Requested - why for this release]:
Perf issue with messaging system in release
I suppose this is intended to be sent on stopped state only: https://searchfox.org/mozilla-beta/rev/50dc5e18d7429a505345f610fae358ef385e1ecb/browser/base/content/browser-siteProtections.js#1677
Instead it causes a lot of messages after stopping document load and a few on tab switch etc.
That seems completely unnecessary to me
|
|
1,603,515 | 14,543,719 |
Created attachment 9115552
2019-12-12 20_24_18-YouTube - Firefox Nightly.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Hovering over many sites (including Bugzilla, youtube and more) cause dotted artifacts to temporarily appear on screen - see attached
|
|
1,603,913 | 14,546,569 |
Created attachment 9115918
wefvfr8s5es31.png
As reported on https://www.reddit.com/r/firefox/comments/eagm0o/since_firefox_71_ive_been_getting_black_boxes_on/
>Since Firefox 71, I've been getting black boxes on pages randomly.
>Moving my mouse around fixes them all instantly.
User reports that disabling WebRender via ```gfx.webrender.force-disabled``` resolves the issue.
|
|
1,604,097 | 14,548,959 |
Steps to reproduce a copy error (an a dev site):
```
$ hg clone https://hg.mozilla.org/automation/phabricator-qa-dev/
$ hg copy TEST TEST2
$ hg commit -m "Bug 1 - copy"
$ moz-phab --no-arc .
```
### Expected
https://phabricator-dev.allizom.org/D1633
(Observable by performing a submit using Arcanist `moz-phab .`)
`"TEST This file was copied to TEST2."`
`"TEST2 This file was copied from TEST."`
### Observed
https://phabricator-dev.allizom.org/D1631
`"TEST This file was moved to TEST2."`
`"TEST2 This file was moved from TEST."`
### Notes
An issue with `hg move` was initially reported in bug 1603447 by :calixte.
He mentioned a similar issue reported by :gsvelto in https://bugzilla.mozilla.org/show_bug.cgi?id=1594344#c15
MozPhab is now reverted to a state where the default action is to use Arcanist.
|
|
1,604,117 | 14,549,131 |
This bug is for crash report bp-3a7dcb48-7d06-412a-8dc6-130c20191214.
```
Top 10 frames of crashing thread:
0 vcruntime140.dll memcpy_repmovs f:\dd\vctools\crt\vcruntime\src\string\amd64\memcpy.asm:115
1 xul.dll mozilla::AudioPacketizer<float, float>::Input dom/media/AudioPacketizer.h
2 xul.dll mozilla::AudioInputProcessing::PacketizeAndProcess dom/media/webrtc/MediaEngineWebRTCAudio.cpp:898
3 xul.dll mozilla::AudioInputProcessing::NotifyInputData dom/media/webrtc/MediaEngineWebRTCAudio.cpp:1051
4 xul.dll mozilla::MediaTrackGraphImpl::NotifyInputData dom/media/MediaTrackGraph.cpp:853
5 xul.dll mozilla::AudioCallbackDriver::DataCallback dom/media/GraphDriver.cpp:876
6 xul.dll passthrough_resampler<float>::fill media/libcubeb/src/cubeb_resampler.cpp:97
7 xul.dll `anonymous namespace'::refill media/libcubeb/src/cubeb_wasapi.cpp:789
8 xul.dll `anonymous namespace'::refill_callback_duplex media/libcubeb/src/cubeb_wasapi.cpp
9 xul.dll `anonymous namespace'::wasapi_stream_render_loop media/libcubeb/src/cubeb_wasapi.cpp
```
There are 2 crashes (from 1 installation) in nightly 73 with buildid 20191214094139. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1603384.
[1] https://hg.mozilla.org/mozilla-central/rev?node=9794b0a3bffc
|
|
1,604,180 | 14,549,597 |
This bug is for crash report bp-220effc3-85b5-4d4a-bc50-7fefe0191216.
```
Top 10 frames of crashing thread:
0 xul.dll mozilla::gfx::DrawTargetD2D1::OptimizeSourceSurface const gfx/2d/DrawTargetD2D1.cpp:2222
1 xul.dll static nsLayoutUtils::SurfaceFromElement layout/base/nsLayoutUtils.cpp:7614
2 xul.dll static nsLayoutUtils::SurfaceFromElement layout/base/nsLayoutUtils.cpp:7774
3 xul.dll mozilla::dom::CanvasRenderingContext2D::DrawImage dom/canvas/CanvasRenderingContext2D.cpp:4430
4 xul.dll mozilla::dom::CanvasRenderingContext2D_Binding::drawImage dom/bindings/CanvasRenderingContext2DBinding.cpp
5 xul.dll mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ThrowExceptions> dom/bindings/BindingUtils.cpp:3151
6 xul.dll js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:549
7 xul.dll Interpret js/src/vm/Interpreter.cpp:3116
8 xul.dll js::RunScript js/src/vm/Interpreter.cpp:424
9 xul.dll js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:590
```
The earliest crash with this signature has bug id 20191209215019
|
|
1,604,405 | 14,551,205 |
I did a mistake when selecting the axis index at https://searchfox.org/mozilla-central/rev/c61720a7d0c094d772059f9d6a7844eb7619f107/dom/gamepad/cocoa/CocoaGamepad.cpp#137. We should use the axis array instead of the button array.
|
|
1,604,622 | 14,553,064 |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0
Steps to reproduce:
Go to the following threejs example:
https://threejs.org/examples/?q=gpu#webgl_gpgpu_protoplanet
Actual results:
The canvas remains black on Firefox for Android.
The console displays the following message:
THREE.WebGLRenderer: WEBGL_draw_buffers extension not supported.
Error: WebGL warning: clear: Framebuffer not complete. (status: 0x8cd6) Bad status according to the driver: 0x8cd6
Error: WebGL warning: clear: Framebuffer must be complete.
Expected results:
You should see particles orbiting each other (it works fine on Firefox for Desktop, tested on Ubuntu)
See the issue discussed on Github Threejs repo: https://github.com/mrdoob/three.js/issues/18177
|
|
1,604,813 | 14,554,477 |
#### Affected versions:
Nightly 73.0a1 (2019-12-18).
#### Affected platforms:
ALL
#### Preconditions:
Make sure that Dom.security.featurepolicy.enabled and permissions.delegation.enabled are set to true.
#### Steps:
1. Launch Firefox with a clean profile and access: https://jan-ivar.github.io/dummy/iframe_iframe_gum_starcross.html
2. Check the remember this decision and click allow on the top page.
3. Navigate to the landing page in the second iframe, click on the camera and select Don't allow.
4. Come back to the main page using the back browser button and refresh the page.
#### Actual result:
Use the camera permission is blocked.
#### Expected result:
Use the camera should be allowed based on step 2.
|
|
1,604,851 | 14,554,733 |
The attached crash information refers to mozilla-central revision 20191217-83fc8cf83221.
We don't have a reproducible crash report for this one, but we keep hitting this assertion as well as variations like
```
Assertion failure: IsIdle(oldState) || IsRead(oldState), at xpcom/ds/PLDHashTable.h:130
```
in the Websockets fuzzing target. This has now reached a rate that it impacts fuzzing (in particular coverage measurements). If the problem is not obvious from the stacks, we could try to record it in RR or a developer could run the target for a while (it takes maybe about an hour to hit this).
|
|
1,604,917 | 14,555,145 |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Open https://app.starbucks.com as a PWA in Fenix Nightly
Actual results:
When opening the Starbucks PWA in Fenix, the theme color is not used.
GeckoView's `onWebAppManifest` provides a theme color of `#A862` instead of `#00A862`, removing the leading zeros.
https://github.com/mozilla-mobile/fenix/issues/5585
Expected results:
Color values should get padded at the start with zeros so that 6-digit colors are given to Android Components/Fenix
|
|
1,612,817 | 14,620,779 |
Created attachment 9124030
Screencast 2020-02-03 11:53:07.mp4
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
Open the network monitor, open any website with more than one (JavaScript-initiated) request. Find two requests which have a stack trace available in the right pane.
Choose one of them, click on the stack trace so that it is visible, then click on the other request which is known to also have a stack trace.
Actual results:
The stack trace panel becomes blank. I have to deselect the stack trace panel (e.g. by selecting the Headers or Cookies tab) and reselect it for the stack trace to show up properly.
A video is attached.
Expected results:
I should be able to keep the stack trace tab open, switch between requests and have the correct stack trace shown automatically.
This appears to be a regression because release versions of FF, e.g. 70.0.1+build1-0ubuntu0.18.04.1 , do not seem to have this issue.
|
|
1,613,045 | 14,622,317 |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0
Steps to reproduce:
With a screen reader such as orca on:
1. Reply to a mail (ctrl-r or reply to)
2. shift-tab until the fields where destination addresses are mentioned
So far, the caret reached the addresses and spoke their status (to, Cc etc). Even in the new layout of the window. Now, shift-tab takes the caret on the labels, which should be buttons (cf bug 1611793) but no longer on any address. Impossible then to review the addresses you reply to or you are writing to.
Actual results:
The caret should be able to go on the addresses, expose them to the screen reader, and they should be removable via del key.
|
|
1,613,047 | 14,622,330 |
**Steps to reproduce**
1. Open the console on site-a.com
1. Enable the CSS filter
1. Navigate to site-with-css-warning.com
**Expected results**
I can see the css warnings
**Actual results**
The css warnings are not displayed
---
This is because in the ensureCssReportingEnabled enhancer, we only parse the stylesheet of the target during the initial redux action, or when the CSS filter is toggled ([devtools/client/webconsole/enhancers/css-error-reporting.js#29-33](https://searchfox.org/mozilla-central/rev/2e355fa82aaa87e8424a9927c8136be184eeb6c7/devtools/client/webconsole/enhancers/css-error-reporting.js#29-33) ).
But with target-switching (occuring at step `3` in our example), we won't trigger any of those actions, which means we don't re-parse the stylesheets to get the warnings.
We should change the heuristic to call `target.ensureCSSErrorReportingEnabled` to fix this issue.
This case is covered by [devtools/client/webconsole/test/browser/browser_webconsole_message_categories.js#57-60](https://searchfox.org/mozilla-central/rev/2e355fa82aaa87e8424a9927c8136be184eeb6c7/devtools/client/webconsole/test/browser/browser_webconsole_message_categories.js#57-60), where the CSS filter pref is set at the very start of the test, and we then navigate to different pages.
|
|
1,613,072 | 14,622,453 |
Latest Firefox Nightly 74.0a1 and Firefox Beta 73.0 20200203203546 on Windows 8.1
The 'Late Writes' section is always visible in about:telemetry even if no data about Late Writes is available: https://searchfox.org/mozilla-central/rev/2e355fa82aaa87e8424a9927c8136be184eeb6c7/toolkit/content/aboutTelemetry.js#2417-2419
Steps to reproduce:
1. Type about:telemetry into the address bar and press Enter.
2. Click on 'Late Writes' in the sidebar.
If the there are no Late Writes listed, that section should not be shown according to the intention of the code and how it worked until version 72.
|
|
1,613,093 | 14,622,578 |
**[Affected versions]:**
- Firefox 73.0 Build ID 20200203203546
- Firefox 74.0a1 Build ID 20200203214717
**[Affected Platforms]:**
- Windows 10
- Mac 10.14
- Linux Debian 9
**[Prerequisites]:**
- Set “browser.search.region” to “US” or “CA”
- Restart the browser
**[Steps to reproduce]:**
1. Open a New Tab page.
2. Scroll down the page until after the “Recommended by Pocket” section.
**[Expected result]:**
“Popular Topics” are displayed.
**[Actual result]:**
“Popular Topics” are missing.
**[Regression]:**
Last good revision: 8680f0205149f322f6646c4d4db896f2ebbb5881
First bad revision: 7fcdfe9a24e467bd95219eaa331aa13c1575796a
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8680f0205149f322f6646c4d4db896f2ebbb5881&tochange=7fcdfe9a24e467bd95219eaa331aa13c1575796a
It looks like bug 1598724 has caused this issue.
**[Additional notes]:**
No matter how many new tabs are opened, “Popular Topics” are not displayed.
“Popular Topics” are displayed after page refresh.
@thecount could you please take a look at this?
|
|
1,613,337 | 14,624,349 |
https://bugs.chromium.org/p/chromium/issues/detail?id=1000799
Seems like we might need migrator updates to continue migrating things chromium is encrypting with oscrypt (the issue mentions cookies, though information elsewhere seems to indicate this may also affect passwords?).
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.