Opened 10 years ago
Closed 7 years ago
#16318 closed feature (fixed)
Improving events API
Reported by: | dylan | Owned by: | Kris Zyp |
---|---|---|---|
Priority: | blocker | Milestone: | 2.0 |
Component: | Events | Version: | 1.8.1 |
Keywords: | Cc: | Colin Snover, ben hockey | |
Blocked By: | Blocking: |
Description
There are some things that are not easy to do with dojo/on and dojo/Evented:
- It is not currently possible or easy to know what event handlers are registered on a given element or a given Dijit
- It is not currently possible to dispatch custom events with names that are “forbidden”
- It is not easy to implement future DOM event APIs transparently
As part of our API improvements towards 2.0, I think these would be good things to figure out for 1.9. What else would we like to see improve in dojo/on and dojo/Evented that we can work on now for 1.9, in preparation for making 2.0 better?
Change History (3)
comment:1 Changed 10 years ago by
Cc: | ben hockey added |
---|
comment:2 Changed 9 years ago by
Milestone: | 1.9 → 2.0 |
---|
comment:3 Changed 7 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
New Evented ( https://github.com/dojo/core/blob/master/src/Evented.ts ) and on ( https://github.com/dojo/core/blob/master/src/on.ts ) now exist.
For the items listed, 1 is not possible with event delegation, 2 I'm not sure of, and 3 I think we have a generally more flexible approach now.
Note: See
TracTickets for help on using
tickets.
per meeting decision punt to 2.0