!= false is not a very common or reliable idiom, because JavaScript has many “falsy” values that you generally want to treat identically. I posted something recently about the danger inherent in exposing public properties of service providers; is it possible that it is relevant to your situation?