Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added new exception, changing isElementClickable to return a more spe… #1967

Conversation

JamesZoft
Copy link

…cific error

@JamesZoft
Copy link
Author

This is for issue #1704

@JamesZoft
Copy link
Author

Opened a spec bug to support this new error code: https://www.w3.org/Bugs/Public/show_bug.cgi?id=29585

@JamesZoft JamesZoft force-pushed the 1704_specific_exception_element_not_clickable branch from d9f96ea to 693136d Compare March 21, 2017 15:20
jreed added 4 commits March 21, 2017 17:23
…tored in the last year, changing so that there isnt random java code in here and added INTERCEPTING_ELEMENT_ERROR to the knownerror stuff
package org.openqa.selenium;

/**
* Created by James Reed on 11/04/2016.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We keep who wrote the code anonymous.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, sorry. Auto comment generation :(

@@ -74,6 +75,7 @@
public static final int ELEMENT_NOT_VISIBLE = 11;
public static final int INVALID_ELEMENT_STATE = 12;
public static final int UNHANDLED_ERROR = 13;
public static final int INTERCEPTING_ELEMENT_ERROR = 14;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this just a random number? Can't remember if we have this defined elsewhere.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I honestly cannot remember any particular reason for 14. I think it may have just been a gap in the existing numbers and I went for it. I can change it to something else if wanted.

@barancev
Copy link
Member

barancev commented Sep 5, 2017

Superceded by bd9d415

@barancev barancev closed this Sep 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants