2d7fe7b749885dce85a312448ab8f30d955d78e7: Bug 1001324 - The Downloads Panel footer should use the same style as the application menu. r=adw, a=ritu
Paolo Amadini <paolo.mozmail@amadzone.org> - Fri, 05 Aug 2016 17:26:45 +0100 - rev 347755
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1001324 - The Downloads Panel footer should use the same style as the application menu. r=adw, a=ritu MozReview-Commit-ID: JFM2gmpqyNL
2065ffb539e10304f2e02007791f8ae045144da5: Bug 1285320 - Part 2: Purge border-image cache when hypothetical SVG viewport changes, if using SVG image with no aspect ratio. r=dholbert, a=ritu
Kevin Chen <kechen@mozilla.com> - Sun, 31 Jul 2016 20:24:00 -0400 - rev 347754
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1285320 - Part 2: Purge border-image cache when hypothetical SVG viewport changes, if using SVG image with no aspect ratio. r=dholbert, a=ritu
20dbba05457b32b4350868102fcd3886b796ac3b: Bug 1285320 - Part 1: Add struct "CachedBorderImageData" to keep cached data for border in nsStyleImage. r=dholbert, a=ritu
Kevin Chen <kechen@mozilla.com> - Sun, 31 Jul 2016 20:23:00 -0400 - rev 347753
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1285320 - Part 1: Add struct "CachedBorderImageData" to keep cached data for border in nsStyleImage. r=dholbert, a=ritu
0e4499ae0f81b2fe9e349f66934f7a2bfbf04035: Bug 1280290 - Split test up to fix intermittent docshell leak. r=jmaher, a=test-only
Rob Wood <rwood@mozilla.com> - Wed, 17 Aug 2016 20:54:15 -0400 - rev 347752
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1280290 - Split test up to fix intermittent docshell leak. r=jmaher, a=test-only MozReview-Commit-ID: 6uX62eVcWSj
71313593e2458fe97824d2419c17f8ec7766e7fb: Bug 1296644 - Allow test_2_conformance__canvas__rapid-resizing.html to pass on Win 7. r=jmaher, a=test-only
Geoff Brown <gbrown@mozilla.com> - Fri, 19 Aug 2016 10:54:11 -0600 - rev 347751
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1296644 - Allow test_2_conformance__canvas__rapid-resizing.html to pass on Win 7. r=jmaher, a=test-only
9aea5a70f2679e59ad80a66785215a10c7073928: Bug 1296059 - Fix test harness to force-enable webgl2. CLOSED TREE
Jeff Gilbert <jgilbert@mozilla.com> - Fri, 19 Aug 2016 16:21:15 -0700 - rev 347750
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1296059 - Fix test harness to force-enable webgl2. CLOSED TREE MozReview-Commit-ID: Lq1Je5HrxFL
e60871a5840385e6f0b920da333b18e7004f96f4: Bug 1290280 - Make bug_423132.js more resilient to the initial browser being remote by default. r=mikedeboer,a=ritu
Mike Conley <mconley@mozilla.com> - Sat, 13 Aug 2016 18:46:38 -0400 - rev 347749
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1290280 - Make bug_423132.js more resilient to the initial browser being remote by default. r=mikedeboer,a=ritu The problem with this test was that it was actually relying on the old broken behaviour where the initial browser of the new window it opens would be flipped from remote back to non-remote before loading its contents and flipping remote again. Because it now starts remote (and stays there instead of doing all of the extra work), the test was more likely to fall into the trap that I described in https://groups.google.com/forum/#!searchin/mozilla.dev.platform/1261842%7Csort:relevance/mozilla.dev.platform/gthFqog3J-M/Ypx-SNhEQgAJ where the promiseBrowserLoaded was firing for the wrong page load, which meant that the cookie hadn't had a chance to be set yet. I've converted the test to use the properly instrumented BrowserTestUtils functions which wait for the window to be properly ready, and it appears to pass on try with multiple retriggers. MozReview-Commit-ID: BtQRx7og52A
05be9a2b29ca242ca0d1dd04b24dfae5f4c0c90a: Bug 1290280 - Add tests for window state restoration remoteness flips. r=mikedeboer,a=ritu
Mike Conley <mconley@mozilla.com> - Wed, 10 Aug 2016 15:46:03 -0400 - rev 347748
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1290280 - Add tests for window state restoration remoteness flips. r=mikedeboer,a=ritu MozReview-Commit-ID: ARtmju65xR9
364dc4a98c9fe6ad4c3608081143b874ed6dc8d4: Bug 1290280 - Improve the logic for flipping the remoteness of the initial browser back to non-remote. r=mikedeboer,a=ritu
Mike Conley <mconley@mozilla.com> - Tue, 09 Aug 2016 13:32:21 -0400 - rev 347747
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1290280 - Improve the logic for flipping the remoteness of the initial browser back to non-remote. r=mikedeboer,a=ritu The code that checks to see whether or not we should flip the remoteness of a browser before loading the session state into it wasn't accounting for the fact that oftentimes, restoreImmediately isn't included, so it's undefined, which coerces to "false-y". This caused us to very quickly destroy a TabParent, very soon after creating it. In some cases, the IPC layer seems to not like that, and throws an OnChannelError, which causes the TabParent ActorDestroy method to be called with an abnormal shutdown reason, which causes the tab crash observer to fire, which bubbles the tab crash event. We should probably make the IPC layer more resilient to this sort of thing, but we should also probably not flip remoteness when we really don't need to. Now instead, when restoring a tab, we detect whether or not it's going to be restored automatically in the near future. If it's not going to be restored automatically, and the browser is remote, we flip its remoteness - otherwise we leave it alone. MozReview-Commit-ID: 5AmPHvzDZlX
e13de0688d79198ad5fe7070707e4963aa695ef7: Bug 1291860 - Don't flip remoteness of pinned tabs on session restore. r=mikedeboer,a=ritu
Mike Conley <mconley@mozilla.com> - Wed, 03 Aug 2016 16:34:20 -0400 - rev 347746
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1291860 - Don't flip remoteness of pinned tabs on session restore. r=mikedeboer,a=ritu The initial browser of new windows starts remote now. When restoring a session, if we're restoring content into the initial tab and it's going to be loaded on demand, then we would flip it to non-remote so that it can't background crash. We'd do this for pinned tabs too, which is silly, since pinned tabs load ASAP. This patch causes us to skip the remoteness flip if the tab we're restoring is pinned. MozReview-Commit-ID: 9eQzfLADzlQ
b80ba1b2fb9c57b44ca8b8dd2553829cb84017de: Bug 1296059 - Restore pref-gating for webidl, and update test_interfaces. - r=mrbkap a=sylvestre
Jeff Gilbert <jgilbert@mozilla.com> - Wed, 17 Aug 2016 12:32:57 -0700 - rev 347745
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1296059 - Restore pref-gating for webidl, and update test_interfaces. - r=mrbkap a=sylvestre MozReview-Commit-ID: Ca3Bcb2uvn5
168b10cafd7a0eb12a434b7b9725cd6ce3156175: Bug 1296059 - Disable WebGL2 and dx_interop for 50. - r=milan a=sylvestre
Jeff Gilbert <jgilbert@mozilla.com> - Tue, 16 Aug 2016 16:01:38 -0700 - rev 347744
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1296059 - Disable WebGL2 and dx_interop for 50. - r=milan a=sylvestre MozReview-Commit-ID: 5etQR9pSAmQ
0b2e1f4c1af39800b1e33d2f2e5e88f9aee5e8a0: Bug 1289280 - Check the input frame sizes for being consistent. r=jya, a=abillings
Michael Niedermayer <michael@niedermayer.cc> - Mon, 01 Aug 2016 13:50:21 +0200 - rev 347743
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1289280 - Check the input frame sizes for being consistent. r=jya, a=abillings Imported from: https://github.com/FFmpeg/FFmpeg/commit/77b0f3f26d33d4f46f274896e0583ad1f5936b7c Suggested-by: BBB Fixed-by: BBB Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> MozReview-Commit-ID: DmBS93ydeuT
a55ede08a8bad53f6fbecf32aea2df6e28980e7f: Bug 1291665 - Unregister from refresh driver in DocumentTimeline::Unlink. r=hiro, a=abillings
Brian Birtles <birtles@gmail.com> - Wed, 17 Aug 2016 09:53:22 +0900 - rev 347742
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1291665 - Unregister from refresh driver in DocumentTimeline::Unlink. r=hiro, a=abillings
84b11aee0b433f8ca33c870804965f5f9e952261: Bug 1255261 - Read current paragraph after pressing stop. r=jaws, a=ritu
Eitan Isaacson <eitan@monotonous.org> - Thu, 18 Aug 2016 10:15:00 -0400 - rev 347741
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1255261 - Read current paragraph after pressing stop. r=jaws, a=ritu We always had to make sure we were one paragraph back from where we wanted to start. That seems broken. I made it so that we start from the current paragraph. MozReview-Commit-ID: 4HMTdXcF644
18102c4b22762693f42bc71e12180a32090731fd: Bug 1290179 - Add bouncer products for SHA1 installers r=Callek a=release DONTBUILD
Rail Aliiev <rail@mozilla.com> - Thu, 18 Aug 2016 11:13:06 -0400 - rev 347740
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1290179 - Add bouncer products for SHA1 installers r=Callek a=release DONTBUILD MozReview-Commit-ID: CHztKWnJKql
0417cb2c8a385549ae12daa88c0e3a19ea185fe0: Bug 1275591 - Enable plugin content blocking by default. r=bsmedberg, a=lizzard
Tobias Schneider <schneider@jancona.com> - Wed, 25 May 2016 08:00:32 -0700 - rev 347739
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1275591 - Enable plugin content blocking by default. r=bsmedberg, a=lizzard
d5c53363e8e424477c1f8e648d9032698871397d: Bug 1288213 - Fix and re-enable intermittent layout view tests. r=gl, a=test-only
Sami Jaktholm <sjakthol@outlook.com> - Thu, 11 Aug 2016 18:41:01 +0300 - rev 347738
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1288213 - Fix and re-enable intermittent layout view tests. r=gl, a=test-only The reason for the intermittent timeouts wasn't actually in the layoutview but in the computed view instead. It turns out computed view didn't handle selection change during an ongoing update from previous selection change correctly. When layout view was moved to the computed view, it caused more things to happen during selection change which slowed the computed view updates triggering this race condition. Whenever selection changed, the previous update was canceled but the promise that was blocking the inspector-updated event from being emitted was never resolved nor rejected. This together with the fact that the layoutview tests didn't properly wait for the initial update after navigation / reload to finish before they triggered a new upload lead to the inspector update to hang waiting for the inspector-updated event and the test to timeout. These changes fix the issues by rejecting the computed-view updated promise whenever the update is canceled. This unblocks the inspector-updated event to be emitted once the selection change has finished and stops the tests from timing out. MozReview-Commit-ID: H4cakxkm4vX
b7b4939fdff36184b67dd518010a4ff2b9640191: Bug 1292728 - Fix broken test test_safe_browsing_initial_download.py after the recent safebrowsing list changes. r=whimboo, a=test-only
Panos Astithas <past@mozilla.com> - Tue, 09 Aug 2016 15:51:48 +0300 - rev 347737
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1292728 - Fix broken test test_safe_browsing_initial_download.py after the recent safebrowsing list changes. r=whimboo, a=test-only MozReview-Commit-ID: 36sbv94hwCD
d23f68f5cb77934e673700bfaaaf607893a2df9b: Bug 1294407: Clean up H264 STAP-A handling r=pkerr a=abillings
Randell Jesup <rjesup@jesup.org> - Wed, 17 Aug 2016 16:31:58 -0400 - rev 347736
Push 6389 by raliiev@mozilla.com at Mon, 19 Sep 2016 13:38:22 +0000
Bug 1294407: Clean up H264 STAP-A handling r=pkerr a=abillings
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip