This removes the unnecessary setting of c-basic-offset from all
python-mode files.
This was automatically generated using
perl -pi -e 's/; *c-basic-offset: *[0-9]+//'
... on the affected files.
The bulk of these files are moz.build files but there a few others as
well.
MozReview-Commit-ID: 2pPf3DEiZqx
--HG--
extra : rebase_source : 0a7dcac80b924174a2c429b093791148ea6ac204
Outline of this patch:
1. Define a new ipdl message called |CloseAfterInvalidationComplete| to trigger the close event after all transactions are complete only if the database is invalidated by the user agent.
2. Make sure the following event sequence is consistent during invalidation according to the steps in |5.2. Closing a database| by the following 2 solutions:
IDBRequest.onerror -> IDBTransaction.onerror -> IDBTransaction.onabort -> IDBDatabase.onclose.
2.1. In parent process, do not force to abort the transactions after invalidation but wait for all the transactions in its child process are complete.
2.2. In child process, make sure that each IDBTransaction will notify its completion to the parent after all its pending IDBRequests are finished.
3. Add test_database_onclose.js to test the close event especially when read/write operation is ongoing.
4. Add test_database_close_without_onclose.js as a XPCShell test because setTimeout() is not preferred in Mochitest to ensure that the IDBDatabase.onclose event won't be sent after closed normally.
For details on extensions in automation and signing, see:
https://wiki.mozilla.org/EngineeringProductivity/HowTo/SignExtensions
MozReview-Commit-ID: 6unn8eJl9PW
--HG--
extra : rebase_source : 3eb93bfa515b7b94b42c1122c1e22903638af562
extra : amend_source : 6717aff0d64992639d0ad9a5cb3c185edfbfb3f2
extra : intermediate-source : 502cf531ec266e44fdfbb1974277bf75282cf066
extra : source : 7566245cc5ea9e15415e71a2599ec72c953189df
CLOSED TREE
Backed out changeset 4fa5b5a25f04 (bug 1251372)
Backed out changeset 502cf531ec26 (bug 1250616)
Backed out changeset 2f25d03334b2 (bug 1250616)
For details on extensions in automation and signing, see:
https://wiki.mozilla.org/EngineeringProductivity/HowTo/SignExtensions
MozReview-Commit-ID: 6unn8eJl9PW
--HG--
extra : rebase_source : b3ec2d27aa2be197e1240edc22f349a3fff0530c
extra : amend_source : bb01dd6a8d27197ed1e70a694d2142417dd18c23
extra : intermediate-source : 10d85d4a79c2684f12deb4dd33468d97d03fb0dc
extra : source : 7566245cc5ea9e15415e71a2599ec72c953189df
For details on extensions in automation and signing, see:
https://wiki.mozilla.org/EngineeringProductivity/HowTo/SignExtensions
MozReview-Commit-ID: 6unn8eJl9PW
--HG--
extra : rebase_source : 0be434fc1c98f738efd397c48535c33191177f9d
extra : amend_source : bb01dd6a8d27197ed1e70a694d2142417dd18c23
extra : source : 7566245cc5ea9e15415e71a2599ec72c953189df
This change renames OriginAttributes.mInBrowser to mInIsolatedMozBrowser and
nsIPrincipal::GetIsInBrowserElement to GetIsInIsolatedMozBrowserElement. Other
methods that pass these values around also have name changes.
Tokens such as "inBrowser" have previously been serialized into cache keys, used
as DB column names, stored in app registries, etc. No changes are made to any
serialization formats. Only runtime method and variable names are updated.
No behavior changes are made in this patch, so some renamed methods may have
nonsensical implementations. These are corrected in subsequent patches
focused on behavior.
MozReview-Commit-ID: 66HfMlsXFLs
For details on extensions in automation and signing, see:
https://wiki.mozilla.org/EngineeringProductivity/HowTo/SignExtensions
MozReview-Commit-ID: 6unn8eJl9PW
--HG--
extra : rebase_source : c11c53c129cb16c5ccb6dd03364768cb18779f6b
extra : amend_source : ebf04756b516843738be361696383c35b187a12e
This method is e10s-compatible. It is async, so it requires
rejiggering the test a little. This also requires fixing up a shim
version for xpcshell tests. Finally, this test is the only user of
SpecialPowers.createDOMFiles, so I removed it.
Be warned. Do not attemp to change the .js "test" source code in ./js
They are meant to check
- the outdated 0666 octal constant is still parsed correctly,
- the outdated 0666 octal constant raises syntax error flag
in strict mode, etc.
So leave them alone.
This makes it clearer that really it's the same thing as FINAL_TARGET,
with preprocessing.
We still keep DIST_FILES in backend.mk because it's shorter and doesn't
really matter.
