search

w3c / uievents

UI Events
https://w3c.github.io/uievents/
Other
147 stars 52 forks source link

Clarify what events are expected from <option> elements in <select> dropdowns #55

Open mikeconley opened 9 years ago

mikeconley commented 9 years ago

I find it unclear what UI events are expected to be fired from the option element when the select that contains the option is in dropdown mode (for example, when the select is not being used for multiple selections, or when the size of the select is 1).

I'm particularly interested in mouse and keyboard events.

The major browsers seem to behave differently. I've highlighted those differences here.

It'd be good if we could hammer out the actual desired behaviour here so that there's less ambiguity in how (if ever) to dispatch events for option elements when in dropdown selects.

I wasn't sure where to file this, so I've cross-filed it here as well.

jdm commented 9 years ago

This repository concerns the UIEvents spec at https://w3c.github.io/uievents/ .

mikeconley commented 9 years ago

I apologize - I lazily copied verbatim from the issue I cross-filed from. Give me a few minutes to update this issue appropriately.

mikeconley commented 9 years ago

Okay, hopefully I've made it more clear how (I think) this issue is applicable to the UIEvents spec.

annevk commented 9 years ago

I think you're correct that this is the right place. Conceptually the UA gets a system UI interaction notification, performs hit testing, translates from layout box to node, creates a MouseEvent, and then dispatches the event at the located node. Something along this chain stops that from happening for dropdown controls in certain UAs.