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.
?? Why such condition? ``` scope.html5 = !!scope.html5``` would suffice right? if it is undefined or null it would be false otherwise true.