New `Element Should Be Enabled/Disabled` keywords

[spooning]

Originally submitted to Google Code by @pekkaklarck on 7 Jan 2011

Selenium API has is_editable method for verifying is an input element enabled or disabled. This functionality should be exposed in the library.

We need to test does the method work only with elements created with <input> tag or are <button>:s also supported.

[spooning]

Originally submitted to Google Code by @jrantanen on 16 Jan 2011

Implementation and tests in Revision 1c4a455b56.

[spooning]

Originally submitted to Google Code by @pekkaklarck on 16 Jan 2011

There's no tests for buttons other than <input type="submit"> yet. I'm pretty sure also <input type="button"> works if other <input>s work, but <button disabled="disabled">Text</button> should be tested separately.

There are also many other <input> types that aren't tested, but as I wrote above I'm pretty sure all they work if other <input>s work. For a full list of different types see e.g. http://www.w3schools.com/TAGS/att_input_type.asp

[spooning]

Originally submitted to Google Code by @jrantanen on 17 Jan 2011

Added tests for <button> and also <input> when there is readonly attribute used. Updated documentation and changed keyword names to "Element Should Be Enabled/Disabled". See Revision 7964d1dad9.

[spooning]

Originally submitted to Google Code by suram.sr... on 14 Mar 2014

Hi Team,

In my project we have a div or link elements where those will be in disabled/enabled mode. Where i am using the code as

Run Keyword And Return Status Element Should Be Enabled //table[@⁠id='viewUsers']/tbody/tr[${i}]/td[9]/div/div/a

It is always throwing the error.

Please let know is this "Element Should Be Enabled" keyword is applicable for Buttons only? or all elements?