Is this the same behavior it had previously?  In the case when the other axes are not in a valid mode it defaults to the behavior of "NONE" mode?

I'd say this should also trigger an error, shouldn't it?  Basically coordinated flight + not attitude for roll = not really defined behavior (in the sense of probably not what they intended to get)