b65a65089ffb622c0f0d55124d77adc788c9c5b7: Bug 1422057 - Extend the clipchain of a display item to the ancestor's clipchain if it is a strict superset. r=mstange
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 06 Jan 2018 09:52:58 -0500 - rev 449874
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1422057 - Extend the clipchain of a display item to the ancestor's clipchain if it is a strict superset. r=mstange See the documentation in the added function for details. MozReview-Commit-ID: 4R0WaSy0tm2
78ca58c296fa61382c4acb401e9c9eb0cb551eb7: Bug 1422057 - Extract a local variable. r=mstange
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 06 Jan 2018 09:52:58 -0500 - rev 449873
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1422057 - Extract a local variable. r=mstange This makes the next patch cleaner. MozReview-Commit-ID: KjqdiBFFlMM
c12c951b5ecc9d410014b11f399f65f135cb39b1: Bug 1422057 - Avoid caching clips across stacking contexts with non-identity transforms. r=mstange
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 06 Jan 2018 09:52:58 -0500 - rev 449872
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1422057 - Avoid caching clips across stacking contexts with non-identity transforms. r=mstange When a clip is defined in WebRender, any transforms on the containing stacking contexts are baked into the clip's position. Therefore, trying to use a clip that was defined inside a transformed stacking context in other parts of the WR display list doesn't work properly. This was a latent bug in ScrollingLayersHelper that was previously not exposed because in these cases Gecko itself creates separate DisplayItemClipChain items. Now that we are going to deduplicate those DisplayItemClipChain items, it exposes this latent bug which we need to fix. MozReview-Commit-ID: Icd7L1JuY8s
4dcb02cef0b78a53dd90cfb79e9d97e16542cb55: Bug 1422057 - Adjust some logging-related things to be more useful. r=mstange
Kartikaya Gupta <kgupta@mozilla.com> - Sat, 06 Jan 2018 09:52:57 -0500 - rev 449871
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1422057 - Adjust some logging-related things to be more useful. r=mstange MozReview-Commit-ID: Idheevum5Fd
27841347525c5e83a67e086d6fd15758c625a9e3: Bug 1428425 - Clean up browser_permissions_dialog.js. r=johannh
Prathiksha <prathikshaprasadsuman@gmail.com> - Sat, 06 Jan 2018 15:42:07 +0530 - rev 449870
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1428425 - Clean up browser_permissions_dialog.js. r=johannh MozReview-Commit-ID: 3cBMSVOmgVi
9d19176e7d25ca310f6cc170602b96c1a92ef3f2: Bug 1363040 - Stop loading tracking-protection-16.svg in windows that don't display it. r=johannh
Prathiksha <prathikshaprasadsuman@gmail.com> - Thu, 04 Jan 2018 22:22:19 +0530 - rev 449869
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1363040 - Stop loading tracking-protection-16.svg in windows that don't display it. r=johannh MozReview-Commit-ID: I6yN3l47k9l
4e3d7247274add5d767d6700209040f76ce8cb80: Bug 1396434 - Test that symbols can be stored as global variables in the console. r=nchevobbe
Oriol Brufau <oriol-bugzilla@hotmail.com> - Mon, 01 Jan 2018 13:17:05 +0100 - rev 449868
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1396434 - Test that symbols can be stored as global variables in the console. r=nchevobbe MozReview-Commit-ID: Ba7Ir2BHEzw
9ea106a104bb4a32b181069d0aed10abb85a754f: Bug 1421538 - Set country field to default country when creating new addresses. r=lchang
Scott Wu <scottcwwu@gmail.com> - Wed, 03 Jan 2018 17:50:44 +0800 - rev 449867
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1421538 - Set country field to default country when creating new addresses. r=lchang MozReview-Commit-ID: 5Bd6TdZOej
d6993ed46421d9b68d4d8b9889170c485bf359c3: Bug 1420982 - Fix for copy as cURL ignoring PATCH data. r=Honza
abhinav <abhinav.koppula@gmail.com> - Fri, 22 Dec 2017 00:41:50 +0530 - rev 449866
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1420982 - Fix for copy as cURL ignoring PATCH data. r=Honza MozReview-Commit-ID: 8GDV8ykAIsH
9fd84f164c7fa0f3c009ce836c75e68a443c4256: Bug 1428353: Allow undisplayed maps to be queried for elements out of the document. r=mats
Emilio Cobos Álvarez <emilio@crisal.io> - Sat, 06 Jan 2018 00:50:58 +0100 - rev 449865
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1428353: Allow undisplayed maps to be queried for elements out of the document. r=mats MozReview-Commit-ID: 69lQNFk5vhG
e1fedb493a2fbafcdb19c564d04c25aafb4417bb: Bug 1427677: Remove nsBindingManager::FindNestedInsertionPoint. r=bz
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 03 Jan 2018 06:38:21 +0100 - rev 449864
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1427677: Remove nsBindingManager::FindNestedInsertionPoint. r=bz No more callers! MozReview-Commit-ID: 1mxi4IjViuC
2cae0b7e4b1c579febf31f5034a5d37442e8947b: Bug 1427677: Get rid of nsContentUtils::HasDistributedChildren. r=bz
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 02 Jan 2018 15:04:38 +0100 - rev 449863
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1427677: Get rid of nsContentUtils::HasDistributedChildren. r=bz The whole function doesn't have much sense. I killed its only DOM use in bug 1427511. Now it only has two callers in nsCSSFrameConstructor, which basically only want to know whether the children of the same node can have different flattened tree parents. So let's check that directly instead (checking whether the element has a binding or a shadow root), and simplify a bit other surrounding code while at it. Leave the XUL popup / menubar code doing the broken thing they were doing beforehand, because it doesn't look to me like it's trivial to fix... They're effectively assuming that the children of the menupopup end up in a single insertion point, which is true, but doesn't need to be. Maybe they should walk the DOM tree? Don't want to dig into that right now, since XUL insertion points can be reordered and all that... Not fun. MozReview-Commit-ID: L4lspkxKENr
3ce838735f7bca0f7edc9a29a51ba9f21232c734: No bug, Automated HPKP preload list update from host bld-linux64-spot-302 - a=hpkp-update
ffxbld - Sat, 06 Jan 2018 11:09:40 -0800 - rev 449862
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
No bug, Automated HPKP preload list update from host bld-linux64-spot-302 - a=hpkp-update
0ebe9bab9a67d580d9ed19abe4d0dd32f85c36fd: No bug, Automated HSTS preload list update from host bld-linux64-spot-302 - a=hsts-update
ffxbld - Sat, 06 Jan 2018 11:09:36 -0800 - rev 449861
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
No bug, Automated HSTS preload list update from host bld-linux64-spot-302 - a=hsts-update
ece8a96dfaa436c9bcf53105877b3923a264ae31: Merge inbound to mozilla-central r=merge a=merge
Andreea Pavel <apavel@mozilla.com> - Sat, 06 Jan 2018 11:50:13 +0200 - rev 449860
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Merge inbound to mozilla-central r=merge a=merge
0894fbaddc88e7f6b9cd6bb5f9cad6cf81254ecc: Bug 1427339 - Build GCC on a Debian-based docker image. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Fri, 29 Dec 2017 15:19:16 +0900 - rev 449859
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1427339 - Build GCC on a Debian-based docker image. r=gps
d20521b7b865edfde71eb6120ff595689f4d6e1b: Bug 1427339 - Make mozconfig.stdcxx work with both CentOS and Debian-built GCCs. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Fri, 29 Dec 2017 15:16:45 +0900 - rev 449858
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1427339 - Make mozconfig.stdcxx work with both CentOS and Debian-built GCCs. r=gps
f1a65f4c4d3d5274565cc4682d71fb80ab770c83: Bug 1427339 - Configure binutils and gcc --with-sysroot=/. r=gps
Mike Hommey <mh+mozilla@glandium.org> - Mon, 25 Dec 2017 10:32:57 +0900 - rev 449857
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1427339 - Configure binutils and gcc --with-sysroot=/. r=gps The system binutils and gcc are built with that option on Debian, but not on CentOS. That makes no practical difference, except for the fact that when building GCC, we use our own-built binutils (as per bug 1427316), but use the system GCC. And a GCC built with --with-sysroot=/ doesn't work with a binutils built without. However, a GCC built without --with-sysroot=/ works fine with a binutils built with it. So this change is compatible with building our GCC on both CentOS and Debian.
840a6e04bcea7d87e362adf14a37b7c17e20f043: Bug 1416879 - Part 6: Test cancellation of diverted client-intercepted streams. r=bkelly
Andrew Sutherland <asutherland@asutherland.org> - Thu, 04 Jan 2018 18:38:43 -0500 - rev 449856
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1416879 - Part 6: Test cancellation of diverted client-intercepted streams. r=bkelly This adds a test where we have a ServiceWorker return 2 different types of streams that Firefox recognizes as downloads which are handled by diversion of the channel to the parent. The diverted downloads are then cancelled and we verify that cancellation actually results in the underlying connections being closed and/or the ServiceWorker notified. Our 2 types of streams are: 1. A pass-through stream that is incrementally delivered through use of an .sjs file that delivers data using setInterval. 2. A SW-authored ReadableStream (which is not enabled by default, so we set a pref.) Determining when the .sjs's stream is canceled is accomplished by opening a second "monitor" connection that only completes when the streaming connection is closed. In all cases we differentiate between cancelation and timeouts firing.
994dc643a2ab62f03fef780a58971b476a4b6f4a: Bug 1416879 - Part 5: FetchStreamReader needs to cancel its reader when it encounters write errors. r=baku, f=bkelly
Andrew Sutherland <asutherland@asutherland.org> - Thu, 04 Jan 2018 18:09:32 -0500 - rev 449855
Push 8527 by Callek@gmail.com at Thu, 11 Jan 2018 21:05:50 +0000
Bug 1416879 - Part 5: FetchStreamReader needs to cancel its reader when it encounters write errors. r=baku, f=bkelly Currently, FetchStreamReader never signals to the JS stream code that the reader has been closed. This means that when a ServiceWorker passes a ReadableStream to respondWith and the HTTP Channel gets canceled, the JS code will keep generating the stream without ever realizing the data's not going anywhere. It's necessary to cancel the reader. Or do something like that, this seems to work!
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip