f1c6fd2742f9a710ce4cc4da990dc44282781c3a: Bug 1377433 - Should not do the sliding-up tour notification transition, r=mossop draft
Fischer.json <fischer.json@gmail.com> - Fri, 30 Jun 2017 06:37:09 -0700 - rev 602682
Push 66488 by bmo:fliu@mozilla.com at Fri, 30 Jun 2017 14:36:00 +0000
Bug 1377433 - Should not do the sliding-up tour notification transition, r=mossop MozReview-Commit-ID: L4aDUF1s9OI
d6a446ef4b3527d4979818ba4c88e720e2ca4265: Bug 1363485 - Update BrowserUITelemetry.jsm draft
UK992 <urbankrajnc92@gmail.com> - Fri, 30 Jun 2017 16:22:06 +0200 - rev 602681
Push 66487 by bmo:urbankrajnc92@gmail.com at Fri, 30 Jun 2017 14:28:54 +0000
Bug 1363485 - Update BrowserUITelemetry.jsm MozReview-Commit-ID: Ah8SAEADJ7O
5dc4dfe68424d672374d3481bd9d7c2de7f595ef: Bug 1363485 - Add migration to new navbar layout draft
UK992 <urbankrajnc92@gmail.com> - Thu, 29 Jun 2017 19:09:43 +0200 - rev 602680
Push 66487 by bmo:urbankrajnc92@gmail.com at Fri, 30 Jun 2017 14:28:54 +0000
Bug 1363485 - Add migration to new navbar layout MozReview-Commit-ID: HIPq5rKgtlA
dc49e4feff86147e105977d573a7e836cc8a6e67: Bug 1363485 - Move the Back, Forward, Reload and Stop buttons outside of the location bar container to the start of the toolbar along with the Home button draft
UK992 <urbankrajnc92@gmail.com> - Thu, 29 Jun 2017 01:09:05 +0200 - rev 602679
Push 66487 by bmo:urbankrajnc92@gmail.com at Fri, 30 Jun 2017 14:28:54 +0000
Bug 1363485 - Move the Back, Forward, Reload and Stop buttons outside of the location bar container to the start of the toolbar along with the Home button MozReview-Commit-ID: 2GxcXMxdbjW
7b9683fa09db9c5779e043d5c9fd64d661cc46a4: Bug 1363104 - Fix perf-reftest to compare perf numbers of basic vs ref pages; r=jmaher draft
Rob Wood <rwood@mozilla.com> - Thu, 29 Jun 2017 18:18:45 -0400 - rev 602678
Push 66486 by rwood@mozilla.com at Fri, 30 Jun 2017 14:26:19 +0000
Bug 1363104 - Fix perf-reftest to compare perf numbers of basic vs ref pages; r=jmaher MozReview-Commit-ID: JMtaa9I0atY
3bd3f99d3cce895f34a5b09817e462d7d236e2c0: Bug 1039200 Part1 - Add migrations and associated test for tags and tags relation table, r?mak draft
milindl <i.milind.luthra@gmail.com> - Fri, 02 Jun 2017 15:46:46 +0530 - rev 602677
Push 66485 by bmo:i.milind.luthra@gmail.com at Fri, 30 Jun 2017 14:11:16 +0000
Bug 1039200 Part1 - Add migrations and associated test for tags and tags relation table, r?mak This adds migration for schema v39. In this we add 2 tables, moz_tags and moz_tags_relation, and get all the folders/tag-bookmarks over to them respectively. MozReview-Commit-ID: CcUWLxCwTaK
101077d1686392fd2756a58e4bae61d36885ac76: Bug 1355746 - Part 3. Test cases for IdleTaskRunner. try: -b do -p linux,linux64 -u mochitest-3 -t none draft
Henry Chang <hchang@mozilla.com> - Thu, 15 Jun 2017 17:32:01 +0800 - rev 602676
Push 66484 by hchang@mozilla.com at Fri, 30 Jun 2017 14:06:44 +0000
Bug 1355746 - Part 3. Test cases for IdleTaskRunner. try: -b do -p linux,linux64 -u mochitest-3 -t none MozReview-Commit-ID: 3RsC1pT9Fzc
85b9a4f58d95798cc702228dc03a3df4ac6c85c4: Bug 1039200 Part1 - Add migrations and associated test for tags and tags relation table, r?mak draft
milindl <i.milind.luthra@gmail.com> - Fri, 02 Jun 2017 15:46:46 +0530 - rev 602675
Push 66483 by bmo:i.milind.luthra@gmail.com at Fri, 30 Jun 2017 14:00:51 +0000
Bug 1039200 Part1 - Add migrations and associated test for tags and tags relation table, r?mak This adds migration for schema v39. In this we add 2 tables, moz_tags and moz_tags_relation, and get all the folders/tag-bookmarks over to them respectively. MozReview-Commit-ID: CcUWLxCwTaK
0bbbe4b9370c5fc68aaa79f72a11fe29990667e0: Bug 1377433 - Should not do the sliding-up tour notification transition, r=mossop draft
Fischer.json <fischer.json@gmail.com> - Fri, 30 Jun 2017 06:37:09 -0700 - rev 602674
Push 66482 by bmo:fliu@mozilla.com at Fri, 30 Jun 2017 13:39:10 +0000
Bug 1377433 - Should not do the sliding-up tour notification transition, r=mossop MozReview-Commit-ID: L4aDUF1s9OI
fda29ed21c5bd5bed4a1f6510399559250ede743: Bug 1377433 - Should not do the sliding-up tour notification transition draft
Fischer.json <fischer.json@gmail.com> - Fri, 30 Jun 2017 06:37:09 -0700 - rev 602673
Push 66481 by bmo:fliu@mozilla.com at Fri, 30 Jun 2017 13:37:40 +0000
Bug 1377433 - Should not do the sliding-up tour notification transition MozReview-Commit-ID: L4aDUF1s9OI
efda5fe3b0ef17a31a4e5ec1787e6a45d52e3932: TMP: apply bug 1372067 draft
Fischer.json <fischer.json@gmail.com> - Tue, 27 Jun 2017 07:34:31 -0700 - rev 602672
Push 66481 by bmo:fliu@mozilla.com at Fri, 30 Jun 2017 13:37:40 +0000
TMP: apply bug 1372067
1f8a73a5e84f34cd683abfba854c8413b0cd49b8: Bug 1095425 - Convert PlacesTransactions to the new Bookmarks.jsm API. r=standard8 draft
Marco Bonardo <mbonardo@mozilla.com> <mbonardo@mozilla.com> - Tue, 28 Apr 2015 15:19:43 +0300 - rev 602671
Push 66480 by bmo:mak77@bonardo.net at Fri, 30 Jun 2017 13:35:41 +0000
Bug 1095425 - Convert PlacesTransactions to the new Bookmarks.jsm API. r=standard8 MozReview-Commit-ID: 12pPCGmzV4X
d536973fe668c6c6046fc3fda82e24f3379e3713: merge mozilla-inbound to mozilla-central a=merge
Carsten "Tomcat" Book <cbook@mozilla.com> - Fri, 30 Jun 2017 12:59:45 +0200 - rev 602670
Push 66480 by bmo:mak77@bonardo.net at Fri, 30 Jun 2017 13:35:41 +0000
merge mozilla-inbound to mozilla-central a=merge
b2f19a20a2eae08e42b09a2f2ce555a40653bdfb: Backed out 2 changesets (bug 1356317) for frequent Win7 debug "Assertion failure: !mCompositeDC"
Phil Ringnalda <philringnalda@gmail.com> - Thu, 29 Jun 2017 22:42:12 -0700 - rev 602669
Push 66480 by bmo:mak77@bonardo.net at Fri, 30 Jun 2017 13:35:41 +0000
Backed out 2 changesets (bug 1356317) for frequent Win7 debug "Assertion failure: !mCompositeDC" Backed out changeset d0cdeb6ffaeb (bug 1356317) Backed out changeset 698042ea9555 (bug 1356317) MozReview-Commit-ID: GUNfDlWpg4p
b2efbed661d39531a1c15bde1aad5a933aff51d2: Backed out changeset 4bad6a20f428 (bug 1367439) for failing browser_all_files_referenced.js. r=backout
Sebastian Hengst <archaeopteryx@coole-files.de> - Fri, 30 Jun 2017 03:46:59 +0200 - rev 602668
Push 66480 by bmo:mak77@bonardo.net at Fri, 30 Jun 2017 13:35:41 +0000
Backed out changeset 4bad6a20f428 (bug 1367439) for failing browser_all_files_referenced.js. r=backout
de6df0b30c56d103c56081d822278f94056c7931: Bug 1377348 - Make nsLookAndFeel final to allow the compiler to devirtualize some calls. r=tn
Mats Palmgren <mats@mozilla.com> - Fri, 30 Jun 2017 03:34:15 +0200 - rev 602667
Push 66480 by bmo:mak77@bonardo.net at Fri, 30 Jun 2017 13:35:41 +0000
Bug 1377348 - Make nsLookAndFeel final to allow the compiler to devirtualize some calls. r=tn MozReview-Commit-ID: 7AoZKsTyb3O
bb6cf8e70673681299fcd7218bbba7905eb0e868: Bug 1377252. Stop using RasterImage::IsUnlocked because it doesn't do what we want. r=aosmond
Timothy Nikkel <tnikkel@gmail.com> - Thu, 29 Jun 2017 20:09:44 -0500 - rev 602666
Push 66480 by bmo:mak77@bonardo.net at Fri, 30 Jun 2017 13:35:41 +0000
Bug 1377252. Stop using RasterImage::IsUnlocked because it doesn't do what we want. r=aosmond We currently use RasterImage::IsUnlocked for two different purposes: 1) to determine that we can't throw away the decoded image in WillDrawOpaqueNow 2) to determine when to send the unlockeddraw notification For 1) what we want to check is mLockCount == 0. For 2) what we actually want to check is mAnimationConsumers == 0. This is because images that are in the visible list in background tabs will have mLockCount == 0 but mAnimationConsumers > 0 and if we are drawing an image we need to make sure it will be animated (mAnimationConsumers == 0 stops the animation). This is what VectorImage already does.
b60b291fce967eb0a6238fa57e95cb2525ee4290: Bug 1335335 - Manually call DidComposite() when transaction was dropped because of obsoleted command r=nical
sotaro <sotaro.ikeda.g@gmail.com> - Thu, 29 Jun 2017 18:06:31 -0700 - rev 602665
Push 66480 by bmo:mak77@bonardo.net at Fri, 30 Jun 2017 13:35:41 +0000
Bug 1335335 - Manually call DidComposite() when transaction was dropped because of obsoleted command r=nical The patch fixes a problem on windows. Before the patch, there was a case that moved tab was not re-rendered. When WebRenderBridgeParent reveived obsolted transaction, DidComposite() was not returned to a client side. It stopped nsRefreshDriver to trigger a next transaction.
3bc8240fce3886b172cf4e4b907b8ad56e4d3a76: Bug 1335335 - Tab move between different windows does not work when e10s is enabled r=nical
sotaro <sotaro.ikeda.g@gmail.com> - Thu, 29 Jun 2017 18:06:11 -0700 - rev 602664
Push 66480 by bmo:mak77@bonardo.net at Fri, 30 Jun 2017 13:35:41 +0000
Bug 1335335 - Tab move between different windows does not work when e10s is enabled r=nical When the tab move happens, related non-root WebRenderBridgeParent is updated as to render to different webrender instance. webrender does not support of sharing resources and keys yet. Then when the tab move happens, the patch just removes all keys and resources that belongs to previous webrender. Ideally all resources that belong to WebRenderBridgeParent should be reallocated in an update webrender. But the patch does not do it, instead it just request WebRenderBridgeChild to re-allocate all resources again for simplicity. Performance improvement will happen in a future patch. This patch support only tab move that uses only raw data external images. Support of native texture external images will happen in a future patch.
34e563f2316bee8e241bb11c752c21ba19a08d3f: Bug 1358907 Part 1a Use callProvider() properly in AddonManager.getActiveAddons r=me
Andrew Swan <aswan@mozilla.com> - Thu, 29 Jun 2017 17:41:53 -0700 - rev 602663
Push 66480 by bmo:mak77@bonardo.net at Fri, 30 Jun 2017 13:35:41 +0000
Bug 1358907 Part 1a Use callProvider() properly in AddonManager.getActiveAddons r=me MozReview-Commit-ID: 1Ocmxm3fLBg
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip