Improve message thrown from Navigator.isDisabled() and Navigator.isReadOnly() when navigator does not contain a form element #345
Comments
|
Originally posted by Chris Prior. The current behaviour of disabled() & readOnly() is to only check the first element in the navigator. This is therefore consistent with the check for only the first element being in the list of supported tags for the operation. Was your intention to change this behaviour to check all elements in the navigator to see for instance whether they were all disabled? |
|
Originally posted by Marcin Erdmann. You are probably right that there is no point in checking more than the first element because isDisabled() and isReadOnly() operate on the first element only. There is https://jira.codehaus.org/browse/GEB-284 which will prevent calling these methods on multi element navigators anyway. We're probably good to close this one now. |
|
Resolved |
Originally created by Marcin Erdmann.
The message should include as much info about the element for which the check failed as possible (at least the tag name, could also use WebElement.toString() if it's informative and relatively consistent across drivers).
The check should be also done for all elements of the navigator, not just the first one.
The text was updated successfully, but these errors were encountered: