removing MessagingRequest

Author: Eduardo Fullea

index.html

@@ -1274,95 +1274,6 @@ <h2>Event handlers</h2>
 
 </section>    
 
-<!------------------------ Interface MessagingRequest ------------------------>
-<section>
-  <h2><a>MessagingRequest</a> Interface</h2>
-  <p>The <a>MessagingRequest</a> interface represents an ongoing operation. It
-  provides callbacks that are called when the operation completes, as well as a
-  reference to the operation's result. A method that initiates an operation
-  (e.g. delete message via the <code>delete</code> method in the
-  <code>Messaging</code> interface) MUST return a MessagingRequest object that
-  can be used to monitor the progress of that operation.
-  <dl title="[NoInterfaceObject] interface MessagingRequest"
-      class="idl">
-    <dt>readonly attribute DOMString readyState</dt>
-    <dd>Indicates the state of the request, with possible string values
-    'processing',if the request has been made and it is progressing, or 'done',
-    if the request has been already completed.</dd>
-
-    <dt>readonly attribute DOMError? error</dt>
-    <dd>An error that occured during the request. Errors are as defined in
-    [[!DOM4]].</dd>
-
-    <dt>readonly attribute any? result</dt>
-    <dd>Indicates the result of the request. The type depends on the sort of
-    request, and is specified in the description of each method that returns a
-    <code>MessagingRequest</code> object, e.g. <code>delete</code> method of the
-    <code>Messaging</code> object.</dd>
-
-    <dt class="no-docs">
-      attribute EventHandler onprogress
-    </dt>
-    <dd></dd>
-
-    <dt class="no-docs">
-      attribute EventHandler onsuccess
-    </dt>
-    <dd></dd>
-
-    <dt class="no-docs">
-      attribute EventHandler onerror
-    </dt>
-    <dd></dd>
-  </dl>
-
-  <section>
-    <h2>Event handlers</h2>
-    <p>
-    <p>The following are the <a class="internalDFN"
-    href="#dfn-eventhandler">event handlers</a> (and their corresponding <a
-    class="internalDFN" href="#dfn-eventtypes">event types</a>) that MUST be
-    supported as attributes by the <a>MessagingRequest</a> object.
-
-    <table class="simple">
-      <thead>
-        <tr>
-          <th>event handler</th>
-          <th>event name</th>
-          <th>event type</th>
-          <th>short description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td><strong><code>onprogress</code></strong></td>
-          <td><code><dfn>progress</dfn></code></td>
-          <td><a><code>ProgressEvent</code></a></td>
-          <td>handles progress events related to MMS sending/fetching
-          operations</td>
-        </tr>
-        <tr>
-          <td><strong><code>onsuccess</code></strong></td>
-          <td><code><dfn>success</dfn></code></td>
-          <td><a><code>Event</code></a></td>
-          <td>handles success of the request</td>
-        </tr>
-        <tr>
-          <td><strong><code>onerror</code></strong></td>
-          <td><code><dfn>error</dfn></code></td>
-          <td><a><code>Event</code></a></td>
-          <td>handles failure of the request</td>
-        </tr>
-      </tbody>
-    </table>
-  </section>
-</section>
-
-  <p class="issue">
-  Use of DOMRequest / DOMFuture to be assessed as part of a broader discussion
-  in W3C SysApps.
-  </p>
-
 
 <!------------------------ Interface SmsMessage ------------------------------>
 <section>