Closed henzycuong1 closed 9 months ago
@henzycuong1 Yep, I'm aware of that. However, my plan is to remove the Selenium dependency.
Therefore, all those:
from selenium.webdriver.support import expected_conditions as ec
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.common.by import By
Won't work.
My reason to do that, is because I really don't like the syntax of selenium's WebdriverWait
.
In my oppinion, something like: elem.wait_for(cond.visible)
* and a timout (wait until exist) at driver.find_elements(timeout:float or None)
** would be way neater.
I could add something like WebdriverWait
to be supported additionally. The native one from selenium won't ever be supported due to structural incompatibilities.
* not implemented yet * * already implemented
Also, I plan to add a propper documentation btw:)
If you really ned Full support for selenium, maybe https://github.com/g1879/DrissionPage is probably. more what you need (unfortanely no english documentation available).
@kaliiiiiiiiii thank you, maybe I'll have to change so much in my project
Example Code:
Error:
Reason:
Solution: Command![image](https://github.com/kaliiiiiiiiii/Selenium-Driverless/assets/55269394/b18b1993-e289-4e44-b849-7e6a2ba4fcce)
class NoSuchElementException(Exception)
and import NoSuchElementException from selenium core. It look like thisyou don't have to create new webdriverwait because in webdriverwait selenium core just need
driver
and running in awhile