The marionette tests for getCardLockRetryCount test retrieving the
retry count for 'pin', 'puk', and an invalid lock type. The former
two must return success or 'NotSupportedError', the latter may only
return 'IllegalAccessError'.
* * *
fix mar
--HG--
extra : rebase_source : 509cd74e783eaf8d77be8b37c7143f3043d69b28
This patch adds getCardLockRetryCount to nsIIccProvider and its
implementations. This method allows callers to query the number
of remaining tries for unlocking a SIM-card lock. Supported locks
are 'pin', 'puk', 'pin2', 'puk2', 'nck', 'cck', and 'spck'. The
call returns a DOM request that returns the retry count in its
success handler, or signals an appropriate error.
Reading the retry count is an optional feature and may not be
supported for all lock types. In this case the DOM request receives
and error with the name GECKO_ERROR_NOT_SUPPORTED. For an invalid
lock type, the error name is GECKO_ERROR_GENERIC_FAILURE.
getCardLockRetryCount replaces retryCount in nsIDOMMobileConnection,
which is now deprecated.
--HG--
extra : rebase_source : d1d11612f836652dca85f7c701f09e7af962e3b7
The method BluetoothDBusService::GetServiceChannel currently blocks the
Bluetooth command thread while waiting for a DBus message, before it
dispatches a runnable to the main thread.
With this patch, the DBus message is processed asyncronously, and the
runnable gets dispatched from the DBus reply handler.
--HG--
extra : rebase_source : 24519b7dd8d59fcbbf78436092610c8db195f6a2
Handler functions for DBus replies sometimes need several data fields
or need to keep state over replies for multiple messages. The DBus API
itself only allows for a single pointer to user data.
The class DBusReplyHandler is a base class for implementing DBus reply-
message handlers. Users of DBus can inherit from this class to implement
message-specific handlers.
--HG--
extra : rebase_source : 91c5f6e8d365922fd3b52fbaf502052f86274f16
Truncated some number of revisions since the previous bump.
========
https://hg.mozilla.org/integration/gaia-central/rev/8da5a527d6d9
Author: Ben Kelly <bkelly@mozilla.com>
Desc: Merge pull request #10582 from wanderview/contacts-vis-mon-pr
Bug 879299: Add visibility_monitor to Contacts app. r=arcturus
========
https://hg.mozilla.org/integration/gaia-central/rev/5dd51d34e38b
Author: Ben Kelly <ben@wanderview.com>
Desc: Bug 879299: Add visibility_monitor to Contacts app
This commit significantly refactors how contacts are loaded and rendered in
the DOM. Placeholder items are initially added to the list and then later
filled in when visible. Images are lazy loaded as before, but will now be
removed when the contact is no longer visible. Search has also been
refactored to help encapsulate the contacts_list and importer_ui internals.
========
https://hg.mozilla.org/integration/gaia-central/rev/b31ab8aa351a
Author: Mike Pennisi <mike@mikepennisi.com>
Desc: Bug 875362 - [MMS] Cannot scroll to bottom of thread list as input field grows r=julienw
This patch addresses an issue where the Compose field could grow to
completely cover the message thread. Now, a "sliver" of space is
reserved to maintain a visual affordance to the underlying thread.
This patch also ensures that messages are not occluded while the Thread
UI is in "Edit" mode.
Previously, the spacing after the final message "bubble" was set to an
arbitrary value of 7rem. This patch sets the spacing to the specified
amount, and ensures that the spacing remains consistent as the Compose
field grows and shrinks (resolving "Bug 882086 - [MMS] [UX] Message
thread. Spacing between the last bubble and input field should be 1.5
rem")
This patch also adds "abbreviated gc log", which produces a not-all-traces CC log.
--HG--
extra : rebase_source : 84eed72c34b7cc8116fbe05258f5de22bf3275bc