Define processing model about auxclick HOT 7 OPEN

Contextmenu is not defined in the UI Event spec. So I was not sure if definition of how it is dispatched belongs here or not. But regarding when to send the auxclick I was kind of copying from existing definition of click regarding down and release and then dispatch click and I thought that was clear enough.
Do you have another example in mind that defines such "description of the UI action" for another event so I can get a better understanding what you would like to see?

from auxclick.

https://w3c.github.io/clipboard-apis/ is close, though it fails to queue tasks to execute its actions.

from auxclick.

As for contextmenu, since you're essentially defining non-primary-mouse-clicks, and contextmenu can be triggered on behalf of one of those, you at least need to show how it integrates into the processing model. You might have to work with the HTML Standard at https://github.com/whatwg/html on desirable layering.

from auxclick.

So you want something like section 6 in that spec. Right?
Let's talk about the contextmenu in the other issue #14. But contextmenu is not triggered by any click action.

from auxclick.

Yeah, though what's important here is how exactly the OS-level action is mapped. That is, I don't know if there's a distinction between a mouseup and an auxclick in terms of OS-level actions. Are those two OS-level actions or is that a distinction that the browser makes as part of the mouseup action?

from auxclick.

I'm not sure what you mean by OS-level action. At first I thought you meant OS-level input to the browser by I don't think that's what you wanted.

from auxclick.

OS-level input sounds about right. We don't have a good shared term for it yet. (I've been using "UI actions", but I'm also confusing it by sometimes throwing in different terms. Sorry about that.)

from auxclick.