add dual listener when on a touch-enabled browser
build event-touch
Merge branch 'dev-3.x' into dual-listener
Merge branch 'dev-3.x' into dual-listener

Conflicts:
	build/event-touch/event-touch-coverage.js
event-tap now has preventDefault(), works on Android 4.0.x and on mouse/touch enabled devices.

event-tap got a bunch of modifications in this commit:
- Dual listener support! Listens to "touchstart mousedown", and based on which one is captured, sets up listeners for either "touchmove", "touchend", "touchcancel", OR the equivalent mouse events. Now, touch events obviously fire a corresponding mouse event, and I didn't want to have a heavy-handed event.preventDefault() in the code. To prevent the corresponding mouse/click events from firing `touchEnd()`, I set up a `needToCancel` boolean that is toggled once the first `touchstart/mousedown` is captured.

- e.preventDefault() works!  You can now do this:
```
    node.on('tap', function (e) {
      e.preventDefault();
      //do some stuff here...
    });
```
update unit tests to work with commit 9cbc2f6
add manual tap test
Modified to fix #960

1. Formatting non-master checkboxes based on the 'select' value.
2. Making the non-master's model 'select' change silent so that it wouldn't re-render the datatable.
Modified to fix #960
#960 reverting changes as per @lsmith comments

- Reverting the formatter config back to string type.
- Added more doc for the `{ silent: true }` change.
Modified new test to be a less complex (sets content to something shorter than the total widget height), while still testing the new fix
Merge branch 'dev-3.x' into dual-listener
Fix #716. Refactored charts to put all cartesian coordinate methods in axis classes and added logarithmic scaling for numeric axis.
Update charts unit tests.
Fixed issue in which the origin was not being correctly calculated for logarithmic charts.
Update charts unit tests.
Fix 909. Fixes typo in NAME param.
Merge branch 'dev-master' into dev-3.x
Merge branch 'dev-3.x' into issue716
Fixed functional test failure in which axis line mistakenly accounted for edgeOffsets.