I am not exactly sure what effect you were after, but if you wanted to restrict the blurring to only the visible  part of the cropped image, you can do that very easily by making your Crop; then Selecting All; and then using the Blur tool.

If you then go to Image/Reveal All, you will see that the Blur has not affected the area beyond the marquee.

I had actually followed your steps exactly —  and I saw the problem that I assumed that you were seeing.

After further testing, I discovered that simply activating a Selection around the visible pixels retained all blurring within the selected area and prevented the problem that you had had previously with the damaged pixels in the masked area beyond your Crop.

Try doing it my way and see if that doesn't solve your problem.

I am not so sure that this IS a Bug: it looks more like a User using a tool in a way that perhaps it was never intended to be used?!

Great list, Conroy - nice work. I wonder if Adobe had such a list before you compiled it.

DEFINITELY a bug!  The inconsistency of it makes the use of the "preserve pixels past edge of image" feature practically useless.

And such an obvious bug it makes me wonder...

Given that Adobe has changed the behavior of Crop to make the preservation of cropped pixels more likely, it's hard to believe such a bug could actually get out to the customers.

As with some other issues (the release of the product with a serious text corruption bug), it seems clear to me that there are several management problems in Adobe's software development process:

• Project planning deficiencies - who wrote the spec for "preserve pixels past the edge" without taking all these things into account?

• Overwhelming pressure to release on time, regardless of all else.

• Process timing issues (release build completed before beta test even starts).

• Inability to properly judge what's acceptable to leave broken in released software and what's a "show stopper".

• Problems in communicating feature development changes to the system test plan.

It really feels like the released code isn't buggy so much as just unfinished.  Has Adobe decided to just release whatever they have every now and then, without a focus on getting it done first?

And worse, now that they've released it, Adobe is faced with a new problem:  Do they finish the code and make it work right in a 13.0.x update, or do they just leave such problems in the product for another major or minor release (e.g., 13.1 or 14.0)? 

• On the one hand, finishing the code is the right thing to do, from a customer quality perspective, but major changes chance exposing new problems, and it would further expose their process problems to the world. 

• On the other hand they could just leave this stuff broken, bringing out fixes in a future update, which might "save face" after a fashion, but send the message that Adobe quality and attention to detail has reached an all-time low.

Speaking of major or minor releases...  Assuming the correction of such problems as are being described in this thread are somehow deemed "feature enhancements" (I wouldn't put it past Adobe management to do this), do the Creative Cloud subscribers get them while people who have bought perpetual licenses do not?

Does anyone here see any good in all this?  I'm struggling to see any.  I suppose you could say that the folks who don't use Photoshop in such a way that requires these tools to work consistenly get some benefit from the other features they did find a way to finish, and of course there's financial benefit for Adobe, so they can continue development rather than close their doors.

I can't imagine that the Adobe engineers could like doing business this way.

-Noel