08bd8b4c28d6986a9acf0bd0c80111f37a13716c: Bug 1418078 - Remove nsIDOMHTMLInputElement. r?bz draft
Adrian Wielgosik <adrian.wielgosik@gmail.com> - Wed, 18 Apr 2018 22:35:32 +0200 - rev 787991
Push 107868 by bmo:adrian.wielgosik@gmail.com at Wed, 25 Apr 2018 20:14:11 +0000
Bug 1418078 - Remove nsIDOMHTMLInputElement. r?bz MozReview-Commit-ID: Gun4oxg1NJZ
be6e55347d37c65d9547949a5caf4b6d2ee8c7f4: Bug 1418078 - Convert XPIDL, C++ users of nsIDOMHTMLInputElement. r?bz draft
Adrian Wielgosik <adrian.wielgosik@gmail.com> - Wed, 18 Apr 2018 22:35:09 +0200 - rev 787990
Push 107868 by bmo:adrian.wielgosik@gmail.com at Wed, 25 Apr 2018 20:14:11 +0000
Bug 1418078 - Convert XPIDL, C++ users of nsIDOMHTMLInputElement. r?bz MozReview-Commit-ID: 9K5wL93cZ4j
7e802d015fc4f986f272957cebe09165709460ff: Bug 1418078 - Convert JS users of nsIDOMHTMLInputElement. r?bz draft
Adrian Wielgosik <adrian.wielgosik@gmail.com> - Wed, 18 Apr 2018 22:29:50 +0200 - rev 787989
Push 107868 by bmo:adrian.wielgosik@gmail.com at Wed, 25 Apr 2018 20:14:11 +0000
Bug 1418078 - Convert JS users of nsIDOMHTMLInputElement. r?bz MozReview-Commit-ID: 55aIiNHS0xs
17046f59a83bccb3c3ae7c016943d4b749269383: Bug 1455755 Move browserSettings.proxyConfig to proxy.settings, r?aswan, mstriemer draft
Shane Caraveo <scaraveo@mozilla.com> - Wed, 25 Apr 2018 14:54:05 -0500 - rev 787988
Push 107867 by mixedpuppy@gmail.com at Wed, 25 Apr 2018 19:55:22 +0000
Bug 1455755 Move browserSettings.proxyConfig to proxy.settings, r?aswan, mstriemer MozReview-Commit-ID: I2gMgr4D2HC
6a4eceb97b5e3ce9dbc766be8356f1a1ec836661: Bug 1453014 - Persist the recording settings to preferences; r?julienw draft
Greg Tatum <gtatum@mozilla.com> - Wed, 18 Apr 2018 11:15:59 -0500 - rev 787987
Push 107866 by gtatum@mozilla.com at Wed, 25 Apr 2018 19:37:27 +0000
Bug 1453014 - Persist the recording settings to preferences; r?julienw MozReview-Commit-ID: JvPGx2ZstiA
1d344e3b2fa290be1390f9445981289f0d824349: Bug 1449199 - Mitmproxy integration with raptor for OSX; r?jmaher draft
Rob Wood <rwood@mozilla.com> - Tue, 24 Apr 2018 09:25:47 -0400 - rev 787986
Push 107865 by rwood@mozilla.com at Wed, 25 Apr 2018 19:24:19 +0000
Bug 1449199 - Mitmproxy integration with raptor for OSX; r?jmaher MozReview-Commit-ID: 1Nnny3OynQw
170735bbe59f488b9c78f57ac11ae12fd2fa430e: Bug 1456487 - Update Firefox Account's first run UUID when re-connecting. r=rnewman draft
Nick Alexander <nalexander@mozilla.com> - Wed, 25 Apr 2018 12:17:05 -0700 - rev 787985
Push 107864 by nalexander@mozilla.com at Wed, 25 Apr 2018 19:17:46 +0000
Bug 1456487 - Update Firefox Account's first run UUID when re-connecting. r=rnewman The behaviour of Android Firefox Account instances recently changed in the face of system "Clear data" commands. To align more closely with common Apps like Dropbox and Whatsapp (which generally don't use Android Account instances), after a "Clear data" Firefox Account's are moved to the Separated state, requiring the user to re-connect them with a password challenge. To achieve this, newly created accounts include a first run UUID; after a "Clear data", the App is killed and restarted, Sync sees a different first run UUID, and the Account is moved to the Separated state. (I honestly don't know what happens if the Sync code never sees a different first run UUID, but that's for another day.) If the user then, in the same first run session, re-connects the Firefox Account... the Sync code will again see the different first run UUID and move the Account to the Separated state. This patch updates the first run UUID when the Account is re-connected, breaking that cycle. MozReview-Commit-ID: 9jcO9Ym54an
88abda604f7b3f8523bdb3dcc46b77932bf13af0: 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 787984
Push 107864 by nalexander@mozilla.com at Wed, 25 Apr 2018 19:17:46 +0000
Bug 1444546 - Post: Remove add_java_jar and support. r=Build MozReview-Commit-ID: J6E2ZOs9r3P
fe7b2f4f549d52f6554a7f09b90342eca6369038: 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 787983
Push 107864 by nalexander@mozilla.com at Wed, 25 Apr 2018 19:17:46 +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
c006c9519f8dbf8d9c75479d52704fac3c292d09: 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 787982
Push 107864 by nalexander@mozilla.com at Wed, 25 Apr 2018 19:17:46 +0000
Bug 1444546 - Part 4: Use GENERATED_FILES for Android JNI wrapper generation. r=jchen,Build MozReview-Commit-ID: 1IjoQdEMqr8
1e50dfe67ffbf0afa538dd3ba641b0383e275b08: 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 787981
Push 107864 by nalexander@mozilla.com at Wed, 25 Apr 2018 19:17:46 +0000
Bug 1444546 - Part 3: Use GENERATED_FILES for Android SDK bindings generation. r=jchen,Build MozReview-Commit-ID: 2blmzKTvpj3
711b61a8ffce98cd3e6074c84fecb05165695d5c: 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 787980
Push 107864 by nalexander@mozilla.com at Wed, 25 Apr 2018 19:17:46 +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
031212e7af8c4d0fd6e02f29840df6fb78d9f20e: 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 787979
Push 107864 by nalexander@mozilla.com at Wed, 25 Apr 2018 19:17:46 +0000
Bug 1444546 - Part 1: hg mv build/annotationProcessors mobile/android/annotations. r=jchen MozReview-Commit-ID: J3Wz83vWAVX
f9c6f60036025a55079edb653bfc0c8afcde77bc: Bug 1418602: Allow theming sidebars (Mac WIP) draft
Connor Masini <masinico@msu.edu> - Thu, 19 Apr 2018 19:14:39 -0400 - rev 787978
Push 107863 by bmo:masinico@msu.edu at Wed, 25 Apr 2018 19:14:44 +0000
Bug 1418602: Allow theming sidebars (Mac WIP) MozReview-Commit-ID: EkArCs4K8rQ
a45dd101a0cc63301b99d981e5cc122e416c7d42: Bug 1418602 - Allow Theming Sidebars (WIP) draft
Connor Masini <cjmasini@gmail.com> - Fri, 23 Feb 2018 12:17:56 -0500 - rev 787977
Push 107863 by bmo:masinico@msu.edu at Wed, 25 Apr 2018 19:14:44 +0000
Bug 1418602 - Allow Theming Sidebars (WIP) MozReview-Commit-ID: 8OcbExWxTkI
5f8a0768343e7ed9f00533e48e26df7c382e9a62: Bug 1408062 - Show hidden tabs that are playing audio r?dao draft
Mark Striemer <mstriemer@mozilla.com> - Fri, 20 Apr 2018 13:15:28 -0500 - rev 787976
Push 107862 by bmo:mstriemer@mozilla.com at Wed, 25 Apr 2018 19:08:51 +0000
Bug 1408062 - Show hidden tabs that are playing audio r?dao MozReview-Commit-ID: FHV3bmXbX9d
28025fc4b44b71b5a64828b1803eca262f921960: Bug 1456677: Make the blocklist service a JSM, with an XPCOM service stub. r?Gijs draft
Kris Maglione <maglione.k@gmail.com> - Tue, 24 Apr 2018 17:46:44 -0700 - rev 787975
Push 107861 by maglione.k@gmail.com at Wed, 25 Apr 2018 19:04:08 +0000
Bug 1456677: Make the blocklist service a JSM, with an XPCOM service stub. r?Gijs Aside from making things easier for JS callers, this also makes it harder to accidentally trigger an early load of the service, which can be expensive during startup. This also makes a slight change to nsPluginHost to initially preserve the previous blocklist state when a plugin is updated, to avoid the risk of the possible additioanl asynchrony unblocking a plugin that should stay blocked. MozReview-Commit-ID: 4EvIGJ1Ke0Z
5bf8cbf2a717f79df44985f22aa166902290b193: Bug 1456942, part 4 - Add a new test for |using|. r=Nika draft
Andrew McCreight <continuation@gmail.com> - Wed, 25 Apr 2018 11:25:24 -0700 - rev 787974
Push 107860 by bmo:continuation@gmail.com at Wed, 25 Apr 2018 18:49:33 +0000
Bug 1456942, part 4 - Add a new test for |using|. r=Nika Bug 1443954 added some new syntax to using, but I noticed that there was not very much existing test coverage, so I wrote a new test that covers all of the possible cases. MozReview-Commit-ID: JRgHCtXHDLZ
e815bf2c30fa5c56cd4f71b6f750bd4520286474: Bug 1456942, part 3 - Specify the error messages for a few tests. r=Nika draft
Andrew McCreight <continuation@gmail.com> - Wed, 25 Apr 2018 11:23:18 -0700 - rev 787973
Push 107860 by bmo:continuation@gmail.com at Wed, 25 Apr 2018 18:49:33 +0000
Bug 1456942, part 3 - Specify the error messages for a few tests. r=Nika Failing IPDL parser tests require that the error message is specified. MozReview-Commit-ID: IGNTVAb5r0Q
dba6afa77449d7df80e36ad9e567edc9dfa52b12: Bug 1456942, part 2 - Pass in a blank message-metadata file. r=Nika draft
Andrew McCreight <continuation@gmail.com> - Wed, 25 Apr 2018 11:14:41 -0700 - rev 787972
Push 107860 by bmo:continuation@gmail.com at Wed, 25 Apr 2018 18:49:33 +0000
Bug 1456942, part 2 - Pass in a blank message-metadata file. r=Nika The IPDL parser now expects a valid message-metadata to be passed in, even though we don't need it for parser tests. Fix this by creating and specifying a blank one. This fixes a regression from bug 1348591. MozReview-Commit-ID: HJ34mqBdUyP
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip