506395 - Should we have a assertDisabled and an assertNotDisabled API in controller.js?

Status: RESOLVED WONTFIX

(Testing Graveyard :: Mozmill, defect)

Description

[cmtalbert]

I'm rather surprised this hasn't come up yet with Mozmill.  You can easily use assertProperty and assertPropertyNotExists to do this but we might want a very clear use case for this functionality.

This would give you a specific API where you call out to test to see if an element is disabled "grayed out".  This way you could do something like this:
* do function foo that causes X state to change
* ensure that in state X control Y is disabled (grayed out).

Should we add these as top level APIs (that just call assertProperty/assertPropertyNotExists under the covers)?

If we want this function, Anthony has volunteered to write it.

Comment 1

[u279076]

With r536 we have assertProperty(el, attrib, value) and assertPropertyNotExist(el, attrib).  I think this can be used universally, making assertDisabled/assertNotDisabled unnecessary.

After some IRC discussion with Clint, he agrees this can be resolved WONT FIX for the time being.  If we run into a situation where we absolutely need assertDisabled/assertNotDisabled in the future, we can add it then.