Why that is how smart filters work. When you Change a document smart filter are them redone. If you change the document aspect ratio deleting some content I can well imagine trying to apply a filter like Liquify may well be a mess.  No real harm has been done its a nondestructive edit just readjust the setting or discard the smart filter and add a new one you do for the documents new aspect ratio and the layer different content. If you do not want that to happen rasterzise the smart object layer before you crop apply the Liquify..

I think the layer is the same size as it was before the canvas was added and the pixels are the same a square block box on white rectangle size you can test that by turning off the visibility of the liquify smart filter. I'm not on the cloud cant test.  The mesh was resized for the new canvas size and has a new size.   The recorded setting for the filter are for the old mesh size.  The mesh was most likely resized correctly for the new canvas size.  However the setting you made were not for that mesh the recorded settings saved in the smart filter are for the old mesh. The old mesh no longer exists the canvas size has changed. Perhaps you can use Liquify advance mode and save the old mesh before changint the canvas size. I do use liquify much and can not use it as a smart filter.

Only thing I might suggest as a workaround for now is working on your entire image (uncropped) as the master, then cropping at the end when you're making your work products.

-Noel

I can hide Liquify smart filter before cropping but it doesn't affects the final result.

Nothing to do with what I meant.

Converting the Liquified SO to an SO should fix its Canvas Size, so the Liquify Smart Filter might be maintained properly on an SO in an SO – but if the Canvas Size of the new SO is the old SO’s Layer Bounds then it probably would be no use.

I relatively often use SOs in SOs etc. … 

If, on changing the Canvas Size, Photoshop should check all SOs in the document for applications of Liquify that might add a (slight) drag on the operation.

conroy wrote:

 

I think the underlying issue is that increasing a dimension of the canvas by using Crop Tool or Image > Canvas Size results in a Smart Object being scaled unlike other layer types which are unaltered. Scaling a SO results in Smart Filters being recalculated.

Increasing canvas size does not scale smart objects.  The smart layers embedded object has not changed, only its associated transform position has been adjusted for the new canvas size. The Op saw that when I suggested he turn of the liquify smart filters visibility. What is happing is the liquify smart filter is using s different mesh after the canvas has been resized so its results are different then before the canvas resize.

 

In contrast, decreasing a canvas dimension by cropping or canvas-sizing does not result in SO scaling and a Smart Filtered SO is unchanged.

.

Yes unlike other type of layers where cropping with crop tool or canvas size these layers mat have pixels removed and in the case of the background layer may have pixels added. Smart layer embedded object remain intact only the associated transform position is adjusted for the new canvas size

JJMack wrote:

 

conroy wrote:

 

I think the underlying issue is that increasing a dimension of the canvas by using Crop Tool or Image > Canvas Size results in a Smart Object being scaled unlike other layer types which are unaltered. Scaling a SO results in Smart Filters being recalculated.

Increasing canvas size does not scale smart objects. [...]

 

I now see you're right about most Smart Objects. However, what do you make of my example of a Lens Correction Smart Filtered Smart Object being upscaled?

The smart layers embedded object has not changed, only its associated transform position has been adjusted for the new canvas size.

Yes, I've always understood that the object embedded inside a SO is always unchanged by operations in the main document.

In my case, the actual SO has its dimensions changed.

Yep, the SO is enlarged when scale is minimum in the filter controls. As before, the images are before crop, during crop before commit, and after crop. Note that after the crop, the checkered pattern is definitely larger despite not entirely filling the enlarged hole in the black surround.

The first time Liquify starts it tests to see if it was invoked as a smart object or from an action. If so, when finished,  it returns the current mesh in an action descriptor that is included in the smart object or action.

So if a Smart Object has other, smaller bounds than the document’s canvas size is the Mesh the size of the Layer or the Document?

In any case I think the important thing is that a longstanding feature request has been implemented (even if it is currently limited to the … Cloud), so: Thanks!

That pop-up you mentioned at first blush sounds like a decent way to handle it.  Something along the lines of the Canvas Size dialog.  You could even have it default to certain settings if it's possible to detect specifically how the canvas size was changed.

ON THE OTHER HAND... 

One has to wonder, though, especially if there are more filters that need this treatment (e.g., Lens Correction) whether a person might see pop-up after pop-up, each time a canvas size is adjusted via the Crop Tool.  That wouldn't be good.

-Noel