Re: [whatwg/dom] Define how script-created click events are special during dispatch (#325)

Sorry for not seeing this thread earlier. We definitely want to fix this in
UI Events, but there are some subtleties in the terminology that I want to
make sure I get right when making this change.

Also, since people will still search for "default action" (it's used
throughout the web), I think we'll still need a glossary entry indicating
that the term is inappropriate and should not be used (and also have
pointers to the "legacy post-dispatch steps").

Is it worth setting aside some time at TPAC for this?

On Thu, Sep 15, 2016 at 7:09 AM, Anne van Kesteren <notifications@github.com
> wrote:

> I talked about this a while back with @smaug----
> <https://github.com/smaug---->. https://dom.spec.whatwg.org/#
> concept-event-dispatch uses "get the parent" to determine where to invoke
> listeners. Something similar is used at the end of dispatch.
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=12230#c29 also explains
> this. That is what we should use here and we should only do it if the
> canceled flag is not set.
>
> Then we can let specifications define "legacy post-dispatch steps" for
> objects that need them (only <a>?). (I don't want to call it "default
> action", not even prefixed with "legacy". I think that would continue to
> cause much confusion.)
>
> Does anyone see problems with that?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/whatwg/dom/issues/325#issuecomment-247338974>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/ABaVSgB11dSpHoTzq6RdNXc-pTQOnWbBks5qqVGxgaJpZM4JziNR>
> .
>


-- 
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/issues/325#issuecomment-247391857