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.
Lol yes, will refactor. It's an exercise in how many variables we can have that include the word `max`.