90d0473fe6aa5e0ceacb3354a7e226cb7383e715: Bug 1559412 - Support web app manifest ImageResource.purpose r=baku
Marcos Cáceres <mcaceres@mozilla.com> - Thu, 15 Aug 2019 12:55:35 +0000 - rev 488430
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1559412 - Support web app manifest ImageResource.purpose r=baku implementation of purpose member Differential Revision: https://phabricator.services.mozilla.com/D38627
e54b58ba5f3a177e8d3abbb5de1e10903a83910d: Bug 1574143 - Make BlocksRingBuffer::Reader RAII - r=gregtatum
Gerald Squelart <gsquelart@mozilla.com> - Fri, 16 Aug 2019 03:55:08 +0000 - rev 488429
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1574143 - Make BlocksRingBuffer::Reader RAII - r=gregtatum In practice the Reader doesn't need to be copied/moved/reassign. BlocksRingBuffer::Read() can just instantiate one on the stack, and pass it by reference to callbacks. Differential Revision: https://phabricator.services.mozilla.com/D42118
2fd28586dfbe3ecc7a08a5dbec3cc39d2c838ee8: Bug 1574143 - Remove BlocksRingBuffer::EntryReserver - r=gregtatum
Gerald Squelart <gsquelart@mozilla.com> - Fri, 16 Aug 2019 03:54:49 +0000 - rev 488428
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1574143 - Remove BlocksRingBuffer::EntryReserver - r=gregtatum The point of the EntryReserver was mainly to have an object that represented a writing lock on BlocksRingBuffer, so potentially perform multiple consecutive writes. After some experience implementing bug 1562604, there's actually no need for it. So instead of having `Put()` create an `EntryReserver`, we now have `ReserveAndPut()` that does the whole work in one function. Differential Revision: https://phabricator.services.mozilla.com/D42116
1050dca058c32f29609390345646ffde7e9f6114: Bug 1574143 - Make BlocksRingBuffer::EntryWriter RAII - r=gregtatum
Gerald Squelart <gsquelart@mozilla.com> - Fri, 16 Aug 2019 04:02:18 +0000 - rev 488427
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1574143 - Make BlocksRingBuffer::EntryWriter RAII - r=gregtatum EntryWriter doesn't even need to be moveable, as BlocksRingBuffer can just create one on the stack, and pass it by reference to callbacks. This removes risks, and potential data copies. Differential Revision: https://phabricator.services.mozilla.com/D42115
37aaf28a693732407ded4ab9e7e153bc680f02a6: Merge mozilla-central to autoland. CLOSED TREE
Csoregi Natalia <ncsoregi@mozilla.com> - Fri, 16 Aug 2019 07:03:46 +0300 - rev 488426
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Merge mozilla-central to autoland. CLOSED TREE
11919743f599ec393c72c61ee7e18ed52b56e435: Bug 1570147 - Use a Set for HiddenFrame.jsm, so that GC can't clean up frames that we're sitll waiting on. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Fri, 16 Aug 2019 03:23:28 +0000 - rev 488425
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1570147 - Use a Set for HiddenFrame.jsm, so that GC can't clean up frames that we're sitll waiting on. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D42253
db86b932e8991caf212e135e69d559104925bae1: Bug 1570147 - Add test for drawSnapshot. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Fri, 16 Aug 2019 03:13:21 +0000 - rev 488424
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1570147 - Add test for drawSnapshot. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D41828
7ef0d6f34119ec4bb8b6f216c9a205bc93d65475: Bug 1570147 - Modify existing drawWindow tests to take a callback for the inner draw function. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Fri, 16 Aug 2019 03:13:04 +0000 - rev 488423
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1570147 - Modify existing drawWindow tests to take a callback for the inner draw function. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D41827
19443ebbd552f2d4240cbc5fc1a8a6af815f5323: Bug 1570147 - Add SpecialPowers API for calling drawSnapshot in the parent and returning the results. r=kmag
Matt Woodrow <mwoodrow@mozilla.com> - Fri, 16 Aug 2019 03:12:52 +0000 - rev 488422
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1570147 - Add SpecialPowers API for calling drawSnapshot in the parent and returning the results. r=kmag Differential Revision: https://phabricator.services.mozilla.com/D41826
25abe5d28a6a8d7f70f05449e6a850379877d159: Bug 1574299. Allow INTERNAL_THREADING_OPTIMIZATIONS when using WARP. r=aosmond
Jeff Muizelaar <jrmuizel@gmail.com> - Thu, 15 Aug 2019 22:37:43 +0000 - rev 488421
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1574299. Allow INTERNAL_THREADING_OPTIMIZATIONS when using WARP. r=aosmond This seems to make a big difference when running tests with WARP. e.g. Assertion failure: frameInfo.mDocFramesSeen == frameInfo.mDocFramesTotal, at z:/build/build/src/gfx/webrender_bindings/RenderThread.cpp:303 and various other browser chrome test failures. The original problem that added this flag only impacted AMD hardware as I recall and we are unlikely to ever be running on WARP in production anyways. When WARP is forced we also don't disable INTERNAL_THREADING_OPTIMIZATIONS. Differential Revision: https://phabricator.services.mozilla.com/D42214
aa2a510029838127f903e0e72fb5190ee427e5fa: Bug 1574327. Add a pref that we can use to disable d3d11 blacklist. r=aosmond
Jeff Muizelaar <jrmuizel@gmail.com> - Thu, 15 Aug 2019 22:39:18 +0000 - rev 488420
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1574327. Add a pref that we can use to disable d3d11 blacklist. r=aosmond We'll use this to enable WARP on CI. Differential Revision: https://phabricator.services.mozilla.com/D42221
76f8cb64876681e93d675465b48c4a6c8b84bc5d: Bug 1574263 - Switch to Tiny mode for DOM Mutationn Breakpoint reps r=Harald
David Walsh <dwalsh@mozilla.com> - Fri, 16 Aug 2019 00:56:14 +0000 - rev 488419
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1574263 - Switch to Tiny mode for DOM Mutationn Breakpoint reps r=Harald Differential Revision: https://phabricator.services.mozilla.com/D42177
03a1e5d857b555b7f400a94ca904786cba968c50: Bug 1491442 - Fix field order. r=fix CLOSED TREE
Markus Stange <mstange@themasta.com> - Thu, 15 Aug 2019 21:52:55 -0400 - rev 488418
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1491442 - Fix field order. r=fix CLOSED TREE
0822612163d60c8c8deb17f0ab5c59de79b05a66: Bug 1491442 - Remove call to ReadBuffer. r=jgilbert
Markus Stange <mstange@themasta.com> - Fri, 16 Aug 2019 01:16:23 +0000 - rev 488417
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1491442 - Remove call to ReadBuffer. r=jgilbert There's no other caller that sets ReadBuffer to anything else, and GL_BACK is the default for default framebuffers. Furthermore, this call triggers GL_INVALID_OPERATION errors when called on a non-default framebuffer. Differential Revision: https://phabricator.services.mozilla.com/D40551
ae86a277bd72b7a3c9b5e2ae40fcb74c33b796da: Bug 1491442 - Don't handle null render targets in this method. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Fri, 16 Aug 2019 01:15:59 +0000 - rev 488416
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1491442 - Don't handle null render targets in this method. r=mattwoodrow There's only one caller and it always passes a non-null render target. Differential Revision: https://phabricator.services.mozilla.com/D40550
706ff8a1badcd0c796e151b9e015bbfed0b20ddf: Bug 1491442 - Call SuspendAsyncCATransactions on window focus changes. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Fri, 16 Aug 2019 01:15:34 +0000 - rev 488415
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1491442 - Call SuspendAsyncCATransactions on window focus changes. r=mattwoodrow Without this, in windows with title bars, such as the bookmark library window, the title bar and the content would update at different times. The title bar paint is done as part of a main thread CoreAnimation transaction. However, by default, we don't get notified of all main thread CA transactions; our only notification mechanism is the updateLayer handler on the PixelHostingView, and that handler is only invoked (the layer is only displayed) if the layer has been marked as needing display. And by default, window focus changes do not mark random views' backing layers as needing display. Usually, what this means is that the window will be painted twice: Once in the main thread transaction, and then another time on the compositor thread once Gecko has noticed a state change and triggered its own composite in response. (Often, Gecko's compositor-side paint will actually happen *before* the main thread paint, because the main thread is often busy with repainting the system menu bar during window focus changes.) Such non-atomic window repaints look glitchy. Calling SuspendAsyncCATransactions will result in a call to updateLayer in the upcoming CoreAnimation transaction and lets us update the entire window in one atomic paint, and it will avoid updating the window early if the compositor thread gets ahead of the main thread. Differential Revision: https://phabricator.services.mozilla.com/D38759
e6e88a4fc6b95571d04db7841603bea7148df02f: Bug 1491442 - Disable window overlay drawing in the CoreAnimation path. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Fri, 16 Aug 2019 01:15:10 +0000 - rev 488414
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1491442 - Disable window overlay drawing in the CoreAnimation path. r=mattwoodrow Window overlay drawing was added as a workaround for the following: When our NSOpenGLContext covered the entire window, it would cover the titlebar contents and hide the window buttons and the title string. It would also not get anti-aliased rounded corner clipping. In windows that use CoreAnimation layers for the window frame, this is no longer a problem, because the CoreAnimation layer tree takes care of these effects: It applies rounded corner clipping to the window content layers, it puts the window buttons on top, and it also puts the title string on top if it is shown. So when we're using CoreAnimation, the existing code needs to be deactivated, otherwise we'd draw those things twice. Differential Revision: https://phabricator.services.mozilla.com/D38760
a5ba7777641703116a83c6b4bbea66308fb6e816: Bug 1491442 - Make sure to never trigger async CA transactions when the main thread might be resizing a window. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Fri, 16 Aug 2019 01:14:47 +0000 - rev 488413
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1491442 - Make sure to never trigger async CA transactions when the main thread might be resizing a window. r=mattwoodrow This avoids most window resizing glitches. Differential Revision: https://phabricator.services.mozilla.com/D40518
24dbae685801b451fba51d0e3788a821038c9321: Bug 1491442 - Support BasicCompositor OMTC rendering in the CoreAnimation path. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Fri, 16 Aug 2019 01:14:22 +0000 - rev 488412
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1491442 - Support BasicCompositor OMTC rendering in the CoreAnimation path. r=mattwoodrow Now CoreAnimation supports all rendering paths. The BasicCompositor OMTC path is used when hardware acceleration is disabled, for example in safe mode or when the user manually disabled it. Differential Revision: https://phabricator.services.mozilla.com/D38758
5aa5080461f8910b5b3e131f7164d236536aaf79: Bug 1491442 - Render accelerated windows into mContentLayer, using OMTC. r=mattwoodrow
Markus Stange <mstange@themasta.com> - Fri, 16 Aug 2019 01:13:52 +0000 - rev 488411
Push 113908 by ccoroiu@mozilla.com at Fri, 16 Aug 2019 09:57:53 +0000
Bug 1491442 - Render accelerated windows into mContentLayer, using OMTC. r=mattwoodrow This makes windows that render using CompositorOGL or WebRender show content. Differential Revision: https://phabricator.services.mozilla.com/D40517
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 tip