P: Hide vector Mask can't reach path

[Franck Payen]

An image is worth a thousand words :



Left, Photoshop CC, right Photoshop Cs6.
In both versions, I can hide the result of a vector mask by shift-clicking on the mask's thumbnail in the layers panel (big red cross).

in Cs6, i then saw the path (italic "vector path of layer 0") and could edit that.
in CC, when a mask's result is not shown, i don't see its path in the path panel, and can't edit that.

Workaround : use the properties panel and set the mask opacity to less than 100%, but it requires 2 clicks...

[ReneDamkot]

Same here.
Up-to-date PS CC on OSX 10.6.8 on an iMac 11.1

Annoying when I need to make a small correction to a clipping path for instance, but need to see the original...

Workaround works, but shouldn't be needed.

[cherryj1977]

Tested on PS CC 14.2 update on OSX 10.6.8 (work) and latest Mavericks 10.9.x (home)

Yes this does not work path is still unelectable, the only workaround is to use Photoshop 6.

Workaround does not work as above.

Please fix this as it's something I use quite a bit!!

[FeedbackCommunityMember]

Hello adobe ??
is there anybody here ??

the problem still here... 7 month after

[Jeanne Rubbo]

This issue is logged in our bug database, so we are aware of it. Thanks for the reports.

[FeedbackCommunityMember]

thank you !

[cherryj1977]

This issue has not been rectified in 14.2.1 update that was recently updated.
Very upset that this has still not been looked at, the only workaround is to use CS6.
Please update on the whereabouts of this fix.

[cherryj1977]

The issue where the vector mask can not be edited while it is deactivated has not be resolved in the latest Photoshop CC update 14.2.2.

Is it possible to have an update on the progress of this?

[daviesdesign]

Yep, STILL finding this very annoying. It means i have to drag the path mask off of the layer to a new one so i can edit the path and see the original image at the same time.... Not cool.

[pacopole]

This has not been rectified even in PS CC 2015.5
Is there any chance that this bug will be patched in the next upgrade?

[J453]

Fixed in 19.1 or later.