Bug 144987 - Change range of possible forces for mouseforcechanged DOM event
Summary: Change range of possible forces for mouseforcechanged DOM event
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-13 21:14 PDT by Beth Dakin
Modified: 2015-05-14 11:19 PDT (History)
3 users (show)

See Also:


Attachments
Patch (3.74 KB, patch)
2015-05-13 21:16 PDT, Beth Dakin
thorton: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Beth Dakin 2015-05-13 21:14:22 PDT
For the time being, let's switch to a 0-3 range:

0 = finger off the trackpad
1 = mousedown / up / click
2 = forcemousedown / forceup
3 = max possible force

That way, if we ever can get force before mousedown (which we do not have access to on the Mac right now), we have a range of values reserved for them.

rdar://problem/20472802
Comment 1 Beth Dakin 2015-05-13 21:16:56 PDT
Created attachment 253093 [details]
Patch
Comment 2 Tim Horton 2015-05-14 11:09:52 PDT
Comment on attachment 253093 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=253093&action=review

> Source/WebCore/platform/PlatformMouseEvent.h:47
> +const double ForceAtClick = 1;
> +const double ForceAtForceClick = 2;

I don't think these should start with capital letters.
Comment 3 Beth Dakin 2015-05-14 11:19:43 PDT
http://trac.webkit.org/changeset/184345