是的，这是一个检查陀螺仪的好点。 你可以很容易地做到

https://developer.apple.com/documentation/webkitjs/devicemotionevent

或者类似的东西

window.ondevicemotion = function(event) {
    if (navigator.platform.indexOf("iPad") != -1 && window.devicePixelRatio == 1) {
        var version = "";
        if (event.acceleration) version = "iPad2";
        else version="iPad Mini";

        alert(version);
    }
    window.ondevicemotion = null;
}​

没有ipad来测试。

是的，这是一个检查陀螺仪的好点。 你可以很容易地做到

https://developer.apple.com/documentation/webkitjs/devicemotionevent

或者类似的东西

window.ondevicemotion = function(event) {
    if (navigator.platform.indexOf("iPad") != -1 && window.devicePixelRatio == 1) {
        var version = "";
        if (event.acceleration) version = "iPad2";
        else version="iPad Mini";

        alert(version);
    }
    window.ondevicemotion = null;
}​

没有ipad来测试。

如果你创建了一堆1“x1”宽的div，并将它们一个接一个地附加到父div，直到边界框从1英寸跳到2英寸?mini上的一英寸和iPad上的一英寸是一样大的，对吧?

这是一个疯狂的镜头，但iPad 2和iPad mini的区别之一是前者没有三轴陀螺仪。也许可以使用WebKit设备定向API来查看您可以从中获得什么样的信息。

例如，该页似乎建议您只有在设备具有陀螺仪时才能获得rotationRate值。

对不起，我不能给一个工作POC -我没有访问iPad mini。也许对这些定向api有更多了解的人可以在这里插话。

不是回答问题，而是问题背后的问题:

您的目标是在更小的屏幕上改善用户体验。UI控件的外观是其中一部分。UX的另一部分是应用程序的响应方式。

如果你将响应点击的区域设置得足够大，以便在iPad Mini上对用户友好，同时保持UI控件的视觉表现足够小，以便在iPad上获得视觉上的愉悦，会怎样?

如果您已经收集了足够多不在可视区域的点击，您可以决定以可视的方式缩放UI控件。

作为奖励，这也适用于iPad上的大手。

不要补偿iPad mini和iPad 2之间的差异，除非你也补偿了胖手指和瘦手指之间的差异。

Apple appears to be deliberately trying not to let you tell the difference. Apple appears not to want us to write different code for the different size versions of iPads. Not being part of Apple myself, I don't know this for sure, I'm just saying that this is what it appears like. Maybe, if the developer community comes up with a fancy detector for iPad minis, Apple may deliberately break that detector in future versions of iOS. Apple wants you to set your minimum target size to 44 iOS points, and iOS will display that in two sizes, the larger iPad size and the smaller iPhone/iPad mini size. 44 points is plenty generous, and your users will certainly know if they are on the smaller iPad, so can compensate on their own.

I suggest stepping back to your stated reason for asking for the detector: adjusting target size for end user comfort. By deciding to design for one size on the large iPad and another size on the small iPad you are deciding that all people have the same size fingers. If your design is tight enough that the difference in size from an iPad 2 and an iPad mini makes a difference, than the size of fingers between me and my wife will make a bigger difference. So compensate for user finger size, not iPad model.

I have a suggestion on how to measure finger size. I'm a native iOS developer, so I don't know if this can be accomplished in HTML5, but here's how I would measure finger size in a native app. I'd have the user pinch two objects together, then measure how close they get together. Smaller fingers will get the objects closer together, and you can use this measurement to derive a scaling factor. This automatically adjusts for iPad size. The same person will have a larger measurement of on screen points on an iPad mini than on an iPad 2. For a game you can call this a calibration step, or not even call it out. Have it as a starting step. For example in a shooting game have the player put the ammo in the gun with a pinching motion.