[css-transitions-2] clarify that CSS transition events are dispatched at the owning element

Author: birtles

css-transitions-2/Overview.bs

@@ -30,6 +30,10 @@ Issue Tracking: Bugzilla bugs for all levels https://www.w3.org/Bugs/Public/bugl
 Abstract: CSS Transitions allows property changes in CSS values to occur smoothly over a specified duration.
 Ignored Terms: translate, rotate, scale
 </pre>
+<pre class=anchors>
+urlPrefix: https://dom.spec.whatwg.org/; type: dfn; spec: dom
+    text: event target
+</pre>
 <pre class=link-defaults>
 spec:css-transitions-1; type:value; text:all
 spec:css-transitions-1; type:dfn; text:cancel
@@ -39,6 +43,7 @@ spec:web-animations-1; type:dfn;
     text:active time
     text:animation class
     text:animation effect
+    text:animation playback events
     text:associated effect
     text:associated effect end
     text:cancel an animation
@@ -222,6 +227,12 @@ properties not normally used with transitions (e.g. an effect that repeats
 multiple times) and hence this section provides a generic definition that
 accounts for the full complexity of the Web Animations model.
 
+The [=event target|target=] for a transition event is
+the transition's [=owning element=].
+If there is no [=owning element=], no transition events are dispatched
+(although the [=animation playback events=] defined in Web Animations are still
+dispatched at the corresponding {{CSSTransition}} object).
+
 To avoid firing redundant events, the set of events to dispatch is based
 on comparing the <a lt="transition phase">phase</a> of the transition in the
 previous [=animation frame=] to its current state.