Expand stroke moves the layer out of the clipping mask

[GenewalDesign]

I don't know if it is a bug or wanted by devs, but it's slightly annoying if you use clipping mask a lot.

Everytime I expand a stroke that I put inside another shape (clipping mask), the resulting shape moves outside the clipping mask, on top of the layer list.

And I have to get my new shape back into my clipping mask.

[GarryP]

I’ve just tried this and, as far as I understand what you are doing, I don’t get what you get – see attached video.
Can you supply a video showing us what you do to get it to happen?

[GenewalDesign]

It happens only when I have an artboard, and my initial shape is outside of it.

I tried your manipulation, the first time when I'm inside the artboard : it behaves like in your video.

And when my clipping mask is outside the artbord, the stroke it moved outside of the clipping mask.

The dropdown menu doesn't display in my video, sorry.

[GarryP]

Ah, I see.

Performing an Expand Stroke when the parent layer is outside of any artboards causes the expanded stroke Curves layer to be placed outside of (above) the parent layer.

I don’t think that should be happening but, as you say, it might be expected behaviour for some reason that I’m not aware of.

It also sometimes happens if the parent layer is partially outside of an artboard, usually when the child layer is wholly outside of the artboard even if the parent layer isn’t – see attached video.

[GenewalDesign]

I should edit the title of the topic, but it will be too long to read.

The key element of that "bug" is "inside/outside of the artboard".

[GarryP]

This all rings a quiet/distant bell for me.
I’m fairly sure that it, or something similar, has come up in the forums before.

Something to do with layers outside artboards not doing something or other.
I can’t remember what the original issue was or what the general consensus was about it.
Maybe it was about ungrouping…?
Something about layers being put on the top of the stack because of the way the software ‘sees’ them.

Hopefully someone with a better memory than me will see this and be able to give a better answer than I can.

[MEB]

Hi @GenewalDesign,
Thanks for reporting this. It is indeed a bug. I'm logging the issue to be looked at.