Actually that is an expected behavior 🤔 If the center of the copied area is outside the canvas, when we paste it will be pasted in the center of the canvas instead of the original position (just to show to the user some feedback that the paste operation worked)

Hmm, still feels like a bug to me, as it's disorienting (to me, anyway) to have the copied sprite suddenly move to the center of the image / view. The user should know where the copy happened because they initiated it. I don't think there's a need to change the copy and paste location of an image just because it's off canvas.

I don't think there's a need to change the copy and paste location of an image just because it's off canvas.

The problem here is that if we don't paste the clipboard content in the center of the editor's viewport, the user might never notice that he/she paste something (and that might be a problem for pixels with 0 < alpha < 255).

I'm not sure that pasting content outside the viewport would be a nice solution because the user would lost any kind of feedback about the Ctrl+V operation.

The pasted item has the floating box surrounding it, though - that shows that they pasted something. If you wanted to, you could just add an additional indicator that shows that something was pasted.

I'll show you my case with a gif where the original copied area is not visible anymore:

You copy, scroll to other area, and paste. If the clipboard is pasted in the original position it would not be visible to the user.

OK, that makes sense - I'm talking about copying something that's off canvas, not off-screen. Here's an example of what I'm talking about:

Notice after each paste that the copied area moves back to the canvas. That's a bit disorienting if you want to do something across multiple frames (like scroll a sprite across the canvas in an animation).

Oh ok! I'll take a look at this issue soon.

Maybe only slightly related, but it'd be cool to keep at least one axis if off screen (if possible) as well. Here's a case where that would have been nice:

Both fixes will be available in the next release.

This fix introduced a regression. Please read this discussion.