be95ec17a58f15cc595c0108e3a1795112df6526: Bug 1364895 - Expose contextualIdentities to webExtensions also if privacy.userContext.enabled is set to false, r=aswan
Andrea Marchesini <amarchesini@mozilla.com> - Tue, 30 May 2017 21:10:14 +0200 - rev 586759
Push 61515 by bmo:gasolin@mozilla.com at Wed, 31 May 2017 02:30:24 +0000
Bug 1364895 - Expose contextualIdentities to webExtensions also if privacy.userContext.enabled is set to false, r=aswan
5b2c84104a7f4774fd120ab38d21b6483bcb63c7: Backed out 2 changesets (bug 1347270) for browser_toolbariconcolor_restyles.js permafail on a CLOSED TREE.
Ryan VanderMeulen <ryanvm@gmail.com> - Tue, 30 May 2017 18:11:02 -0400 - rev 586758
Push 61515 by bmo:gasolin@mozilla.com at Wed, 31 May 2017 02:30:24 +0000
Backed out 2 changesets (bug 1347270) for browser_toolbariconcolor_restyles.js permafail on a CLOSED TREE. Backed out changeset 445cb4d47d4f (bug 1347270) Backed out changeset f2b7f1d599e3 (bug 1347270)
a5a48d0240308bf82ff8e6290a69d709256bdbaf: Bug 1367028 part 3 - Add tests for the new serialization code. r=dholbert
Xidorn Quan <me@upsuper.org> - Tue, 30 May 2017 13:44:44 +1000 - rev 586757
Push 61515 by bmo:gasolin@mozilla.com at Wed, 31 May 2017 02:30:24 +0000
Bug 1367028 part 3 - Add tests for the new serialization code. r=dholbert MozReview-Commit-ID: GuoOCAKTUuB
2b57daca7dcb350482c31d1e99be71004cefae8b: Bug 1367028 part 2 - Simplify serialization of computed value of rect values in border-image props when possible. r=dholbert
Xidorn Quan <me@upsuper.org> - Tue, 30 May 2017 13:27:46 +1000 - rev 586756
Push 61515 by bmo:gasolin@mozilla.com at Wed, 31 May 2017 02:30:24 +0000
Bug 1367028 part 2 - Simplify serialization of computed value of rect values in border-image props when possible. r=dholbert MozReview-Commit-ID: s6TP7oB9l3
43c472a9bfb4779d560f9c9e139ceb38cf619aae: Bug 1367028 part 1 - Simplify serialization of specified rect values in border-image props when possible. r=dholbert
Xidorn Quan <me@upsuper.org> - Mon, 29 May 2017 14:53:58 +1000 - rev 586755
Push 61515 by bmo:gasolin@mozilla.com at Wed, 31 May 2017 02:30:24 +0000
Bug 1367028 part 1 - Simplify serialization of specified rect values in border-image props when possible. r=dholbert MozReview-Commit-ID: C4mNCHqeIoX
38d72735ee8a235c90598cfdfce99409b79ebcc9: servo: Merge #17094 - Update gl_generator to 0.5.3 to make output of some build scripts deterministic (from luser:update-gl-generator); r=emilio
Ted Mielczarek <ted@mielczarek.org> - Tue, 30 May 2017 15:25:18 -0500 - rev 586754
Push 61515 by bmo:gasolin@mozilla.com at Wed, 31 May 2017 02:30:24 +0000
servo: Merge #17094 - Update gl_generator to 0.5.3 to make output of some build scripts deterministic (from luser:update-gl-generator); r=emilio This is simply the result of running: cargo update -p gl_generator --aggressive Source-Repo: https://github.com/servo/servo Source-Revision: 47d6bba3559666f16f4f309ab397c0c16b6c254e
2c8b721cffdb112e6cf377a393f101b8b6fdc006: Bug 1367852 - Fix symbol dumping for gtest xul.dll r=ted
Chris Manchester <cmanchester@mozilla.com> - Tue, 30 May 2017 12:11:32 -0700 - rev 586753
Push 61515 by bmo:gasolin@mozilla.com at Wed, 31 May 2017 02:30:24 +0000
Bug 1367852 - Fix symbol dumping for gtest xul.dll r=ted A pdb file name that differs from a dll file name prevents us from dumping symbols for the gtest xul on Windows. This name differed to accommodate fix_stack_using_bpsyms.py failing in the presence of two xul.sym files, which has since been fixed. MozReview-Commit-ID: I5pA5HjMeRe
463ad37994b0fd9b3eec67755e9f6a450af3a1fc: Bug 1367852 - Defer file read to reduce peak memory use in mozjar when dumping symbols. r=ted
Chris Manchester <cmanchester@mozilla.com> - Tue, 30 May 2017 12:11:21 -0700 - rev 586752
Push 61515 by bmo:gasolin@mozilla.com at Wed, 31 May 2017 02:30:24 +0000
Bug 1367852 - Defer file read to reduce peak memory use in mozjar when dumping symbols. r=ted Passing a file object intead of a string of the file's contents defers reading the file to a place Python can free the resulting string earlier, reducing peak memory consumption when packaging symbols and avoiding a MemoryError on Windows 32 builders in automation. MozReview-Commit-ID: H0R6BbjwhOu
445cb4d47d4f80d58f10eb263035e0045f6e7b93: Bug 1347270: remove the nsIDOMWindowUtils::ElementsRestyled API. r=bholley
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 30 May 2017 11:38:53 +0200 - rev 586751
Push 61515 by bmo:gasolin@mozilla.com at Wed, 31 May 2017 02:30:24 +0000
Bug 1347270: remove the nsIDOMWindowUtils::ElementsRestyled API. r=bholley MozReview-Commit-ID: AKsEWc7Wpip
f2b7f1d599e35c8ca376ce4393cd94258bcfe2ba: Bug 1347270: Rewrite test_media_queries_dynamic.html using restyleGeneration. r=bholley
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 30 May 2017 00:43:15 +0200 - rev 586750
Push 61515 by bmo:gasolin@mozilla.com at Wed, 31 May 2017 02:30:24 +0000
Bug 1347270: Rewrite test_media_queries_dynamic.html using restyleGeneration. r=bholley MozReview-Commit-ID: 3zPETl6WFyc
407ded6901eda45c23d3cd61182176dd7e2c8a9b: Bug 1347807 - wiping the server should cause the engine's lastModified to be reset to zero. r?rnewman draft
Mark Hammond <mhammond@skippinet.com.au> - Wed, 31 May 2017 11:01:13 +1000 - rev 586749
Push 61514 by bmo:markh@mozilla.com at Wed, 31 May 2017 02:18:24 +0000
Bug 1347807 - wiping the server should cause the engine's lastModified to be reset to zero. r?rnewman By having the test server correctly report a 404 on a missing collection, we exposed a bug in the engines. When a "normal" sync starts, we start by querying info/collections, and set the lastModified attribute on the engine to whatever lastModified is reported. However, if the collection doesn't exist, we set lastModified to 0. This has the subtle side-effect of causing Sync to skip the "incoming" process - and that process does *not* handle/expect a 404 querying the collection. If anything in-between the info/collections query and the sync itself causes the server to be wiped (eg, version mismatches in _syncStartup), .lastModified isn't reset, so the sync attempted to process "incoming", saw the 404 and failed. While this wasn't fatal (as the next sync would re-query info/collections and reset .lastModified at that time), the error is unexpected. Without the. .lastModified change, test_corrupt_keys failed for this exact reason (it did the wipe, but that sync got a 404 attempting to process incoming.) MozReview-Commit-ID: JTAGf37WcQd
38aa72d8e18849164942372c3be4db6a1d32978c: Bug 1368875 - Count {video: true} and {audio: true} toward cam and mic counts respectively. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Tue, 30 May 2017 21:57:37 -0400 - rev 586748
Push 61513 by jbruaroey@mozilla.com at Wed, 31 May 2017 01:58:08 +0000
Bug 1368875 - Count {video: true} and {audio: true} toward cam and mic counts respectively. MozReview-Commit-ID: BgdvRLpueit
2ced08f8a0fa90380e515ef563a7d129bf7afd12: Bug 1366996 - Fix uninitialized members in nsUrlClassifierInfo. r?francois draft
DimiL <dlee@mozilla.com> - Wed, 31 May 2017 08:52:34 +0800 - rev 586747
Push 61512 by bmo:dlee@mozilla.com at Wed, 31 May 2017 01:00:19 +0000
Bug 1366996 - Fix uninitialized members in nsUrlClassifierInfo. r?francois This was found by Coverity Scan (CID 1409773, 1409774). MozReview-Commit-ID: LA7oPMobbie
722e572fa7b5bf6141de453089f80947a2c7a2a7: Bug 1366996 - Fix uninitialized members in nsUrlClassifierInfo. r?francois draft
DimiL <dlee@mozilla.com> - Wed, 31 May 2017 08:52:34 +0800 - rev 586746
Push 61511 by bmo:dlee@mozilla.com at Wed, 31 May 2017 00:55:12 +0000
Bug 1366996 - Fix uninitialized members in nsUrlClassifierInfo. r?francois This is found by Coverity Scan (CID 1409773, 1409774). MozReview-Commit-ID: LA7oPMobbie
39032c43c581eb3b83a8466f2d2c73cda1a6923f: Bug 1368782 - Always use rule order for cascading child sheets. r?dbaron draft
Xidorn Quan <me@upsuper.org> - Wed, 31 May 2017 10:51:25 +1000 - rev 586745
Push 61510 by xquan@mozilla.com at Wed, 31 May 2017 00:52:19 +0000
Bug 1368782 - Always use rule order for cascading child sheets. r?dbaron MozReview-Commit-ID: IzEsMvzGqIm
40d071be0200ea0673fc467fb4045ea5f71fe7ef: mybase-stylo draft
Xidorn Quan <me@upsuper.org> - Mon, 12 Sep 2016 11:21:19 +1000 - rev 586744
Push 61510 by xquan@mozilla.com at Wed, 31 May 2017 00:52:19 +0000
mybase-stylo MozReview-Commit-ID: KhkzDKnGGhJ
e877275347cc6dd5d2c7e550a43e23dc389de80a: Bug 1308337 - Post: Remove old background telemetry code r=nalexander draft
Grigory Kruglov <gkruglov@mozilla.com> - Tue, 11 Apr 2017 22:31:18 -0400 - rev 586743
Push 61509 by bmo:gkruglov@mozilla.com at Wed, 31 May 2017 00:50:28 +0000
Bug 1308337 - Post: Remove old background telemetry code r=nalexander MozReview-Commit-ID: CONHqQWzB6c
b75df193692909abbf8493178bbbc10da04b6a95: Bug 1308337 - Part 8: Receive sync telemetry, construct and upload sync pings r=nalexander draft
Grigory Kruglov <gkruglov@mozilla.com> - Mon, 29 May 2017 23:39:35 -0400 - rev 586742
Push 61509 by bmo:gkruglov@mozilla.com at Wed, 31 May 2017 00:50:28 +0000
Bug 1308337 - Part 8: Receive sync telemetry, construct and upload sync pings r=nalexander This patch includes some "pre" work, which should have been a separate patch (my apologies!): - telemetry ping is (needlessly) coupled with information about where it should be uploaded. It wasn't a problem before, since core pings are "upload right away", and are never bundled together during an upload. However, for sync ping, we need to bundle a bunch of "syncs" and "events" (down the road) into one single "sync ping", and as such we need separate representation for a "ping that is not meant to be uploaded directly". - instead of dealing with the coupling directly, a simpler approach is taken: - a "ping" is split into two types of pings: local and outgoing - outgoing ping is what the old "ping" was - a data bundle that is ready to be uploaded - local ping is not meant to be uploaded directly, but is intended to be a part of an outgoing ping, along with other local pings - the main difference between local and outgoing pings is the URL: local pings don't have it while outgoing pings do have it. As background telemetry is received via LocalBroadcastManager, it is processed as follows: - telemetry data is processed into "local pings" which are stored on disk - as enough telemetry is gathered, or we hit one of "let's upload now" conditions, the persisted local pings are gathered into an "outgoing ping" via a SyncPingBundleBuilder, which is persisted on disk. - upload of the bundled "sync ping" is attempted - as individual "local pings" are processed into outgoing "Sync ping" bundles, they are removed from disk Hooks for the upcoming event telemetry data are established, to make that work easier. MozReview-Commit-ID: 4TAT2fKrAYZ
263ae87412204d505b4e0545d02fc47df10eddad: Bug 1308337 - Part 7: Instrument Crypto Keys stage r=nalexander draft
Grigory Kruglov <gkruglov@mozilla.com> - Mon, 29 May 2017 17:20:20 -0400 - rev 586741
Push 61509 by bmo:gkruglov@mozilla.com at Wed, 31 May 2017 00:50:28 +0000
Bug 1308337 - Part 7: Instrument Crypto Keys stage r=nalexander MozReview-Commit-ID: 8a9zKsdhkbv
dc5d6cec373b5e928b6aa28f2e5eef5829e8929d: Bug 1308337 - Part 6: Instrument FetchInfoConfiguration stage r=nalexander draft
Grigory Kruglov <gkruglov@mozilla.com> - Mon, 29 May 2017 21:49:57 -0400 - rev 586740
Push 61509 by bmo:gkruglov@mozilla.com at Wed, 31 May 2017 00:50:28 +0000
Bug 1308337 - Part 6: Instrument FetchInfoConfiguration stage r=nalexander MozReview-Commit-ID: HvDWBVBxb5I
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip