Click function doesn't work all the time
Categories
(Remote Protocol :: Marionette, defect)
Tracking
(Not tracked)
People
(Reporter: pierre.marsaa, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36
Steps to reproduce:
So, it's a beug on tiktok website.
Here is the python code :
from selenium import webdriver
from selenium.webdriver.common.keys import Keys
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
just launch tiktok on the browser
fp = webdriver.FirefoxProfile("/home/pierre/.mozilla/firefox/0dcl56q3.default-release")
driver = webdriver.Firefox(executable_path='./geckodriver',firefox_profile=fp)
driver.get("https://www.tiktok.com/@programm___r?lang=en")
click on the box that shows notification
driver.find_element_by_class_name('jsx-1737374796.header-inbox-icon').click()
wait until the pop up of notification appears and so we can see the "followers" category button
WebDriverWait(driver,20).until(EC.presence_of_element_located((By.XPATH,'/html/body/div[1]/div/div[1]/div/div[3]/div[2]/div[2]/div/div[1]/div/span[5]')
supposed to click on the "followers" category
driver.find_element_by_xpath('/html/body/div[1]/div/div[1]/div/div[3]/div[2]/div[2]/div/div[1]/div/span[5]').click()
Actual results:
when I click on the notification button, a pop-up with notification and category appears, but if I try to click on the "followers" category with the click() function, the pop-up disappear.
Expected results:
It's supposed to click on the followers category so I can see all the latest followers
Comment 1•5 years ago
|
||
Pierre, can you please attach a trace log from geckodriver?
https://firefox-source-docs.mozilla.org/testing/geckodriver/TraceLogs.html
Thanks
Comment 2•5 years ago
|
||
There is nothing that we can do here without a trace log or a working example. The element with the class name jsx-1737374796.header-inbox-icon cannot be found, and maybe you need to be signed in? I'm happy to reopen the bug if the requested trace logs from comment 1 have been provided.
Updated•3 years ago
|
Description
•