Closed
Bug 964261
Opened 10 years ago
Closed 10 years ago
Declare a widget to events created by TabParent::InjectTouchEvent
Categories
(Core :: Panning and Zooming, defect)
Core
Panning and Zooming
Tracking
()
People
(Reporter: vingtetun, Assigned: vingtetun)
References
Details
Attachments
(1 file, 2 obsolete files)
1.57 KB,
patch
|
kats
:
review+
|
Details | Diff | Splinter Review |
Kats, I forgot to set the widget for the event. As a result it returns some weird result when we try to tap as the the coordinates hits: http://mxr.mozilla.org/mozilla-central/source/layout/base/nsLayoutUtils.cpp#1503
Assignee | ||
Comment 1•10 years ago
|
||
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8365944 -
Attachment is obsolete: true
Attachment #8365944 -
Flags: review?(bugmail.mozilla)
Attachment #8365963 -
Flags: review?(bugmail.mozilla)
Comment 3•10 years ago
|
||
Comment on attachment 8365963 [details] [diff] [review] widget.sendtouchevent.patch Review of attachment 8365963 [details] [diff] [review]: ----------------------------------------------------------------- ::: dom/ipc/TabParent.cpp @@ +1933,5 @@ > aRotationAngles[i], > aForces[i]); > + > + if (msg == NS_TOUCH_END || msg == NS_TOUCH_CANCEL) { > + t->mChanged = true; Why this? Please add a comment explaining why this is needed.
Assignee | ||
Comment 4•10 years ago
|
||
Does the comment help ?
Attachment #8365963 -
Attachment is obsolete: true
Attachment #8365963 -
Flags: review?(bugmail.mozilla)
Attachment #8366274 -
Flags: review?(bugmail.mozilla)
Comment 5•10 years ago
|
||
Comment on attachment 8366274 [details] [diff] [review] widget.sendtouchevent.patch Review of attachment 8366274 [details] [diff] [review]: ----------------------------------------------------------------- It helps a bit. It doesn't fully explain why we want to treat all injected touch events as changed, but I guess that's a reasonable decision given that we're not tracking which touches are actually changing between calls to injectTouchEvent. ::: dom/ipc/TabParent.cpp @@ +1934,5 @@ > aForces[i]); > + > + // Consider all injected touch events as changedTouches. For more details > + // about the meaning of changedTouches for each event, see > + // https://developer.mozilla.org/fr/docs/Web/API/TouchEvent.changedTouches Remove the "fr/" from the URL here since that sends it to the french-locale page.
Attachment #8366274 -
Flags: review?(bugmail.mozilla) → review+
Assignee | ||
Comment 6•10 years ago
|
||
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #5) > Comment on attachment 8366274 [details] [diff] [review] > widget.sendtouchevent.patch > > Review of attachment 8366274 [details] [diff] [review]: > ----------------------------------------------------------------- > > It helps a bit. It doesn't fully explain why we want to treat all injected > touch events as changed, but I guess that's a reasonable decision given that > we're not tracking which touches are actually changing between calls to > injectTouchEvent. > > ::: dom/ipc/TabParent.cpp > @@ +1934,5 @@ > > aForces[i]); > > + > > + // Consider all injected touch events as changedTouches. For more details > > + // about the meaning of changedTouches for each event, see > > + // https://developer.mozilla.org/fr/docs/Web/API/TouchEvent.changedTouches > > Remove the "fr/" from the URL here since that sends it to the french-locale > page. Is it not what is spoke by everybody ? :)
Assignee | ||
Comment 7•10 years ago
|
||
https://hg.mozilla.org/integration/b2g-inbound/rev/742240197149
Target Milestone: --- → mozilla29
Comment 8•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/742240197149
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 9•10 years ago
|
||
Blocks a blocker, needs uplifting to 1.3 to go with the other bug.
blocking-b2g: --- → 1.3?
Updated•10 years ago
|
blocking-b2g: 1.3? → 1.3+
Updated•10 years ago
|
status-b2g-v1.3:
--- → affected
status-b2g-v1.4:
--- → fixed
status-firefox27:
--- → wontfix
status-firefox28:
--- → wontfix
status-firefox29:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•