following bug 740079 To get along with the synchronous `status' property, it would be nice to support `onstatuschange' callbacks. There are a few use cases where this would be easier than a set of onconnect / onconnecting / ondisconnect / etc. event listeners and it would be more XHR-like.
Created attachment 614702 [details] [diff] [review] Patch v1 This should be pretty straightforward. The one thing I wondered about was whether it was worth it to change the internal (IPC) notifications to follow the DOM API. I decided against it since not all of the notifications did exactly the same thing (in particular, disconnect is handled a little differently). Any opinions on that would be welcome.
Assignee: nobody → mrbkap
Status: NEW → ASSIGNED
Attachment #614702 - Flags: review?(jones.chris.g)
Attachment #614702 - Flags: feedback?(kaze)
>+ * - disconnected: Fires when we either fail to connect to an access >+ * point (transition: onassociate -> ondisconnect) or >+ * when we were connected to a network but have >+ * disconnected for any reason (transition: onconnect -> >+ * ondisconnect). nit: transition: associated -> disconnected transition: connected -> disconnected
Here’s a preliminary front-end: https://github.com/andreasgal/gaia/pull/1226
Attachment #614702 - Flags: review?(jones.chris.g) → review+
Attachment #614702 - Flags: feedback?(kaze) → feedback+
OS: Linux → All
Hardware: x86 → All
Target Milestone: --- → mozilla14
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.