Odd behavior: Direct Select tool on a compound path with an inside or outside stroke (can't hide)

[jordanc54706939]

I've never noticed this behavior through many versions of AI and was wondering if anyone knows why it would behave this way or if it's somehow just me.

If you have a compound path with a stroke (specifically an inside or outside aligned stroke), if you use your direct selection tool to click on an individual anchor point of the compound path (or clicking and dragging over part of the object (basically selecting only part of the object and not the object in it's entirety) then you cannot hide the object.

Selecting the entire compound path object allows it to be hidden.

Selecting a single anchor point of a compound path with a CENTER aligned stroke allows it to be hidden

Selecting a single anchor point of a NON-compound path with center/inside/outside aligned stroke allows it to be hidden.

The only condition that seems to break the ability to hide the object is selecting only a portion of the compound path object when the stroke is set to inside or outside alignment.

Can anyone else confirm they get the same behavior?

[Kurt Gold]

I can confirm this behaviour.

Surprisingly, when trying to hide a part of a compound stroked path with the assumed alignment to inside or outside and then releasing the entire compound path, the part that was not hidden then suddenly gets hidden (which is an unexpected behaviour and probably a bug).

[Abhishek Rao]

Hi @Christopher25321881xb6a and @Kurt Gold,

Thank you both for reporting and confirming this behavior. I was able to test this on my end as well and can see the same behavior occurring. I also noticed that this is not limited to the latest version, as it can be reproduced in Illustrator 29.8.3 too.

Could you please test this in 29.8.3 on your side as well and let me know if you observe the same results? I'm checking this further with the product team, and I'll share an update here once I hear back.

Thanks again for taking the time to report this and help us dig deeper.

Abhishek

[jordanc54706939]

Hey there,

I just insalled 29.8.3 and can confirm the same behavior. I forgot I still had 28.0 installed and this behavior goes back to at least that version as well.

Thanks for everyone's attention to this issue.