Checklist before requesting
Problem Statement
Currently, if a user prefers to add a timeout to their Tab.find() or WebElement.find() calls, it must be provided for each call, as a keyword argument. This can create repetitive and unruly code for those who wish to have a timeout on all .find() calls, especially when accounting for page loads and procedurally-populated pages.
Proposed Solution
I would like to see a new argument added to Tab() or Chrome() instances which sets a global value for timeout that will be used if one is not explicitly provided to a .find() call.
Alternatives Considered
No response
Additional Context
No response
Importance
Nice to have
Contribution
No, I don't have the capacity to implement this
Checklist before requesting
Problem Statement
Currently, if a user prefers to add a
timeoutto theirTab.find()orWebElement.find()calls, it must be provided for each call, as a keyword argument. This can create repetitive and unruly code for those who wish to have a timeout on all.find()calls, especially when accounting for page loads and procedurally-populated pages.Proposed Solution
I would like to see a new argument added to
Tab()orChrome()instances which sets a global value fortimeoutthat will be used if one is not explicitly provided to a.find()call.Alternatives Considered
No response
Additional Context
No response
Importance
Nice to have
Contribution
No, I don't have the capacity to implement this