Changes between Initial Version and Version 1 of Ticket #15878, comment 9


Ignore:
Timestamp:
Mar 1, 2013, 5:17:53 AM (9 years ago)
Author:
bill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15878, comment 9

    initial v1  
    11PS: The idea behind a synthetic event like dijit/a11yclick (which perhaps should just be called dijit/click) is that app code call {{{on(node, a11yclick, ...)}}} instead of {{{on(node, "click", ...)}}}.   If code follows that rule, the on.emit() call doesn't have to emit "click", it could emit "dojoclick" etc., similar to how the other code in dojo/touch works.   That would be more straightforward, albeit users would need to be trained to do {{{on(node, a11yclick, ...)}}}.
     2
     3The reasons a11yclick is currently emitting a "click" event are:
     4   1. for native browser behavior.   For example, dijit/Checkbox is an actual <input type=checkbox> so we depend on the browser rather than javascript to toggle it.
     5   2. because the app may be listening for "click" itself, rather than dijit/a11yclick