Copy link to clipboard
See attached files.
The result is that the first row of pixels is not included. The included image starts at the 2nd row. See the screenshot "i-result.png".
Thanks for the sample files. I've asked engineering to take a look. Workaround: put the layer into transform and drag around until the pixels appear, then you can nudge it into exact position.
@peter.f , is this a general problem with all older smart objects, or just this specific one? I could imagine that this particular case might be falling victim to our canvas layout where the line falls between pixels, and we round down (to null) for that thin line. If the workaround Jeff suggests works, then I'm inclined to let this issue ride, as inserting additional draw routines in for this narrow use case might be an expensive toll to pay for all smart objects.
Let me know if this makes sense; thanks for the report!
Ah, @peter.f , I think I'm getting closer. This only happens for me when using the Transform command, and only with transparent backgrounds (move tool and non transparent background seems good); are you seeing it affecting non transparent backgrounds in any of your other use cases?