Open
Bug 1349851
Opened 7 years ago
Updated 1 year ago
Implicitly wait in switching frame
Categories
(Testing :: General, defect, P3)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: andrew.prokopyev, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170317212436 Steps to reproduce: https://github.com/SeleniumHQ/selenium/issues/3521#issuecomment-284090555 I got one finding that if we use: self.driver.implicitly_wait(30) It works fine when to find an element, can take minimum 0 second to maximum 30 seconds. but in case of switching frame(window) it takes total maximum 30 seconds , means it always wait 30 before switching to frame. e.g. self.driver = webdriver.Firefox() self.driver.implicitly_wait(30) self.driver.get('https://somedomain.com') self.driver.switch_to.frame('main') self.driver.find_element_by_css_selector("[name=id]").send_keys('test') self.driver.find_element_by_css_selector("[name=password]").send_keys('test') self.driver.find_element_by_css_selector("[name=submit]").click() self.driver.switch_to_default_content() Actual results: It always wait specified time before switching to frame. Expected results: It should switch to frame or wait specified time if frame doesn’t exists
![]() |
||
Updated•5 years ago
|
Priority: -- → P3
Updated•1 year ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•