# "pointerdown" Never Called On Partially Off-Screen Sprites
**URL:** https://phaser.discourse.group/t/pointerdown-never-called-on-partially-off-screen-sprites/8472
**Category:** Phaser 3
**Created:** [December 27, 2020, 5:22am UTC](https://phaser.discourse.group/t/pointerdown-never-called-on-partially-off-screen-sprites/8472 "2020-12-27T05:22:49Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@EliSussman](https://phaser.discourse.group/u/EliSussman)
#### Post date: [December 27, 2020, 5:22am UTC](https://phaser.discourse.group/t/pointerdown-never-called-on-partially-off-screen-sprites/8472/1 "2020-12-27T05:22:49Z")
I have a game with square and rectangle sprites. I noticed that when sprites move partially off screen to the left or top, they can no longer be interacted with (clicked via pointerdown). I made a very barebones project with 1 js file to test this, and it still happens. This issue doesn’t occur if the object is partially off-screen to the right or bottom though. If the object is fully on screen, no issue occurs. If the object even moves a few pixels off-screen to the left or top sides, it can no longer be clicked. Just changing the x or y location from something \>0 to -20 causes the issue to occur. This happens in both Chrome and Firefox. Any help would be greatly appreciated. I hope I’m just doing something stupid I can facepalm about.
Here is the barebones code that still has this issue:
[Barebones Code](https://pastebin.com/FbA1uY6y)
---
### Author:  [@samme](https://phaser.discourse.group/u/samme)
#### Post date: [December 27, 2020, 9:35pm UTC](https://phaser.discourse.group/t/pointerdown-never-called-on-partially-off-screen-sprites/8472/2 "2020-12-27T21:35:25Z")
Use `this.input.enableDebug(sprite)` etc. to see if the hit area is in the right place.
---
### Author:  [@EliSussman](https://phaser.discourse.group/u/EliSussman)
#### Post date: [December 28, 2020, 2:51am UTC](https://phaser.discourse.group/t/pointerdown-never-called-on-partially-off-screen-sprites/8472/3 "2020-12-28T02:51:57Z")
I realized I was using version 3.9 and we’re now on version 3.50…So I updated and problems are solved after a few changes that had to do with the update.