Bug 1214058: Part 2 - Run add-on update tests against comparable JSON and RDF manifests. r=Mossop I tried to keep the changes to existing tests as minimal as possible. There were a few exceptions, though: * test_update_ignorecompat.js was completely broken. I couldn't figure out why it was suddenly failing after I changed it to use `add_test`, and it turned out that it had been failing all along, but in a way that the harness didn't pick up. * I changed most of the `do_throw` in update callbacks to `ok(false` because it took me about an hour to figure out where the test was failing when I hit one of them. * I made some changes to sync `test_update.js` and `test_update_ignorecompat.js` where one appeared to have been changed without updating the other. * I made `promiseFindAddonUpdates` a bit more generic, because I was planning to convert most of `test_update.js` to use it, rather than nested callbacks. I changed my mind a quarter of the way through, but decided to keep the changes, since they'll probably be useful elsewhere.

Bug 1214058: Part 1 - Add a simplified JSON-based add-on update protocol. r=Mossop

Bug 1220682 - Clear exceptions on single-arg init. r=bz

Bug 1220765 - 43.0b1 build1 fennec repacks failing to upload and submit to taskcluster, DONTBUILD r=rail, a=releases

Bug 1219310 - part 2 - keep track of how much pref file we have read; r=njn Looking at a preference file read with strace typically looks like: open("...", O_RDONLY) = X ... read(X, "...", SIZE) = SIZE read(X, "...", SIZE) = 0 ... There's no reason to call Read() and make another syscall to determine there's no data left for reading. We can keep track of how much we've read at minimal cost and thus determine for ourselves when we are done.

Bug 1219310 - part 1 - ask the prefs file for its size directly; r=njn Calling nsIInputStream::Available on nsIFileInputStreams is relatively expensive, as it requires three system calls: one to determine the current file position, one to seek to the end file position, and one to rewind to the previous file position. We can do better by asking the file for its size directly, prior to opening the stream. This only requires one system call, stat, and is thus superior--at least in considering the number of system calls.

No bug - [css-grid] Add a small fuzz factor to make this reftest pass on Windows. r=me

Bug 1211260 - [css-grid] Follow-up: address a code readability nit that I missed. r=dholbert

Bug 1220693 - Lazily trigger ICU default-time-zone recreation only at the instant where the new default time zone is going to be used, rather than every time the time zone might have changed, as apparently ICU's default-time-zone computation is a lot of work. r=till

Bug 1220693 - Make mozilla::Atomic<enum class> work even on compilers that don't have <atomic>. r=froydnj

Bug 1000592 - Enable CSS Grid by default in non-release channels. r=dholbert

Bug 1176775 part 2 - [css-grid] Testcases for 'auto' min-sizing and intrinsic 'min-width|height'.

Bug 1176775 part 1 - [css-grid] Implement "Implied Minimum Size of Grid Items" (special min-width/height:auto behavior). r=dholbert

Bug 1163435 part 2 - tests.

Bug 1163435 part 1 - [css-grid][css-flexbox] Propagate an explicit CB width/height to the reflow state to resolve percentage lengths for grid items properly. Resolve percent against the size in the same axis for abs.pos. children too. r=dholbert Grid items are supposed to use the size of their 'grid area', not their grid container, as their containing block.

Bug 1215957 - Reftests.

Bug 1215957 - Start at the end of the explicit grid also when matching plain negative number lines. r=dholbert

Bug 1215182 - Reftests.

Bug 1215182 - [css-grid] Make our "Implicit Named Areas" detection match the spec. r=dholbert

Bug 1211260 - Implement the new Grid Placement Conflict Handling: "If the placement for a grid item contains two lines, and the start line is further end-ward than the end line, swap the two lines." r=dholbert https://drafts.csswg.org/css-grid/#grid-placement-errors