# Phaser 3.17.0

**URL:** <https://phaser.discourse.group/t/phaser-3-17-0/2488>\
**Category:** Phaser 3\
**Created:** [May 17, 2019, 2:07pm UTC](https://phaser.discourse.group/t/phaser-3-17-0/2488 "2019-05-17T14:07:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gabriel\_Cho](https://yyz2.discourse-cdn.com/free1/user_avatar/phaser.discourse.group/gabriel_cho/32/1327_2.png) [@Gabriel\_Cho](https://phaser.discourse.group/u/Gabriel_Cho)\
**Post date:** [May 17, 2019, 2:07pm UTC](https://phaser.discourse.group/t/phaser-3-17-0/2488/1 "2019-05-17T14:07:09Z")

</div>

So I updated from 3.16.2 to 3.17.0 and found piculiar bugs. There are two issues.

1. pointerup isn’t fired when dragging sometimes.

> i have a scrollable container with setInteractive().on(“pointerdown”,\<\>).on(“pointermove”,\<\>).on(“pointerup”)  
> i press, drag for a short distance and release the mouse button, and pointerup isn’t called. on a mobile device, it’s fine (so looks like it’s mouseup not bubbling up). currently i use window.addEventListener(“mouseup”) as a workaround.

1. duplicate pointermove call on release. I calculate distance travelled in last 2 frames to determine if i should scroll the view or not. so if i flick a finger, it should scroll, but i slow down at the last second, it shouldnt. It was working fine on 3.16.2, but all of sudden dx (this frames’s pointer.x - last frame’s pointer.x) is always 0. found out that “last pointer move” is from “mouseup” event. eg ) pointer.event.type was “mouseup”. currently i check this pointer.event.type on pointermove, and if it’s mouseup, i manually call pointerup event as workaround.

gabe

---

<div class="post-metadata">

**Author:** ![scottwestover](https://yyz2.discourse-cdn.com/free1/user_avatar/phaser.discourse.group/scottwestover/32/7442_2.png) [@scottwestover](https://phaser.discourse.group/u/scottwestover)\
**Post date:** [May 17, 2019, 9:44pm UTC](https://phaser.discourse.group/t/phaser-3-17-0/2488/2 "2019-05-17T21:44:20Z")

</div>

Hi @Gabriel_Cho,

Thanks for taking the time to share the issues you found. By chance, did you happen to create issues on the GitHub repo? These issues may get additional visibility if there are added there.

Here is a link in case you need it: [Phaser 3 Repo](https://github.com/photonstorm/phaser/issues)

---

<div class="post-metadata">

**Author:** ![prob](https://yyz2.discourse-cdn.com/free1/user_avatar/phaser.discourse.group/prob/32/628_2.png) [@prob](https://phaser.discourse.group/u/prob)\
**Post date:** [May 18, 2019, 12:21am UTC](https://phaser.discourse.group/t/phaser-3-17-0/2488/3 "2019-05-18T00:21:34Z")

</div>

> [@DragEnd event not firing everytime](https://phaser.discourse.group/t/dragend-event-not-firing-everytime/2460):
>
> Hi guys, DragEnd event is not working all time. You can check the attached link which is phaser lab example for drag event. If we drag fast dragend is not firing most of the time. Don’t know if this is a bug.(I am using Phaser 3.17) [Example for drag](https://labs.phaser.io/view.html?src=src%5Cinput%5Cdragging%5Cdrag%20distance%20threshold.js)

---

<div class="post-metadata">

**Author:** ![jbgomez21](https://yyz2.discourse-cdn.com/free1/user_avatar/phaser.discourse.group/jbgomez21/32/1284_2.png) [@jbgomez21](https://phaser.discourse.group/u/jbgomez21)\
**Post date:** [May 20, 2019, 8:22pm UTC](https://phaser.discourse.group/t/phaser-3-17-0/2488/4 "2019-05-20T20:22:32Z")

</div>

Hi @Gabriel_Cho

I confirm that with version 3.16.2 ‘pointerup’ works correctly but with version 3.17.0 I have the same problem, ‘pointerup’ is not always fired.

Problem detected in Samsung galaxy S10 with Android 9

![error](https://global.discourse-cdn.com/free1/uploads/phaser1/original/2X/d/d77395c650352a6c5dba100651942a3d8c7f193a.jpeg)

---

<div class="post-metadata">

**Author:** ![Dmitriy](https://yyz2.discourse-cdn.com/free1/user_avatar/phaser.discourse.group/dmitriy/32/1784_2.png) [@Dmitriy](https://phaser.discourse.group/u/Dmitriy)\
**Post date:** [May 21, 2019, 8:35pm UTC](https://phaser.discourse.group/t/phaser-3-17-0/2488/5 "2019-05-21T20:35:11Z")

</div>

I also faced this problem and I was helped by the addition of the queue. Here’s the code:

> ```
> input: {
> queue: true
> },
> 
> ```