Photoshop: Stamp Layers behaves different if the only paint layer is the background layer

  • 1
  • Problem
  • Updated 8 years ago
  • Acknowledged
  • (Edited)
There is a bug with the Stamp Layers command. If you use cmd-opt-E (on Mac) with multiple layers selected, they will correctly create a new, merged layer at the top using the selected layers. However, if the only paint layer is the background layer, then the background layer will be replaced with the merged layers, and re-adjusted by the adjustment layers above it. There is no new layer created at the top. I believe this is not the intended behavior.
Photo of Ken Fleisher

Ken Fleisher

  • 3 Posts
  • 0 Reply Likes

Posted 8 years ago

  • 1
Photo of Charles Badland

Charles Badland

  • 60 Posts
  • 4 Reply Likes
May not be intended behavior, but an easy workaround is to option+double click on the Background to turn it into a layer. Now Stamp Merge should work as expected.
Photo of Ken Fleisher

Ken Fleisher

  • 3 Posts
  • 0 Reply Likes
Thanks for the reply. Sure, a workaround is easy, but I was sort of curious if others have noticed this bug and if it is in fact a bug. How do I go about filing a bug report with Adobe? I'm not a developer...
Photo of Jeanne Rubbo

Jeanne Rubbo, Employee

  • 125 Posts
  • 27 Reply Likes
I've gone ahead and logged this in our bug database. Thanks for the report!
Photo of Charles Badland

Charles Badland

  • 60 Posts
  • 4 Reply Likes
From what I gather, all Adobe Photoshops bugs are now filed here at Photoshop.com. I guess just by posting like you already have in this Photoshop Family "Problems" category.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15434 Posts
  • 2280 Reply Likes
Official Response
Ken,

Cool find. Note that the history step that is recorded is "Stamp Layers" not "Stamp Visible."

Try using Cmd + Opt + Shift + E as your workaround. You'll not in this case, "Stamp Visible" is performed correctly.

We'll take a look at this. One of the problems with changing something like this that it may break existing actions that expect the current behavior (Even if the present behavior is somewhat expected) - so that may affect our decision making on performing a change here.
Photo of Ken Fleisher

Ken Fleisher

  • 3 Posts
  • 0 Reply Likes
Thanks for the replies! Glad to see that this is now reported as a bug.