WaitForEnabled (maybe others?) not always properly waiting

[PandaMagnus]

I made some assumptions on nested stack traces, and certain methods (WaitForEnabled and possibly others,) improperly throw instead of waiting and then returning true/false.

Need to do a bit of investigation, but it should be safe to remove the exception filters that check for inner stack traces.

[PandaMagnus]

I see what happened. The element selector was incorrect, so no element was found. This is likely correct behavior, but may come down to expectations. If the element doesn't exist, perhaps WaitForEnabled/Disabled should still return false instead of throwing? I'll ask around for feedback.