81bfd5cadb33ac9544a37de22c0980d22eb91ce7: Bug 1297156: Always use the content security policy from the triggering principal for favicon loads. draft
Dave Townsend <dtownsend@oxymoronical.com> - Wed, 11 Apr 2018 13:01:47 -0700 - rev 780715
Push 106099 by dtownsend@mozilla.com at Wed, 11 Apr 2018 20:47:47 +0000
Bug 1297156: Always use the content security policy from the triggering principal for favicon loads. Normally we use the CSP defined by the principal of the node loading something. In the case of a xul:image element loading a favicon we need to use the triggering principal. MozReview-Commit-ID: EYVMGWzw03k
1c5532d3395792985df7e057a4ca8ca45479cf22: Bug 1297156: Check favicon loads from the system principal against the content policy. draft
Dave Townsend <dtownsend@oxymoronical.com> - Wed, 11 Apr 2018 12:56:00 -0700 - rev 780714
Push 106099 by dtownsend@mozilla.com at Wed, 11 Apr 2018 20:47:47 +0000
Bug 1297156: Check favicon loads from the system principal against the content policy. When a system principled xul:image element attempts to load anything we currently bypass content policy checks. This change makes us continue to respect the content policy when loading favicons. MozReview-Commit-ID: B3CUXqtvsqG
490748389a401067742e9d307432004dd8334edf: Bug 1297156: Fix the naming of the triggering principal argument in nsContentUtils. draft
Dave Townsend <dtownsend@oxymoronical.com> - Wed, 11 Apr 2018 12:56:52 -0700 - rev 780713
Push 106099 by dtownsend@mozilla.com at Wed, 11 Apr 2018 20:47:47 +0000
Bug 1297156: Fix the naming of the triggering principal argument in nsContentUtils. nsContentUtils::LoadImage accepts an argument labelled as aLoadingPrincipal but we actually pass in triggering principals and it passes it along to a method that accepts a triggering principal so this renames the argument. MozReview-Commit-ID: LWrm7DVCJ3o
5b5240fde632696af7e009fbf2957e27a2f3735a: Bug 1297156: Include content security policy when structured cloning principals. draft
Dave Townsend <dtownsend@oxymoronical.com> - Wed, 11 Apr 2018 12:52:47 -0700 - rev 780712
Push 106099 by dtownsend@mozilla.com at Wed, 11 Apr 2018 20:47:47 +0000
Bug 1297156: Include content security policy when structured cloning principals. When JavaScript sends an nsIPrincipal to the main process we use the structured clone algorithm to serialize it. Currently this discards any content security policy on the principal. This change includes that information so the CSP directives can be seen in the main process. MozReview-Commit-ID: 6s48xtaawrf
38ef658d9b29545bb2aa5711c6711cffaf88a8da: Bug 1453480 - Update fluent to 0.6.4 and fluent-dom to 0.2.0. r?stas draft
Zibi Braniecki <zbraniecki@mozilla.com> - Wed, 11 Apr 2018 13:06:35 -0700 - rev 780711
Push 106098 by bmo:gandalf@aviary.pl at Wed, 11 Apr 2018 20:46:23 +0000
Bug 1453480 - Update fluent to 0.6.4 and fluent-dom to 0.2.0. r?stas MozReview-Commit-ID: La8uSw0sq4p
c3013b94961d32b38c447e57e4ff1289fe1a679b: Bug 1451033 - Extract Normandy ClientEnvironment into reusable module r?Gijs draft
Mathieu Leplatre <mathieu@mozilla.com> - Wed, 04 Apr 2018 12:02:09 +0200 - rev 780710
Push 106097 by mleplatre@mozilla.com at Wed, 11 Apr 2018 20:42:35 +0000
Bug 1451033 - Extract Normandy ClientEnvironment into reusable module r?Gijs MozReview-Commit-ID: G6Awri9tDyK
19de32c8912eac5c6f7447cefd951b3a418ed12d: Bug 1444546 - Post: Remove add_java_jar and support. r=Build draft
Nick Alexander <nalexander@mozilla.com> - Tue, 06 Mar 2018 14:48:20 -0800 - rev 780709
Push 106096 by nalexander@mozilla.com at Wed, 11 Apr 2018 20:41:15 +0000
Bug 1444546 - Post: Remove add_java_jar and support. r=Build MozReview-Commit-ID: J6E2ZOs9r3P
500c3ce72a4a8be2fafc06979438125a924a4f4d: Bug 1444546 - Part 4b: Make AnnotationProcessor avoid writing, like Python's FileAvoidWrite. r=jchen draft
Nick Alexander <nalexander@mozilla.com> - Mon, 26 Mar 2018 09:36:19 -0700 - rev 780708
Push 106096 by nalexander@mozilla.com at Wed, 11 Apr 2018 20:41:15 +0000
Bug 1444546 - Part 4b: Make AnnotationProcessor avoid writing, like Python's FileAvoidWrite. r=jchen This allows us to invoke AnnotationProcessor more than is strictly necessary and not trigger expensive native code compilations unless the native code has actually evolved. MozReview-Commit-ID: H1BIzJsdyIh
9c2986b9401330813a4081603c520392f0368413: Bug 1453463 - Update existing code to be more efficient by using the new map. r?botond draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 11 Apr 2018 15:51:29 -0400 - rev 780707
Push 106095 by kgupta@mozilla.com at Wed, 11 Apr 2018 20:40:33 +0000
Bug 1453463 - Update existing code to be more efficient by using the new map. r?botond This updates existing bits of code (notably one of the GetTargetAPZC methods) to use the new map for more efficient lookups. Places that used GetTargetNode with a presshell-ignoring comparator can now use GetTargetAPZC as well. MozReview-Commit-ID: GFjO6KigVop
6d7d082dabbfad57b67a5e5faf13d8c7864a5710: Bug 1453463 - Keep an APZC map on APZCTreeManager. r?botond draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 11 Apr 2018 15:51:29 -0400 - rev 780706
Push 106095 by kgupta@mozilla.com at Wed, 11 Apr 2018 20:40:33 +0000
Bug 1453463 - Keep an APZC map on APZCTreeManager. r?botond We are already building an almost-what-we-want map in the TreeBuildingState, so I modified to be exactly what we want, and then just move it to the APZCTreeManager once the tree build is done. MozReview-Commit-ID: 40RVwYv93wR
087e62d466c7a1383283733b58ee1e0719017a06: Bug 1453463 - Refactor to make unordered_maps with guid keys a little cleaner. r?botond draft
Kartikaya Gupta <kgupta@mozilla.com> - Wed, 11 Apr 2018 15:51:29 -0400 - rev 780705
Push 106095 by kgupta@mozilla.com at Wed, 11 Apr 2018 20:40:33 +0000
Bug 1453463 - Refactor to make unordered_maps with guid keys a little cleaner. r?botond This is mostly just moving the existing hash function and introducing additional helpers to create maps with presshell-ignoring guid keys. We can use this in one place trivially so I did that as well. MozReview-Commit-ID: G8nMS1PECT4
66958ba30d44efedf97be1c49ec3aff803befbe8: Bug 1453480 - Update fluent to 0.6.4 and fluent-dom to 0.2.0. r?stas draft
Zibi Braniecki <zbraniecki@mozilla.com> - Wed, 11 Apr 2018 13:06:35 -0700 - rev 780704
Push 106094 by bmo:gandalf@aviary.pl at Wed, 11 Apr 2018 20:35:29 +0000
Bug 1453480 - Update fluent to 0.6.4 and fluent-dom to 0.2.0. r?stas MozReview-Commit-ID: La8uSw0sq4p
acf4472120bb753b10901e8a1294038b2e09c013: Bug 1444546 - Post: Remove add_java_jar and support. r=Build draft
Nick Alexander <nalexander@mozilla.com> - Tue, 06 Mar 2018 14:48:20 -0800 - rev 780703
Push 106093 by nalexander@mozilla.com at Wed, 11 Apr 2018 20:33:31 +0000
Bug 1444546 - Post: Remove add_java_jar and support. r=Build MozReview-Commit-ID: J6E2ZOs9r3P
ecf2facd3faec9f4c2f59ddc98a36cc8539cbacb: Bug 1418464 - Part 4b: Make AnnotationProcessor avoid writing, like Python's FileAvoidWrite. r=jchen draft
Nick Alexander <nalexander@mozilla.com> - Mon, 26 Mar 2018 09:36:19 -0700 - rev 780702
Push 106093 by nalexander@mozilla.com at Wed, 11 Apr 2018 20:33:31 +0000
Bug 1418464 - Part 4b: Make AnnotationProcessor avoid writing, like Python's FileAvoidWrite. r=jchen This allows us to invoke AnnotationProcessor more than is strictly necessary and not trigger expensive native code compilations unless the native code has actually evolved. MozReview-Commit-ID: H1BIzJsdyIh
83ac621c887230b295aea5f500c081d6eb65ba46: Bug 1444546 - Part 4: Use GENERATED_FILES for Android JNI wrapper generation. r=jchen,Build draft
Nick Alexander <nalexander@mozilla.com> - Tue, 06 Mar 2018 20:09:37 -0800 - rev 780701
Push 106093 by nalexander@mozilla.com at Wed, 11 Apr 2018 20:33:31 +0000
Bug 1444546 - Part 4: Use GENERATED_FILES for Android JNI wrapper generation. r=jchen,Build MozReview-Commit-ID: 1IjoQdEMqr8
ea5315a0512e03349958f96cb85cf5d540b891c3: Bug 1444546 - Part 3: Use GENERATED_FILES for Android SDK bindings generation. r=jchen,Build draft
Nick Alexander <nalexander@mozilla.com> - Tue, 06 Mar 2018 19:19:48 -0800 - rev 780700
Push 106093 by nalexander@mozilla.com at Wed, 11 Apr 2018 20:33:31 +0000
Bug 1444546 - Part 3: Use GENERATED_FILES for Android SDK bindings generation. r=jchen,Build MozReview-Commit-ID: 2blmzKTvpj3
953fd1e68e107b64f982e369deea9d6ed4654b89: Bug 1444546 - Part 2: Build annotationProcessors with Gradle. r=jchen draft
Nick Alexander <nalexander@mozilla.com> - Thu, 22 Feb 2018 16:11:14 -0800 - rev 780699
Push 106093 by nalexander@mozilla.com at Wed, 11 Apr 2018 20:33:31 +0000
Bug 1444546 - Part 2: Build annotationProcessors with Gradle. r=jchen We want annotationProcessors to be compiled and archived into a JAR at build time, ready to generate JNI wrappers. (That is, until we turn the whole thing into a real annotation processor.) But even if we do use a real annotation processor, we still need to generate SDK bindings, which is less clearly expressed as an annotation processor. (It's more of a build step.) Gradle provides a huge number of ways to organize build logic to achieve this: see https://docs.gradle.org/current/userguide/organizing_build_logic.html. Unfortunately, the best such way -- putting the code into $topsrcdir/buildSrc -- has key disadvantages: 1) it pollutes the top-level $topsrcdir, and there's no way to change the location of buildSrc (https://github.com/gradle/gradle/issues/2472); 2) it's complicated to have a dependent project (mobile/android/annotations) expose its code via a buildSrc project; 3) using buildSrc at all appears to conflict with the Android-Gradle plugin version that we are using. Therefore, this commit does something much simpler: it adds a Java-only project and uses the resulting Gradle "Jar" task and archive output as input to the existing Gradle "generate JNI wrappers" task. MozReview-Commit-ID: 2OyYLPneE1M
95e5262f42c16444183eb1e9ce4893c9ff808364: Bug 1444546 - Part 1: hg mv build/annotationProcessors mobile/android/annotations. r=jchen draft
Nick Alexander <nalexander@mozilla.com> - Thu, 22 Feb 2018 13:51:15 -0800 - rev 780698
Push 106093 by nalexander@mozilla.com at Wed, 11 Apr 2018 20:33:31 +0000
Bug 1444546 - Part 1: hg mv build/annotationProcessors mobile/android/annotations. r=jchen MozReview-Commit-ID: J3Wz83vWAVX
0859c70cdf72eb604775473dc7dfa12a7319e8c3: Bug 1449624 - Make single-locale repacks use correct locale. r=mshal draft
Nick Alexander <nalexander@mozilla.com> - Tue, 20 Mar 2018 17:00:38 -0700 - rev 780697
Push 106093 by nalexander@mozilla.com at Wed, 11 Apr 2018 20:33:31 +0000
Bug 1449624 - Make single-locale repacks use correct locale. r=mshal This was an oversight in the landing of Bug 1443208. We need to set AB_CD explicitly for the invoked target, and, due to the way that l10n.mk is written, we also need to set the additional internal variables IS_LANGUAGE_REPACK and REAL_LOCALE_MERGEDIR. MozReview-Commit-ID: 29lQXYiOf6a
6af496dc2d66c9b2567d3d2fbed46c608a950435: Bug 1412375 - bump fuzziness slightly. r?kats draft
Alexis Beingessner <a.beingessner@gmail.com> - Wed, 11 Apr 2018 16:30:08 -0400 - rev 780696
Push 106092 by bmo:a.beingessner@gmail.com at Wed, 11 Apr 2018 20:30:26 +0000
Bug 1412375 - bump fuzziness slightly. r?kats MozReview-Commit-ID: JuB96mZa72f
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip