P: Keyboard shortcuts for navigating layers DO NOT work with hidden layers

Hi Jeffrey, thanks for the reply. So when this was implemented, nobody thought that anyone would ever need to navigate to a hidden layer, ever? I can understand that most of the time, people may only need to navigate visible layers, but to simply leave out navigating to hidden layers seems like an oversight to me.
Couldn't you add a modifier key? Like maybe ALT-[ and ALT-] only navigate visible layers, but CTRL-ALT-[ and CTRL-ALT-] can navigate ALL layers. Just a suggestion.

Hi Keith, the support person you talked to was correct that this behavior is 'as designed.' Many operations for selected layers require them to visible so in the majority of cases it didn't make sense to add them to the selection (similar to how the move tool rejects selecting hidden layers when marquee dragging with the move tool). I was one of the folks who did the work to add the ability to select more than one layer at a time in CS2 - when the behavior was added. I've made this topic a feature request.

I never complained on any company untill I met Adobe 🙂 I really would like to think highly of them when I use their product every day for years. They do some good stuff, but in my opinion there's something wrong with their policy. There are some easy things to get fixed, but for some reason if not enough users reported them we have little chance for success. For ex. I wait each month for another patch they release regulary latelly. I see they fix like they say most disturbing consuments issues. After months of waiting there showed only one many poeple had problem with and only because some customer came with brilliant note they finally could do something about it.

But why I say it? Because I hoped when the most serious bugs will be fixed they finally take care of those "less important". Nah. I was shocked that after a month of waiting they only sorted out one serious bug. If they had time to fix others why only one? My conclusion is simple. There weren't any other large group of customers complaining about. So I guess if not that one bug then perhpas there would not be update for Photoshop this month. I hope I'm wrong, but true is that isn't fun to wait too long for some basic stuff there shouldn't be problem about at all.

Monopoly makes more engineers working harder wouldn't encourage more poeople go buy Adobe products. Scripting in Photoshop let me still have amazing time with this application, but I can not say only good things though. There's some limit.

We all pay money and there are not enough engineers to hold everyone's hand. Sorry if that bothers you, but its a fact.

Thanks for the suggestion, Cristen. A couple of people have suggested the feature request, but nobody explained that it's just a different post type. I will give that a shot if this doesn't get an official response within like a week.
David: I understand exactly how support works. YOU don't understand that I EXPECT a certain level of support when I pay this kind of money for a product, especially on a SUBSCRIPTION basis. Adobe thinks they can get away with providing the bare minimum support that is designed to make people give up, just because they have a virtual monopoly hold on premium creative tools, and if I could switch, I would, but I can't so I am forced to insist on getting PROPER support. I am sorry that you are fine with their current level of support, but I am not. I told you earlier I want nothing from you, you are not adding anything to the discussion and it seems your purpose here is just to stir the pot. Please stop and go away. I will not respond to you after this.

I don't think you understand how support works. They don't have time to give you a long explanation of why a specific feature was implemented like it was. This may never be changed, unless a lot of other people upvote it as a problem affecting them.

Unfortunately, Adobe staff here have a lot of other duties that come first, and the recent update/bug fix I expect consumed much of their time. The most you can do is keep the thread alive by posting from time to time in it, so it bumps to the top again. Or consider an entirely new post that treats it as a feature request (idea) if the thing goes cold.

Nothing from you, thanks! Useful information from an actual Adobe employee. An estimate for how long this will take to fix. In the unlikely event that this actually ISN'T a bug, I'd like an explanation as to why it was implemented this way and the use cases they had in mind when they did it, because it sure isn't useful the way it is. That's what I was sent here for by Adobe chat support.

What do you want to hear? Its not currently possible. Its not a bug. Adobe will presumably consider it for a future release.

Still no Adobe employee, and I'm no closer to getting this bug resolved.