Re: [whatwg/dom] Redesign fire an event and target override (#344)

domenic approved this pull request.

Merge at will, just found a couple more potential nits.

>  
- <li><p>Initialize <var>event</var>'s {{Event/type}} attribute to <var>e</var>.
+ <li><p>Let <var>event</var> be the result of <a for=Event lt=constructor>invoking</a> the initial
+ value of <var>eventConstructor</var> with <var>e</var> as argument.

"with the argument _e_"

> -<a>Fire an event</a> makes that process easier to write
-down. If the <a>event</a> needs its {{Event/bubbles}} or
-{{Event/cancelable}} attribute initialized, one could write
-"<a>fire an event</a> named
-<code>submit</code> with its {{Event/cancelable}} attribute
-initialized to true".
+<p class="note no-backref">Fire in the context of DOM is short for creating, initializing, and
+<a>dispatching</a> an <a>event</a>. <a>Fire an event</a> makes that process easier to write down.
+
+<div class="example no-backref" id=firing-events-example>
+ <p>If the <a>event</a> needs its {{Event/bubbles}} or {{Event/cancelable}} attribute initialized,
+ one could write "<a>fire an event</a> named <code>submit</code> at <var>target</var> with its
+ {{Event/cancelable}} attribute initialized to true".
+
+ <p>Or, when a custom constructor is required, "<a>fire an event</a> named <code>click</code> at
+ <var>target</var> using <code>MouseEvent</code> with its {{Event/isTrusted}} attribute initialized

Use `{{MouseEvent}}` instead of `<code>MouseEvent</code>` to get some free auto-linking.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/344#pullrequestreview-4287960