Bug 887923 - Switch Task.jsm from promise.js to Promise.jsm. r=mano
Merge m-c to fx-team
Bug 986458 - Disable browser_whitelist7.js on Win/OSX debug for perma-fails with chunked mochitest-bc.
Bug 608820 - Disable browser_bug567127.js on Win/OSX for frequent failures.
CLOSED TREE
Merge m-c to fx-team on a CLOSED TREE.
Bug 989549 - Call signOut() in FxAccountsClient.jsm from signOut() in FxAccounts.jsm. r=markh
Bug 992373 - Items in the panel jump up slightly when the customization transition finishes. r=Gijs, mikedeboer.
Bug 992747 - toolbar visibility setting doesn't work for non-customizable toolbars, r=jaws
Bug 981827 - Make Android and Desktop FxAccounts client use same key parameters. r=rnewman
Bug 990685: Dispatch document-element-inserted for XUL documents. r=bz
Bug 968419 - Store and submit a persistent health report identifier; r=rnewman, r=bsmedberg

Up to this point, Firefox Health Report has generated and submitted a
random UUID with each upload. Generated UUIDs were stored on the client.
During upload, the client asked the server to delete all old UUIDs.
Well-behaving clients thus left at most one record/ID on the server.

Unfortunately, clients in the wild have not been behaving properly. We
are seeing multiple documents on the server that appear to come from the
same client. Clients are uploading new records but failing to delete the
old ones. These old, undeleted "orphan" records are severely impacting
the ability to derive useful knowledge from FHR data because it is
difficult, resource intensive, and error prone to filter the records on
the server. This is undermining the ability for FHR data to be put to
good use.

This patch introduces a persistent client identifier. When the client is
initialized, it generates a random UUID. That UUID is persisted to the
profile and sent as part of every upload.

For privacy reasons, if a client opts out of data submission, the client
ID will be reset as soon as all remote data has been deleted.

We still issue and send upload IDs. They exist mostly for forensics
purposes so we may log client behavior and more accurately determine
what exactly misbehaving, orphan-producing clients are doing.

It is worth noting that this persistent client identifier will not solve
all problems of branching and orphaned records. For example, profile
copying will result in multiple clients sharing a client identifier. A
"client ID version" field has been added to facilitate an upgrade path
towards client IDs with different generation semantics.

--HG--
extra : rebase_source : b761daab39fb07b6ab8883819d68bf53462314a0
Bug 974893 - Remove EnterCompartment and keep the global with the value in Promise, r=bz
Bug 920573 - HTTP cache v2: Remove all cache files during shutdown when "Clear history when Firefox closes" + "Cache" setting is checked, r=honzab
Backed out changeset 7fa9564a2486 (bug 974893) for build failures
Bug 974893 - Remove EnterCompartment and keep the global with the value in Promise, r=bz
Bug 993410 - Improve coverage of nsTArray post barriers test r=terrence
Bug 992486 - Part 1: Add API to RotatedContentBuffer for drawing in multiple passes. r=roc
Bug 992486 - Part 2: Make ContentHostSingleBuffered able to handle updates that cross the rotation boundary. r=nical
Bug 992486 - Part 3: Clean up ClientThebesLayer a bit. r=roc
Bug 992486 - Part 4: Make ClientThebesLayer use multiple draws. r=roc