Summary: | [EFL][WK2] Correct the parameters of WebPlatformTouchPoint. | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Eunmi Lee <enmi.lee> | ||||
Component: | WebKit EFL | Assignee: | Eunmi Lee <enmi.lee> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | gyuyoung.kim, kenneth, laszlo.gombos, lucas.de.marchi, rakuco, webkit.review.bot | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Eunmi Lee
2012-11-20 20:35:20 PST
Created attachment 175331 [details]
Patch
This looks good to me. I think it would also help if we could consistently order the arguments everywhere so that screen/device position comes first and content position follows (e.g. in WebEventFactory::createWebTouchEvent(), NativeWebTouchEvent::NativeWebTouchEvent()). Kenneth, what do you think ? Comment on attachment 175331 [details]
Patch
Could this be tested somehow? At least the content position part should be testable
Comment on attachment 175331 [details] Patch Clearing flags on attachment: 175331 Committed r135491: <http://trac.webkit.org/changeset/135491> All reviewed patches have been landed. Closing bug. (In reply to comment #3) > (From update of attachment 175331 [details]) > Could this be tested somehow? At least the content position part should be testable Actually, I found and tested this problem on Tizen. I agree with you and we need test cases to test positions. |