fit-ui 2.11.14 → 2.11.16

package/dist/Fit.UI.js

@@ -682,7 +682,7 @@ Fit._internal =
 {
 	Core:
 	{
-		VersionInfo: { Major: 2, Minor: 11, Patch: 14 } // Do NOT modify format - version numbers are programmatically changed when releasing new versions - MUST be on a separate line!
+		VersionInfo: { Major: 2, Minor: 11, Patch: 16 } // Do NOT modify format - version numbers are programmatically changed when releasing new versions - MUST be on a separate line!
 	}
 };
 
@@ -5833,6 +5833,8 @@ Fit.Device =
 	// maxTouchPoints				Chrome 35+	IE 11+	Safari 13+		https://developer.mozilla.org/en-US/docs/Web/API/Navigator/maxTouchPoints
 	// Pointer media queries		Chrome 41+	Edge12	Safari 9+		https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pointer
 
+	var pointerQueriesSupported = window.matchMedia && (window.matchMedia("(any-pointer:coarse)").matches === true || window.matchMedia("(any-pointer:fine)").matches === true);
+
 	// Older touch enabled browsers such as IE11 running on early hybrid devices like Surface tablets, will not have
 	// OptimizeForTouch become true because IE11 does not support pointer media queries (e.g. pointer:fine). Furthermore such
 	// devices detached from mouse and keyboard (tablet mode) will not have HasMouse become false, also due to the lack of pointer
@@ -5841,12 +5843,6 @@ Fit.Device =
 	// the desired experience, which must ensure that the Fit.Device flags are set appropriately after Fit.UI has loaded, but before
 	// any widgets or controls are created.
 
-	// Detect lack of high precision pointer device (mouse)
-	if (window.matchMedia && matchMedia("(pointer:fine)").matches === false) // Will not detect e.g. IE11 in "tablet mode" - see comment above
-	{
-		Fit.Device.HasMouse = false;
-	}
-
 	// Detect touch support using fairly new maxTouchPoints property (Safari 13+) if possible. If not, then try alternatives.
 	// Some browsers on modern devices with support for both touch and mouse returns false for ("ontouchstart" in window),
 	// since it historically has been used to detect "touch only" devices. Therefore we also check against ("TouchEvent" in window).
@@ -5857,16 +5853,18 @@ Fit.Device =
 		Fit.Device.HasTouch = true;
 	}
 
-	// Determine whether user experience should be optimized for touch.
-	// Obviously we should optimize for touch if touch is supported and no mouse is present.
-	if (Fit.Device.HasTouch === true && Fit.Device.HasMouse === false)
+	// Detect lack of high precision pointer device (mouse).
+	// If pointer queries are not supported, then assume a mouse is not present if touch capabilities are detected, which
+	// will be the case on old touch devices (e.g. Safari v. 8 and below on iOS or Chrome v. 40 and below on Android).
+	if ((pointerQueriesSupported === true && matchMedia("(any-pointer:fine)").matches === false) ||
+		(pointerQueriesSupported === false && Fit.Device.HasTouch === true))
 	{
-		Fit.Device.OptimizeForTouch = true;
+		Fit.Device.HasMouse = false;
 	}
-	// Else, determine whether to optimize the user experience for touch on hybrid devices.
-	// Only optimize for touch in this case if device's primary pointer is NOT high precision (mouse).
-	// When a high precision pointer device is the primary pointer, then we prefer a desktop like experience.
-	else if (Fit.Device.HasTouch === true && window.matchMedia && matchMedia("pointer:fine").matches === false)
+
+	// Determine whether user experience should be optimized for touch
+	if ((pointerQueriesSupported === true && matchMedia("(pointer:coarse)").matches === true) ||				// Optimize for touch if this is the primary pointing device
+		(pointerQueriesSupported === false && Fit.Device.HasTouch === true && Fit.Device.HasMouse === false))	// Optimize for touch if this is supported and no mouse is detected
 	{
 		Fit.Device.OptimizeForTouch = true;
 	}