Photoshop: Inconsistency of placement pasting from clipboard into artboards

  • 2
  • Problem
  • Updated 4 years ago
  • Solved
  • (Edited)
So this new bug has appeared after the latest update (which thankfully fixed a few previous ones). So we all know and got used to having an object from, say, clipboard (raster or vector, doesn't matter) pasted into the center of the 'viewport'. That is when I paste something onto the canvas, it's being put right into the middle of the screen. But when working with the artboards the objects are placed in the middle of the artboard (center-center) which is inconsistent and unintuitive. Is this how it was intended to be?
Photo of Dmitrij Paskevic

Dmitrij Paskevic

  • 13 Posts
  • 1 Reply Like
  • curious

Posted 4 years ago

  • 2
Photo of Christopher Butler

Christopher Butler, Photoshop Development

  • 10 Posts
  • 9 Reply Likes
Official Response
Yes, the behavior you describe is intended. We are trying to respect the layer insertion index and to keep the newly pasted layer visible within the artboard.

There are actually three regions we try to respect:
1) the document bounds
2) The target insertion index parent artboard bounds
3) the viewport bounds.

Previously we only worried about (1) and (3) and then let artboard auto-nesting drop the new layer into any artboard it might land in. People didn’t like that, especially since that frequently disrespected the intended insertion layer.

Now, we pay attention to (2), and if the intended target insertion point is within an artboard that is visible, we should slide the new sheet to be visible within the artboard but also keeping the desired layer insertion index.

So yes, centering in the target artboard is the intended behavior, as well as having the correct layer order within that artboard based on the prior selection.

There may be some opportunity for further polish. For example, an issue I was made aware of this morning where the new layer can be outside the view if you are zoomed into some corner of the target artboard. That's a bug that is being logged and which we intend to fix at some point.

Please let us know if you see other such cases that need attention.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 16284 Posts
  • 2586 Reply Likes
Official Response
This should be solved in the 2015.1.2 update released today: