Feature/ngui doublerange fix

input[type=range] behavior changed with angular 1.3

this PR fixes doublerange directive, but at same time gives up on using html5 mode in coopr because that UI is not practical for the end user.
If we pass in a value from the scope (which is a boolean) this could be avoided. Logically every view in angular is tied to a scope (I suppose). If that is the case can we expect people using directive to do this,

```html
<my-doublerange
  html5mode ="scope.html5mode">
</my-doublerange>
```