91799 2012-07-19 16:54:49 -0700 Touch force values can be outside the valid range on Android 2019-02-06 09:19:08 -0800 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Android Android RESOLVED WONTFIX P2 Normal --- 1 rbyers benm peter oldest_to_newest 674078 0 rbyers 2012-07-19 16:54:49 -0700 The TouchEvent v2 spec says that force should be between 0 and 1: http://dvcs.w3.org/hg/webevents/raw-file/default/touchevents.html#widl-Touch-force On Android I can easily get values greater than 1. We should probably try to infer the maximum value (maybe by keeping track) and scale appropriately. Alternately we should consider not reporting force at all (in order to avoid a compatibility burden later). Test pages I used are: http://www.rbyers.net/paint.html http://www.rbyers.net/eventTest.html (with 'simple' turned off to get force/radius info) Ben, please reassign as appropriate. 782598 1 rbyers 2012-12-04 09:13:45 -0800 +peter who said he could look into this. benm said: Force correlates to the Android MotionEvent.getPressure API, which the documentation states that the value "generally ranges from 0 (no pressure at all) to 1 (normal pressure), however values higher than 1 may be generated depending on the calibration of the input device." Would it be reasonable to just trunacte the values we get out of the Android API at 1 in order to be compliant? 1044616 2 rbyers 2014-10-28 14:54:45 -0700 Obsolete. Fixed in chromium. 1503320 3 lforschler 2019-02-06 09:19:08 -0800 Mass move bugs into the DOM component.