With the completely non-blocking handling of 'GetProperties' message
there is no need for BluetoothArrayOfDevicePropertiesRunnable any longer.
--HG--
extra : rebase_source : 8cbdf1bfdf4aec3dfd797326a6846931a8099723
BluetoothArrayOfDevicePropertiesRunnable used to block while waiting
for the results of the 'GetProperties' messages it sends over DBus. With
this patch, each 'GetProperties' operation is performed asyncronously
and the result is handled in a DBus reply handler. The same reply handler
gets used for all 'GetProperties' messages until all devices have been
processed. In this case the final Bluetooth reply runnable gets
dispatched.
The old function GetPropertiesInternal is now unused and has been
removed.
--HG--
extra : rebase_source : 6e5ed63ce2077e16bcaf995c3ca89f923ec8b37e
========
https://hg.mozilla.org/integration/gaia-central/rev/0265b24e1593
Author: Eric O'Connor <eric@bocoup.com>
Desc: Bug 898666 - [clock] Clock refactor alarm object and add test
(Rebased with UI regression fix for alarm ordering.)
1. An Alarm constructor is used to create new Alarms, instead of
creating new object literals.
2. The AlarmsDB API is changed to pass error messages in the
function(err, value) {...} style.
3. Asyncronous API calls are checked using callbacks. The async
functions in Utils make this easy (although including async.js
would be easier.
4. Testing is added for the Alarm object.
5. Added mock_alarmsDB and mock_mozAlarms for testing Alarms
6. Fixed alarm_edit tests. Moved to a new alarm_edit_test.js file.
7. Add tests for new utils methods (async and safeCpuLock)
8. Rename some variables. Remove "_name" naming scheme.
9. Removed in app alarm set indicator
10. Protect id, repeat, and enabled properties on the Alarm object.
r=jugglinmike
RecordFrameMetrics gets called on a variety of layers. Previously it would
incorrectly set mZoom for a number of these layers. For scrollable container
layers inside the main document, it would set the mResolution from the
presShell's resolution, thus compounding the painted resolution.
Furthermore, for iframes inside the document, it would assign mZoom the
value from TabChild's mLastMetrics, which is only meant to apply to the
top-level document. Prior to multi-apzc work these values were never used
so it didn't matter but now they are so they should be assigned correctly.
========
https://hg.mozilla.org/integration/gaia-central/rev/7d2cf0d6f8cb
Author: Mike Pennisi <mike@mikepennisi.com>
Desc: Revert "Bug 898666 - [clock] Clock refactor alarm object and add test"
This reverts commit 3746b1cdc0e344460c58cd52f85564b0c4f5940a due to a
UI regression in the ordering of Alarm list items.
========
https://hg.mozilla.org/integration/gaia-central/rev/b3e578bc32ce
Author: Salvador de la Puente González <salva@unoyunodiez.com>
Desc: Merge pull request #11792 from lodr/bug-906756-changing-algorithms
Bug 906756 - Algorithms for merging givenName and familyName changed.
r=arcturus
========
https://hg.mozilla.org/integration/gaia-central/rev/872fb0e0a347
Author: lodr <salva@unoyunodiez.com>
Desc: Bug 906756 - Algorithms for merging givenName and familyName changed.
New tests added.
Adapt and merge changed to allow specifying the master contact.
Name composition centralized to avoid code repetition.
These were already marked as fuzzy on B2G for 83 pixels. With the B2G emulator BGRA patch now deployed on the test slaves, it appears from reftests logs that the fuzziness needs to be updated from 83 pixels to 90 or 91 pixels depending on the test.
