You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's pretty common when working with WebDriver to want to handle the specific errors returned, such as ElementNotInteractable etc.
I understand fantoccini wants to not expose the webdriver crate types etc but it would be good to provide an equivalent so that these specific error variants can be used in calling code.
There's a related issue where StaleElementReference is treated as NoSuchElement which is also not ideal, since they're not actually interchangeable and may warrant a different course of action depending on which error is returned.
If we don't want to expose the ErrorStatus enum, is it better to duplicate it and provide a From impl? Any better options?
The text was updated successfully, but these errors were encountered:
Unfortunately even a From impl would mean that updating webdriver would be a breaking change. I think it'd be okay for us to basically copy their error enumerations into this crate though, and then just mark those as #[non_exhaustive]!
It's pretty common when working with WebDriver to want to handle the specific errors returned, such as
ElementNotInteractable
etc.I understand fantoccini wants to not expose the webdriver crate types etc but it would be good to provide an equivalent so that these specific error variants can be used in calling code.
There's a related issue where
StaleElementReference
is treated asNoSuchElement
which is also not ideal, since they're not actually interchangeable and may warrant a different course of action depending on which error is returned.If we don't want to expose the
ErrorStatus
enum, is it better to duplicate it and provide aFrom
impl? Any better options?The text was updated successfully, but these errors were encountered: