We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

Support for Leadfoot APIs for automation with latest Gecko driver & Firefox

  • 1 vastaus
  • 2 henkilöllä on sama ongelma
  • 12 näyttöä
  • Viimeisin kirjoittaja hellosct1

more options

I have noticed that some Leadfoot APIs fail when they are run with Gecko Driver 0.23, Firefox 60.4.0 ESR & Selenium 3.14.

Leadfoot APIs which are KO with latest versions of Gecko Driver & Firefox -

find (with implicit timeout)

getCurrentUrl

get 404

executeAsync - tests - string

executeAsync - tests - function

executeAsync - tests - -> error

frame switching (#switchToFrame, #switchToParentFrame)

find (with implicit timeout)

findDisplayed

waitForDeleted


A complete list of LeadFoot APIs is attached.

Would it be possible to know if there is a roadmap to support these APIs?

Please note - with older versions of Gecko Driver (0.18 & 0.19.1, 0.20 & 0.21), there were a lesser number of APIs which were failing

i.e. only 3

getCurrentUrl

get 404

frame switching (#switchToFrame, #switchToParentFrame)

Thank you.

Best Regards,

Bhumika K

I have noticed that some Leadfoot APIs fail when they are run with Gecko Driver 0.23, Firefox 60.4.0 ESR & Selenium 3.14. Leadfoot APIs which are KO with latest versions of Gecko Driver & Firefox - find (with implicit timeout) getCurrentUrl get 404 executeAsync - tests - string executeAsync - tests - function executeAsync - tests - -> error frame switching (#switchToFrame, #switchToParentFrame) find (with implicit timeout) findDisplayed waitForDeleted A complete list of LeadFoot APIs is attached. Would it be possible to know if there is a roadmap to support these APIs? Please note - with older versions of Gecko Driver (0.18 & 0.19.1, 0.20 & 0.21), there were a lesser number of APIs which were failing i.e. only 3 getCurrentUrl get 404 frame switching (#switchToFrame, #switchToParentFrame) Thank you. Best Regards, Bhumika K

Muokattu , muokkaaja BhumikaK

Kaikki vastaukset (1)

more options

Hi,


I think we need to send your message on our bugzilla so that the teams can process it

http://bugzilla.mozilla.org/

Thank's