Danil B

This seems to be related to your `renderer.render(graphics)` call, as far as I can tell, you had a Viewport container rendered before that call, and it seems to be a...

I guess that you should call `resize` method on viewport after each resize of your canvas, you can use resize-observer for instance. Here you can see that viewport updates its...

@wighawag I think it's not, because you may want to have several viewports on the screen, and in that case that is not possible to guess the way you would...

Well seems that I am wrong, and there is an option `forceHitArea`. But there is no any intention to resize viewport on resize of the canvas in the source code

@Heilemann That is browser api, which lets you observe size changes of a HTML element https://developer.mozilla.org/en-US/docs/Web/API/ResizeObserver

You can create your own plugin, which will hanlde that, just create an instance of a drag plugin inside of it, and proxy calls of corresponding methods, I did something...

Simply because events are fired synchronously, and inside of viewport it has some other code to do after it fired zoom-end event. Destroy method does something like `this.transform = null`...

Are you listening the wheel event this way `viewport.on("wheel", (e) => console.log(e))`? If you are, then you should check out the documentation of Federated Events system of pixijs, this event...

There is no simple way to do that, since viewport just firest the event that way. You can copy the source code of a wheel plugin and add custom parameters...

But why would you need to check if the pointer is inside of an image? Why cant you just check if the image is still visible in viewport? You just...