Opened 9 years ago
Closed 5 years ago
#15261 closed defect (patchwelcome)
dojo/mouse usage is fragmented and counterintuitive
| Reported by: | Karl Tiedt | Owned by: | Kris Zyp |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.13 |
| Component: | Events | Version: | 1.7.2 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
the new eventing code is awesome.... however the idea behind dojo/mouse seems half baked...
Not only are users going to have to drag through learning connect vs on differences (no scoping... on doesnt work for ALL things like connect would etc etc) now they have to deal with remembering *when* to use a 2nd module just to get *SOME* mouse events to work properly...
why doesnt dojo/mouse wrap *all* mouse events so there is a unified *common* means of registering mouse events?
Change History (4)
comment:1 Changed 9 years ago by
| Component: | Core → Events |
|---|---|
| Owner: | set to Kris Zyp |
comment:2 Changed 8 years ago by
comment:3 Changed 8 years ago by
By that thought lets split getters and setters in to separate files... Maybe everyone doesn't brewed both... The point is they are all mouse events they shouldn't be fragmented...
comment:4 Changed 5 years ago by
| Milestone: | tbd → 1.12 |
|---|---|
| Resolution: | → patchwelcome |
| Status: | new → closed |
Given that no one has shown interest in creating a patch in the past 3+ years, I'm closing this as patchwelcome.
Your suggestion would perhaps be less confusing, but it would mean that apps require() dojo/mouse when they don't need to, bloating their code.