05e5403bdb90dc63a958a99d682e0539c6c8d7a3: Bug 1352016 - P4. Enable NV12 preference. r=mattwoodrow
Jean-Yves Avenard <jyavenard@mozilla.com> - Sun, 10 Sep 2017 17:56:36 +0200 - rev 430093
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1352016 - P4. Enable NV12 preference. r=mattwoodrow Makes it easier to change the value should our detection be broken. MozReview-Commit-ID: KXMjZVLXNg5
6304896839d76c7405ac95029fa6c021e4509a95: Bug 1352016 - P3. Check if NV12 rendering is usable when allocating D3D11 surface. r=mattwoodrow
Jean-Yves Avenard <jyavenard@mozilla.com> - Sun, 10 Sep 2017 17:54:31 +0200 - rev 430092
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1352016 - P3. Check if NV12 rendering is usable when allocating D3D11 surface. r=mattwoodrow MozReview-Commit-ID: EgA6lEeIyBj
2bd972867854e5f0359ce5387816323f9eeb670b: Bug 1352016 - P2. Allow nsIGfxInfo service in GPU process on Windows. r=dvander
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 13 Sep 2017 16:35:14 +0200 - rev 430091
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1352016 - P2. Allow nsIGfxInfo service in GPU process on Windows. r=dvander We'll need it to determine if NV12 D3D11 surface are operationals. MozReview-Commit-ID: FvsxGhnv7H1
369f2167e1277fee6f5c48d37c2044b351597e7b: Bug 1352016 - P1. Add method to check if NV12 rendering is usable. r=mattwoodrow
Jean-Yves Avenard <jyavenard@mozilla.com> - Sun, 10 Sep 2017 17:51:35 +0200 - rev 430090
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1352016 - P1. Add method to check if NV12 rendering is usable. r=mattwoodrow It will allow to blacklist all NVidia Tesla and AMD UVD3 GPU. MozReview-Commit-ID: LaJqyIj0Yau
1682167a89460705853970f382905370a03e74c5: Bug 1390488 - Pass the childProcessTmpDir from the parent process to the GPU process. r=froydnj
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 13 Sep 2017 11:26:25 -0400 - rev 430089
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1390488 - Pass the childProcessTmpDir from the parent process to the GPU process. r=froydnj The GPU process doesn't have the directory service enabled, so it can't find a tmp dir to put its .extra files for crash reports. Even if we do enable the directory service, we still don't get the correct "content process tmp dir" in the GPU process, because the UUID baked into that folder is passed via the preferences service, and that isn't initialized in the GPU process either. Rather than unneccessarily initialize all this stuff in the GPU process just to get one folder name, we can pass that folder name directly in the argv list. See comments 12-19 on the bug for further discussion of the various solutions attempted/explored. MozReview-Commit-ID: 1sFg27hIe7S
e05d7bb3a80fe117f328b77e0b7bd81b4f10bad9: Bug 1390488 - Clean up ifdef indenting and balancing comments, no functional changes. r=froydnj
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 13 Sep 2017 10:17:39 -0400 - rev 430088
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1390488 - Clean up ifdef indenting and balancing comments, no functional changes. r=froydnj This function is very large and has many nested ifdefs. Without this cleanup it was really hard to figure out where all I needed to add code. MozReview-Commit-ID: IeA0AWW62Mn
6c65c331b97fdf61b0efbb0b5b9de84cb6588805: Bug 1367077 - 4. Remove LoginManagerParent.login; r=kmag
Jim Chen <nchen@mozilla.com> - Wed, 13 Sep 2017 11:52:04 -0400 - rev 430087
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1367077 - 4. Remove LoginManagerParent.login; r=kmag Mobile code now loads LoginManagerParent lazily, similar to nsBrowserGlue on desktop, so we no longer need LoginManagerParent.login. MozReview-Commit-ID: 8tnWnev344
8a3e6fbd6511d12292c0a0497bf56a779fc20bba: Bug 1367077 - 3. Move form fill event listeners out of browser.js; r=sebastian
Jim Chen <nchen@mozilla.com> - Wed, 13 Sep 2017 11:52:04 -0400 - rev 430086
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1367077 - 3. Move form fill event listeners out of browser.js; r=sebastian Move the form fill event listeners out of browser.js and into BrowserCLH.js, and update them to support chrome windows, so we can handle form fill events for Fennec, custom tabs, and PWAs. MozReview-Commit-ID: Fb5gWmGvxfE
215f47ca940c83a7f3be50859397d120464046da: Bug 1367077 - 2. Move PromptService startup to BrowserCLH; r=snorp
Jim Chen <nchen@mozilla.com> - Wed, 13 Sep 2017 11:51:55 -0400 - rev 430085
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1367077 - 2. Move PromptService startup to BrowserCLH; r=snorp Use the BrowserCLH for PromptService startup, to consolidate startup handling code and also to delay loading PromptService. MozReview-Commit-ID: 25UgVH7wrrs
3af67a62be1bddd81d4900300fbfcefe4e056466: Bug 1367077 - 1. Move startup utility functions into GeckoViewUtils; r=snorp
Jim Chen <nchen@mozilla.com> - Wed, 13 Sep 2017 11:51:55 -0400 - rev 430084
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1367077 - 1. Move startup utility functions into GeckoViewUtils; r=snorp Move `addLazyGetter` and `addLazyEventListener` utility functions from GeckoViewStartup.js into GeckoViewUtils.jsm, so they can be used for both Fennec and standalone GeckoView. Also switch to "chrome-document-loaded" for loading DownloadNotifications because that's later in the startup sequence. MozReview-Commit-ID: 1caMtufkHGR
93c0ebba5978da90527217f2c28319d78e65759d: servo: Merge #18480 - Store microtask queues directly in GlobalScope (from servo:rc-microtask-queue); r=jdm
Anthony Ramine <n.oxyde@gmail.com> - Wed, 13 Sep 2017 09:18:41 -0500 - rev 430083
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
servo: Merge #18480 - Store microtask queues directly in GlobalScope (from servo:rc-microtask-queue); r=jdm Source-Repo: https://github.com/servo/servo Source-Revision: 2c576e5613b16ba9353461498086b279c283e018
5b931afbbbdeefd398d0d6ab0aeccf9e5f8393cf: Bug 1399172 - Add highlight styling to Flash notification r=johannh
Doug Thayer <dothayer@mozilla.com> - Tue, 12 Sep 2017 10:21:06 -0700 - rev 430082
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1399172 - Add highlight styling to Flash notification r=johannh The Flash (plugin) notification buttons have been restyled temporarily to make them in line with other doorhangers. There is further work being done to use PopupNotifications.jsm fully for these notifications, rather than PopupNotifications + a custom XBL binding. However, this won't make it for 57, so this change fixes the temporary restyle to ensure that the default button is blue. MozReview-Commit-ID: FSlmOdLd8SW
fc4449801edc967b1321765b0d07ab47caf758dc: Bug 1399172 - Add buttonhighlight to update doorhangers r=johannh
Doug Thayer <dothayer@mozilla.com> - Tue, 12 Sep 2017 10:08:01 -0700 - rev 430081
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1399172 - Add buttonhighlight to update doorhangers r=johannh The highlight styling was recently added, causing update notification buttons to both be styled as grey. This fixes that to style them as blue again. MozReview-Commit-ID: HDSA9NWBmIA
dc2bacb89a6bc38cf41831965f55f6838e12cb28: Bug 1387718 - Use instant scroll behavior when dragging something over the tab strip scroll buttons. r=mconley
Dão Gottwald <dao@mozilla.com> - Wed, 13 Sep 2017 12:52:44 +0200 - rev 430080
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1387718 - Use instant scroll behavior when dragging something over the tab strip scroll buttons. r=mconley MozReview-Commit-ID: DiIcdlWd1ic
b061a65e51d79e985415b6c3c8e1fffa28159616: bug 1399082 - about:telemetry l10n fixes r=flod
Chris H-C <chutten@mozilla.com> - Tue, 12 Sep 2017 14:12:55 -0400 - rev 430079
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
bug 1399082 - about:telemetry l10n fixes r=flod We were reusing "all sections" in more than one way, which isn't a globally- permissable language use. Embedding the substring directly takes care of it while at the same time embedding it within its context. MozReview-Commit-ID: CTQhFWEajRo
31078c9f49c180f1effb267087e79a6a7c98f9e8: bug 1398431 - Don't let off-thread CCs get you down r=Dexter
Chris H-C <chutten@mozilla.com> - Wed, 13 Sep 2017 10:44:22 -0400 - rev 430078
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
bug 1398431 - Don't let off-thread CCs get you down r=Dexter Since we don't atomically retrieve session and subsession snapshots, there's a possibility that off-thread accumulations can happen in between the two getPayload calls in test_checkSubsessionHistograms. CYCLE_COLLECTOR_WORKER* are the obvious first choice. MozReview-Commit-ID: 5lseRAJ1Rg6
e5b9fcb0f622b00e71dd057b864603b5653e969d: Bug 1397855 - Enable py2 and py3 linter on testing/xpcshell. r=ahal
Steve Armand <stevea1@mac.com> - Thu, 07 Sep 2017 21:15:35 -0400 - rev 430077
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1397855 - Enable py2 and py3 linter on testing/xpcshell. r=ahal MozReview-Commit-ID: CsfIcI1ma7J
fcf7e964aba53f8a967f055a474e49d05107e24f: Bug 1392390 - Create a reftest selftest harness, r=jmaher
Andrew Halberstadt <ahalberstadt@mozilla.com> - Mon, 11 Sep 2017 16:08:01 -0400 - rev 430076
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1392390 - Create a reftest selftest harness, r=jmaher This just adds two basic tests, one for a passing test and another for a failing one. In mochitest, we use privileged APIs to also tests crashes, assertions, asan and leaks. But these APIs aren't available to reftests so I'm not sure how we can test these things. I figure it's not worth holding the framework up on this though, I'll file a follow-up to figure out something to do for that. MozReview-Commit-ID: 59TSbsugT5T
832cd947704341347a00c8e32ec1b7ff46bc942d: Bug 1392390 - Refactor common code out of mochitest selftests and into a new moztest.selftest module, r=jmaher
Andrew Halberstadt <ahalberstadt@mozilla.com> - Mon, 11 Sep 2017 16:06:06 -0400 - rev 430075
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Bug 1392390 - Refactor common code out of mochitest selftests and into a new moztest.selftest module, r=jmaher This includes code for downloading a Firefox binary, downloading + setting up a tests.zip and running output through mozharness' output parsers. This is all stuff that will also be required for the reftest selftests. I couldn't think of a better location to put this stuff, suggestions welcome. MozReview-Commit-ID: 59TSbsugT5T
0e706b53052c86b247bb8037d1a3fbf2e913045e: Backed out changeset a3b2778fa597 (bug 1389470) for leaks. a=oops
Ryan VanderMeulen <ryanvm@gmail.com> - Wed, 13 Sep 2017 12:36:18 -0400 - rev 430074
Push 7761 by jlund@mozilla.com at Fri, 15 Sep 2017 00:19:52 +0000
Backed out changeset a3b2778fa597 (bug 1389470) for leaks. a=oops MozReview-Commit-ID: 3kkJTmUXdrX
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip