I see now, I get the same glitched results. It's strange that the problem only occurs at a specific stack order.
Well, I think it's not that much specific as "every following shader gets screwed" sort of thing.
But it's definitely a bug.
Amen to that! Finally someone gets it!
Now I understand why one of my drop shadow shaders behaves weirdly when I change the opacity of an object or layer it's applied to. It's probably related to the problem you depicted in the other topic.
Huh, you also have a drop shadow Shader? Or it hasn't been published?
My guess is that it happens in C2's compositor. Maybe it can be an overlook caused by some kind of render optimization (?).
I have a very recent Nvidia card with up to date drivers, so there's only a very small chance of being a driver's bug.
And I have tested on a very old and semi-old Nvidia cards. Now we just have to hope this does get considered a problem and not "standard behaviour" and gets fixed. Most of my pixel-friendly Shaders depend on it.
Edit: I would submit a bug report for both of these, but then the best way to show it is using my own Shaders so that might complicate things... Oh well, might just go ahead and do it (but probably tomorrow).