mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
610 527 коммитов 615 Ветки 98 Теги 5,7 GiB
Граф коммитов

82 Коммитов

Автор SHA1 Сообщение Дата
Kris Maglione fcedebb912 Bug 1471102: Move more code out of ExtensionUtils.jsm. r=aswan 
MozReview-Commit-ID: Fqlv5BRuuW8

--HG--
extra : rebase_source : 348f037abd9cecfa080183bc365e5f005eac1bd6
extra : amend_source : 05dbfd12f553fc3f2a93374402e34d271e26d767
 2018-06-25 19:30:21 -07:00
Mark Hammond cc7fecadc3 Bug 1457071 - allow all extension-storage data to be deleted from the profile. r=glasserc 
MozReview-Commit-ID: Dnb2kdcz1CH

--HG--
extra : rebase_source : be65881f76e0fb004d718cbb6f841c44beeebe26
 2018-04-26 17:53:56 +10:00
Kris Maglione 202290f6bb Bug 1451215: Run codespell on code. r=aswan 
MozReview-Commit-ID: HIilZTKcQUY

--HG--
extra : rebase_source : 48ba4b4ac06f6d146ce81050da6c60b6f7c3fbfc
extra : amend_source : cba3e4c100a57889851eaaffff3696d1285655ea
 2018-04-03 22:22:07 -07:00
Florian Quèze 682b1ec3b2 Bug 1440284 - change this.EXPORTED_SYMBOLS back to var EXPORTED_SYMBOLS in JS modules, r=mccr8. 2018-02-23 20:50:01 +01:00
Andrew McCreight 5dec0e0beb Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian 
This patch was autogenerated by my decomponents.py

It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.

It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <![CDATA[, """ or '''. The first two
cover comments, the third one covers JS, the fourth covers JS embedded
in XUL, and the final two cover JS embedded in Python. This also
applies if the removed line was the first line of the file.

It covers the pattern matching cases like "var {classes: Cc,
interfaces: Ci, utils: Cu, results: Cr} = Components;". It'll remove
the entire thing if they are all either Ci, Cr, Cc or Cu, or it will
remove the appropriate ones and leave the residue behind. If there's
only one behind, then it will turn it into a normal, non-pattern
matching variable definition. (For instance, "const { classes: Cc,
Constructor: CC, interfaces: Ci, utils: Cu } = Components" becomes
"const CC = Components.Constructor".)

MozReview-Commit-ID: DeSHcClQ7cG

--HG--
extra : rebase_source : d9c41878036c1ef7766ef5e91a7005025bc1d72b
 2018-02-06 09:36:57 -08:00
Kris Maglione 918ed6c474 Bug 1431533: Part 5a - Auto-rewrite code to use ChromeUtils import methods. r=florian 
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm

MozReview-Commit-ID: 1Nc3XDu0wGl

--HG--
extra : source : 12fc4dee861c812fd2bd032c63ef17af61800c70
extra : intermediate-source : 34c999fa006bffe8705cf50c54708aa21a962e62
extra : histedit_source : b2be2c5e5d226e6c347312456a6ae339c1e634b0
 2018-01-29 15:20:18 -08:00
Cosmin Sabou 9a65a40178 Backed out 3 changesets (bug 1431533) for Android mochitest failures on testEventDispatcher on a CLOSED TREE 
Backed out changeset a1eca62826a1 (bug 1431533)
Backed out changeset 34c999fa006b (bug 1431533)
Backed out changeset e2674287e57f (bug 1431533)
 2018-01-30 07:17:48 +02:00
Kris Maglione 6476f95b13 Bug 1431533: Part 5a - Auto-rewrite code to use ChromeUtils import methods. r=florian 
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm

MozReview-Commit-ID: 1Nc3XDu0wGl

--HG--
extra : source : 12fc4dee861c812fd2bd032c63ef17af61800c70
 2018-01-29 15:20:18 -08:00
Brindusan Cristian af8879d1eb Backed out 2 changesets (bug 1431533) for ESlint failures on a CLOSED TREE 
Backed out changeset 6e56f4c8843e (bug 1431533)
Backed out changeset 12fc4dee861c (bug 1431533)
 2018-01-30 02:32:43 +02:00
Kris Maglione c276bb9375 Bug 1431533: Part 5a - Auto-rewrite code to use ChromeUtils import methods. r=florian 
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm

MozReview-Commit-ID: 1Nc3XDu0wGl

--HG--
extra : rebase_source : c004a023389f1f6bf3d2f3efe93c13d423b23ccd
 2018-01-29 15:20:18 -08:00
Edouard Oger d149a0176b Bug 1426306 - Store only derived keys instead of storing kB/kA. r=glasserc,markh,rfkelly 
MozReview-Commit-ID: Hgv5hxSH4qX

--HG--
extra : rebase_source : fa6d45480a2078e841c72b2c8c92541811633737
 2018-01-05 15:56:00 -05:00
Kris Maglione 4a4c4fdfd4 Bug 1421459: Update to ESLint 4 "indent" rule. r=aswan 
MozReview-Commit-ID: LxLDWlsIlSk

--HG--
extra : rebase_source : 5762bdf08ff6c09c1b29f87366bddb552e4c74b2
extra : amend_source : 922a0c03722bd5a81daace7f0289ec3228191cfb
 2017-11-28 14:13:59 -08:00
Ethan Glasser-Camp d6e50cf832 Bug 1416077 - Disable retries on storage.sync requests r=markh 
--HG--
extra : rebase_source : 0c5c70626d8450dcb818ab964bdd28121d1abe18
 2017-11-10 13:06:10 -05:00
Kris Maglione 541e9a6989 Remove unused imports. r=trivial (no bug) 
MozReview-Commit-ID: EEVSPkAgORY

--HG--
extra : rebase_source : 8a3da61bdf0f65c518e6cea3c6f5cacf42c6d24d
 2017-11-09 16:39:57 -08:00
Thom Chiovoloni f1e51079aa Bug 1414997 - Ensure extension storage sync initializes Kinto exactly once r=glasserc 
MozReview-Commit-ID: 3vYEp4eqpJO

--HG--
extra : rebase_source : 51ebc92697d37722691360fc027d8f367d4c8ab4
 2017-11-06 19:53:49 -05:00
Thom Chiovoloni 76a3991796 Bug 1400467 - Make WeaveCrypto use promises instead of spinning event loops r=eoger,markh 
MozReview-Commit-ID: 64dewKKaAOJ

--HG--
extra : rebase_source : e8d48e05ad8dac214358b0a9979b011a65ed07a8
 2017-09-15 19:21:31 -07:00
Ethan Glasser-Camp 4f6356f118 Bug 1395215: remove asynchrony from addListener, r=kmag 
MozReview-Commit-ID: HzjfFiIR7hE

--HG--
extra : rebase_source : c41f720165e11dddc6cf9e4b11d39e2dbbfcd3ed
 2017-09-05 16:11:39 -04:00
Mathieu Leplatre b4905330e7 Bug 1377533 - Remove scattered references to Kinto and Sqlite in blocklist clients r=glasserc,mgoodwin 
MozReview-Commit-ID: FExozSDHgNN

--HG--
extra : rebase_source : 892c1c5825ac20243ce74118d4df437ec99cfe2c
 2017-06-30 12:07:28 -07:00
Wes Kocher 21b928e4f3 Backed out changeset e6189da47385 (bug 1377533) for frequent xpcshell failures in test_ext_storage_sync_crypto.js a=backout 
MozReview-Commit-ID: BLXHot0UsDU
 2017-08-31 10:27:03 -07:00
Mathieu Leplatre a25448ced8 Bug 1377533 - Remove scattered references to Kinto and Sqlite in blocklist clients r=glasserc,mgoodwin 
MozReview-Commit-ID: FExozSDHgNN

--HG--
extra : rebase_source : de71abafa6e32970f61914fa00115b677b2c9c16
 2017-06-30 12:07:28 -07:00
Nicolas Ouellet-Payeur 5a0bb50ea8 Bug 1392148 - Remove aliases to CommonUtils in util.js r=markh 
MozReview-Commit-ID: 1fv6AN0TMNW

--HG--
extra : rebase_source : 083c73e50bfdb2dd121aa483e5aa53ae0e35768d
 2017-08-24 22:41:44 -07:00
Sebastian Hengst 5b02cef919 Backed out changeset 0f63d6c1f3c6 (bug 1377533) for frequently failing xpcshell's toolkit/components/extensions/test/xpcshell/test_ext_api_permissions.js. r=backout 2017-08-24 18:34:43 +02:00
Mathieu Leplatre 5361ecfb8d Bug 1377533 - Remove scattered references to Kinto and Sqlite in blocklist clients r=glasserc,mgoodwin 
MozReview-Commit-ID: FExozSDHgNN

--HG--
extra : rebase_source : 3c02d9d13ed9d417171305bf7aa3523b69b8a3fb
 2017-06-30 12:07:28 -07:00
Kris Maglione 0ecfcbc93e Bug 1388215: Part 3 - Use JIT-friendly defineLazy*Getters methods when defining many lazy imports. r=florian 
MozReview-Commit-ID: APoFwUhDFdj

--HG--
extra : rebase_source : 15761873b91efaf1d338b6361bf7168ab4348e0d
 2017-08-09 13:03:36 -07:00
Kris Maglione f87ef7bd44 Remove unused lazy imports. r=trivial (no bug) 
MozReview-Commit-ID: rqUFJw7Wsb

--HG--
extra : rebase_source : cdda5d87fe33bdb9dacc1846fd67f3cb4154f230
 2017-08-02 21:09:38 -07:00
Mark Banner 35f3666937 Bug 1380009 - Enable the ESLint no-return-await call to avoid unnecessary intermediate promise creation. r=mossop 
MozReview-Commit-ID: EnhSBHMjurr

--HG--
extra : rebase_source : 74ba4c10e369067629af95bf705a9acd0df1089b
 2017-07-11 22:49:55 +01:00
Edouard Oger 9d1dc7c4a7 Bug 1368560 part 2 - Move Svc.Crypto to Weave.Crypto. r=markh 
MozReview-Commit-ID: 74IFsVjZSgz

--HG--
extra : rebase_source : 00f77b7a24a509d5e9fabb8ee7793a59b38f639f
 2017-05-29 13:24:01 -04:00
Ethan Glasser-Camp f9f6f160da Bug 1364135: Clean up detection/handling of deleted keyrings, r=kmag,MattN 
MozReview-Commit-ID: CoOwUazDRSL

--HG--
extra : rebase_source : d027c47f1b5740fa9916420b5dafdac935264ff8
 2017-05-11 13:15:20 -04:00
Ethan Glasser-Camp 72d89acea8 Bug 1358120: correctly handle failed authorizations, r=kmag 
This code seems to have never worked correctly. This code was based on
an error style that is thrown from one part of kinto-http.js but then
immediately rethrown using a different format. On top of that, the
code as written tries to parse JSON out of the response body and use
that. Instead, let's use the response status code, since that feels a
little more robust.

MozReview-Commit-ID: B5MG5tpduCd

--HG--
extra : rebase_source : 9f4ba94ef215297db6ba3b126852984a9a7878fe
 2017-05-15 16:46:30 -04:00
Ethan Glasser-Camp ceed266119 Bug 1350088: Recover when we hit "server was flushed", r=kmag 
This is another edge case that seems to be linked to the server-side
data loss bug in Kinto. It seems like you can get into a "server was
flushed" case if one device hadn't seen the most recent keyring before
another client caused the server to be wiped. We don't expect this to
happen in the future, but it affects some number of our users who were
already using storage.sync, so build a recovery pathway for them.

MozReview-Commit-ID: K0BJNQgN6Z4

--HG--
extra : rebase_source : 5a8707bc1edc1f30306a301d3c9f7b10a1f2fb76
 2017-05-19 16:43:32 -04:00
Mark Banner d1dfdb8a14 Bug 1367232 - Clean up various ESLint global definitions in toolkit/. r=mossop 
MozReview-Commit-ID: Hhm4YBansg1

--HG--
extra : rebase_source : 3cb49159fa3f5dae12e4eb21f22e747850fdf184
 2017-05-19 09:22:48 +01:00
Kris Maglione e272c4c239 Bug 1365005: Cleanup async code after Task.jsm migration. r=aswan 
MozReview-Commit-ID: FNKSsBqq6Kf

--HG--
extra : rebase_source : f6e5056fc2de0b13b4b77e27fe88c2d4063b1445
extra : amend_source : 42473dedc3280e225eb243ce5a87d552ba5f9ee2
 2017-05-15 12:07:06 -07:00
Florian Quèze 5e3539e504 Bug 1353542 - massive script-generated patch converting Task.async and Task.spawn calls, and generators clearly identifiable as tasks, rs=Mossop. 2017-05-12 14:42:39 +02:00
Florian Quèze 2e2f358aa9 Bug 1353542 - pre-script hand-written cleanup patch, r=Mossop. 2017-05-12 14:41:20 +02:00
Ethan Glasser-Camp 4f4ee59962 Bug 1359879: add logging and robustness to key syncing, r=kmag 
It seems like the server-side keyring is getting deleted somehow. This
causes syncing of the keyring to fail. We haven't completely
fixed the root problem yet, but this adds logging to try to flag
down the dangerous operation of deleting a bucket to make sure we
aren't doing that by accident. We also try to recover from the
server-keyring-was-deleted situation by wiping all storage.sync data,
the same as if we found a keyring that we couldn't decrypt.

MozReview-Commit-ID: JMB0IxApbGq

--HG--
extra : rebase_source : 54982a374aa5c7d7e60e8175b99734c672b91799
 2017-05-01 14:22:51 -04:00
Ethan Glasser-Camp 232842cc9f Bug 1351678: Handle resolved conflicts correctly, r=kmag 
The elements of the SyncResultObject#conflicts field are {local,
remote} pairs.  However, the elements of the SyncResultObject#resolved
field are just the resolutions, and trying to access "local" and
"remote" fields of those resolutions causes a crash. Add a test that
demonstrates the error, and then fix it.

MozReview-Commit-ID: LF0NBw5VKBC

--HG--
extra : rebase_source : 7711111d35cfe962f57c7d08d74bad2e37090b7c
 2017-04-20 13:44:46 -04:00
Kris Maglione 3d8483182d Bug 1333477: Part 2 - Remove "browser" environment from ESLint settings. r=aswan 
MozReview-Commit-ID: LCxI6JVp7Xo

--HG--
extra : rebase_source : d0fc6519f3b6872f76a9df533f3eddf1352c2559
extra : histedit_source : 790c0f2322f2b3a3d35b8bf6d7b3f7b705f33fcd%2Cdae80b78b03f25f165f1fc575667df394a43b572
 2017-03-12 14:16:13 -07:00
Ethan Glasser-Camp bf7f47db2b Bug 1328974: Record metrics for chrome.storage.sync usage, r=bsmedberg,kmag 
MozReview-Commit-ID: 7c2CHLuXxS6

--HG--
extra : rebase_source : f56bf58bfdf2f3ecb7fb5dbe8ee22d3a3569ae34
extra : source : c48083c4b41537af44a38722e64d8e10987ba199
 2017-01-17 13:25:02 -05:00
Ethan Glasser-Camp b228d5b47d Bug 1321570 - use dependency injection for fxAccounts, r=kmag 
Get rid of the ugly hack where test code monkeypatches a singleton to
convince the rest of the ExtensionStorageSync code that a fake user is
logged in. Instead, take a handle to the fxAccounts service at
construction time. Test code can provide any kind of fxAccounts it
wants, including one that has a hard-coded user.

This provokes a bunch of changes:

- ExtensionStorageSync is now no longer a singleton, but a class. You
  have to instantiate it in order to do anything with it. A global
  instance extensionStorageSync is provided for use by Sync code as
  well as WebExtension code.

- CryptoCollection is now also a class, and each ExtensionStorageSync
  instance has its own CryptoCollection. This dependency should maybe
  also be injected, but for the time being it doesn't provide us any
  value to do so.

- Converting singletons with asynchronous methods to classes is a pain
  in the neck. We convert async method foo from `foo:
  Task.async(....)` to `async foo() { .... }`. While we're here,
  convert KeyRingEncryptionRemoteTransformer#decode to async/await to
  eliminate a need for `let self = this`.

- Update Sync code and WebExtension code to use extensionStorageSync.

- There's a cyclic dependency where CryptoCollection#sync depends on
  ExtensionStorageSync#_syncCollection which depends on
  CryptoCollection#getKeyRing. As a short-term hack, we now require an
  ExtensionStorageSync argument to CryptoCollection#sync.

- KeyRingEncryptionRemoteTransformer now takes a handle to fxAccounts
  on construction time as well. Because this is the only
  EncryptionRemoteTransformer subclass that accesses fxAccounts, we
  can get rid of the hack where the tests monkeypatch something in the
  EncryptionRemoteTransformer prototype.

- CollectionKeyEncryptionRemoteTransformer now takes a handle to a
  CryptoCollection, rather than relying on a global one.

- A bunch of methods that previously assumed access to fxAccounts now
  check if fxAccounts is present (i.e. if we're on Android). Strictly
  speaking, this isn't required by this change, but it helps make
  certain kinds of failure a little easier to diagnose.

- Update tests, including extracting a domain-specific helper method
  to hide the use of CollectionKeyEncryptionRemoteTransformer. We now
  no longer monkeypatch in our mock fxaService, but pass it to the
  test so that it can do whatever it wants with it. We also provide an
  ExtensionStorageSync instance for convenience. Access to the global
  cryptoCollection is now done through an ExtensionStorageSync
  instance.

To summarize, we've gone from a situation where a bunch of singletons
had implicit dependencies on other singletons in a shared global
namespace, to a situation where dependencies are provided explicitly
using method/constructor arguments. This highlights some of the
dependencies present:

- ExtensionStorageSync depends on CryptoCollection and fxAccounts if
  it needs to sync

- Every collection created via openCollection needs a handle to
  CryptoCollection so it can correctly create its remote transformers

- CryptoCollection needs a handle to fxAccounts so it can create its
  own remote transformer for its special collection

Most of this is only possible, or at least much easier, because we no
longer try to juggle Sqlite connections but just keep one around
forever.

However, please note:

- CryptoCollection needs a handle to ExtensionStorageSync to actually
  perform syncing logic because that's where we foolishly put the
  logic to make requests

- There's still a backing Sqlite store which is shared by everything

- There's still a singleton tracking contexts that opened extensions
  which we manage to try to clean contexts up correctly

MozReview-Commit-ID: DGIzyRTdYZ1

--HG--
extra : rebase_source : 305a98b8e1ece3ae7a5e8a2fdb5c58d8e7c496d9
 2017-01-10 16:44:01 -05:00
Ethan Glasser-Camp 4f7afb05a6 Bug 1321570 - Move ExtensionStorageSync crypto out of services/sync, r=kmag 
Since services/sync doesn't ship on Android, this meant
conditionally-defining some variables such as `cryptoCollection` and
`CollectionKeyEncryptionRemoteTransformer` depending on whether or not
we were on Android. However, none of these definitions really rely on
functionality that isn't present on Android (although you can't really
use them yet either). Move the dependency together with the dependant
code so we can simplify a bit. This lets us remove conditional uses of
`cryptoCollection` and `CollectionKeyEncryptionRemoteTransformer`.

Because the WebExtensions source directory has more stringent eslint
rules, we end up reformatting and commenting a bit in addition to
moving.

MozReview-Commit-ID: 2ddDeymYFNi

--HG--
rename : services/sync/tests/unit/test_extension_storage_crypto.js => toolkit/components/extensions/test/xpcshell/test_ext_storage_sync_crypto.js
extra : rebase_source : f84c0810b6a447f2104f96c9dc9d6139743f269c
 2017-02-13 15:06:02 -05:00
Ethan Glasser-Camp 3a3e213b7d Bug 1333810: Hash record IDs during encryption, r=kmag,rnewman 
This does a sha256 of record IDs, the same way we do for collection
IDs, during encryption.

The way we compute the new ID (using an overridden method) is a little
bit of a hack, but we use the new ID as part of the HMAC. This also
invalidates a previous assumption, which is that we kept record IDs
the same during decryption.

MozReview-Commit-ID: Gbzlo9OE1he

--HG--
extra : rebase_source : 3a303cce50e60ecf0cd709da4ebef5ff98bff314
extra : intermediate-source : 033163eeac84466553d4f9636093c3b824d7cf2b
extra : source : c5c115baff4a729b064e74e87821f7ee3b9d3edb
 2017-01-31 13:09:38 -05:00
Ethan Glasser-Camp adede591b2 Bug 1333810: Redo hashing of collection ID, r=kmag,rnewman 
This ties the collection ID used for a given extension to the "salts"
record. This blocks an attack where, given the user's ID, an attacker
could just hash all the extension IDs on addons.mozilla.org to
generate possible hashed collection IDs.

MozReview-Commit-ID: OABsOOMn2F

--HG--
extra : rebase_source : 7c43968b9b7d695c98f00f99d7349d39eb1dc514
extra : source : ed19b98e6b8beb3009cee342bb97eb5684c02af6
 2017-01-30 19:07:02 -05:00
Ethan Glasser-Camp b2aa4480f7 Bug 1333810: Add salts to the keys record, r=kmag,rnewman 
Because these need to be encrypted with kB like the keyring does, and
wiped at the same time as the keyring does, just smush them into the
keyring. Rename `ensureKeysFor` to `ensureCanSync`, but don't update
it to return the salts -- for now, we don't need that.

MozReview-Commit-ID: DOJxdx5ugKl

--HG--
extra : rebase_source : 02fdae5d434232395d91a626213d91d4bdff40bc
 2017-01-30 16:03:59 -05:00
Ethan Glasser-Camp 1549e45546 Bug 1331467: Enable chrome.storage.sync by default, r=kmag 
MozReview-Commit-ID: 76wXwJGobIt

--HG--
extra : rebase_source : 8cc08b6d41c3b3e35cb92627e497a3925ef50376
 2017-01-18 11:44:17 -05:00
Ryan VanderMeulen cf7b3c6971 Backed out changeset 442d75009799 (bug 1331467) for test_ext_storage_content.html failures. 2017-01-20 18:33:47 -05:00
Ethan Glasser-Camp 4b188f8d49 Bug 1331467: Enable chrome.storage.sync by default, r=kmag 
MozReview-Commit-ID: 76wXwJGobIt

--HG--
extra : rebase_source : c4e29d8beabd7d4d6cb0b53adf26e1a30c320b18
 2017-01-18 11:44:17 -05:00
Mark Banner 582fcb8090 Bug 1329614 - [eslint] Catch more cases of importing globals from 'var foo = Cu.import('...');'. r=jaws 
MozReview-Commit-ID: 5NKHHb70YA6

--HG--
extra : rebase_source : 4551e56f56065349fb9ddc8d90e67f9dc84c1701
 2017-01-09 10:12:26 +00:00
Ethan Glasser-Camp e1c5d29c37 Bug 1319742 - UUIDs should be strings, not objects, r=markh 
`generateUUID()` returns an `nsID`, which is not exactly the same as a
UUID. `nsID`s can be converted to strings using `toString()`, but if
you use `JSON.stringify()`, they become `{}`. Object comparison in JS
performs identity comparison, which would be useless even if the UUIDs
were sensible, which they aren't. As a result, trying to sync keyrings
always failed, because it always seemed like UUIDs had changed, even
when they hadn't.

Because it never occurred to me that UUIDs wouldn't be strings, I
never even wrote a test for this. Correct this, and fix the test.

Thanks to :vasilica_mihasca and :markh for reporting and diagnosing this.

MozReview-Commit-ID: EthxkFFwRbQ

--HG--
extra : rebase_source : 7b2a258d85bf8aab2bf9895e3a8cac9d34ab8435
 2016-11-29 14:15:55 -05:00
Mark Hammond ec4f115396 Bug 1320193 - remove trailing \n from log message. r=glasserc 
MozReview-Commit-ID: LwdPOwXmS5i

--HG--
extra : rebase_source : b24ad9ec2ccb30e33e24731d0b19fdcc08348792
 2016-11-25 09:01:05 +11:00
Ethan Glasser-Camp 4742db4baa Bug 1317841 - Update version of kinto.js to v6.0.0, r=MattN 
This major version of kinto.js released without a FirefoxStorage
adapter. Since Gecko is the only project with a need for this adapter
as well as the only one who can use it, that file moves to this repo
as a new kinto-storage-adapter.js. This file is mostly a copy of the
most recent FirefoxStorage.js, plus some other non-exported utility
functions copied from kinto.js to make it work.

This changes the export of the kinto-offline-client.js from a
`loadKinto` function which returns the Kinto class, to the actual
Kinto class itself, with the user expected to "hook up" the
adapter. It turns out that this doesn't change much in how we actually
use Kinto, since we were always previously explicitly selecting the
Kinto adapter.

This release of kinto.js also changes some of the build options
around, which changes the minified output of kinto-offline-client.js.

There are still some outstanding stylistic complaints about
FirefoxAdapter having to do with its _init static method which is
public and the fact that sometimes FirefoxAdapter manages its own
Sqlite connection and sometimes it doesn't. These will be addressed in
a future patch.

MozReview-Commit-ID: HF0oNCEDcFs

--HG--
rename : services/common/kinto-offline-client.js => services/common/kinto-storage-adapter.js
extra : rebase_source : 11d01e573b259798305494ac072575247ac01e2c
 2016-11-15 19:38:53 -05:00