32595f9e73d376499b5d1d26b1954a37a9c7e600: Bug 1497707, part 3 - Remove various unused things from nsComponentManager r=froydnj
Andrew McCreight <continuation@gmail.com> - Wed, 17 Oct 2018 20:45:42 +0000 - rev 497569
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1497707, part 3 - Remove various unused things from nsComponentManager r=froydnj Depends on D8169 Differential Revision: https://phabricator.services.mozilla.com/D8170
f37f2d39ec9cddf0d6fed933422c854bfebca488: Bug 1497707, part 2 - The second argument to nsComponentManagerImpl::RegisterModule is always null r=froydnj
Andrew McCreight <continuation@gmail.com> - Wed, 17 Oct 2018 20:45:42 +0000 - rev 497568
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1497707, part 2 - The second argument to nsComponentManagerImpl::RegisterModule is always null r=froydnj This allows some code to be deleted, including a KnownModule ctor. Depends on D8168 Differential Revision: https://phabricator.services.mozilla.com/D8169
80bf9ddf5bedaaded17e4d0f3a2860ed73892c10: Bug 1497707, part 1 - Get rid of xpcIJSModuleLoader r=kmag
Andrew McCreight <continuation@gmail.com> - Wed, 17 Oct 2018 20:45:41 +0000 - rev 497567
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1497707, part 1 - Get rid of xpcIJSModuleLoader r=kmag This interface is only used for a few testing functions. Just move them to Cu. Differential Revision: https://phabricator.services.mozilla.com/D8168
f6404da759c5d8834f367bde898dd1fcd54fc904: Bug 1498873 - Simplify a check. r=bzbarsky
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 17 Oct 2018 20:40:08 +0000 - rev 497566
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1498873 - Simplify a check. r=bzbarsky And make will-change: position properly create an abspos cb while at it, since the check was missing the `mWillChangeBitfield & ABSPOS_CB` bit. Differential Revision: https://phabricator.services.mozilla.com/D8743
1249680014b0b4faf9eed339f9716755322bb33d: Bug 1499473: Simplify TabGroup a bit, now that ThrottledEventQueue::Create is infallible. r=smaug
Jim Blandy <jimb@mozilla.com> - Wed, 17 Oct 2018 20:41:59 +0000 - rev 497565
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1499473: Simplify TabGroup a bit, now that ThrottledEventQueue::Create is infallible. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D8915
b77bde54527692f87c31a60112d3cb57ec13298e: Bug 1498873 - Pass the right frame to PushAbsoluteContainingBlock to determine whether we're a fixed-pos containing block. r=bzbarsky
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 17 Oct 2018 20:22:38 +0000 - rev 497564
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1498873 - Pass the right frame to PushAbsoluteContainingBlock to determine whether we're a fixed-pos containing block. r=bzbarsky When we're creating a scrollframe with let's say, display: flex or grid, the containing block is the grid container itself, but the transformed frame is the scroll frame. This is the only caller that (incorrectly) passes the same frame to PushAbsoluteContainingBlock. Our painting code deals with it, mostly, because it starts from the placeholder to paint fixed items, and it hits the scrollframe, but it gets confused sometimes causing the issue described here. I'll find a way to add a crashtest for this, and maybe a reftest, though this works in non-WR. We should probably add a few more assertions to the frame constructor... Differential Revision: https://phabricator.services.mozilla.com/D8724
7f9d03c29a6ffd82c1b5e17c14e27a2ae9d64434: Bug 1487100 - Allow opening the input stream for original content when alt-data is available r=michal,luke
Valentin Gosu <valentin.gosu@gmail.com> - Wed, 17 Oct 2018 12:27:37 +0000 - rev 497563
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1487100 - Allow opening the input stream for original content when alt-data is available r=michal,luke In trying to use fetch with alt-data, we sometimes want the benefit of using alt-data but the JS consumer actually needs to use the original HTTP response from the server. To get around this problem, we introduce a new API - nsICacheInfoChannel.getOriginalInputStream(nsIInputStreamReceiver) that asyncly receives the input stream containing the HTTP response in the cache entry. Depends on D8071 Differential Revision: https://phabricator.services.mozilla.com/D8072
dd1c31ea78c2b15d14750d137037a54d50719997: Bug 1487100 - Allow calling nsICacheInfoChannel.preferAlternativeDataType(altDataType, contentType) multiple times r=michal,luke
Valentin Gosu <valentin.gosu@gmail.com> - Wed, 17 Oct 2018 13:58:30 +0000 - rev 497562
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1487100 - Allow calling nsICacheInfoChannel.preferAlternativeDataType(altDataType, contentType) multiple times r=michal,luke This patch changes the way we set and handle the preferred alternate data type. It is no longer just one choice, but a set of preferences, each conditional on the contentType of the resource. For example: var cc = chan.QueryInterface(Ci.nsICacheInfoChannel); cc.preferAlternativeDataType("js-bytecode", "text/javascript"); cc.preferAlternativeDataType("ammended-text", "text/plain"); cc.preferAlternativeDataType("something-else", ""); When loaded from the cache, the available alt-data type will be checked against "js-bytecode" if the contentType is "text/javascript", "ammended-text" if the contentType is "text/plain" or "something-else" for all contentTypes. Note that the alt-data type could be "something-else" even if the contentType is "text/javascript". The preferences are saved as an nsTArray<mozilla::Tuple<nsCString, nsCString>>. Differential Revision: https://phabricator.services.mozilla.com/D8071
b0f3a71aca93651a580a5814f75c914f5c9cbdcd: Bug 1499803 - collect media Telemetry Scalar in Release version. r=chutten
alwu <alwu@mozilla.com> - Wed, 17 Oct 2018 18:50:12 +0000 - rev 497561
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1499803 - collect media Telemetry Scalar in Release version. r=chutten The autoplay shield-study which will run on Release 63 needs one of these data and we also want to analysis other data in order to improve the user experience of blocking-autoplay. Differential Revision: https://phabricator.services.mozilla.com/D9014
1d8eba4911f02fd91a0072bbc12ddbbb70d13b42: Bug 1499778 - Remove StaticId. r=xidorn
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 17 Oct 2018 19:48:35 +0000 - rev 497560
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1499778 - Remove StaticId. r=xidorn Destructors in statics are ok now. Differential Revision: https://phabricator.services.mozilla.com/D9004
3506efe6428a9247e324af7a06dc82f61af781f1: Bug 1497977 p6 - Also send a collection_changed push notification when uploading our client record following an fxa device id change. r=nalexander
Edouard Oger <eoger@fastmail.com> - Wed, 17 Oct 2018 18:23:14 +0000 - rev 497559
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1497977 p6 - Also send a collection_changed push notification when uploading our client record following an fxa device id change. r=nalexander Depends on D8611 Differential Revision: https://phabricator.services.mozilla.com/D8612
60c949b40f469cdb459a1ec9d31efce727593c3a: Bug 1497977 p5 - Flag local client record for upload on fxa device id change. r=nalexander
Edouard Oger <eoger@fastmail.com> - Wed, 17 Oct 2018 18:23:12 +0000 - rev 497558
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1497977 p5 - Flag local client record for upload on fxa device id change. r=nalexander Depends on D8610 Differential Revision: https://phabricator.services.mozilla.com/D8611
ea10b0217cec23ce84efefcf437e9a81c33e31fd: Bug 1497977 p4 - Trigger an upload of our own client record after FxA device registration. r=nalexander
Edouard Oger <eoger@fastmail.com> - Wed, 17 Oct 2018 18:23:09 +0000 - rev 497557
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1497977 p4 - Trigger an upload of our own client record after FxA device registration. r=nalexander Depends on D8609 Differential Revision: https://phabricator.services.mozilla.com/D8610
5238702906f63d95d2fae62f33aa53cb61de7e49: Bug 1497977 p3 - Retry a device registration immediately after recovering from a unknown device error. r=nalexander
Edouard Oger <eoger@fastmail.com> - Wed, 17 Oct 2018 18:23:07 +0000 - rev 497556
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1497977 p3 - Retry a device registration immediately after recovering from a unknown device error. r=nalexander Depends on D8607 Differential Revision: https://phabricator.services.mozilla.com/D8609
e720c16aa7c6da10135d26da34cd4030b2c83713: Bug 1497977 p2 - Handle fxaccounts:password_changed push messages. r=nalexander
Edouard Oger <eoger@fastmail.com> - Wed, 17 Oct 2018 18:22:59 +0000 - rev 497555
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1497977 p2 - Handle fxaccounts:password_changed push messages. r=nalexander Depends on D8606 Differential Revision: https://phabricator.services.mozilla.com/D8607
3901ae585e3ae25f76b20e0fb8f44f1a9a4dfff0: Bug 1497977 p1 - Renew the fxa device registration/client record on FxA account reconnection. r=nalexander
Edouard Oger <eoger@fastmail.com> - Wed, 17 Oct 2018 18:22:57 +0000 - rev 497554
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1497977 p1 - Renew the fxa device registration/client record on FxA account reconnection. r=nalexander Differential Revision: https://phabricator.services.mozilla.com/D8606
affe4a683227c556ec3d21bbf9e9024fa4a71a4a: Bug 1499136 - Disable dom.xhr.standard_content_type_normalization for now due to webcompat issues; r=hsivonen
Thomas Wisniewski <twisniewski@mozilla.com> - Wed, 17 Oct 2018 17:04:14 +0000 - rev 497553
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1499136 - Disable dom.xhr.standard_content_type_normalization for now due to webcompat issues; r=hsivonen Disable dom.xhr.standard_content_type_normalization for now due to webcompat issues Differential Revision: https://phabricator.services.mozilla.com/D8789
b67ac3f5e1aca5c8348375497fb7a0108a576179: Bug 1476491 - Adjust the flexbox line styles to match the css grid line styles. r=gl
Micah Tigley <mtigley@mozilla.com> - Wed, 17 Oct 2018 18:08:31 +0000 - rev 497552
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1476491 - Adjust the flexbox line styles to match the css grid line styles. r=gl Differential Revision: https://phabricator.services.mozilla.com/D8600
0623ed3cb752851d5f96618b6a5f7c3048b49b60: Backed out 3 changesets (bug 1435871) for mochitest crashes. CLOSED TREE
Dorel Luca <dluca@mozilla.com> - Wed, 17 Oct 2018 23:06:14 +0300 - rev 497551
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Backed out 3 changesets (bug 1435871) for mochitest crashes. CLOSED TREE Backed out changeset 8eab3320b8c5 (bug 1435871) Backed out changeset 29777ddd9def (bug 1435871) Backed out changeset afdc3066f12c (bug 1435871)
63248a593eae0a14ffc33ab0057cf41d3ecb8018: Bug 1489443 - Set GCC_USE_GNU_LD based on linker kind. r=froydnj
Nick Alexander <nalexander@mozilla.com> - Wed, 17 Oct 2018 19:46:03 +0000 - rev 497550
Push 9996 by archaeopteryx@coole-files.de at Thu, 18 Oct 2018 18:37:15 +0000
Bug 1489443 - Set GCC_USE_GNU_LD based on linker kind. r=froydnj The desired outcome of this change is that we'll set -Wl,--version-script based on linker kind and not on the output of $LINKER -v. This is a cheap way to address a simple problem that has a complicated ideal solution. The underlying issue is that in some situations, when targeting Android, a macOS system ld is interrogated to determine if a cross-compiling linker "is GNU ld" and a particular linker feature is set in that situation. The macOS system ld doesn't pass the "is GNU ld" test, and the linker feature isn't set; that causes link failures, even though the actual linker has nothing to do with the system ld. The ideal solution is to test for linker capabilities dynamically. We do a lot of that in old-configure.in, and we don't do any of that in toolchain.configure. Rather than start testing in toolchain.configure, we hard-code: a cheap solution to the immediate problem. MinGW suffers somewhat from the opposite problem: the linker "is GNU ld" (compatible), but the linker checks don't happen at all. We hard-code for MinGW based on the C compiler instead. Differential Revision: https://phabricator.services.mozilla.com/D8471
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip