Ignore stack layout 存在BUG：
我希望卡片拉伸时，图片尺寸固定在卡片右上角，但是勾选Ignore stack layout 并没有用
Editing to add translation:
Ignore stack layout bug:
I want the image size to be fixed at the top right corner of the card when the card is stretched, but checking Ignore stack layout doesn’t help.
Hello @eric-000! Thank you for posting, and welcome to the forum.
Since this forum is English-based, I’ve edited your post to add a translation, and I’ll answer in English. I hope you don’t mind.
Regarding your case, I’m afraid I don’t fully understand your goal. If my response doesn’t help, attaching a video showing the issue in action will.
If the issue is about placing elements inside Frames, it’s not a matter of tweaking Stacks Layout options, but changing the pinning of the elements in the frame, instead of looking at the Stacks Layout options.
I am attaching a video that shows this option in action:
If you want to resize an image to stay in place, you’ll have to pin the image to the top right within a Frame. See video:
I hope I’m understanding your issue properly! Let me know if that’s not the case.
Perhaps you should open the frame’s layout and fix the rectangular shape at the top right first, so the Ignore stack layout will become ineffective.
@JorgeF
Thanks for your reply. My card uses a layout, and I want the image to be fixed in the upper right corner of the card. I checked “Ignore stack layout” for the image, but the image did not move.
这是我使用figma做的，我想到到这个效果
Thanks for the videos @eric-000, I can see what you mean now!
I can reproduce the problem. Our engineers will investigate the issue.
Thanks for reporting!
Hello @eric-000 - We’ve been looking into it, and it’s indeed a bug, good catch!
While we investigate it, the workaround is to move these images manually. Since it only affects the manual resizing of frames, it should not significantly impact your workflow.
In any case, I’m sorry for any inconvenience this might have caused 
- We’re working on it
Hi @eric-000! Here I am once again 
We’ve been taking a look and I can tell we’ve fixed the issue, which will be included in a future Sketch release.
Again, thanks for reporting