Re: [w3c/uievents] Reflect the reality for the focus event order (#290)

@danburzo commented on this pull request.



> -   before focus is shifted, and does bubble.
-
-   <p class="note">
-   When using this event type, the content author can use the event's
-   {{FocusEvent/relatedTarget}} attribute (or a host-language-specific
-   method or means) to get the currently focused element before the
-   focus shifts to the next focus <a>event target</a>, thus having
-   access to both the element losing focus and the element gaining
-   focus without the use of the EVENT{blur} or EVENT{focusout} event
-   types.
-   </p>
+   A <a>user agent</a> MUST dispatch this event when an <a>event target</a>
+   receives focus. The <a>event target</a> MUST be the element which
+   received focus. The [=focus=] event MUST fire before the dispatch of
+   this event type. This event type is similar to [=focus=], but does
+   not bubble.

Small typo: 

```suggestion
   bubble.
```

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

Message ID: <w3c/uievents/pull/290/review/915075230@github.com>