Make nsTouchEvent::touches store Touch instead of nsIDOMTouch

RESOLVED FIXED in mozilla25

Status

()

defect
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: Ms2ger, Assigned: Ms2ger)

Tracking

Trunk
mozilla25
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Posted patch Patch v1Splinter Review
No description provided.
Attachment #764679 - Flags: review?(dzbarsky)
Comment on attachment 764679 [details] [diff] [review]
Patch v1

Review of attachment 764679 [details] [diff] [review]:
-----------------------------------------------------------------

::: content/events/src/nsDOMTouchEvent.cpp
@@ +19,1 @@
>  {

I think for nested templates we don't put a space after the first <
Same thing everywhere else.

@@ +184,5 @@
>        // for touchend/cancel events, don't append to the target list if this is a
>        // touch that is ending
>        if ((mEvent->message != NS_TOUCH_END &&
>             mEvent->message != NS_TOUCH_CANCEL) || !touches[i]->mChanged) {
> +        if (touches[i]->mTarget == mEvent->originalTarget) {

Target().  I have a patch somewhere that moves these variables from nsIDOMTouch to Touch, and we'll want them to be protected.

::: layout/base/nsPresShell.cpp
@@ +5864,1 @@
>    if (!node) {

Target().  Same everywhere else.

::: widget/nsGUIEvent.h
@@ +34,1 @@
>  

This seems unfortunate because it will be included all over the tree.  Can you move the ctor/dtor out of line?
Attachment #764679 - Flags: review?(dzbarsky) → review+
https://hg.mozilla.org/mozilla-central/rev/12acd6ba4220
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → mozilla25
You need to log in before you can comment on or make changes to this bug.