This article is in need of a technical review.
This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.
MozSmsEvent represents events related to WebSMS text messages.
MozSmsEvent also inherite properties from
- A boolean indicating whether the event bubbles up through the DOM or not.
- A boolean indicating whether the bubbling of the event has been canceled or not.
- A boolean indicating whether the event is cancelable.
- A reference to the currently registered target for the event.
Indicates whether or not
event.preventDefault()has been called on the event.
- Indicates which phase of the event flow is being processed.
- The explicit original target of the event (Mozilla-specific).
- The original target of the event, before any retargetings (Mozilla-specific).
- A reference to the target to which the event was originally dispatched.
- The time that the event was created.
- The name of the event (case-insensitive).
- Indicates whether or not the event was initiated by the browser (after a user click for instance) or by a script (using an event creation method, like event.initEvent)
MozSmsEvent inherite methods from
Initializes the value of an Event created through the
event.preventBubbleObsolete since Gecko 24
Prevents the event from bubbling. Obsolete, use
event.preventCaptureObsolete since Gecko 24
- Cancels the event (if it is cancelable).
- For this particular event, no other listener will be called. Neither those attached on the same element, nor those attached on elements which will be traversed later (in capture phase, for instance)
- Stops the propagation of events further along in the DOM.
MozSmsEvent is used for the following events:
- Fired whenever an SMS is delivered to a recipient.
- Fired whenever an SMS is received.
- Fired whenever an SMS is sent.
This is a non standard implementation, but it is discussed at W3C as part of the System Application Working Group.
|Messaging API||Editor's Draft||Editor Draft (WIP).|
For obvious reasons, support is primarily expected on mobile browsers.
|Feature||Chrome||Firefox (Gecko)||Internet Explorer||Opera||Safari|
|Basic support||Not supported||Not supported||Not supported||Not supported||Not supported|
|Feature||Android||Firefox Mobile (Gecko)||IE Mobile||Opera Mobile||Safari Mobile|
|Basic support||Not supported||12.0 (12.0) Moz||Not supported||Not supported||Not supported|