Closed Bug 1111057 Opened 10 years ago Closed 10 years ago

Make MobileConnectionCallback consistently async

Categories

(Firefox OS Graveyard :: RIL, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1070831

People

(Reporter: pgravel, Unassigned)

Details

Most MobileConnectionCallback function have a built-in asynchronous step, except for the error cases that result in FireDetailedError, which makes behavior a little inconsistent when issuing callbacks.
http://mxr.mozilla.org/mozilla-central/source/dom/mobileconnection/MobileConnectionCallback.cpp#387

Requesting that an async step be added for the error callbacks that use FireDetailedError()
(In reply to pgravel from comment #0)
> Most MobileConnectionCallback function have a built-in asynchronous step,
> except for the error cases that result in FireDetailedError, which makes
> behavior a little inconsistent when issuing callbacks.
> http://mxr.mozilla.org/mozilla-central/source/dom/mobileconnection/
> MobileConnectionCallback.cpp#387
> 
> Requesting that an async step be added for the error callbacks that use
> FireDetailedError()

Hi,
The section of code is going to be removed in https://bugzilla.mozilla.org/attachment.cgi?id=8536486
After that, I think your concern will be released.
I am going to close this bug as duplicate of bug 1070831. Feel free to reopen it if i misunderstand something or you disagree, thank you.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
blocking-b2g: 2.2? → ---
No longer blocks: CAF-v2.2-metabug
You need to log in before you can comment on or make changes to this bug.