Bug 1418078 - Remove nsIDOMHTMLInputElement. r?bz MozReview-Commit-ID: Gun4oxg1NJZ

Bug 1418078 - Convert XPIDL, C++ users of nsIDOMHTMLInputElement. r?bz MozReview-Commit-ID: 9K5wL93cZ4j

Bug 1418078 - Convert JS users of nsIDOMHTMLInputElement. r?bz MozReview-Commit-ID: 55aIiNHS0xs

Bug 1455755 Move browserSettings.proxyConfig to proxy.settings, r?aswan, mstriemer MozReview-Commit-ID: I2gMgr4D2HC

Bug 1453014 - Persist the recording settings to preferences; r?julienw MozReview-Commit-ID: JvPGx2ZstiA

Bug 1449199 - Mitmproxy integration with raptor for OSX; r?jmaher MozReview-Commit-ID: 1Nnny3OynQw

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

Bug 1444546 - Post: Remove add_java_jar and support. r=Build MozReview-Commit-ID: J6E2ZOs9r3P

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

Bug 1444546 - Part 4: Use GENERATED_FILES for Android JNI wrapper generation. r=jchen,Build MozReview-Commit-ID: 1IjoQdEMqr8

Bug 1444546 - Part 3: Use GENERATED_FILES for Android SDK bindings generation. r=jchen,Build MozReview-Commit-ID: 2blmzKTvpj3

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

Bug 1444546 - Part 1: hg mv build/annotationProcessors mobile/android/annotations. r=jchen MozReview-Commit-ID: J3Wz83vWAVX

Bug 1418602: Allow theming sidebars (Mac WIP) MozReview-Commit-ID: EkArCs4K8rQ

Bug 1418602 - Allow Theming Sidebars (WIP) MozReview-Commit-ID: 8OcbExWxTkI

Bug 1408062 - Show hidden tabs that are playing audio r?dao MozReview-Commit-ID: FHV3bmXbX9d

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

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

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

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