WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
144987
Change range of possible forces for mouseforcechanged DOM event
https://bugs.webkit.org/show_bug.cgi?id=144987
Summary
Change range of possible forces for mouseforcechanged DOM event
Beth Dakin
Reported
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
Attachments
Patch
(3.74 KB, patch)
2015-05-13 21:16 PDT
,
Beth Dakin
thorton
: review+
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Beth Dakin
Comment 1
2015-05-13 21:16:56 PDT
Created
attachment 253093
[details]
Patch
Tim Horton
Comment 2
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.
Beth Dakin
Comment 3
2015-05-14 11:19:43 PDT
http://trac.webkit.org/changeset/184345
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug