Photoshop incorrectly creates history panel entry for Copy Style

[jrsigerson]

I believe this behavior is new to 26.1.0; i.e. it's been doing this for a while, and I suspected it could have workflow consequences only I didn't run up against it in real life until now. 

Workflows or automations that manipulate history can break. Going back to a previous state to copy a layer style will now discard all intermediary steps. If one of those steps involves nested smart objects, one could easily throw away a substantial amoun of work by doing something that was harmless until very recently. 

This has to be an error, as there's no user interface benefit nor conceivable use case for undoing a Copy Layer Style event (without bending over backwards to create far-fetched hypothetical situations).

This is on MacOS 13.6.7

[Stephen Marsh]

Agreed, this has been previously reported (I'll try to dig up the link to help tie these two topics together).

It's either a bug, or a new (unwanted) feature, we don't know yet as this appears to be undocumented and Adobe have not yet commented.

[Okan5CA7]

I see you are more understanding this time Stephen. Thanks for the information. Also thanks for not marking your own comment as "correct answer".

Shout out to the developers out there. Please make our job easier instead of harder. Before implementing a new feature, don't forget to consider the opinions of millions of users around the world. The "Copy Style" feature is disrupting my entire workflow and ruining my progress. I tried to bring this up before but the "Forum Volunteers" tried to blame me and claim I was wrong instead of understanding me. I hope you don't do this and remove this pointless "Copy Style" feature or make it optional. Thank you

Your toxic user Okan.

[Stephen Marsh]

I see you are more understanding this time Stephen. Thanks for the information. Also thanks for not marking your own comment as "correct answer".

By @Okan5CA7 

Unlike your previous discussion post, this topic was marked as a bug report. It is unknown if this is a bug or a new feature, so it's premature to mark a correct answer.

Your previous discussion asked a simple question that Jane correctly answered. I marked her reply as correct, and I still stand by that.

Unlike your discussion, this bug report contained pertinent information, that the user is running Photoshop v26.1.0, while your discussion didn't contain such critical information, and I couldn't reproduce the issue when testing in v2019, v2021 and v2024. It was only later that another member clarified that things had changed in v2025, which I was not and still am not using until it is bedded in.

I cross-linked these two related topics together as part of the forum maintenance that I regularly perform as a forum volunteer. This is also the case for marking correct answers.