Re: [w3c/editing] [execCommand] Replace Editing[Before]InputEvent to InputEvent (#206)

@marcoscaceres commented on this pull request.



> @@ -710,17 +672,12 @@ <h2 id="methods-to-query-and-execute-commands">
                 would not be <a href="#enabled">enabled</a>.
               </p>
             </li>
-            <li>[=Dispatch=] an [=event=] at <var title="">affected editing
-            host</var> that uses the <a>EditingBeforeInputEvent</a> interface.
-            The event's {{Event/type}} attribute must be initialized to
-            "beforeinput"; its {{Event/isTrusted}}, {{Event/bubbles}}, and
-            {{Event/cancelable}} attributes must be initialized to true; its
-            <code title="dom-EditingBeforeInputEvent-command"><a href=
-            "#dom-editingbeforeinputevent-command">command</a></code> attribute
-            must be initialized to <var title="">command</var>; and its
-            <code title="dom-EditingBeforeInputEvent-value"><a href=
-            "#dom-editingbeforeinputevent-value">value</a></code> attribute
-            must be initialized to <var title="">value</var>.
+            <li>[=Dispatch=] an [=event=] at <var>affected editing host</var>

Nit: I wonder if we should use the "fire an event" algo here instead? Also, does all this happen sync or at these queued tasks (and if so, what task source)? 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/pull/206#pullrequestreview-409673018