The check here causes issues when using units other than vmax. Rather than taking a sledgehammer/all-or-nothing approach, this check should be made later on to determine if vmax support is necessary, and should only apply fixes for vmax.
// added check for IE11, since it *still* doesn't understand vmax!!!
if (!isBuggyIE) {
isBuggyIE = !!navigator.userAgent.match(/Trident.*rv[ :]*11\./);
}
Hi,
The check here causes issues when using units other than
vmax
. Rather than taking a sledgehammer/all-or-nothing approach, this check should be made later on to determine ifvmax
support is necessary, and should only apply fixes forvmax
.