1163188 - WebSMS has no timeout or cancel

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::SMS, defect)

Description

[coolaj86]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36

Steps to reproduce:

Channel: FxOS 3.0-prerelease

I was the Open West conference for a Firefox OS presentation in a room with no cell service and, not realizing that, I decided to test the WebSMS API.

result = navigator.mozMobileMessage.send(number, message);


Actual results:

After several minutes neither the success nor the error handler fired. I tried several more times (due to https://bugzilla.mozilla.org/show_bug.cgi?id=1163172). At the end of the talk I closed my laptop and walked out of the room. Somewhere down the hallway I got one of the messages on my phone.


Expected results:

Best case: an immediate error with a message "no service available" or similar

Good case: some sort of timeout error

Also good: a way to cancel a message after a timeout on my end.

Not bad: maybe some sort of queue system that I can check for pending messages (along with some sort of state object to know if it was my app or another that is managing it).

I just want some way to know in a timely fashion (seconds, not minutes) if I should store the message and try again later.

It may be better to have something more like the alarms api

var result = navigator.mozMobileMessage.send(number, message, { state: state });
navigator.mozMobileMessage.on('send', function (obj) {
  console.log("queued message was sent");
  console.log(obj);
});
navigator.mozMobileMessage.cancel(result.id); // throws error if '.id' isn't a pending message

Comment 1

[Julien Wajsberg [:julienw]]

Mass closing of Gaia::SMS bugs. End of an era :(

Comment 2

[Julien Wajsberg [:julienw]]

Mass closing of Gaia::SMS bugs. End of an era :(